Date pickers are terrible if not near the current date. Ones for long-term data sets where you set the start and end date are a huge pain. Like getting inflation data starting in 1960, or coronavirus data starting in 2019.
Date pickers are terrible if not near the current date. Ones for long-term data sets where you set the start and end date are a huge pain. Like getting inflation data starting in 1960, or coronavirus data starting in 2019.
https://wd.imgix.net/image/vvhSqZboQoZZN9wBvoXq72wzGAf1/uh0U...
From left to right: Chrome desktop, Chrome mobile, Safari desktop, Safari mobile, and Firefox desktop
I think at minimum they could've chosen 1980 or something as a default. 0% of their users were born today so not setting a default makes no sense
We're actually expecting users to follow through on that?
Yes I agree, that ideally the users would find it more obvious how to use the date picker properly and not just tap the left and right arrow to navigate
However in the screenshot I posted, I don't think any of the solutions have made this functionality very obvious. Except maybe Firefox lol. But Chrome's implementation on mobile seems even worse than Safari's!
What would you propose as a solution?
400+ clicks isn't even a bare minimum. It should be considered broken and tossed out right away.
https://designnotes.blog.gov.uk/2013/12/05/asking-for-a-date...
https://design-system.service.gov.uk/components/date-input/
(unlike the blog post, it uses actual Day Month Year labels rather than placeholders)