This question is locked. New answers and comments are not allowed.
I saw something in a previous thread that defaulting the date picker's view to selecting a year range first is not implemented. I'd like to make a case of why it is super important.
Think about a user and them entering a date of birth field. Pretty common I say. So they get a view with days. They go, hmm, do I have to click left arrow a million times to get to my year? They have no idea that they need to click on the middle-top area to change the view. Why? Because all other date pickers do not have such an implementation.
Possible design ideas:
1. Allow the developer to default whether or not the view should in year range, month, range or day range
2. Be more obvious that the middle-top area is actually clickable
Although it may seem like a no biggie to some, this is a huge user experience flaw that really does need to be corrected. I hope that you listen and implement such an easy requirement.
Think about a user and them entering a date of birth field. Pretty common I say. So they get a view with days. They go, hmm, do I have to click left arrow a million times to get to my year? They have no idea that they need to click on the middle-top area to change the view. Why? Because all other date pickers do not have such an implementation.
Possible design ideas:
1. Allow the developer to default whether or not the view should in year range, month, range or day range
2. Be more obvious that the middle-top area is actually clickable
Although it may seem like a no biggie to some, this is a huge user experience flaw that really does need to be corrected. I hope that you listen and implement such an easy requirement.