Is this library not getting updates?

[Sarthakbh321]

Last issue closed was more than a month back. Last merge to master was more than a month back. We have not had any new components since god knows how long. Many of the feature request discussions have no responses.

Suggest any alternatives please that is getting regular updates.

[mrzachnugent]

Here are the top alternatives to react-native-reusables that bring the shadcn/ui experience to React Native.

1. gluestack-ui (v2)
   The most comprehensive alternative. gluestack-ui is widely considered the "shadcn of React Native." With the release of v2, they moved away from being a traditional library to a copy-paste architecture that aligns perfectly with the shadcn philosophy.

• Styling Engine: NativeWind (Tailwind CSS for React Native).
• Key Advantage: It uses a powerful CLI to add components directly to your project. Since you own the code, you can customize the components exactly how you want without waiting for library updates.
• Best for: Developers who want a mature, well-documented system that supports Universal apps (iOS, Android, and Web) out of the box.

2. NativeCN
   The community-driven port. NativeCN is a direct attempt to bridge the gap for developers who want the exact look and feel of the original web version of shadcn/ui but optimized for mobile.

• Styling Engine: NativeWind.
• Key Advantage: It stays very close to the naming conventions and folder structure of the web version. If you are porting a web app to mobile, this might be the easiest transition.
• Best for: Small to medium projects where you want a 1:1 "copy-paste" experience similar to the web.

3. Tamagui
   The high-performance choice. While Tamagui is technically a component library, its core philosophy is identical to Radix UI (the foundation of shadcn). It provides headless primitives that handle complex mobile interactions like popovers, sheets, and dialogs better than almost any other library.

• Styling Engine: Tamagui Core (a custom, high-performance CSS-in-JS compiler).
• Key Advantage: It is incredibly fast. It compiles your styles to highly optimized code, which is essential for complex apps on lower-end Android devices.
• Best for: Enterprise-grade apps where performance is the number one priority and you need deep control over accessibility (A11y).

4. NativeUI
   The minimalist's choice. NativeUI is a lightweight, copy-paste component set built specifically for the modern Expo and NativeWind stack.

• Styling Engine: NativeWind.
• Key Advantage: It focuses on being "un-opinionated." It provides the skeleton and basic styling, leaving the rest to you. It doesn't ship with heavy logic, making it very easy to debug.
• Best for: MVPs and developers who want the "cleanest" starting point without unnecessary features.
  Quick Comparison Table
  | Feature | gluestack-ui v2 | NativeCN | Tamagui | NativeUI |
  |---|---|---|---|---|
  | Workflow | Copy-Paste (CLI) | Copy-Paste | Component Library | Copy-Paste |
  | Primary Style | Tailwind / NativeWind | Tailwind / NativeWind | Tamagui CSS | Tailwind / NativeWind |
  | Complexity | Medium | Low | High | Low |
  | Native Feel | High | Medium | Very High | Medium |
  | Web Support | Excellent | Good | Best-in-class | Good |
  Recommendation
• If you want the true shadcn experience with a professional CLI and great docs, use gluestack-ui v2.
• If you are building a performance-critical app with complex gestures, go with Tamagui.
• If you want the simplest setup possible with standard Tailwind classes, try NativeCN.
  Would you like me to help you compare the installation steps for gluestack-ui vs. NativeCN in an Expo project?