Add a Screen to Expo Router by Creating One File
Skip manual navigator registration: in Expo’s managed workflow, a new file under app/ becomes a route—here is how to add it, wire it into a tab layout, and verify it.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Skip manual navigator registration: in Expo’s managed workflow, a new file under app/ becomes a route—here is how to add it, wire it into a tab layout, and verify it.
Waku defaults to React Server Components for every route, turning only the smallest interactive widgets into client code. This post explains why, how file‑based routing shapes that boundary, walks through a filterable list example, and discusses trade‑offs you’ll need to manage.
Expo Router turns files under app/ into routes and URLs, removing duplicate deep-link configuration. See how layouts and dynamic segments work across iOS, Android, and web.
Nuxt's file-based routing turns a directory of Vue components into a working blog without manual route config. Pair it with @nuxt/content for Markdown-driven posts and static generation for fast, SEO-friendly pages.
Expo Router replaces hand-wired React Navigation stacks with file-based routing. Here's a concrete three-screen migration, what typed routes catch, and where the convention fights back.
Expo Router replaces centralized navigation configs with a file-based system under app/. Learn how layouts, dynamic segments and deep linking map to the file system and what breaks when you move files.
Optional catch‑all routes in Expo Router Expo Router implements file‑based routing where a file named [[...slug]].tsx creates an optional catch‑all segment that can match zero or more path parts. Static route files such as settings.tsx coexist in the same app/ directory, but the documentation does not explicitly state which pattern wins when both could match