How gercamjr/auto-organize-me works
Project type and purpose
• This is a single‐repository, full-featured Expo/React Native mobile application (“Auto Organize Me”) for car mechanics.
• It’s an offline-first client app that manages clients, vehicles, jobs, appointments, photos, and invoicing on a local SQLite database.
File structure
• Top‐level: App.tsx (entry), index.ts, Expo configs (app.json, metro.config.js, babel.config.js).
• assets/: static images and fonts.
• src/contexts/: React Context providers (AuthContext, DatabaseContext).
• src/hooks/: repository hooks (useClientRepository, useJobRepository, useVehicleRepository) implementing the repository pattern.
• src/navigation/: React Navigation definitions organized by feature (Auth, Clients, Vehicles, Jobs, Main, Root).
• src/screens/: Feature folders (auth, client, job, vehicle), each containing all related UI screens.
• src/utils/: Theming and shared utilities (theme.ts).
• Config files: ESLint, Prettier, tsconfig, CI/CD workflow in .github/workflows.
README for additional insights
• Tech stack: TypeScript, React Native Paper (UI), React Navigation, Expo-SQLite, Context API.
• Architecture hints: “repository pattern for database operations,” “offline first.”
• CI/CD: GitHub Actions → linting → EAS Build → release.
Final recommendations
• Every architectural element—from the Expo entry point through to the SQL tables.
• Keep it detailed: the goal is a one-page view that a new engineer can use to orient themselves immediately.