Awesome React Native: a curated list with no changelog behind it

The repository is a README and four image files, so there is nothing to install

Treat this as a document rather than a package. The root of the repository holds .github/, .gitignore, CONTRIBUTING.md, README.md and four image files: arn.png, arn.svg, icon.png and icon.svg. There is no source directory, no manifest, no build output and no LICENSE file, the recorded license is unknown, and there are no GitHub releases. The practical consequence is that you cannot install it, cannot depend on a version of it, and cannot bookmark a tag as a known good state. When you want to know what changed, your only move is to diff the default branch, which is called master rather than main, against your own last read of it. For a list whose value rests on entries being removed once they rot, that gap matters: removals carry as much signal as additions and leave no trace.

The maintenance claim has no dates, no badges and no removal log

The file states that every entry is checked for maintenance and relevance, and that what appears there works with modern React Native. Nothing in the repository records how that check happens. There are no dates beside entries, no maintenance badges, no New Architecture compatibility column, and no log of what was pulled out and why. The list itself points at a tool that publishes such signals: React Native Directory is described as a searchable, filterable directory with maintenance and New Architecture compatibility signals. The consequence for a reader is that this file can tell you a library exists and roughly what it is for, while the question of whether it still builds against the current architecture has to be answered elsewhere, and for anything shipping native code that is the question that decides adoption.

Seven UI toolkits sit in one bucket with nothing to choose between them

Components is the widest heading in the contents list, split into seventeen subsections running from UI and Lists through Maps & Location, Animation & Gestures, Internationalization, Notifications, Web & WebViews and Other Platforms. The UI subsection then names seven toolkits back to back: react-native-paper for Material Design, React Native Elements for themed and composable cross-platform components, Tamagui as a universal kit with an optimizing compiler and full parity between React Native and web, gluestack-ui on Tailwind-style utility classes, react-native-ui-kitten on the Eva Design System, NativeBase, and Shoutem UI. Each line runs about a sentence and none are compared with each other. So the list reliably measures the size of your choice and says nothing about which one to take, and adopting two of them means carrying two sets of spacing and theme conventions into one app.

Expo is named as the recommended framework, and upgrades route to two diff tools

The Getting Started section makes an editorial call that shapes everything after it. Expo is called the recommended framework for building React Native apps, with file-based routing, native modules, builds and updates out of the box, while the bare React Native documentation is listed first for environment setup, guides and API reference. The upgrade story is delegated rather than explained: Upgrade Helper is a web tool that shows the exact diff between two React Native versions, and rn-diff-purge is the raw version to version diff data powering it. React Native Directory sits beside them as the filterable catalogue, and Expo Examples as the reference implementations. The consequence is that a project not on Expo gets documentation links and little else from this section, and version planning for everybody rests on two projects this file only points at.

The MCP entries can drive simulators and real devices, which is a different kind of dependency

AI-Assisted Development is the newest heading in the contents list and it holds two very different classes of thing. Agents & Skills collects the Expo AI Agents Guide on agent setup, llms.txt and best practices, the Claude Code and Expo guide, Expo Skills, and Anthropic's public agent skills repository. MCP Servers collects Expo MCP for EAS logs, documentation search and deployment workflows, mobile-mcp for automation across iOS, Android, emulators, simulators and real devices, ios-simulator-mcp for driving the simulator, taking screenshots and inspecting the view hierarchy, and Maestro, an end to end testing framework with a built in MCP server. The list's own promise covers compatibility with modern React Native. It says nothing about whether an agent able to walk your view hierarchy is something you want beside your app.

The description promises news, and the contents list has no news heading

The repository description covers components, news, tools and learning material, and the contents list delivers the first three of those. There is no news heading, no announcements section and no dates anywhere in the table of contents. The top level sections are Getting Started, AI-Assisted Development, Components, Data, Services & Integrations, Payments & Monetization, Development Tools, Starters & Boilerplates, Open Source Apps, Learning and Staying Up to Date, with Data broken into state management, storage and databases, and networking, and Development Tools into tooling and IDE, debugging, testing, builds and OTA updates, and building libraries. Time sensitive facts consequently have no home in this file. A project that changes pricing, drops a platform or stalls will sit in the list until a reader notices, and any copy you paste into internal notes carries no version marker with it.

A separate website and an untagged master branch leave you with no version to pin

The project points at a site of its own at www.awesome-react-native.com while the entries live in the README, and the file does not say which of the two is authoritative or how they are kept in step. Add a default branch called master, no GitHub releases, and a last push on 2026-08-26, and the maintenance picture is clear: the file is refreshed on a regular cadence through pull requests, which CONTRIBUTING.md invites, but it ships nothing versioned for you to hold on to. The entries worth the read, from react-native-svg and react-native-svg-transformer for drawing, through react-native-vector-icons and lottie-react-native, to on device inference via llama.rn, react-native-executorch and react-native-fast-tflite, are all third party projects on their own release cycles that this file does not track.

Editorial conclusion

Use this list as a map of the territory and nothing more. It is a fast way to find the seven UI toolkits, the on-device inference projects and the version diff tooling without searching for each name, and the file was last pushed on 2026-08-26. It cannot tell you which entry still builds against the current architecture, when a link went stale, or how two entries compare, so before adopting anything from it, check the project's own repository for New Architecture support and a recent commit, and pin the version you test against.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository