Overview
A native iOS app for fast, accurate nutrition tracking: scan barcodes, search APIs, or pick favorites; set daily goals; and export progress as PDF. The UI is deliberately simple and consistent to minimize friction.
Problem
Most food trackers feel slow and cognitively heavy. We wanted a flow that works anywhere (portrait/landscape, iPhone/iPad), respects local units, and keeps users in a quick “add → confirm → done” loop.
Solution
Streamlined onboarding (locale-aware units + BMI) and a responsive dashboard for calorie/macro progress. Users log items via barcode scan, favorites, or API search; categorize by meal; set date/time from a calendar/time picker; and generate shareable PDF summaries.
Features
Onboarding & profile
- Video-background login; works in portrait & landscape across iPhone/iPad
- Locale-aware inputs: ft/in ↔︎ cm; lb ↔︎ kg; BMI computation (underweight/healthy/overweight)
- Profile + goals: name, gender, height, weight; daily calories, carbs, protein, fat
Tracking & history
- Dashboard with daily goal and live progress ring
- Add foods by barcode scan, favorites, or Nutritionix API search
- Meal categories (breakfast/lunch/dinner/snack) + date/time picker (interactive calendar)
- History feed for today/yesterday and full timeline
- One-tap PDF report generation
Favorites & editing
- Create/edit foods (name, serving size/unit, calories, total fat, saturated fat, cholesterol, sodium, carbohydrates, protein)
- Custom thumbnails via camera or photo library (with permission prompts)
- Delete items; changes reflected immediately in search/logging
Search & media
- Local database search across favorites (results as tappable cards with nutrition)
- Nutritionix API search for broader items (e.g., Apple Pie → nutrition + add to log or favorites)
- Fitness videos: recommendations + YouTube search; playable with title/date/time thumbnails
Data & Models
External nutrition via Nutritionix; device camera for barcodes and thumbnails; YouTube for video metadata. Local, typed models keep logs/favorites snappy and resilient offline/online.
Architecture
Modules: profile/goals, foods/favorites, logging/history, media, and reporting. Actions normalize API/barcode inputs, compute dashboard totals, and emit PDF summaries. Permissions handled at capture time.
HCI / UX Notes
Low cognitive load via consistent components, clear affordances, large touch targets, and predictable focus states. Primary actions are one-tap; forms respect locale defaults and remember last inputs where helpful.
Role, Status & Next Steps
- My role: Backend lead; approved final UI/UX; ensured smooth, intuitive HCI throughout
- Status: Prototype complete; polishing and expanding data sources
- Next: Weekly/monthly trend insights; offline-first caching; optional cloud sync