expo-project-structure

Topics in the source

• Expo Project Structure
• src/ and src/app
• components/ — reusable UI
• screens/ — screen bodies
• server/ + app/api/ — separate server code
• Platform-specific code
• Colocate styles and tests
• AI and config files

A starting skeleton for a new Expo app — one with no committed folder structure yet. Apply only to new projects. If the app already has a layout, follow its existing conventions and leave files where they are — a default to start from, never a standard to enforce or migrate toward. When unsure whether a project is new, ask before moving anything. The whole layout, assembled from the rules below: Keep app code under src/ to separate it from config files. Expo Router supports both app/ and src/app/ out of the box — to switch, move the folder and restart the bundler. The default template aliases @/ to ./src/ in tsconfig.json. src/app is routes-only: every file there becomes a route, so nothing else belongs in it. Everything below lives in sibling folders. Generic, reused UI (button, card, table) with one named export each. Name files in kebab-case (bar-chart.tsx), matching the default create-expo-app template. When a component grows, give it its own folder with the root in index.tsx and colocate its private sub-components beside it — the import path (@/components/table) stays unchanged. Because app/ files must be routes, complex screen UI that isn't reused has no home there. Once a sc

This is an excerpt. Refer to the complete source and its current requirements.