# Build brief — a focused alternative to MealWise > **Verdict:** Yes, for personal use · **Buildability:** 90/100 · **Category:** Home > **Source:** https://www.canitbevibecoded.com/mealwise > Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from MealWise. Verify current pricing and capabilities before acting. ## Context **MealWise** — Turn one natural-language meal request into a practical, budget-aware recipe. It currently costs $7.99/mo. A useful personal version is absolutely one-shottable: a small local app can turn a typed meal request, ingredients, budget, servings and time into a structured recipe. What does not arrive in one session is MealWise's native iPhone finish, voice input, authenticated quota enforcement, optional cross-device sync, and the ongoing work of keeping AI output reliable and safe to use. This brief describes a focused, single-operator replacement for the part of MealWise that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest. ## What you are building Turn one natural-language meal request into a structured recipe with ingredients, portions, estimated costs and cooking steps, then save it locally. - Plan meals, run shared household lists, and keep family routines in one place. - A responsive interface with real empty, loading, success, and error states. ## Requirements ### Functional - A modern browser. ### Data and integrations - An OpenAI-compatible API key. Each of these needs a real account, credential, or quota. Set them up before writing feature code. ### Non-functional - Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support. - Security: server-side secrets, validated input, and no credentials in the client bundle. - Reliability: retries with backoff on external calls, and a clear failure state when a provider is down. - Portability: the operator can export their data and leave without losing it. ## Implementation brief Build a personal MealWise-like recipe generator in an empty repository. Use Next.js 15, TypeScript, Tailwind CSS, IndexedDB, and the OpenAI Responses API; do not offer alternative stacks. Make the first run work with npm install and npm run dev. Add an .env.example containing only OPENAI_API_KEY. Create one mobile-first page with a natural-language meal request box. Let the request include ingredients on hand, budget, servings, dietary preferences, exclusions, time and equipment. Send it to the model with a strict JSON schema. Render one complete recipe with title, servings, ingredients, estimated ingredient costs, total cost, cost per person, steps and a practical tip. Clearly label all costs, allergen handling and nutrition-related content as estimates to verify. Save accepted recipes locally in IndexedDB. Include a searchable saved-recipe library and deletion controls. Provide loading, empty, offline, malformed-model-response and retry states. Validate input and safely render all model output as text. Keep the API key server-side and never log meal requests or recipes. Write focused tests for schema parsing and per-person cost calculation. Create a README with setup, data location, privacy behavior and limitations. Do not add accounts, billing, analytics, cloud sync, voice input, push notifications or background jobs. Do not claim live grocery prices, dietary safety, allergy safety, nutritional accuracy or food-safety guarantees. Finish by running the tests and listing the exact commands used. ## Delivery standard - Inspect the repository first, then write a short implementation plan before writing code. - Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data. - Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations. - Include responsive layouts plus genuine empty, loading, success, validation, and failure states. - Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data. - Add structured logs around every external call and return actionable errors without leaking sensitive details. - Write unit tests for the core logic and one automated test of the main user journey. - Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations. ## Acceptance criteria - [ ] A clean install starts the app using only the README and .env.example. - [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable. - [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state. - [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control. - [ ] Tests, type checking, linting, and a production build all pass with no ignored failures. - [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified. ## Non-goals Do not build these, and do not claim to have replaced them: - Native iPhone interaction and voice dictation. - Server-side authentication, quota enforcement and abuse protection. - Optional cross-device sync. - Recipe refinement and regeneration polish. - Ongoing AI-quality, food-safety and operational maintenance. ## What you still own after launch - Secure credentials, rotate secrets, and handle provider rate limits. - Run migrations, backups, restores, and dependency updates. - Test the critical journey after every model, API, or hosting change. - Monitor failures and fix the edge cases a first prompt will miss. ## Risk **Manageable.** A personal version is realistic if you test the critical journey and keep reliable backups. Editorial confidence in this assessment: high. No reviewed project implementation is linked yet. ## Existing alternatives Before building, compare these checked options: - [RecipeSage](https://recipesage.com/) — A free recipe keeper with planning, shopping lists and an AI cooking assistant; less focused on one-shot budget recipes - [Mealie](https://mealie.io/) — A self-hosted household recipe server with imports and meal planning; you bring both the recipes and the server --- Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/mealwise