It's a good thing (tm) that no matter which app I open up, the date picker looks the same, and works the same. This is the nice thing about native apps. So I wish we would stop reinventing wheels like this (once again, no offence intended to the author – this is a more of general critique).
I'd love it if there were also some + and - buttons so I could easily add one month, one year etc.
Plus, I'm a big fan of reinventing the wheel. The final chapter of date pickers has not been written, IMHO, and am grateful for these types of experiments. I can easily imagine a "cover flow" inspired picker being great for certain use cases, like buying tickets.
Per @yoz-y down thread, I agree with need for text input. I like Fantastical's approach. Had hoped it'd become more common.
Point was that nobody has considered it perfect from day one.
My portfolio is filled with regrets where I chose something interesting over something obvious.
Also, in the calendar app, when creating an event, i carefully select the date and time, and then i scroll down to set an alarm - and about half the time, the date picker takes my scroll so i lose the date i just entered. So annoying.
Col.topAnchor.constraint(equalTo: topAnchor, constant: 0).isActive = true
Col.bottomAnchor.constraint(equalTo: bottomAnchor, constant: 0).isActive = true
Col.leftAnchor.constraint(equalTo: leftAnchor, constant: 0).isActive = true
Col.rightAnchor.constraint(equalTo: rightAnchor, constant: 0).isActive = true
Col.topAnchor.constraint(equalTo: topAnchor, constant: 0),
Col.bottomAnchor.constraint(equalTo: bottomAnchor, constant: 0),
Col.leftAnchor.constraint(equalTo: leftAnchor, constant: 0),
Col.rightAnchor.constraint(equalTo: rightAnchor, constant: 0),
GitHub example with better readability:
The rule that I followed was:
Use activateConstraints if you actually have a performance problem and otherwise activate constraints one by one.
However since this is a framework this rule may not apply because you don't know how it will be used.
All it takes is forgetting to add `.isActive = true` to a single constraint and nothing will work, and it can be so difficult to spot.
Windows 10’s Time picker is the absolute worst - clearly designed for touch-based devices it’s horribly inappropriate for mouse+keyboard devices: scrolling with the mousewheel is much slower than it should be, and there isn’t even direct numeric entry from the keyboard, it’s maddening.
Going from concept to polished completion and publication is a big success!
The idea of various use cases don't seem to get enough play in UI component design, imo (or maybe I'm just not reading the right bits?). I'd like there to be some "this component is designed for these use cases - A & B. if you desire use case C, look at component X." and so on.
I see a lot of requests in this thread for just typing the date. I agree that natural language input like Fantastical is the best experience. I built an open-source NLP date parsing library so I have a lot of interest in this, but even I’ll admit the reason it’s not more common is that internationalization is extremely difficult when dealing with user input. There are 100 ways an English speaker might enter a date, and 20000 ways an international user might. Depending on your user base, it’s often easier to just use a fixed input space.
Design wise, yours does look much nicer though so kudos to that!
Forcing the user to use a tighltly packed scrolling control with inertia is not a good idea. Yes, it might look cool in a demo, but - i think - it's a terrible user experience.
(Try it, enter a date a month and a half in the future)
If the phone knows how to display it, then it should know what to expect when accepting text entries.
Also - this doesn’t solve the biggest issue with the native date picker - just let me type the damn date already.
Is there similar datepicker for Flutter?
I can't understand why it's so hard to get a decent datepicker in general.
You should only:
* Tap on years and months to select one
* Tap on your preferred day
* Being able (programming side) to select a range
* Being able to input your date inside a preformatted text field that can validate it
Windows from 7 to 10 nailed it, period. So bad that's for desktop-only users.
Where in Windows 10? Surely not the clock at the bottom-right, in the task-bar? That's probably the bit of UI I hate the most (and on Win10 that's a long list).
Please provide some sort of keyboard for input.
iOS dev community doesn't write tests as does Ruby community, which makes me really really sad.