Theme First UI Development
Published: ....
Last modified: ....
Share this post on BlueskySee discussion on Bluesky
A recent trend within the Frontend development space has been around enabling something I have been calling Theme First UI Development. Tools like Emotion, Styled-System, Theme-UI, React, and concepts like Design Systems, and Design Tokens have really driven the push for building applications based on a finite set of scale-based tokens.This approach to building features and applications isn’t entirely new, however new tools have pushed it to the forefront of web development.
The core benefits of doing Theme First UI Development are:
- Consistency by Default
- Separation of Theme and Implementation
- Rapid Development
Consistency By Default
Describing a set of Design Tokens, as the core fundamental pillars of a larger theme, as a scale applied to default values enables consistent UI to be the default. If your development team is only describing the UI using a collection of Design Tokens then you can be sure that styles like spacing, font styling, and colors will align across the application.
Separation of Theme and Implementation
By developing theme first, changes made to the design system by tweaking the design tokens will apply everywhere across the application and lead to consistency during thematic evolution, as well as limited impact to changing feature code. Making a change to the primary color within an application only needs to happen once within the design tokens, and it trickles everywhere through the application.
Rapid Development
By leveraging Theme First UI Development, designers and developers don't need to spend time picking out stylistic elements of the feature, and instead can focus on developing a better customer experience. When you don't design or develop against a set theme or collection of design tokens you can end up spending a majority of the time finding the right color, or font size for your feature, instead of spending that time iterating on the value you are delivering to the user.
These are a collection of the core benefits of Theme First UI Development, but there are many more as well. Feel free to share some of the benefits you find with this approach on Twitter.
Tags:
Related Posts
Web Development
Published: ....
I recently launched a rewrite and redesign of this personal website, I figured I'd talk a bit about the changes and new features that I added along the way!
Published: ....
A quick tip to implementing CSS theming that's compatible with Server Side Rendered applications!
Published: ....
A brief overview on how we launched The Bikeshed Podcast, including a deep dive in our recording and distribution workflows!
Published: ....
A quick tip outlining how to provide specific TypeScript type definitions for a local module!
Published: ....
Some rough thoughts on building a file-system routing based web application
Published: ....
Slicing software: why vertical is better than horizontal.
Published: ....
What if you could author an entire web application in a single file?
Published: ....
A quick way to handle resetting internal state in components when a parent form is submitted!
Published: ....
A brief look at Import Maps and package.json#imports to support isomorphic JavaScript applications!
Published: ....
A collection of tech talks that I regularly re-watch and also recommend to everyone!
Published: ....
Some features and functionality that I'd like within a React Server Component compatible framework.
Published: ....
A (running) collection of Bluesky tips, tools, packages, and other misc things!
Published: ....
A quick look at a small but powerful pattern I've been leveraging as of late!
Published: ....
A proposal for a minimal variant of TypeScript!
Published: ....
Sharing a few core recommendations when working within monorepos to make your life easier!
Published: ....
This is a quick post noting that Next.js should now work with Deno v2!
Published: ....
React components have a fundamental contract that is often unstated in their implementation, and you should know about it!
Published: ....
Replace that old useState and useEffect combo for a new and better option!
Published: ....
A quick look at the applications and tools that I (generally) use day to day for web development!
Published: ....
There are a variety of different markdown "standards" out there, and sometimes they're not all that consistent
Published: ....
Proposing a solution for sharing core "business" logic across services!
Published: ....
There's a common gotcha when creating Web Request and Response instances with Headers!
Published: ....
Feature toggles are often underused by most software development teams, and yet offer so much value during not only feature development but also refactors
Published: ....
A quick introduction to my new side project, hohoro. An incremental JS/TS library build tool!
Published: ....
Two neat tricks for enhancing your site's favicon!
Published: ....
The various risks and pitfalls of open source software run by corporations.
Published: ....
A monorepo template for managing a library and documentation together.
Published: ....
How we solved an almost show-stopping production bug, and how you can avoid it in your own projects.
Published: ....
A(nother) deep dive into one of my recent side projects; tails - a plain and simple cocktail recipe app.
Published: ....
When did semver major changes become so scary?
Published: ....
Leveraging service monitors properly to improve service observability.
Published: ....
A brief recap of how Wayfair changed it's CSS approach not once but twice in the span of 5 years!
Published: ....
A deep dive into one of my recent side projects; microfibre - a minimal text posting application
Published: ....
Pair programming can be good sometimes - but not all the time
Published: ....
A few thoughts on using Suspense with GraphQL to optimize application data loading
Published: ....
A few thoughts on what to do after you launch a new project
Published: ....
A few quick thoughts on burn out and taking a break
Published: ....
A few thoughts on managing complex UI component state within React
Published: ....
A quick overview of the new lifecycle methods introduced in React 16.3
Published: ....
A few thoughts and patterns for using styled-jsx or other CSS-in-JS solutions
Published: ....
A few thoughts on the redesign of my personal site, adopting Next.js and deploying via Now
Published: ....
A few weird things about JavaScript
Published: ....
Building a calendar web application
React
Published: ....
A quick tip to implementing CSS theming that's compatible with Server Side Rendered applications!
Published: ....
A quick way to handle resetting internal state in components when a parent form is submitted!
Published: ....
Some features and functionality that I'd like within a React Server Component compatible framework.
Published: ....
React components have a fundamental contract that is often unstated in their implementation, and you should know about it!
Published: ....
Replace that old useState and useEffect combo for a new and better option!
Published: ....
Revising my previous blog post on React Error Boundaries and my preferred go-to implementation!
Published: ....
A few thoughts on using Suspense with GraphQL to optimize application data loading
Published: ....
A few thoughts on managing complex UI component state within React
Published: ....
A quick overview of the new lifecycle methods introduced in React 16.3