New answers tagged dates
Displaying the day of the week (e.g. Monday, Tuesday) usually only makes sense when the date is either recently passed (i.e. within the last week) or in the future. When a date has recently passed, stating the day of the week makes it easier to recognise within that limited context. For future events, knowing on what day of the week it's due to take place is ...
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 ...
You could explicitly place a button named "Done". So whenever user is done with his date selection then user will tap on done button. On action of done button you could check the validation part and show a alert with respect to your check.
When the user has moved on to the next field. In other words, when the user have completed the date field and moved on to the next field eg; address. This way, you would be sure that the user has decided on his selection.
Ballistics A concept some term ballistics provides a good guide for this. It asserts that: A system should not interrupt a user while performing a task, until the latest point possible or necessary. The idea is that users formulate an action plan for a task (or subtask) and any interruption that is not essential diverges users from their original plan ...
I have zero experience of iOS listener events (if that is what they are called). This is the way I would deal with this (if I have understood the context properly). So your application requires the user to be above a certain age. Say 13, you would expect the user to enter in the year field a value equal to or less than 2002. If this is your goal showing ...
The safest (and simplest) time to check the wheel is when the user completes the form. You can also check if the spinner has been blurred (e.g. the user moves on from the selection) to give the user a more responsive experience. Both these methods ensure the user has completed the input. In response to your comment, I mean you should determine that the user ...
It depends on the context. For example, the most common use for dates in an email program is viewing the most recent messages. In this context, sorting undated messages as newer than everything else would clog up the view, so undated messages get sorted as if they were infinitely old. On the other hand, if lack of a date represents an incompletely-entered ...
Logical ordering by date would put the empty date entries first. Is it possible to make the date a required field? Depending on the nature of the application that may be the best approach.
We face that ALL the time at work (sales orders, etc...). The newest items default to the top and the dateless items are placed at the bottom (under the oldest date). To find them the user has to select ascending order to place them at the top. Users don't have the slightest problem with them.
In OS X Finder "No Date" items are shown last (after the oldest), there is no sorting by ascending order there, but I personally would still keep it at the bottom of the list in ascending order, too.
Top 50 recent answers are included