expo-router-expert

File-based routing in Expo Router automatically maps your app directory structure to routes. Create files in your app folder—folders become route segments, and files become pages. Expo Router generates the navigation stack from this structure, eliminating manual route configuration and reducing navigation boilerplate across mobile and web platforms.

Dynamic routes in Expo Router use bracket syntax: name a file [slug] to capture URL parameters. Access parameters via useLocalSearchParams() hook, and define TypeScript types for strong type safety. This pattern handles blog posts, product pages, and other parameter-driven content across web and mobile.

Layouts in Expo Router wrap child routes and persist UI across navigation. Create a _layout.tsx file to define shared headers, tab bars, or drawers. Child routes automatically nest under the layout, enabling complex multi-level navigation hierarchies without repeating wrapper code.

Deep linking in Expo Router maps URLs to routes automatically based on your file structure. Configure linking in app.json to handle custom schemes and domains, then use the file path to determine which route opens. Deep links work across mobile and web, routing users directly to specific pages from external sources.

Expo Router provides built-in TypeScript support with strong typing for routes and URL parameters. Define parameter types using hooks like useLocalSearchParams and useSearchParams, enabling autocomplete and compile-time safety. This prevents runtime navigation errors and improves developer experience across large apps.

File-based routing requires strict directory conventions and may feel restrictive for highly dynamic or programmatic routing needs. Route guards and conditional routes require additional middleware patterns. Complex nested routes can become deeply nested directories, and some advanced navigation patterns need custom hook composition.