Tag Info

Hot answers tagged

109

Imagine you’re telling a friend a story about a time you took a flying class. You want to give an idea of when the story takes place. What format should you supply the time in? Should you say “The date was 2014/12/31 and the time was 16:05:03 PST”? Of course not. The point of the story isn’t the exact time you took the class. You want to focus on ...


43

Not enough reputation to comment, but on many sites with this "friendly" time, you can actually hover to get the exact time. Try it over on this question's "asked" and "active" times on the right hand side.


23

This is the use of relative timestamps. In relative timestamps, accuracy isn't important, and immediacy of scanning prevails over accuracy, so things like this may happen, where you see "1 year ago" until Aug 15, 2015, where you'll see 2 years ago. There's a lot of controversy about this approach, and IMHO, it's correct that you could add something a bit ...


11

You've caught a common bug (IME) in the implementation of these relative time/date stamps -- at a step-change in the precision you lose a lot of information due to rounding, and the rounding is always down. It's common (I assume due to a built in library) on Android apps to get "59 minutes ago" (more precise than needed) then "1 hour ago" displayed for the ...


2

What's the user's goal? Clearly, the design is intending to let the user set a recurring monthly reminder. At least, that's clearly the intent on the 1st through the 30th of the month. Would it be wrong to simply round down any number that exceeds the number of days in a given month? That is consistent with the intent. Because, seriously, I can't think of ...


2

One plausible UX reason for this is preventing the situation where a user sees a date, fails to notice the year, and due to the proximity of month/day, assumes that the post was made within the past few days/weeks rather than (possibly many) years ago. This sort of user error can lead to embarrassing answers/comments/follow-ups on content where they're no ...


1

Design for the user's likely intent It's overwhelmingly likely that the user who indicates Annually wants the alarm to repeat annually. Allowing the leap-year technicality to prevent the alarm from going off annually is a violation of likely user intent. The question then becomes, how to deal with the leap year? There are three possibilities: Prevent ...


1

My gut reaction would be the last day of the month... so 2/28/17. But there's so much guess work involved that I think you're better off to give the user a preview before having them set the alarm. So if that's not what the user want, they can edited it before saving. So something like: The alarm will go off on: 2/29/16, 2/28/17, 2/28/18 ... until the ...


1

Usualy, software supports two sub-patterns for the monthly reccurence pattern: based on the day of the month (1 - 31) two descriptive fields You want to use the first sub-pattern but users would create more unambiguous reminder for the last day of the month with the second. The second sub-pattern should consist of two list values, first having options ...



Only top voted, non community-wiki answers of a minimum length are eligible