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 ...
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:
| 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.
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 ...
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 ...
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 ...
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.
Given today's date, 6/20/2016, I offer my users these choices:
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 ...
The international standard ISO 8601 specifies a notation that uses the slash “/” between dates expressed in the year-month-day notation, e.g.
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 ...
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 ...
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 ...
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&...
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 ...
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 ...
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
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.
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 ...
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 ...
Please see ISO 8601
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 ...
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 ...
As already said, there's no standard. However, if there was one, it would look differently...
When using YYYY-MM-DD for dates, then you really should not use QQ-YYYY for quarters. The point for the ISO field ordering is that they're ordered according to their weight: Year is more important than month, and so on.
This way you can sort the dates as string ...
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
If 90% of scenario is covered by Today+10 days, then perhaps something like this could work, without having to worry about Next | Previous or losing your current place.
It takes up more space, but it's also less finicky.
download bmml source – Wireframes created with Balsamiq Mockups
Today is indicated as bold. You also need month, because date ...
Stick to conventions and consistency
This is really simple: if user is charged on day 5 of the month, he should be charged on day 5 next month. Most users plan in anticipation and they know that every fifth day of the month they will be charged for a service. Otherwise, see what would happen
How about if the deadline was sometime during the last week, you display:
Last [day of the week]
so your example would be:
Overall, your dashboard (with a mixture of deadlines), assuming it was a Wednesday, might show:
2 days ago
Alternatively, you could use stick with friendly ...
In my experience if you want them to focus on something, you need to make it as clear as possible. If you are looking to have them focus on the month, then you should focus on the month directly.
Comparing your two examples, the second one is far, far easier to understand, but I would definitely use the full month names, instead of dates. I think the month ...
When you are not dealing with century old events - it will make perfect sense to use YY instead of YYYY.
Even Stackexchange follows the same pattern:
"asked Jan 6 '09"
MM/DD or DD/MM does change continent wise, but the YY or YYYY remains the same for entire world (At least in countries that use English as official language).
ISO 2014, though ...
I thought the argument about yyyy rather than yy had been dealt with in the run-up to y2k? There are almost certainly people reading this who will be alive to see 2099 turn to 2100, and there are almost certainly coders who have failed to learn the lesson whose code will go horribly pear-shaped come 2100 (when it will still be in use by somebody, somewhere). ...