Read on Twitter
The two hardest things in Computer Science are not cache invalidation and naming things; they are naming things and taxonomizing things.
Let's take UI components as an example.
(thread
)
Let's take UI components as an example.
(thread
)
Is a switch a separate control or a checkbox styled differently?
Or is it really a labeled slider with two states?
(screenshot from @openuicg )
Or is it really a labeled slider with two states?
(screenshot from @openuicg )
Are tabs and accordions separate controls or different styling of the same underlying semantics?
After all, they both provide a list of buttons for showing one panel of content at a time.
(image credit: https://uxdesign.cc/little-things-in-ux-design-part-1-tabs-v-s-accordions-47390e4910c3 )
After all, they both provide a list of buttons for showing one panel of content at a time.
(image credit: https://uxdesign.cc/little-things-in-ux-design-part-1-tabs-v-s-accordions-47390e4910c3 )
What about a button group for choosing one option out of many? Is that a separate UI component or different styling for radio buttons?
Is a <select> semantically equivalent to these too?
(screenshots: @CodePen, @dabblet, OSX Finder)
Is a <select> semantically equivalent to these too?
(screenshots: @CodePen, @dabblet, OSX Finder)
Is a star rating just a discrete progress bar?
Is a progress ring just a styled progress bar?
Or maybe it's a hollow pie chart?
(screenshots: @shoelace_style )
Is a progress ring just a styled progress bar?
Or maybe it's a hollow pie chart?
(screenshots: @shoelace_style )
To clarify, the questions are *examples*, meant as food for thought and to demonstrate how difficult creating taxonomies of things can be. I am NOT asking for responses!
But I would love similar examples if you have encountered them!
But I would love similar examples if you have encountered them!
