expo-app-conventions

The best way to structure an Expo app is to use a canonical folder layout that enforces Expo Router for routing, Zustand for state management, and NativeWind for styling to ensure architectural consistency.

To organize files in an Expo project, follow a standardized convention that places routing, components, state management, API clients, and utilities into specific predefined directories to maintain consistency.

Yes, the standard Expo app convention explicitly enforces NativeWind for styling, alongside Expo Router for navigation and Zustand for state management, to provide a definitive, opinionated stack.

You need an opinionated stack for your Expo application to solve the problem of maintaining consistency and structure across projects and developers, ensuring files are placed correctly and architectural standards are met.

Yes, you can use this Expo app structure for both starting a new project and adding new features, consulting the defined conventions to ensure files are placed in the correct directories and adhere to the established stack.

The limitation of using this predefined Expo folder structure is its strictly opinionated nature, requiring the use of Expo Router, Zustand, and NativeWind, which may not suit projects already using alternative routing or state management libraries.