5 ms·
In situations with ambiguity like this, it's probably best to ask the user instead of make assumptions. I would not be remotely perturbed if my phone had a pop
by bshipp 8y ago
In situations with ambiguity like this, it's probably best to ask the user instead of make assumptions.
I would not be remotely perturbed if my phone had a pop up when I stepped off the plane asking me if I still wanted to wake up at 7AM local or would prefer to wake up at 10AM UTC.
I would be greatly perturbed if it assumed the latter and I missed my meeting, all because I forgot to set a timezone when I originally inserted it a month prior.
- BurritoAlPastor 8y agoIf, at 12:30 AM on a Tuesday, you ask Siri to remind you about something “tomorrow”, Siri will ask if you meant Wednesday or Tuesday. I always thought that was a nice touch.
- enobrev 8y agoIn Gmail (and Inbox, RIP), the 12:30am "Snooze" action assumes "tomorrow" means 8am the same day. I'm not sure what time the switch-over becomes "8am the next day". I think around 4 or 5am. Once I learned that's what happens, it became just as useful as "later today". I use both quite a bit. I'd definitely rather not be asked every time - especially since I work at night and do most of my email management in that timeframe
- atomwaffel 8y agoWhat do you suggest in situations where you can’t do that? Last summer, I travelled on a sleeper train from Lisbon to Madrid, which are in different time zones. At the time that I set my alarm, my phone had no way of knowing that it would automatically jump an hour ahead in the middle of the night. In that specific case, it woke me up according to local time, which is what I expected. But what if I had crossed the time zone boundary less than an hour before I wanted to be woken up?
- Dylan16807 8y agoFor the question of crossing a time zone boundary while using local time, I'd say the answer is obviously to go off the moment local time passes the alarm time. Going the other way is a more fun problem, but a few hours of debouncing is fine for anyone moving at suborbital speeds.
- bshipp 8y agoIf I'm going from my personal experience when travelling across timezones, I generally set my phone to the local time, check it about 5 times, call the front desk and request a wake-up call, and set the bedside alarm. All three have failed me at one time or another and I'm a little paranoid about sleeping through meetings!
- Swizec 8y agoIn my experience assuming I think of my calendar as anything other than local time is always wrong. 10+ years of using calendars in different timezones and I have never once meant anything other than “9am when I’m there” It’s my calendar, why would I set it to events in a way that’s not relative to my time reference?
- enobrev 8y agoI agree with this as you've stated it, but there's a difference with a personal event, like an alarm, and a calendar event. For instance, say there's an 1pm CT meeting every Tuesday for a remote team. When I head to the East Coast for a week, that _should_ mean 2pm ET, but if the assumption is "1pm when I'm there", since the "there" has changed if my calendar doesn't adjust accordingly I'm going to be an hour early to the meeting.
- bshipp 8y agoThis has happened to me numerous times. I set up an appointment in Outlook assuming I'll be there remotely via webconference and then end up having to travel there in person. I've been bitten enough times to double-check the timezone now, but that was a hard-earned lesson that most calendars tend to use the timezone the appointment was created in unless explicitly told otherwise.
- nugator 8y agoI'm a swede watching a lot of NFL and college games. Often the only thing I see are American times and need to input them easily in my calendar. Then I'm more interested in inputing "1pm EST" into my calendar and let the calendar figure out when to alert me of the game.
- blago 8y agoBecause you may have an appointment at the place you are going, not the place where you are now.