3

When the date of birth is asked to the user, with a Date Picker on mobile, what should be the default date to show on Date Picker? Current date makes no sense to me as it is probably too far from the date the user has to select.

EDIT 1. I'm talking about a Date Picker on Mobile. When the users selects the date picker it needs to open in a date and then the user starts moving it. Date pickers do have a default date. I cannot have a Date Picker without default date. enter image description here enter image description here

Improve this question
4
  • If you know the age range of majority of your users, set the rate according to their birth date, it would be the nearest... You can always show no default anyway! – Sarah Akhavan Oct 14 '16 at 8:34
  • 6
    You seem to be working on the assumption that there should be a default date in the first place. Why not have them empty? That way there is less risk of the user thinking the field is already complete and submitting it with the wrong date. – JonW♦ Oct 14 '16 at 8:47
  • Have a look at this solution, interesting >> uxdesign.cc/rethinking-the-date-picker-ui-99b9dcb303ad – JMax Feb 15 '19 at 9:41
  • That's a very nice solution, @JMax!! – poqueque Feb 17 '19 at 16:22
1

Depending on the target audience of the app, i reckon one could set the default date as the minimum expected age . For eg if the minimum expected age is 18 , show the default date as 01-Jan-1998 in the widget

Improve this answer
1
  • 18 would seem to be a sensible if arbitrary number. When you become older it's tedious having to wind back through too many decades to find your year of birth. – PhillipW Oct 24 '16 at 17:39
8

You shouldn't set a default for a birthday. Just as you shouldn't set a default for:

  • Name
  • Email
  • Credit card number
  • Credit card expiry date
  • etc.

The line of reasoning goes like this:

Usability

Usability is a measure of performance load, which is broken down to:

  • Cognitive load - the effort users expend when perceiving, interpreting and making decisions regarding the next action. Normally meassured in time between exposure to the interface and action onset.
  • Performance load - the effort user expend when taking an action. Measured using mouse miles, mouse clicks, keystrokes etc.

So unless some business goals take priority, the a key role of a design (and a system in general) is to minimise performance load.

A very tired person sleeping on a gauge saying 36% complete

Social threshold

When making UX decision we sometimes use data or guesstimates as to what percentage of users will benefit from a particular design.

For instance, you may see from analytics that 98% of users has a display size wider than 1200px. So setting your layout width to 1200px may benefit 98% of users, but for the remaining 2% the layout may start stacking, or you can force horizontal scroll - neither is ideal. But all taken into account, it seems a reasonable change to make.

Some set the social threshold to the famous 80/20 rule - if more than 80% of the users will benefit, it's a design worth going ahead with. But, as always, many variables could affect such decisions.

A screenshot of google analytics stats for display size

Cost/benefit analysis

Cost/benefit is another commonly employed analysis helping to make design decisions.

If you do set a default date, you will get 'perfect hit' in very roughly 1 in 15000 users (assuming an age span of 40 years). That's around 0.007% of the users.

You may argue that 0.007% is better than 0% (with no default), so lets consider the cost for all the other 99.993% of users:

They may wonder why the field is populated, which could increase the cognitive load a bit. But perhaps the main danger here is security - in the age of cookies, it may appear to some that the form was field previously by another user, it which case some privacy concerns may arise. At any rate, you run the risk of confusing users.

A child photo with the caption 'Ooops, did I do that?'

Conclusion

The overall approach to this problem can be depicted like so:

A diagram showing data and design feeding cost benefit analysis that then outputs whether the design should get a go ahead.

So given the low percentage of those who will benefit from a birthday default, and the potential security and confusing cost nearly all users will experience, this seems like a clear-cut don't provide a default.

Improve this answer
1
  • Thanks for your answer, but I have added as an Edit to original question, on mobile there is a default date where the date picker is opened, usually current date. – poqueque Oct 15 '16 at 13:39
0

I do not think that you should show the minimum age. This will lead to more people just using that that date to log in. If you were to data mine this, the information would not be reliable.

why not just use the --/--/---- format?

Its quick and easy, allows for the users to quickly pick their birthdate. If your target audience is 25-35 years old have the years in the year box start from 1980 to 1994.

Although I will admit, I have just randomly selected dates before. Just to get in.

Improve this answer
1
  • Please check the edit. In Mobile the standard for selecting dates is use a Date Picker, not an input text. Date pickers do have an initial date shown when opened. – poqueque Oct 15 '16 at 13:42
0

If you have an age limit for your users, you could auto calculate that from the current date and populate as default.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.