New answers tagged

0

Going by your comments, here is what I would go with download bmml source – Wireframes created with Balsamiq Mockups This approach allows you to specify the date as well as gives a reference point for the number of dates before the product is considered as expired or unfit for consumption.


3

Without knowing the full context of your question, I would start off with the lowest common denominator and expand out from there to a maximum of two levels. What I mean could be expressed by the following rules or formulas: w days late (where w = 1 to 6) x weeks, w days late (where x = 1 to 3, w = 1 to 6) y months, x weeks late (where y = 1 to 11, x = 1 ...


1

Visually, it'd be more appealing to see if there is a leading zero before a single digit number. The digital numbering system 'naturally' goes with this style, and it feels like there'd be more symmetric perfection when sets of two digits are chained together (Image1) instead of a 1-2-2 pattern (Image2). Image1 Image2 Symmetry, familiarity & ...


1

Why not use the default/existing pattern of iOS? They are all single digit below 10; with this the user doesn't see anything different than what the system itself shows to him/her. Which also reduces user's cognitive load. On the other hand. How many iOS users change their default time settings, if at all there is an option to do that? I'm sure they will ...


2

I'm not aware of any studies for this but I would say there are a couple of possible answers. If you're displaying time in 12hour format (i.e. 10:00AM and 10:00PM) then you could easily display hours below 10 as a single digit. On the other hand, if you're displaying time in a 24hour format (i.e. 10:00 and 22:00) then you're more likely to find that a ...


5

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 January 5 February 4 March 5 April 4 May 4 June 3 July 3 ...


0

According to Dr. Math there are 30.42 days in an average month so you'd be "safe" rounding down to 30. :-) That aside, 30 days seems like a fair and intuitive number to use for most people. From a practical standpoint it's usually easier for a programmer to deal with too. Of course, whoever inserts the data into a datastore would be wise to use a reliable ...


4

You don't need to over think this. Unless there are regulatory constraints it can be whatever you want it to be and your users will take it as corporate policy. (By the way is there existing corporate policy relating to the definition of a month in other areas? If so leverage those decisions.) If you want to be thorough, and have the time and resources, you ...


0

You can also use Windows Phone Date Picker Format. To Select Date you have to swipe up or down to change date.


0

I just wanted to share here how I improved my original version, it works now. Live demo. Not optimal yet in terms of UX, I'll update thanks to all your contributions in the different answers and useful remarks. As pointed by some people, I'll add the months as well. (Any idea of how to do it is JavaScript without hardcoding ['Jan', 'Feb', 'Mar' ...]?)



Top 50 recent answers are included