4 ms·
Do those older UI standards deal with responsive and touch elements? I agree that it's high time for a set of "web app UI framework" primitives and best practi
by solardev 3y ago
Do those older UI standards deal with responsive and touch elements?
I agree that it's high time for a set of "web app UI framework" primitives and best practices, something like Material or MUI but actually a collaborative standard. It's stupid to have to reinvent basic cards, modals, wizards etc. from scratch every time.
But the web has also rapidly evolved alongside newer needs and form factors (phones, geo stuff, real-time multiplayer, etc.) in a way that a lot of older UIs didn't explicitly account for.
And also, WASM right now doesn't really have a UI layer. And Canvas doesn't work that great with responsiveness.
Not that I disagree with what you said; it's a great goal to aim for!
- baudaux 3y agoWhy are you saying that canvas does work great with responsiveness ? Do you mean that drawing in canvas is slow ?
- solardev 3y agoDoesn't, you mean? Elements inside a canvas can't be easily reflowed around each other the way you can with divs and blocks and flex and grid etc. You basically have to reinvent the responsive UI layer that CSS has been slowly improving over the last decade or two. Is that what you were asking, or did I misunderstand?
- baudaux 3y agoYes, doesn’t work great (sorry ) You replied exactly to my question. The idea behind exaequOS is not reinventing CSS at all but to support “Classic” apps (terminal, graphic toolkit, OpenGL) and html/css apps
- solardev 3y agoOh absolutely! Sorry, that comment wasn't directed at exaequOS, but discussing some older human interface guidelines and older UX standards. Just pointing out that interfaces have evolved since then. But that's not the point of exaequOS and that's okay!
- baudaux 3y agoExaequOS could also run html/css/webassembly apps in order to take benefit of web ui frameworks.
- BoorishBears 3y agoThose already exist: https://www.radix-ui.com/primitives https://www.radix-ui.com/primitives https://react-spectrum.adobe.com/react-aria/ https://react-spectrum.adobe.com/react-aria/ Even MUI has one :https://mui.com/base-ui/getting-started/ https://mui.com/base-ui/getting-started/ - There are some attempts for a lower level version of this at the web component level, but they tend to do nowhere
- solardev 3y agoRight, exactly, but I'm saying it's too bad those things aren't part of the living WHATWG standards/guidelines, and built into HTML or some new higher-level component markup language that browsers can adopt. A "Javascript UI components framework" similar to the UI kits that native Android and iOS have. It's silly to have to reinvent all those basics for every site/company/platform, and it's unfortunate that HTML hasn't really caught up to the app world, still thinking of itself mostly for documents.
- troupo 3y ago> primitives and best practices, something like Material or MUI Material is very far from best practices. Their "designers" had to conduct user studies with hundreds of people to figure out that "text fields have to look like text fields" and still failed to do that: https://medium.com/google-design/the-evolution-of-material-designs-text-fields-603688b3fe03 https://medium.com/google-design/the-evolution-of-material-d...
- solardev 3y agoI agree! We usually tend to modify away Material's default minimalism in favor of usability, too. But I'm just trying to point out the difference in goals between a cross-platform OS and a cross-platform UI framework.