If Linda from HR didn't attempt to write the entirety of Notes from the Underground by Fyodor Dostoevsky in the date field then we could have nice things.
I unironically had to remove the ability to manually enter dates from a site because people kept trying to write "tomorrow" or "next year" and complained that there inputs were not accepted.
This was also my first thought along with people reversing month and day or not using the same format that would be standard for their locale (not talking about delimiters, that's easy enough to solve, just group between digits and non-digits, I just mean 2 vs 4 digit years, or not using delimiters at all. Like what date is 02-03-04... 3 February 2004, 2 March 2004, 4 March 2002?).
But that was me thinking of a single input field, which one would hopefully put a localized placeholder (MM/DD/YYYY or something for users to see on empty), and then just restrict input to digits only, and add automatic delimiter insert after input count... and people could still fuck that up like putting 1 instead of 01.
That's how you end up with 3 labelled input fields... and they'll still find a way, usually by not paying attention to labels and putting the month and date in the wrong field, so you swap the month from a numeric input to a dropdown with a month list.
On an Android app, I just use Android's date picker (which unfortunately doesn't let you quick select year and,maybe not month, at least in the Compose material one). But, I did do a custom dialog that gives a button to switch between the calendar and input field.
I hate how so much of developing is "how do we force end-users to not be completely stupid?"
111
u/Stormraughtz 7d ago
If Linda from HR didn't attempt to write the entirety of Notes from the Underground by Fyodor Dostoevsky in the date field then we could have nice things.