react-native-bottom-tabs
AGENTS.md1.5k starsChanged 6 months agoMITView on GitHub
This is a React Native library for Bottom Tabs using native platform primitives (SwiftUI's TabView on iOS and BottomNavigationView on Android). It can be used as a standalone library or as a drop-in replacement for the bottom tabs in React Navigation / Expo Router. It is designed to be a drop-in replacement for JavaScript-based bottom tabs. Use agent-device only for app/device automation tasks. Before planning commands, run agent-device --version and read agent-device help workflow. For exploratory QA, read agent-device help…
1 other project uses a version of this.
Trending
Quiet since July.thin dataabout the whole repository
Most recently taken up by
- callstackincubator/react-native-bottom-tabsword for word, first seen Oct 9, 2026
Who's talking about callstack/react-native-bottom-tabs
- Cap-go/capacitor-native-navigation“Improve native tabbar parity”GitHub · Jun 11, 2026 · 1 reactions
- EuroPython/europython-companion“Bump @bottom-tabs/react-navigation from 1.3.1 to 1.4.0”GitHub · Jul 9, 2026
- neuland-ingolstadt/neuland.app-native“build(deps): bump @bottom-tabs/react-navigation from 0.11.2 to 1.3.1”GitHub · Jun 22, 2026
- react-navigation/react-navigation“color pkg duplicates”GitHub · Mar 31, 2026
- Yimura/RemoteUnlockApp“chore(deps): bump react-native-bottom-tabs from 0.9.0 to 1.1.0”GitHub · Jan 9, 2026
The biggest 5 of 6 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 6
Talked about on GitHub (6 times).
On GitHub · 6
- Jun 11, 2026Improve native tabbar parity — Cap-go/capacitor-native-navigation1 reaction · 3 comments
- Jul 9, 2026Bump @bottom-tabs/react-navigation from 1.3.1 to 1.4.0 — EuroPython/europython-companion0 reactions · 1 comment
- Jun 22, 2026build(deps): bump @bottom-tabs/react-navigation from 0.11.2 to 1.3.1 — neuland-ingolstadt/neuland.app-native0 reactions · 5 comments
- Mar 31, 2026color pkg duplicates — react-navigation/react-navigation0 reactions · 4 comments
- Jan 9, 2026chore(deps): bump react-native-bottom-tabs from 0.9.0 to 1.1.0 — Yimura/RemoteUnlockApp0 reactions · 1 comment
1 more on GitHub
- Dec 15, 2025chore(deps): bump react-native-bottom-tabs from 0.10.0 to 1.1.0 — mneves75/dnschat0 reactions · 1 comment
Other versions1 project uses a version of this.
Word for word · 1
- callstackincubator/react-native-bottom-tabs★ 1.5k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- agent-deviceSkill
The file
Files
React Native Bottom Tabs
This is a React Native library for Bottom Tabs using native platform primitives (SwiftUI's TabView on iOS and BottomNavigationView on Android).
It can be used as a standalone library or as a drop-in replacement for the bottom tabs in React Navigation / Expo Router.
It is designed to be a drop-in replacement for JavaScript-based bottom tabs.
agent-device usage
Use agent-device only for app/device automation tasks. Before planning commands, run agent-device --version and read agent-device help workflow. For exploratory QA, read agent-device help dogfood. For logs, network, traces, or runtime failures, read agent-device help debugging. For React Native component trees, props/state/hooks, slow renders, or rerenders, read agent-device help react-devtools. For React Native apps, overlays, Metro/Fast Refresh blockers, and routing to React DevTools or debugging evidence, read agent-device help react-native.
Use the CLI in the integrated terminal. If agent-device is not on PATH but the user installed it globally in another shell, resolve the command the same way the user would from a normal terminal session and run that absolute path instead. This may require inspecting shell startup behavior or package-manager/global bin locations; do not assume the agent process PATH is the user's PATH. Do not silently fall back to npx -y agent-device@latest; ask or use an exact version. MCP is only a discovery/help router and does not expose device automation tools. Prefer open -> snapshot -i -> act -> re-snapshot -> verify -> close. Use current refs such as @e3 for exploration and selectors for durable replay. Keep mutating commands against one session serial. Capture screenshots, logs, network, perf, traces, recordings, and .ad replay scripts only when they add evidence.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.