How orelchalfon/tutiai works
Project type and purpose
• This is a cross-platform mobile (and web) application scaffolded with Expo’s “create-expo-app.”
• It uses React Native + Expo SDK for UI and device APIs, and employs file-based routing under the app/ directory.
File structure
• Top-level directories/files:
• app/ – the routing and screen definitions (with a (tabs) subfolder for tab-based navigation).
• assets/images/ – static image assets.
• constants/ – theme definitions.
• scripts/ – utility scripts (e.g., reset-project).
• Config/build files: app.json, tsconfig.json, eslint.config.js, package.json, **pnpm-*.yaml**.
• No backend code; this is strictly the client side.
README for additional insights
• Confirms Expo CLI is used for local development (Metro Bundler → bundling JS/TSX → serving to devices).
• File-based routing (React Navigation under the hood).
• Offers emulator/simulator/Expo Go as targets.
Main components and their interactions
a. Developer Toolchain
• Terminal & IDE (VS Code) → runs npx expo start
• Expo CLI & Metro Bundler
b. Runtime Hosts
• Android emulator / iOS simulator / Expo Go / Web browser
c. The React Native App
• Navigation Layer (file-based routes in app/)
• Screen Components (TSX files under app/)
• UI Component Library (components/)
• Theming & Styling (constants/ + hooks/)
• Asset Store (assets/images/)
d. External/Native Modules
• Expo SDK modules (camera, file-system, sensors, etc., if used)
• Third-party libraries from node_modules
Architectural patterns and design principles
• Modular separation: screens vs. generic components vs. utilities/hooks.
• File-based routing implements a declarative navigation graph.
• Theme & hook abstraction centralizes styling decisions.
• Static assets are co-located under assets/ for bundling.