The directory covers the current React Native toolchain
Awesome React Native is a hand-edited index, with sections for UI, navigation, data, testing, deployment, open-source apps, and learning. The August 26, 2026 rewrite added Expo-era tools, New Architecture libraries, AI agents, MCP servers, and on-device inference. It also removed dead, archived, and superseded entries. That reset matters because a mobile library list decays quickly when native APIs, build systems, and framework defaults change.
The README is 28,684 bytes and is the entire product. Entries usually get one sentence and a link. That restraint makes scanning easy: a developer can move from lists to maps or storage without reading mini essays. It also limits what inclusion tells you. You get the editor's shortlist, not supported React Native ranges, recent release dates, native configuration steps, bundle impact, or results from a sample app.
Editorial rules require activity within roughly 12 months
The contribution guide gives maintainers a real bar. A suggested project should have a release or meaningful commit within about 12 months, work with current React Native, and preferably support the New Architecture. Libraries also need adoption or unusual technical value. Commercial services can appear when they are widely used. Removal pull requests are welcome when a project is dead, archived, or superseded.
Those rules are better than an unfiltered link dump, though they are still judgments made during review. The repository does not publish a machine-readable record showing when each entry was last checked. Its opening claim says listed projects work with modern React Native, but a 3-CPU sandbox cannot prove hundreds of linked packages against iOS, Android, Expo, and bare workflows. Treat the rule as a screening method rather than a warranty.
React Native Directory gives the missing compatibility signals
The list itself points readers to React Native Directory, which is the better tool once your question becomes specific. Directory supports search and filters, with maintenance and New Architecture data attached to packages. Awesome React Native is stronger earlier in the decision: its categories can show you that several approaches exist, including native navigation, React Navigation, and Expo Router, without asking you to know the right package name first.
A sensible workflow uses both. Start here to understand the field, then check candidates in Directory and their own repositories. For a dependency that crosses the native boundary, confirm the exact framework version, iOS and Android requirements, Expo compatibility, and release activity. The 2026 editorial pass reduces obvious dead ends, but it cannot replace building the candidate inside your application.
What happened when we ran it
We did not run commit 6733606. Our sandbox inspection found no supported language ecosystem and no Dockerfile, so there was no install, build, or test target that could produce a meaningful result. Saying that plainly is important: the repository is a curated Markdown document, and any build result would belong to one of the projects it links, not to Awesome React Native.
The sandbox had 3 CPUs and 8 GB of RAM, but neither resource affected the outcome. There were no package counts, timings, test counts, audit results, or vulnerability findings to report. A reader can clone the repository for an offline copy, yet the normal use is simply reading the rendered README on GitHub. Setup ease is therefore excellent, while software verification is outside this project's scope.
The 2026 rebuild followed five years without a commit
Git history adds useful context to the fresh-looking page. commit 6733606 rebuilt the list on August 26, 2026. The preceding visible content commits were from April 2021, a gap of about five years. A companion commit removed the dead site and toolchain and declared the GitHub README to be the product. This is recent maintenance, but it is too early to infer a steady editorial cadence from one large cleanup.
GitHub showed 35,688 stars, 1 combined open issue and pull request, and a push on August 26, 2026 when fetched. The open item was a pull request proposing Sherlo in the testing section, which fits the stated contribution model. There was no latest GitHub release. For a list, releases are optional, though their absence means consumers cannot follow named snapshots or release notes.
Short descriptions cannot settle dependency risk
Several entries use confident labels such as standard, fast, or native. Those are navigation aids copied into a compact editorial format, not results from a shared benchmark. The repository does not claim to inspect transitive dependencies, security advisories, accessibility behavior, commercial terms, or migration cost. Each candidate still needs its own review, especially libraries that access cameras, location, payments, notifications, or device credentials.
That boundary is why the list works best for discovery. It is broad enough to expose newer names beside familiar ones, and opinionated ordering saves time compared with a raw registry search. Use it to produce a shortlist, then demand stronger evidence from the actual projects. On that narrower job, Awesome React Native is useful. As a final buying guide, it stops one step too soon.