Hot answers tagged

126

|All| or last | 365 | 30 | 7 | days


118

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 ...


83

There is no universally good answer to this question, but there are definitely two pros of YYYY: by showing the two leading numbers you can easily tell e.g. 1911 from 2011, you know exactly where the year is in cases when the year is from the range XX01-XX12. In other words: Notation Possible interpretations: ----------- ------------------------- 09/...


77

I don't have a pointer to published research - but in my experience US folk will always assume the US MM/DD/YYYY format unless they are knowingly using an non-US site, and are already aware of the potential differences. If you have to use numbers only then the format that causes least confusion across cultures in my experience is YYYY-MM-DD since it ...


72

Consider this: | Past year | Past month | Past week | This is much less likely to be misunderstood than "last year", and is a common way of presenting menus for selecting a time range. For example, the filters for Google search and Reddit's top posts use this exact wording.


68

I would go with this kind of UI, reasoning: Users only select the dates that he/she is applying leave for without having to think about first day of leave and first day of work. Leave balance is not displayed on the same screen as it might get too cluttered and might confuse the users. For "leave balance" checking, I would suggest to make it accessible from ...


63

As a rule, it's never OK to use a 2-digit year. If you can prove that using a 4-digit year will cause thousands of babies and cute fluffy bunnies to die horribly, that could be an exception to the rule, but probably not. I have seen hundreds of costly process failures simply because a programmer thought it was perfectly OK to use a 2-digit year or a local ...


52

Let 3 days ago mean 3 days ago (not 3 business days). It seems perfectly reasonable for a Monday-Friday company to want to schedule server maintenance to be due on Sunday morning when traffic to their web services is low. If your UI usually reflects number of business days, when they come in on Monday morning, alerting them that their event is "1 day ...


47

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.


28

Given today's date, 6/20/2016, I offer my users these choices: Today 6/20/2016 Yesterday 6/19/2016 Last 7 Days 6/14/2016 - 6/20/2016 Last 30 Days 5/22/2016 - 6/20/2016 This Month 6/1/2016 - 6/20/2016 Last Month 5/1/2016 - 5/31/2016 This Year 1/1/2016 - 6/20/2016 Last Year 1/1/2015 - 12/31/2015 All Time First Record ...


27

The international standard ISO 8601 specifies a notation that uses the slash “/” between dates expressed in the year-month-day notation, e.g. 2014-07-15/2015-08-01 This is the only reasonable globalized notation. But it should normally be used only a) internally in data representation when a date range needs to be represented as one string and b) as the ...


27

Rather than saying: The deadline was 3 days ago How about phrasing it: The deadline is 1 day overdue


24

Date pickers are helpful when your concerned dates fall within the context of a month or so but not several years apart as jumping between years would require laboriously many clicks. Date selectors are not just helpful in reducing the typing errors but they also standardize the formats when several correct variations are possible. For Americans, the ...


24

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 ...


24

If "Day" means something other than "Calendar Day", be specific. A user reading "3 days ago" will assume Friday if they are reading on Monday, and I find it hard to believe that people will know that "3 days ago" on Monday actually refers to the previous Wednesday. You could use specific term such as "working day&...


21

People operate on dates in variety of ways: absolute (e.g. December, 21) relative (e.g. yesterday, last Monday, tommorow, next Friday, next week, soon, etc.) As you see, relative way is often prevalent. Calendar with next/previous dates extends the context of use and support relative date references and natural dates flow. Finally, calendar is just a ...


21

Timestamps aren't meant for most users Showing friendly names such as 2 hours ago or yesterday can quickly provide context to the user as opposed to showing them 2015-01-27 18:54:03.259 Mixing both formats together will always cause friction (anything that forces a user to ask a question in their mind adds to cognitive friction). In almost all cases ...


20

The UK site GOV.UK published some initial test findings about how users on mobile devices use a DOB field they were testing against. Initial reports suggested that having two dropdowns (one for day and one for month) followed by a text field for year was well received by users, although not exclusively. (emphasis mine). ...This tested much better, and ...


19

I would skip the 'Last' altogether and go with Lifetime | 1 year | 30 days | 7 days At most it would take the user one try to remember what it means, especially if you display the date range of the selected period once selected


17

Take this example: 01/02/07. At first look, it could be anything. Now, let's make it YYYY: 01/02/2007. Quite a bit of difference, right? This is one of the main reasons for the YYYY format. Very few datapoints are in 2-digit / 2-digit / 4-digit format, and this helps avoid a bit of confusion.


14

What is the context of your application? Context really matters for dates. Consider the two following situations. A budgeting application where users plan spending for future years A college reunion signup where users enter their graduation date Clearly if people are planning, they would be annoyed to get a date in the past and if people are entering ...


13

I’ve considered the question recently due to travelling and booking hostels. The same problem appears there, since whether you book the night or the day can be confusing indeed. For usability reasons, the left one is a better choice since the user doesn’t have to do the maths. In this case, the best way to help the user is to be clear in the definition of ...


13

Is this for a system where "working days" can change (like this is a piece of software for use by various client businesses), or are working days always M-F? In either case, you could change the assumption to be that it's counting working days. If that's made known to the users, then you can do the math appropriately and not have to worry about it. So if ...


12

As long as it truly is within a single year, a range slider seems appropriate here. via Kevin Anderson on Dribbble EDIT: The date range picker on the google finance site solves the problem with my previous answer. This example doesn't "snap" to month increments, but a different implementation certainly could.


12

If you are asking for data that usually follows a particular format, then ask for it in that format. Visually people are used to months shown in a calendar, so show it in a calendar, and let them select the months that they want. Visually it is very easy for someone to see whether they have the months that they want like that. Here is a quick example of ...


12

Please see ISO 8601 (eg http://en.wikipedia.org/wiki/ISO_8601) yyyy-mm-dd hh:mm:ss First, this is simply the largest to the smallest unit. No other argument--no matter how tightly held--can seem to overcome this logic. The 4-digit year removes any confusion as to what the other numbers represent--even when the hyphens are left out. (Use of a 2-digit ...


12

If you want to refer to a point in time, you need to either give the time, or give a relative time. So that translates to either something like 11:32 today or 5 hours ago. Simply stating "5 hours" tells you nothing really as it is a measurement of a duration of time and nothing more without a reference point. So don't use this. When people use forums and ...


12

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 ...


11

If a range of months could span across the year end, perhaps a circular dial makes more sense. Since you have limited vertical space it would have to be a dropdown though. Something like this perhaps:


11

I think it's better to put n-dash symbol (U+2013) without spaces on sides. This is typographically right. There is no strict rules about it so you are free to use western tradition. What is the difference between dash and n-dash, you can read here: http://en.wikipedia.org/wiki/Dash


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