←back to thread

Pikaday: A friendly guide to front-end date pickers

(pikaday.dbushell.com)
286 points mnemonet | 1 comments | 11 Nov 25 14:58 UTC | HN request time: 0s | source
Show context
carlosjobim ◴[11 Nov 25 15:01 UTC] No.45887999[source]▶
They are wrong. Most OS native date pickers are very bad from a usability perspective. A javascript date picker fixes these issues, and allows more functions.

And why are they arguing against their own product? Even making up bogus claims that using js date pickers would be illegal in Europe?

replies(3): >>45891225 #>>45891256 #>>45893582 #
SoftTalker ◴[11 Nov 25 22:10 UTC] No.45893582[source]▶
You know what's bad? A bespoke date picker that behaves differently from how the date picker works on the rest of the apps on the device.

Usability doesn't matter when there's an established behavior. Users get used to how it works, and then differences cause stumbling blocks.

Use the native date pickers.

replies(1): >>45894979 #
1. carlosjobim ◴[12 Nov 25 00:42 UTC] No.45894979[source]▶
The native date pickers are of low quality for usability. They have been so unpopular for so long, that you don't have any users who are accustomed to them. Because almost no apps or websites use the native date pickers.

If you're fine with loosing most of your customers because they can't use your website, then go ahead with native date pickers. But I'm not going to ask my customers to scroll on a list of numbers on their iPhone or try to pinpoint a microscopic calendar on their computer to pick a date. User comes first. Developer comes last.