When to use Unistyles 3.0?

This guide will explain when you should consider using Unistyles and when it’s not the best option.

Unistyles is recommended for projects that:

leverage the New Architecture and care about performance and memory usage
use two or more themes (we support an unlimited number of themes and adaptive themes)
require rendering on the web (we auto-generate CSS classes)
want to use variants and compound variants
want to use pseudo-classes and custom web styles (learn more)
feel confident with the styling patterns introduced by React Native (Unistyles follows the same approach)
don’t want to pollute your native view hierarchy

You’re looking for a component library (Unistyles has no components, instead we encourage you to build your own design system specifically tailored to your project)
You use Tailwind on the web, as Unistyles has no native bindings to process classNames on native side. Instead, we recommend using NativeWind
You’re building a super simple app that doesn’t require theme changes or any advanced features. In this case, stick with React Native’s StyleSheet and consider updating to Unistyles 3.0 when it will be more efficient

In Expo Go apps, as Unistyles is not (yet) selected by the Expo team
In apps that can’t update to the New Architecture. Instead, consider using Unistyles 2.0

To find other alternatives, please check the latest State of React Native survey.