Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more! Learn more →
Similar projects and alternatives to styletron
Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
A utility-first CSS framework for rapid UI development.
Appwrite - The Open Source Firebase alternative introduces iOS support . Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more!
👩🎤 CSS-in-JS library designed for high performance style composition
Zero-runtime CSS in JS library
React CSS Modules
Seamless mapping of class names to CSS modules inside of React components.
Access the most powerful time series database as a service. Ingest, store, & analyze all types of time series data in a fully-managed, purpose-built database. Keep data forever with low-cost storage and superior data compression.
Full CSS support for JSX without compromises
An enterprise-class UI design language and React UI library
⚡️ Simple, Modular & Accessible UI Components for your React Applications
MUI Core: Ready-to-use foundational React components, free forever. It includes Material UI, which implements Google's Material Design.
🤖 Headless UI for building powerful tables & datagrids for TS/JS - React-Table, Vue-Table, Solid-Table, Svelte-Table
Completely unstyled, fully accessible UI components, designed to integrate beautifully with Tailwind CSS.
:atom_symbol: React primitive UI components built with styled-system.
🧱 A suite of React components .
Next generation utility-first CSS framework.
The worlds fastest React UI kit also happens to work on Native + Web seamlessly 🙏
A design system for building modern websites and applications.
styletron reviews and mentions
Tailwind CSS v3
9 projects | news.ycombinator.com | 9 Dec 2021
Some technical thoughts as someone who could care less about fanboyism:
- One point where atomic CSS frameworks are supposed to shine over conventional CSS is bundle size, since they (at least the good ones) compile to only a single rule for any used value, rather than potentially repeating rules for semantically different classes.
- Another point where atomic CSS frameworks shine is just sheer volume of banging code out. When the bulk of your output is visual, mastering tools based on shorthands like tailwind, emmet, etc can feel very productive.
- Purely atomic CSS frameworks can make some workflows more difficult, e.g. by having too granular call sites and not allowing "let's see what happens to the overall theme if I do this design change" iterative style of work, or because workflows that edit CSS on the fly via browser devtools can no longer be used to limit impact within semantic lines (e.g. "I want to change padding only on buttons, without breaking everything else that happens to depend on the same padding value"). There are both design-oriented and debugging-oriented workflows that are affected in similar ways.
- You generally don't get visual regressions at a distance w/ atomic CSS. This matters at organizations where desire for pixel precision and simultaneously fickle design teams are the norm. But conversely, "can we just change the font size to be a bit bigger across the site" can often run into issues of missed spots. On a similar note, designs may become inconsistent across a site over time due to the hyper local nature of atomic CSS oriented development.
- Custom rules may as well be written in APL; they usually aren't documented and it takes a "you-gotta-know-them-to-know-them" sort of familiarity to be able to work with them (or get back to them after a while).
- There are some tools that mix and match atomic CSS with other paradigms. For example, styletron can output atomic CSS for the bundling benefits, but looks like React styled components from a devexp perspective, and has rendering modes that output traditional-looking debug classes for chrome devtool oriented workflows.
The main theme to be aware of: proponents rarely talk of maintenance, so beware of honeymoon effect. Detractors often omit that traditional CSS (especially at scale) also requires a lot of diligence to maintain. So think about maintenance and how AOP vs hyperlocal development workflows interact with your organization's design culture.
5 React.js UI Component libraries.
9 projects | dev.to | 11 Aug 2021
It is created, managed, and utilized by Uber. It includes a wide range of attractive components, with accessibility as the top focus. It is quick since it is built with the Styletron engine. Style overrides can be used to tweak themes, but in my experience, I've never required them because the design vibe they're trying for is precisely what I want.
Just-In-Time: The Next Generation of Tailwind CSS
 https://www.styletron.org/  https://baseweb.design/blog/getting-started-with-styletron#getting-started-with-styletron
@blocz/react-responsive v3 is out
3 projects | dev.to | 12 Mar 2021
When we created the library, we were using styletron for our styles, and we wanted to bind the breakpoints we defined in @blocz/react-responsive with the breakpoints used for our styles.
A note from our sponsor - Appwrite
appwrite.io | 22 Mar 2023
styletron/styletron is an open source project licensed under MIT License which is an OSI approved license.