Cross-Platform React Native UI Toolkit
25.9k
Stars
4.7k
Forks
151
Open issues
30
Contributors
AI Analysis
React Native Elements is a cross-platform UI component library for React Native that provides pre-built, themed components for iOS and Android mobile applications. It serves developers building mobile apps who need a consistent, production-ready component library rather than building UI from scratch. It is not for web development or single-platform-only projects.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
React Native Elements: A mature cross-platform UI toolkit with broad component coverage and a decade of community use
React Native Elements (RNEUI) is a comprehensive UI component library for React Native, covering standard primitives like Buttons, Cards, Inputs, Avatars, and Overlays with built-in theming support. It targets React Native developers who want a ready-made, cross-platform (iOS, Android, Web) component foundation rather than building from scratch. With ~25,800 GitHub stars, an npm package split into @rneui/base and @rneui/themed, an active Discord, and a VS Code extension, it has clearly accumulated a large community over its ~10-year lifespan. It matters as one of the longest-standing React Native UI toolkits with consistent theming primitives.
Created in September 2016 — early in the React Native ecosystem — it established itself as a go-to UI kit before many alternatives existed. The rebranding from 'react-native-elements' to the @rneui scoped packages signals a maturity milestone.
Early mover advantage in the React Native UI space, combined with MIT licensing and active community contributions, drove initial star accumulation. Growth has leveled off significantly: only 3 stars gained in the last 7 days as of mid-2026, suggesting the project has plateaued in new mindshare while retaining its existing user base. The React Native ecosystem has matured with more specialized alternatives, likely diffusing new interest.
25,849 GitHub stars and 4,678 forks over nearly a decade suggest substantial real-world usage. The @rneui/base and @rneui/themed npm packages show live download badge tracking. An Expo demo app, VS Code extension, and Open Collective backers/sponsors provide additional signals of genuine adoption. Exact npm download counts are not available in the provided metadata, but the trajectory and community infrastructure strongly imply meaningful production usage across many projects.
Likely a monorepo (evidenced by separate @rneui/base and @rneui/themed packages) with a component-per-package separation. The README implies theming is a first-class concern. React Native Web support suggests components are likely built on React Native primitives without native modules. The codebase language is listed as MDX, which likely reflects documentation-heavy monorepo structure rather than the actual implementation language.
Codecov badge is present in the README, indicating automated test coverage tracking is in place. Specific coverage percentage is not stated in the README excerpt but the CI/CD workflow and codecov integration suggest active quality monitoring.
Last push was May 21, 2026 — approximately 35 days before the evaluation date — indicating the project is actively maintained. GitHub Actions workflows are referenced. The presence of an active Discord, GitHub Discussions, and Open Collective sponsorship suggests an ongoing, organized maintenance structure. Not stagnant, though commit frequency details are unavailable from metadata alone.
ADOPT IF: you need a stable, well-documented, design-agnostic React Native UI library with cross-platform support and an established ecosystem for a new or existing project where long-term API stability matters. AVOID IF: you require strict Material Design compliance, need highly performant or animation-heavy components, or want a modern headless/unstyled architecture — newer alternatives may serve those needs better. MONITOR IF: you are building a greenfield app in mid-2026 and want to see whether RNEUI releases keep pace with the latest Expo SDK and React Native architecture (new architecture / Fabric) requirements.
Independent dimensions
Mainstream potential
4/10
Technical importance
6/10
Adoption evidence
7/10
- Star growth has plateaued (3 stars in 7 days), suggesting declining new mindshare relative to newer alternatives like GlueStack, Tamagui, and react-native-reusables.
- Uncertain compatibility status with React Native's New Architecture (Fabric/JSI) is not addressed in the README excerpt — projects not adopting New Architecture support may face deprecation pressure.
- Community-maintained open source with Open Collective funding may face sustainability challenges if key maintainers reduce involvement, as has happened with several large React Native libraries.
- The React Native UI toolkit space is fragmented and actively evolving; RNE's design-agnostic approach, once a strength, may appear undifferentiated compared to more opinionated or more flexible modern alternatives.
- MDX listed as primary repository language likely reflects documentation tooling rather than implementation, but this metadata quirk may obscure the true technical stack for new evaluators.
RNE will likely remain a stable, widely-used library for existing codebases and developers familiar with it, but is unlikely to recapture top-of-mind status for greenfield React Native projects as the ecosystem shifts toward utility-first and headless component patterns.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://reactnativeelements.com
- Language
- MDX
- License
- MIT
- Last updated
- 2mo ago
- Created
- 120mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
`ButtonProps` children type incompatible with React 19+ JSX ((state: PressableStateCallbackType) => ReactNode not assignable to ReactNode)
TS Bug - @rneui/base@5.0.0 — Undeclared type dependency causes IconProps to lose color/name/size
@testing-library/jest-native + @testing-library/react-native in peerDependencies (v5)
Slider not align / duration line not in align with maximun track line
Top contributors
Similar repos
wix/react-native-ui-lib
React Native UI Library is a comprehensive component library and design system...
founded-labs/react-native-reusables
React Native Reusables ports shadcn/ui components to React Native using...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
|
25.9k | — | MDX | 8/10 | 2mo ago |
|
|
7.1k | — | TypeScript | 8/10 | 2w ago |
|
|
246.4k | — | JavaScript | 10/10 | 10h ago |
|
|
126.2k | — | C++ | 9/10 | 10h ago |
|
|
8.5k | — | TypeScript | 8/10 | 1w ago |
|
|
14.4k | — | TypeScript | 8/10 | 1w ago |
React Native Paper follows Material Design specifications closely, giving it stronger visual consistency for Android-first or Material-oriented apps. RNE is more design-agnostic and flexible, but Paper has been growing faster recently with ~14,400 stars and strong Callstack backing.
Wix's UI lib is TypeScript-first, used heavily in production by Wix itself, and includes more advanced animation and gesture components. It has fewer stars (~7,100) but may have deeper production hardening in complex enterprise scenarios.
react-native-reusables is a newer, headless/unstyled component approach inspired by shadcn/ui patterns. It has ~8,400 stars but represents a different philosophy — composable primitives over pre-styled components — which appeals to developers wanting full style control.
NativeBase evolved into GlueStack UI, which offers a utility-first styling approach and has attracted significant mindshare from the NativeBase migration path. GlueStack may be pulling developers who want a more modern architecture away from RNE.
Tamagui offers performance-optimized, universal (React Native + web) UI components with a compile-time optimization approach. It appeals to developers prioritizing performance and design tokens, though it has a steeper learning curve than RNE.