Inspiration

NutriMind AI was inspired by a problem our team sees in everyday life: people want to eat better, but food decisions usually happen quickly and without enough context. A packaged snack label can be confusing. A cooked meal may not have any nutrition label at all. At the same time, each person’s needs are different based on their goals, allergies, lifestyle, and health conditions.

We wanted to build a consumer health app that helps people make better food decisions at the moment they need them. Our goal was to combine personal health context, food scanning, journaling, and AI-assisted coaching into one practical mobile experience.

What It Does

NutriMind AI is an Android nutrition tracker and food decision assistant.

Users can:

  • Create a local profile with age, height, weight, gender, lifestyle, goals, allergies, medical conditions, and food habits.
  • Scan packaged food labels using the camera.
  • Upload existing food label images or PDFs from the phone.
  • Describe cooked meals when labels are not available.
  • Get a personalized food suitability verdict using a color-coded scale: Bad, Poor, Fair, Good, Excellent.
  • Understand ingredient risks such as sugar, sodium, processed fats, allergens, and goal-specific concerns.
  • Log meals and physical activities in natural language.
  • Export weekly food tracking data into local files organized by year, month, and week.
  • Send structured context to the user’s own ChatGPT app or web session for deeper coaching, while keeping the app from collecting ChatGPT credentials or conversation history.

How We Built It

We built NutriMind AI as a native Android application using Java and Android Studio. The UI is implemented programmatically, which helped us move quickly during the hackathon and iterate on flows, navigation, OCR, journaling, and visual design.

The app uses:

  • Native Android Java for the mobile application.
  • Android camera intents for packaged food and cooked meal capture.
  • Android file picker for uploading existing images or PDFs.
  • ML Kit Text Recognition for on-device OCR on food labels.
  • SharedPreferences for local login, session, and profile persistence.
  • Local file export for weekly nutrition tracking.
  • Android share intents to hand off structured nutrition prompts to ChatGPT.

The food scan flow accepts input from OCR, upload, or typed text, then evaluates it against the user profile. The app keeps the numeric scoring logic internal, but shows users a simpler color-coded suitability scale so the result is easier to understand.

How We Used Codex and GPT-5.6

Codex was central to our workflow throughout the project. We used it as a coding partner across product planning, architecture, Android implementation, UI/UX iteration, debugging, and build verification.

Codex helped us:

  • Turn the initial business requirements into a high-level and low-level design.
  • Choose a practical Android architecture for a hackathon build.
  • Implement local onboarding, profile setup, and session handling.
  • Add navigation behavior so the Android back button works correctly.
  • Build and refine the side drawer navigation.
  • Add camera capture, image upload, PDF upload, and OCR support.
  • Improve OCR so unclear or non-food images are not incorrectly treated as food.
  • Add weekly export functionality for food logs.
  • Improve the app theme, colors, typography, and food verdict UI.
  • Build, install, and test the app on the Android emulator.

GPT-5.6-style reasoning was especially useful for translating broad product ideas into concrete user flows and implementation details. As a team, we made product decisions around privacy, mobile usability, and health safety, while Codex accelerated the engineering work and helped us keep iterating quickly.

Challenges We Faced

One major challenge was making food scanning feel trustworthy. Early versions treated almost any captured image as if it contained food information. That was not acceptable for a health-related app. We improved this by adding OCR validation, so the app now checks whether the extracted text actually looks like a food label before producing a verdict.

Another challenge was balancing personalization with privacy. We wanted users to benefit from ChatGPT without asking them to log into ChatGPT inside NutriMind AI. The final approach uses a handoff model: NutriMind creates a structured nutrition prompt and sends it to the user’s own ChatGPT app or web session. This keeps ChatGPT login and memory inside ChatGPT, not inside our app.

UI/UX was also a challenge. The app went through several navigation and design iterations: basic top tabs, then a fixed rail, then a collapsible drawer, then icon-based navigation, and finally a more polished health-dashboard theme. This taught us how much mobile usability depends on small details like keyboard behavior, back navigation, readable cards, and clear visual hierarchy.

What We Learned

We learned how to scope a health-focused consumer app for a hackathon while still making it useful, responsible, and demo-ready. The biggest lesson was that nutrition guidance is not only about generating advice. It also needs personal context, uncertainty handling, safe fallbacks, and clear user communication.

We also learned more about Android camera workflows, OCR integration, local persistence, emulator testing, and designing an app that combines local functionality with AI handoff rather than sending everything to a backend.

What’s Next

Next, we would like to connect real product databases and quick-commerce APIs so healthy alternatives can include live pricing, availability, and delivery ranking. We also want to improve cooked meal recognition using multimodal AI, add richer nutrition estimates, and create a clinician-friendly weekly report view for users managing chronic conditions or recovery diets.

Built With

Share this project:

Updates