jutsu-expo:expo-router

File-based routing in Expo apps uses the app directory structure to automatically define routes. Create an app folder with _layout.tsx as the root layout and index.tsx as your home screen. Expo Router maps files and folders to routes, eliminating manual route configuration and reducing navigation boilerplate.

Yes. Expo Router supports dynamic segments using bracket notation—files like users/[id].tsx create routes that accept parameters. Deep linking integrates automatically, allowing you to link directly to specific screens with URL parameters passed as route props.

Nested layouts are created by placing _layout.tsx files in subdirectories. Tab groups use directory names wrapped in parentheses, like (tabs)/_layout.tsx, which define tab structure without affecting the URL path. This keeps your app directory clean while maintaining complex UI hierarchies.

File-based routing automatically generates routes from your file structure, eliminating hardcoded route definitions. Manual navigation requires explicit route registration and navigation logic. Expo Router's file-based approach scales navigation configuration with your app's growth and reduces error-prone boilerplate.

Expo Router supports both TypeScript and JavaScript. TypeScript enables type-safe routing with automatic intellisense for route names and parameters, but it's optional. You can start with JavaScript and migrate to TypeScript later as your app grows.

Yes. Expo Router supports unlimited nesting of layouts and groups. Root layouts wrap your entire app, nested layouts apply to subdirectories, and grouped directories organize segments without affecting routes. This flexibility enables intricate UI structures from simple directory hierarchies.