Frozen demo: a saved copy of the router page after three messages. The Send box is disabled here. Run it live with node --env-file=.env server.mjs from the repo. Development journey.

Jev model router

hi there, how are you
nanoopenai/gpt-5-nanoconfidence 1Jev 705 msreply 2961 ms
balanced
0%fast
0%nano
100%frontier
0%
Hi there! I'm here and ready to help. How can I assist you today?
tell me the best way to build an app to track my diet using AI
balancedanthropic/claude-sonnet-5confidence 0.94Jev 541 msreply 12532 ms
frontier
0%nano
0%balanced
95%fast
5%
# Building an AI Diet Tracking App Here's a practical approach broken into decisions you'll need to make: ## 1. Define Core Features First - **Food logging method**: Photo recognition, text/voice input, or barcode scanning? - **Tracking scope**: Calories only, or full macros/micros? - **AI's role**: Just food identification, or also meal suggestions/coaching? ## 2. Tech Stack Options **Fastest path (recommended for MVP):** - **Frontend**: React Native or Flutter (cross-platform mobile) - **Backend**: Node.js/Python (FastAPI) + PostgreSQL - **AI/Food Recognition**: - Use existing APIs instead of training your own model: **Google Vision API**, **LogMeal**, or **Foodvisor API** - For nutrition data: **USDA FoodData Central** (free) or **Nutritionix API** **Build from scratch (more control, more work):** - Fine-tune a vision model (like CLIP or a custom CNN) on food datasets (Food-101, Nutrition5k) - Requires more ML expertise and data pipeline work ## 3. Recommended Architecture for MVP ``` User takes photo → Image sent to Vision API (food identification) → Match against nutrition database → User confirms/adjusts portion → Log saved with macros/calories → Display in dashboard/history ``` ## 4. AI Features Worth Adding (in priority order) 1. **Photo-to-food recognition** (highest value, use existing API) 2. **Natural language logging** ("I had a chicken salad") using GPT-4o/Claude API to parse into structured nutrition data 3. **Portion size estimation** from photos (harder, less accurate—consider skipping initially) 4. **Personalized insights** ("You're consistently low on protein") using simple rule-based logic before jumping to ML 5. **Conversational coaching** via LLM API for suggestions ## 5. Practical Build Order 1. Start with **manual + voice/text logging** using an LLM to parse free text into structured data (this alone is huge UX improvement over typical apps) 2. Add **barcode scanning** (Open Food Facts API is free) 3. Add **photo recognition** last—it's the most complex and least accurate feature 4. Layer in analytics/insights once you have data flowing ## 6. Cost-Conscious Tips - Don't train your own food recognition model initially—existing APIs are good enough and save months - Cache nutrition lookups to reduce API calls - Use GPT-4o-mini or Claude Haiku for text parsing (cheap, fast, accurate enough) --- **Quick question to narrow this down further:** Are you building this for personal use/learning, or planning to ship it to other users? That changes how much I'd emphasize scalability, auth, and data privacy from the start.
Please build this tracker app for me.
balancedanthropic/claude-sonnet-5confidence 0.73Jev 436 msreply 8197 ms
fast
1%balanced
80%frontier
19%nano
0%
# Tracker App I'd be happy to help you build a tracker app! However, I need more details to create exactly what you need. Trackers can vary widely, so let me ask some clarifying questions: ## What are you tracking? - [ ] Habits/daily goals - [ ] Expenses/budget - [ ] Fitness/workouts - [ ] Tasks/to-dos - [ ] Time (time tracking for work/projects) - [ ] Mood/health symptoms - [ ] Something else (please describe) ## Platform - Web app (browser-based) - Mobile app (iOS/Android) - Desktop app - Simple script/CLI tool ## Key Features (examples) - Add/edit/delete entries - Categories or tags - Daily/weekly/monthly views - Charts or statistics - Reminders/notifications - Data export (CSV, etc.) - Multi-user support / login - Offline support ## Tech Preferences - Any specific language/framework? (e.g., React, Python, plain HTML/JS) - Should data be saved locally (browser storage/file) or in a database? - Any design style you like (minimal, colorful, dark mode, etc.)? --- ### If you want to get started quickly: Tell me just **one sentence** like: > "A habit tracker web app where I can check off daily habits and see my streak, using HTML/CSS/JS with local storage." ...and I'll build the whole thing right away with sensible defaults. The most default choice would be: **A simple, clean web-based Habit Tracker** — add habits, check them off each day, see streaks, stores data in browser local storage, no login required, works instantly in browser. Want me to just build that default version now? Or tell me your specific idea and I'll build that instead!