You can use whatever you like!

https://docs.uniwind.dev/tailwind-basics#advanced-pattern-variants-and-compound-variants

Pro beta will be released before end of this month!

Pro beta will be released before end of this month!

Has the official release date for the Pro version been set?

End of this month 😪

We had to make OSS version stable. Right now we're polishing pro, building licensing system and redesigning landing page. We're almost there..

Uniwind can handle some tasks during build time, which is why it’s on par with Unistyles 3.0, which performs everything at runtime.
Uniwind Pro will do both approaches, making it the fastest.

is there any example how you will handle Pressable with pressed state with animation with or without pro version?

@Brentlok do you have any video / code snippet for Reanimated from alpha?

I have that one
https://github.com/user-attachments/assets/30e9aaa0-c8d6-4273-9019-93825ef293e9

is there any example how you will handle Pressable with pressed state with animation with or without pro version?

If you're asking about the code, it should look something like that

<Pressable className="bg-red-500 active:bg-red-300 transition-colors" />

Nothing special, just your regular tailwind classes. It will work in the pro version out of the box

You don't need to setup Unistyles. Everything will be a part of Uniwind package.

Also things like keyboard avoid or safe area will be custom classes in the future in uniwind? since as far as i know it's not something that is part of tailwind by default.

It's part of Tailwind, but requires eg. react-native-safe-area-context. We will inject this values directly from C++ (no 3rd party dependency).

but if i want to use it style and not in the css classes of tailwind/uniwind. It will be possible ? or i guess i will need to use useUniwind hook to get the theme values etc to do custom stylesheet ?

Why do you want to use style? Like in the entire app or for some components?

You can use styles even now, they will override classNames.
If you want to access theme variables then you need to use useResolveClassNames

We know the Pro version is powerful, but how does the free version compare to NativeWind

Faster, more stable, 99% feature parity.
https://github.com/Unistyles-OSS/uniwind-benchmarks

Does UniWind support dynamic theme creation

No, we rely on Tailwind compiler and Tailwind 4 syntax. There is no JS in the middle like with Tailwind 3

No, we rely on Tailwind compiler and Tailwind 4 syntax. There is no JS in the middle like with Tailwind 3

I spent some time digging into the source code and tried adding a setThemeCSSVariables method in useUniwind.native.ts to enable dynamic theme updates. Although my implementation is a bit rough, it seems to work for updating theme variables at runtime.

Do you think this approach could be a good starting point for a PR, or as a reference for supporting dynamic/custom themes in the future?

import { useEffect, useState } from "react";
import { Uniwind } from "../core";
import { UniwindStore } from "../core/native";
import { StyleDependency } from "../types";
export const useUniwind = () => {
 const [theme, setTheme] = useState(Uniwind.currentTheme);
 const [hasAdaptiveThemes, setHasAdaptiveThemes] = useState(
 Uniwind.hasAdaptiveThemes
 );
 const setThemeCSSVariables = (newVars: Record<string, unknown>) => {
 Object.defineProperties(
 UniwindStore.vars,
 Object.getOwnPropertyDescriptors(newVars)
 );
 UniwindStore.notifyListeners([StyleDependency.Theme]);
 };
 useEffect(() => {
 const dispose = UniwindStore.subscribe(() => {
 setTheme(Uniwind.currentTheme);
 setHasAdaptiveThemes(Uniwind.hasAdaptiveThemes);
 }, [StyleDependency.Theme]);
 return () => {
 dispose();
 };
 }, []);
 return {
 theme,
 hasAdaptiveThemes,
 setThemeCSSVariables,
 };
};

It is definitely possible to achieve dynamic themes support but we need to take some things for consideration

• should you be able to change the theme (even light/dark) while you've updated theme variables?
• could you change variables for specific theme? For example only changing variables for a dark theme
• web implementation - your implementation won't work on web since UniwindStore in native only

And to match our API, this method should be placed under Uniwind config.ts, since it doesn't require any state, there's no need for it to be inside a hook

Uniwind looks very promising but compared to Tamagui you offer fewer components.

Hey! We don’t ship our own components, we only provide bindings for existing React Native components. It’s hard to compare a full UI Kit like Tamagui with a styling library like Uniwind.

If you’re looking for ready-made components, check out HeroUI Native (the first UI Kit powered by Uniwind).

You don’t get a preview of the existing React Native components.

Same as above, we’re not a UI Kit 😁

It’s not clear at first glance if you can use the same components on the web and native.

That’s exactly what Uniwind is designed for. You write once and your styles run cross-platform. We can definitely improve the visibility of this point.

How easy is it to take existing Tailwind 4 components and convert them to Uniwind components?

You should approach it from the opposite direction. Start from mobile, make it work there first, and then bring it to the web. You’ll need React Native Web to make the components cross-platform.