Mike's Notes
A helpful article published on Medium discusses what selection control to use and where. It is based on the experience of teams using the Lyft Design System and builds on a previous article also listed below from 2019.
I need the Pipi CMS to automatically pick the correct selection control for any UI based on simple rules. The rules are explicitly described in the two Medium articles below.
This also builds on the work of the EU-funded Cameleon Project, which was to create Model-Driven User Interfaces. After 10 years of serious work, the Cameleon Project has gone nowhere, possibly overtaken by the arrival of HTML5 and mobile phones some 15 years ago.
However, I have found a way to put all that excellent research to good use in the Pipi CMS Engine. And the Lyft Design System articles answer some of my remaining unanswered questions.
The full range of selection options presented by Lyft is tempered by some good points by Adam Silver, who argues that functionality should first be made on web UI to preserve accessibility. I agree, given that Pipi is built to generate workplace enterprise tools. Adam has a website with many valuable tips on providing web forms.
Resources
- https://medium.com/tap-to-dismiss/a-better-segmented-control-9e662de2ef57
- https://medium.com/tap-to-dismiss/select-to-proceed-996d19c8a7a4
- https://www.blog.ajabbi.com/2023/12/model-driven-user-interfaces.html
- https://www.blog.ajabbi.com/2023/12/pipi-9.html
- https://adamsilver.io/blog/form-design-from-zero-to-hero-all-in-one-blog-post/
A better segmented control
No comments:
Post a Comment