Open-source project
jondot/awesome-react-native avatar
jondot/awesome-react-native

Awesome React Native: A Curated List That Tracks the Ecosystem's Fast-Moving Edge

Awesome React Native components, news, tools, and learning material!

35,706 stars4,063 forksJavaScriptLicense varies

At a glance

What is it?
This review of the awesome-react-native list examines its structure, its AI-focused sections, and how it filters for maintenance and modern React Native compatibility. It is a directory, not a package, so its value depends on how well its curation matches your needs.
Who is it for?
Adopt this list if you want a human-curated starting point for discovering React Native libraries, especially if you are exploring AI-assisted development or need a quick scan of what is current. Do not adopt it as your only source of truth: it is a list, not a package manager, and it cannot tell you whether a library works in your specific runtime.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Yes. The repository last received commits 81 days ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 13, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • jondot/awesome-react-native35,706 ★ · +16
Star history
Repository2026-08-182026-11-13
jondot/awesome-react-native35.7k35.7k

16 Stars in the last 87 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What This List Solves and Who Should Use It

Awesome React Native is a curated directory of libraries, tools, and learning resources for building React Native apps. It solves a discovery problem: the React Native ecosystem is large and fragmented, with many packages that look similar but differ in maintenance status, native code requirements, and compatibility with the New Architecture. The list is aimed at developers who want a filtered starting point rather than a raw search result. It is not a package or a framework. You do not install it. You browse it, click through to repositories, and decide for yourself. The target reader is an engineer evaluating options, not someone looking for a drop-in dependency. The README states that every entry is checked for maintenance and relevance, and that if it is here, it works with modern React Native. That is a strong claim, and it is the list's core value proposition. But it is also the thing you should verify yourself, because curation is only as good as the last review.

How the List Is Organized: From Components to AI Agents

The table of contents reveals a structure that has evolved well beyond the classic component roundup. There are the expected categories: UI, Lists, Navigation, Forms, Image and Camera, Video and Audio, Maps, Charts, Animation, Styling, Internationalization, Notifications, and WebViews. Then there is a Data section covering state management, storage, and networking, plus Services, Payments, and Development Tools. The most notable addition is a top-level AI-Assisted Development category with subcategories for Agents and Skills, MCP Servers, On-Device AI, and AI App Builders. This reflects a real shift in how React Native apps are built and what they contain. The list is not just a static index; it is a signal of where the ecosystem is moving. For example, the On-Device AI subcategory includes react-native-executorch, llama.rn, and react-native-fast-tflite, which are specific libraries for running models locally. The MCP Servers subcategory lists Expo MCP, an Expo-hosted server for EAS logs, documentation search and deployment workflows, and mobile-mcp, an MCP server for mobile automation on iOS, Android, emulators, simulators and real devices. This organization is useful because it separates concerns: you can find a UI library without wading through AI tooling, or vice versa.

The Curation Filter: Maintenance and New Architecture Compatibility

The README makes two explicit claims about curation. First, every entry is checked for maintenance and relevance. Second, if an entry is on the list, it works with modern React Native. The second claim is important because the React Native ecosystem has been through the New Architecture transition, and many older libraries do not support it. The list does not show you the maintenance check or the compatibility check; it only shows the result. That is a trade-off. You get a filtered list, but you lose the evidence. The README also points to React Native Directory as a separate resource that gives searchable, filterable information with maintenance and New Architecture compatibility signals. So the list is not trying to replace a directory; it is a curated layer on top of the ecosystem. The practical implication is that you should treat the list as a shortlist generator, not as a certification. If a library is missing, it might be unmaintained, or it might just not have been reviewed yet. The list is only as current as its last PR merge.

Getting Started and Using the List: Commands and Workflow

There is no installation command for awesome-react-native. You use it by visiting the GitHub repository or the homepage at http://www.awesome-react-native.com. The README includes a Getting Started section that links to the official React Native documentation, Expo, React Native Directory, Upgrade Helper, and rn-diff-purge. That is the real workflow: you start here, then jump to the specific tool. For example, if you are upgrading a project, the list points you to Upgrade Helper, which shows the exact diff between two React Native versions. If you are choosing a UI kit, you browse the Components section and click through to each repository. The list also has a contributing file, CONTRIBUTING.md, which means you can propose additions via pull requests. That is the only 'command' involved: git clone, edit, submit a PR. The list is a living document, and its maintenance depends on community contributions. The README says PRs are welcome, so the curation is not a single editor's opinion but a crowd-sourced filter with some oversight.

