react-native-ui-lib wins on the compare page when the product is a phone and the missing pieces are specific. otf-kit wins on that same page when the product also has a web app, a theme picker, or a kit with auth and payments. The coverage checklist below is the live page at the compare page, read on 28 September 2026. Kit prices that the compare page does not spell out come from pricing the same day.
The page calls the library RNUI, and sometimes Wix RNUI. It describes it as one of the longest-running and broadest React Native component libraries: 100+ components, used heavily inside Wix and across the React Native ecosystem. It is React Native only. It has its own design language and it ships theming primitives. The FAQ says Wix maintains it as a public artifact of their internal system, and that releases are regular.
otf-kit, on the same TL;DR, is the other bet. Cross-platform from the start, with web parity through Radix. Seventeen picker-driven themes. Paid full-stack kits beside the components. The page says the component count favors RNUI on native, and that otf-kit closes the gap on web parity and on product shape.
Count the native surface before you count the web one
The matrix is the whole argument in two numbers. otf-kit lists 80+ native components and 198+ web components. RNUI lists 100+ native components and no web rendering. Platforms are web plus iOS plus Android, against iOS plus Android only.
If the roadmap has no web app, the 198+ is irrelevant and the 100+ is the lead. The page's first win for RNUI is that case: React Native only, no web-parity plan, and you want the broadest component coverage. The second win is more useful, because it names the surfaces. Wheel Picker. A slider with custom thumbs. A carousel with parallax. The page says those exist in RNUI and do not exist in most alternatives.
The FAQ is stricter than the win list. otf-kit does not ship a wheel picker or a carousel in the SDK directly. The SaaS Dashboard kit includes a basic carousel. A wheel picker means a community package. The page says RNUI is more feature-complete on these niche surfaces. The migration section names the hard leftovers again: Wheel Picker, Hint, and Image with custom overlays. For those, the page says you can keep RNUI installed as a peer and use both libraries.
That peer line belongs on the checklist as a third option, not as a failure. The FAQ says the two libraries do not share a theme system and still coexist. Use otf-kit for the common UI, about the way the page puts it as the 80 percent case, and reach for RNUI when the screen is one of those niche components. I am using the page's "80%" as its wording for the common set, which is a different number from the "80+ native components" in the matrix.
What you give up if you leave the catalog
Write these down before a migration PR, because the page is explicit that RNUI still fits.
You are already on Wix's stack, or the team already knows the API. Familiarity is a listed win, not a sentimental one.
You want Reanimated-driven animation built into the components. The matrix row says RNUI's animation is Reanimated-based built-ins. otf-kit's cell says Motion plus GSAP integrations. Those are different animation stacks. Moving because you dislike one of them is a real reason. The page does not say one is faster.
You rely on the theme manager and color system RNUI already ships. otf-kit's theme cell is 17 picker-driven themes, swappable at runtime. RNUI's cell is "theme manager plus colors." A designed set of 17 is not the same object as a theme manager you already configured. If the product's colors live in RNUI's manager, the 17 are a replacement project, not a free upgrade.
The engine row is the other thing you would be adopting on purpose. otf-kit is Tamagui, described as compile-time. RNUI is StyleSheet-based, with custom theming. The win list says to prefer otf-kit when you want that compile-time model over the runtime StyleSheet approach. If you do not want it, the page is not telling you to switch.
Pricing on this axis is simple. Both component layers are free. RNUI is free and MIT. The otf-kit SDK is free. The kits are the paid part, at $99 each on the compare page, named SaaS Dashboard and Fitness. RNUI's kit cell says none.
What the catalog cannot grow into
The page's reasons to move are also specific.
Web parity. RNUI's web cell says none. otf-kit's says Radix-based web components with a parity API. The decision line under the title is: pick RNUI for the broadest React Native-only coverage from a battle-tested library. Pick otf-kit for cross-platform parity, the 17 swappable themes, or a full-stack kit.
A kit with auth, Stripe, and Drizzle wired. That stack list is the page's, in the "when otf-kit wins" section. RNUI does not ship it. The closing block prices the Everything Bundle at $149 and Fitness at $99, with the Fitness line "auth, DB, workouts, live demo ready." SaaS Dashboard shows up in the same footer as 11 screens with billing wired, at $99. Demos linked from the page: the Fitness demo and the SaaS demo.
Pricing is the rest of that ladder. Free SDK: $0, 220+ pieces, 5 design themes in dark and light, full source, AI configs for Cursor, Claude, and Lovable, community support, 1 seat. The 17 themes are the compare-page claim. The 5 are the free-tier card. Landing template: $9, one client project. Kit: $99, with SaaS Dashboard, Fitness, and Arcade live, login and payments and a database wired, 12 months of updates, one client project, 1 seat. Booking is Preview, through the bundle until it is live. Marketplace is coming soon and is not sold on its own. Bundle: $149 against $531, save $382, 4 delivered kits and all 15 landing templates, lifetime updates, 1 seat. The pricing page marks Fitness and Arcade as web plus mobile, and SaaS Dashboard as web. Team is custom for 5 seats and unlimited client projects, with no price printed.
The button sample is small beside that, and it shows the API shift you would be buying. RNUI takes a label prop and a backgroundColor. otf-kit's native Button takes variant="default" and the label as children, imported from @otfdashkit/ui-native. The migration section says the larger shift is styling. RNUI's modifier props, such as <View bg-blue50>, are its own pattern. otf-kit uses Tamagui's prop API on native, and the page says bg="$blue50" works, plus the style prop.
A checklist you can tick
Stay on RNUI when every box below is true. The app is React Native only. You use at least one of Wheel Picker, the custom slider, the parallax carousel, Hint, or Image overlays. You want Reanimated inside the components. You already know the API or you are on the Wix stack. You do not need a web twin or a kit.
Move the common screens when any of these is true. A web app has to share the component API. You want 17 runtime themes. You want Tamagui's compile-time style path. You want the $99 kit with auth, Stripe, and Drizzle rather than a component library alone.
Keep both when the common screens can move and the niche ones cannot. The page allows that peer dependency. It also says the theme systems stay separate, so budget a visual seam.
The matrix, the niche-component list, and the button sample are on the compare page. Open pricing only after the coverage boxes say a kit is actually the thing you are missing. The free SDK is the GitHub repo.
Top comments (0)