mobile-file-organization

Place file-based routes in the app/ directory using route groups like (auth) and (app), and keep business logic in src/features/ with types.ts, queries.ts, and actions.ts per feature. Shared UI goes in src/components/ only when used by two or more route groups.

Files use kebab-case such as depth-button.tsx, components use PascalCase like DepthButton, and hooks follow the use-*.ts pattern such as use-auth.ts. Constants use UPPER_SNAKE and functions use camelCase.

Route groups like (tabs)/ organize screens without appearing in the URL, dynamic routes use [id].tsx syntax, and layout files named _layout.tsx render Stack or Tabs navigators. Hidden routes are configured with options href set to null in the layout.

Move a component to src/components/ when it is used in at least two different route groups, has no feature-specific dependencies, and works with theme tokens alone. Keep it in the feature folder if it is coupled to feature data types or business logic.

Use named exports only, with the sole exception of route components which require default exports for Expo Router. Barrel files are acceptable in src/components/index.ts but not inside feature folders.