Where the List Falls Short: Gaps and Failure Modes

The biggest limitation is that the list cannot tell you why an entry is included or excluded. The README says entries are checked for maintenance and relevance. A library that was current six months ago might now be unmaintained, and the list might not have caught up. Another failure mode is the absence of version-specific guidance. Entries are one-line descriptions, so you have to click through to the repository for version support and setup details. The list is a pointer, not a tutorial. If you are looking for a quick comparison of two libraries, the list gives you names but not side-by-side features. Finally, the list is biased toward what the community submits. If a niche library is not submitted, it will not appear, even if it is excellent. That is a real gap for engineers working on less common integrations.

A Real Alternative: React Native Directory and Its Different Approach

The README itself names the main alternative: React Native Directory. That site is a searchable, filterable directory of React Native libraries, and it includes maintenance and New Architecture compatibility signals directly on each entry. The difference in approach is fundamental. Awesome React Native is a hand-curated list with a human editor or editors reviewing entries and grouping them into categories. React Native Directory is described in the README as a searchable, filterable directory with maintenance and New Architecture compatibility signals. The trade-off is that a curated list can make editorial judgments about quality and relevance, while a directory is more mechanical. For example, a directory might include a library that is technically compatible but poorly designed, whereas a curated list might exclude it. Conversely, a curated list can miss new libraries until someone submits a PR, while a directory might pick them up automatically. For an engineer, the practical advice is to use both: browse the curated list for recommendations, then check React Native Directory for the maintenance and compatibility data you need to make a final decision.

Maintenance and Upgrade Cost: What the Material Implies

The repository itself has no license listed, which is a concern if you plan to reuse any of its content, such as the list structure or descriptions. The license field is unknown, so you should assume all rights reserved until the maintainer clarifies. That is a legal risk, not a technical one. The maintenance cost of the list is borne by the community. The README says PRs are welcome, and there is a CONTRIBUTING.md file, so the list is open to external updates. The default branch is master, and the repository is not archived, and the last push was on 2026-08-26. The upgrade cost for a user is low: you do not install anything, so there is no dependency to update. The cost is time spent reviewing the entries and verifying them yourself. The list can become stale, and you have to check the linked repositories for the latest information. The list's own links to Upgrade Helper and rn-diff-purge show that the maintainers care about version upgrades, but the list itself does not version its content. You get the current state of the master branch, and that is it.

Editorial conclusion

Adopt this list if you want a human-curated starting point for discovering React Native libraries, especially if you are exploring AI-assisted development or need a quick scan of what is current. Do not adopt it as your only source of truth: it is a list, not a package manager, and it cannot tell you whether a library works in your specific runtime. Before relying on any entry, verify its license, its support for the New Architecture, and its actual maintenance history via the linked repository. The list's own claim that every entry 'works with modern React Native' is a curation promise, not a guarantee, so treat each link as a lead, not a verdict.

Frequently asked questions

Is React Native still relevant in 2026, according to awesome-react-native?

The file was last pushed on 2026-08-26 and still leads with React Native and Expo as the starting point, with Expo called the recommended framework for building React Native apps. It also carries a full AI-Assisted Development section covering agents and skills, MCP servers, on-device AI and AI app builders.

What does awesome-react-native say React Native is mainly used for?

Its AI App Builders entries describe the target plainly: a0.dev generates complete React Native apps and ships them to the app stores, and Rork generates Expo and React Native projects compiling to native iOS, Android and web. The category headings cover navigation, maps and location, image and camera, notifications, and payments and monetization.

Does awesome-react-native indicate that React Native is obsolete?

The file makes no such claim and the repository is not archived. It still directs readers to reactnative.dev and Expo, delegates version diffs to Upgrade Helper and rn-diff-purge, and separates the seventeen Components subsections from three under Data and five under Development Tools.

Does awesome-react-native cover React the web library, and can it settle the question of moving away from React?

The entries shown are React Native libraries, from react-native-paper, react-native-svg and react-native-vector-icons to llama.rn and react-native-fast-tflite, so it is not a source for judging that question.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/jondot-awesome-react-native.svg)](https://hysenlabs.com/projects/jondot-awesome-react-native)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/jondot-awesome-react-native.svg)](https://hysenlabs.com/projects/jondot-awesome-react-native)

Was this useful?