# RNUI as org design system vs a thinner custom layer

You already standardized on Wix [React Native UI Lib (RNUI)](https://github.com/wix/react-native-ui-lib) for React Native. The library is a full UI toolset: foundations, `ThemeManager`, modifiers, and a deep component catalog maintained for modern React Native architectures. The question is no longer "is RNUI good enough to start?" It is whether RNUI should be the **org-wide mobile design system**, or whether a **thinner custom RN layer** on top of a smaller primitive set will cost less to operate across apps.

This is an org-architecture decision, not a product-kit pitch. Keep RNUI when multi-app theming, RTL, and token ops fit its foundation model. Prefer a thinner custom layer when your apps diverge faster than a shared ThemeManager can absorb.

---

*This is an excerpt. Read the full post at [otf-kit.dev/blog/rnui-org-design-system-vs-custom-layer](https://otf-kit.dev/blog/rnui-org-design-system-vs-custom-layer) — full-stack kits your AI coding agent can actually ship to production. [Browse the kits →](https://otf-kit.dev)*