21–30 of 73 posts
The never ending battle between customizability and uniqueness. If there were a standard library (adopted by all browsers) similar to the default look of iOS and Android apps, but in return you couldn't customize the look, would y'all go with that?
can someone explain in layman terms what is headless UI?
It's not a thing, this is just a term made up on the spot by the author of this article to describe a component library that has no built-in style. "What does it even do then" you ask. It implements basic accessibility patterns so you only deal with high level UI elements and not have to worry about having the correct `role-` or `aria-` attributes. That and composite elements such as tabs or modals Why no style? Most…
Isn't the point of an UI to have an ... UI after all? The only ones that I can see being headless here are customers buying in to headless UIs, headless CMSs quackery.
Try building a fully accessible dropdown from scratch in React? This is what these libraries solve.
An example from Radix UI: https://youtu.be/pcMYcjtWwVI
Cool to see more competition to Headless UI [0] by the Tailwind guys [0]: https://headlessui.dev/
Cool to see more competition to Headless UI [0] by the Tailwind guys [0]: https://headlessui.dev/
It would be cool to go back to HTML=schematics and CSS=styling.
Maybe CSS needs to become more capable tool to place divs more easily?
Earlier quoted context omitted.
From the developer perspective, I can certainly relate. From the user perspective, yet another widget with subtly different behaviour is very annoying. I'd much rather you add drag and drop handling to the existing widget so that everyone benefits and UIs remain consistent.
Yeah I get this argument for native apps, but does it really make sense in the context of a React app? If I'm combining components from different authors, what's more important to the user is consistency between components in my application, not consistency for an individual component across different unrelated sites.
Hell, back in the 2000s, even web apps used native widgets, and we shamed websites that implemented their own UIs in Flash because they were bloated and inaccessible. Now we do it in Javascript and it's considered okay, even though all the same objections apply. And with Electron apps we've managed to combine all the worst aspects of web apps and native apps - they're slow, non-native and not cross-platform, and don't have text search, and still have to be installed.