Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
One of the things why I have web development.
If you go to any other UI framework like iOS, Android, Windows, anything but web, there is always a standard date picker.
Btw, even if I implied that the web is a UI framework, and most web devs seem to see it that way, I actually claim that the web (html, css, js) is NOT a UI framework. It’s just being abused as one and that’s where most of the problems come from. -
@ojt-rant won’t work since 1/2/2023 is ambiguous and depends on the user’s region, which the user might not have disclosed, so there is no way for the AI to know.
-
@Lensflare it could ask the user to select the correct spelling of "color" or "colour".
-
@ojt-rant as there are only two regions on this world
-
@usr--2ndry only people on the american continuent use that crazy backwards method :D. The rest of use day, month, year.
-
@ojt-rant it‘s not that simple.
What about users which speak a different language than English?
Even if the user has a preference for color or colour, it doesn‘t mean that it corresponds with the preference for the date format.
And the whole point of it was to avoid the need to ask the user stuff or let him select the format.
Date formats in text form are inherently ambiguous and that‘s why we have UI date pickers. -
@Lensflare my parachute is on and I'm bailing out of this plane.
My friend said an intern designed this UI for an internal site.
No. Just... no
The aCalendar app let's you choose vibration pattern, it's one of the better settings I've seen.
When you take User Experience to the next level. Just what I was thinking
Credits : Riot App
Date pickers!
After several decades of web development and even longer time to experiment with electronic UI on other devices, why is there no consistent best practice and everyone tries reinventing the weel to choose their own set of problems and annoyances?
The root cause, obviously, is using Gregorian calendar and localized display and input format in the first place, so there is no way to make a data unambiguous without a graphical calendar. Who even came up with any of those 9/10/11 formats and why?
So we need to use date pickers and make the users spend several minutes clicking, swiping or scrolling to enter their birthday - past at least one decade - and a booking date - in the near future - using the same interface with the same presets.
But users compare different offers, so they will use different sites, so they will have to handle different date pickers on different sites in a short period of time and carry unnecessary mental load.
rant
datepicker
ux
ui