react-native-ai vs extro
Two of the top mobile and browser extensions, side by side: score, setup, license, activity and what each review found.
react-native-ai
Expo chat and image app with an Express proxy for multiple LLMs
extro
WXT and React browser extension starter with Supabase auth and AI
| What we compare | react-native-ai | extro |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 68, popular | 11, niche |
| Freshness | 100, active | 100, active |
| Maintenance | 11, weak | 10, weak |
| Easy to run | 33, some setup | 33, some setup |
| Agent-ready | 0, none | 0, none |
| Facts from GitHub and the README | ||
| Stars | 1.3k | 413 |
| License | MIT (permissive) | MIT (permissive) |
| Last commit | Jul 2026 | Aug 2026 |
| Last release | None published | None published |
| Language | TypeScript | TypeScript |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
react-native-ai
Scaffolded with npx rn-ai: an Expo React Native app with streaming chat and image screens plus an Express server that proxies to OpenAI, Anthropic, Gemini, Z.ai GLM 5.2 and Moonshot Kimi K2.7, with Gemini image generation. Keys stay in server/.env; five themes ship and models are added by editing constants.ts and a server route. For teams starting a mobile AI assistant with keys off the device.
Who it is for: Mobile teams starting a multi-provider AI chat app
Strengths
- Server proxy keeps API keys off the device and leaves room for auth
- Streaming responses from all five LLM providers
- Gemini image generation wired on the server
- Five themes with a documented pattern for adding more
Weaknesses
- Adding a model touches the app screen, constants, utils and a server route
- No auth implemented; the proxy is where you add it
- No persistence of chats described
- Last commit 2026-07
- TypeScript, OpenAI, Anthropic, Google Gemini, Z.ai
- Needs OpenAI, Anthropic, Gemini, Z.ai or Moonshot API keys, GEMINI_API_KEY for images
- GitHub template
extro
Bun-based WXT project for Chrome (MV3) and Firefox (MV2) with every entrypoint (popup, side panel, devtools, new tab, options, content) preconfigured, Supabase OAuth shared across pages, storage, messaging, i18n, OpenPanel analytics, shadcn/ui, Biome, unit tests and a publish workflow. Native AI integration is marked experimental. For teams shipping a React extension with accounts; billing is marked coming soon.
Who it is for: Teams building a React browser extension with accounts and AI
Strengths
- All extension entrypoints wired, including side panel and devtools
- Auth session and storage shared between popup, content and options pages
- CI publishing to Chrome Web Store and Firefox Add-ons
- Plasmo variant maintained on a separate branch
Weaknesses
- AI integration is marked experimental and thinly documented in the README
- Billing is listed as coming soon
- Firefox builds target MV2 and load only in temporary mode
- Requires Bun
- TypeScript, Vercel AI SDK, browser built-in AI (experimental)
- Needs Supabase project, OpenPanel (analytics, optional)
- GitHub template
- env example file