How ka4733231-cloud/food works
NutriBite is a food and nutrition platform spanning a web frontend, Expo mobile app, and FastAPI service. Its main user journey is scanning food, estimating nutrition, and logging meals; recipe discovery, planning, grocery management, assistant chat, and subscriptions are additional capabilities. The backend persists domain data in a relational database and can consult USDA FoodData Central. Some web and backend route implementations were not excerpted, so uncertain links are omitted or marked unverified.
Main entry points: main.py FastAPI endpoints · useNutriBiteStore.ts Mobile app state · client.ts REST API client · app.js Web application
Components 21
User Applications
- Mobile navigation
apps/mobile/app/(tabs)/_layout.tsx - Food scanning
apps/mobile/app/(tabs)/scan.tsx - Recipe discovery
apps/mobile/app/(tabs)/recipes.tsx - Recipe details
apps/mobile/app/recipe/[id].tsx - Meal planner
apps/mobile/app/(tabs)/planner.tsx - Nutrition dashboard
apps/mobile/app/(tabs)/index.tsx - Profile and plans
apps/mobile/app/pricing.tsx - Mobile app state
apps/mobile/src/store/useNutriBiteStore.ts - REST API client
apps/mobile/src/api/client.ts - Web application
frontend/js/app.js - Web pages and routes
frontend/js/router.js - Web state
frontend/js/state.js
API and Intelligence
- FastAPI endpoints
backend/app/main.py - Food recognition
backend/app/services/vision_service.py
Food and Planning
- Nutrition analysis
backend/app/services/nutrition_service.py - Nutrition assistant
backend/app/services/assistant_service.py - Recipe and meal data
backend/app/seed_data.py
Persistence
- Domain models
backend/app/models.py - Relational database
backend/app/database.py
Other components
- Food app user
- USDA FoodData Central
Connections 22
- Food app user → Mobile navigation: uses
README.md - Food app user → Web application: uses
README.md - Food scanning → REST API client: submits scans
apps/mobile/app/(tabs)/scan.tsx - REST API client → FastAPI endpoints: calls scan API
apps/mobile/src/api/client.ts - FastAPI endpoints → Food recognition: runs recognition
backend/app/main.py - FastAPI endpoints → Nutrition analysis: gets nutrition
backend/app/main.py - FastAPI endpoints → Nutrition assistant: processes chat
backend/app/main.py - FastAPI endpoints → Domain models: queries domain
backend/app/main.py - FastAPI endpoints → Relational database: opens sessions
backend/app/main.py - Nutrition analysis → Domain models: queries foods
backend/app/services/nutrition_service.py - Nutrition analysis → USDA FoodData Central: searches foods
backend/app/services/nutrition_service.py - Recipe and meal data → Relational database: seeds records
backend/app/seed_data.py - Recipe discovery → Mobile app state: reads state
apps/mobile/app/(tabs)/recipes.tsx - Recipe details → Mobile app state: reads state
apps/mobile/app/recipe/[id].tsx - Meal planner → Mobile app state: updates plan
apps/mobile/app/(tabs)/planner.tsx - Nutrition dashboard → Mobile app state: reads diary
apps/mobile/app/(tabs)/index.tsx - Profile and plans → Mobile app state: reads subscription
apps/mobile/app/pricing.tsx - REST API client → FastAPI endpoints: requests nutrition
- REST API client → FastAPI endpoints: sends assistant chat
apps/mobile/src/api/client.ts - Web application → Web pages and routes: routes pages
- Web application → Web state: uses state
- FastAPI endpoints → Recipe and meal data: uses seeded assets
backend/app/main.py