Skip to main content
The mobile application uses file-based routing from apps/mobile/app. This root is configured by the expo-router plugin in apps/mobile/app.json.

​
Route groups

The current route tree uses groups to separate navigation concerns: Parentheses organize layouts without becoming URL segments. Each group can define _layout.tsx; the root apps/mobile/app/_layout.tsx composes providers and top-level navigation.

​
Add a route

Create the file under the appropriate active group. For example:
Keep the route focused. Import reusable domain behavior or a package-owned screen rather than placing provider integration and shared business rules in the route. Use Expo Router APIs for navigation:
Confirm the path against the generated route types and existing calls. Route groups can appear in explicit hrefs even though they do not appear in the final URL.
Do not add active routes to apps/mobile/src/app. The current screen generator writes there, but Expo Router does not scan that directory in this project.
  • Put the route under apps/mobile/app.
  • Add or update the nearest _layout.tsx when presentation or access rules change.
  • Preserve authentication, onboarding, app-lock, and modal boundaries.
  • Keep visible labels in @amisi-mobile-starter/i18n.
  • Track user navigation actions through typed analytics where appropriate.
  • Test deep links and back behavior on both platforms.
  • Run bun run verify.