Health, home and travel decision
Menu Vista
A technically capable developer can build a useful menu-translation + nutrition prototype using existing OCR, translation libraries/APIs and public nutrition data, but matching MenuVista's claimed cuisine-specific accuracy, curated photos, and edge-case handwritten/PDF coverage would require proprietary data and product polish that are hard to reproduce.
Visit website↗Built by Romain, who ships 3 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off31 h to build
$75/mo6 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- 1) Extract text from a photo/PDF (OCR). 2) Parse extracted text into menu structure (sections, dish names, descriptions, prices). 3) Translate dish names/descriptions via translation API and local heuristics. 4) Infer ingredients/allergens and map dishes to nutrition entries (lookup or model). 5) Present results in a mobile/web UI with saved menus and 'show waiter' view.
What it still won’t have
- Proprietary, food-specialized translation/nutrition models and curated dish-photo database
- App polish, mobile-native camera UX and offline mobile support
- Large labelled dataset for cuisine-specific ingredient->nutrition mapping and rare language/handwriting corner cases
- Ongoing QA and edge-case coverage across many cuisines and handwritten menus
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Menu Vista does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a menu-translation web service and minimal mobile-friendly frontend using Next.js (React) + Node/Express backend, PostgreSQL, and deploy to Vercel (frontend) + a small VPS or Heroku for backend. Core features in scope: 1) upload/capture photo or PDF and run OCR (Tesseract or Google Vision) with bounding boxes; 2) parse OCR output into menu sections and dishes; 3) translate dish names/descriptions via LibreTranslate or a paid translation API with food-aware postprocessing; 4) extract ingredients and flag common allergens using rule-based NER + small local lookup; 5) map dishes to nutrition estimates via a public nutrition database (USDA or local CSV) or a simple ML model and show calories/protein/carbs/fat/fiber; 6) UI to filter/sort by nutrient, save menus, and display a waiter-facing 'flip' view. Out of scope: training large proprietary models, building a large curated dish-photo corpus, offline native mobile app. Include error handling, input validation, unit tests for parsing/translation/mapping logic, and integration tests for OCR->parse->translate->nutrition flow.
How we checked
How the score was reached
- Partly verdict base52
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score59
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productMenu Vista - Translate Restaurant Menus Instantly
- official docsMenu Vista features (site content)
- official pricingMenu Vista pricing (page returned Page Not Found but site lists features)
Integrity checks
What held up, and what did not.
