Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User should see a reminder when somebody is in a different time zone and likely asleep #2650

Open
holmesworcester opened this issue Nov 1, 2024 · 5 comments

Comments

@holmesworcester
Copy link
Contributor

Use case: a group of journalists are working spread out over many time zones.

They have a mutual expectation to be responsive in pretty much any of their waking hours. Often when someone is in a radically different time zone they wake up to a ton of frustrated messages from somebody, followed by some messages describing the person's realization that they were actually in another timezone all along.

The best solution seems something like the bot notices that Slack gives you when you message someone who is probably away.

@holmesworcester holmesworcester moved this to Backlog - Desktop & Backend in Quiet Nov 1, 2024
@holmesworcester
Copy link
Contributor Author

Figma: https://www.figma.com/design/zyJklMWsgvDuNJT3Cb7OeX/Time-zone-availability?node-id=13-37&t=CpQohjumP3hmc25S-

Feedback:

  • Journalism org opted for hard-coding the timezone alert hours to 9am-10pm
  • We don't have to autodetect the timezone (it's tricky because there are two devices that might report different timezones) but having to remember to change the timezone manually seemed like it would be annoying. One solution is to ask users if they'd like to change their timezone and one user mentioned Notion as an example that does this well.
  • We should probably remove the "autodetect timezone" checkbox for the reason that devices might disagree, but we could also have a prompt that displays only when devices disagree if that seems better.

@jgaylor
Copy link
Collaborator

jgaylor commented Nov 22, 2024

I think we should autodetect based on the 'active' device at the moment and if it's different from a previously active device or location we provide that info to the user in a prompt. Something like "Would you like to change your timezone to your current location or keep your default setting" at the same time we can show what it will be set to based on their choice. Wdyt?

@holmesworcester holmesworcester moved this from Backlog - Desktop & Backend to Design - Awaiting External Feedback in Quiet Dec 2, 2024
@holmesworcester holmesworcester moved this from Design - Awaiting External Feedback to Design - Awaiting Internal Feedback in Quiet Dec 4, 2024
@holmesworcester
Copy link
Contributor Author

if it's different from a previously active device or location we provide that info to the user in a prompt.

As long as there's a "don't ask me again" preference, I like this. I'm not sure how to define "active device" though. I think it's more that we just ask if the current device timezone is different than the currently set timezone.

So the setting should be "ask to use detected timezone" and not "autodetect timezone".

@holmesworcester holmesworcester moved this from Design - Awaiting Internal Feedback to Design - Awaiting External Feedback in Quiet Dec 16, 2024
@jgaylor
Copy link
Collaborator

jgaylor commented Dec 16, 2024

Sounds like a good option, and we should add it to the timezone mockups. Changing the status to "Design in progress" to queue it up to add.

@jgaylor jgaylor moved this from Design - Awaiting External Feedback to Design In Progress in Quiet Dec 16, 2024
@jgaylor
Copy link
Collaborator

jgaylor commented Dec 19, 2024

@holmesworcester Timezone availability Figma is updated based on our discussion.

Needs component finishing once you're good with it.

@jgaylor jgaylor moved this from Design In Progress to Design - Awaiting Internal Feedback in Quiet Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Design - Awaiting Internal Feedback
Development

No branches or pull requests

2 participants