Menu Translation Application
A concept for translating a venue menu into a guest's language at the table, without reprinting anything.
This is a concept, not a delivered project.
Interface outline. Structure is shown; no live or client data is published.
The business problem
What was going wrong
In a region with a large multilingual population and a steady flow of visitors, a printed menu excludes people. Reprinting in multiple languages is expensive, goes out of date the moment a price changes, and still misses whoever speaks the language you did not print.
The solution
What we proposed
A concept that keeps one source menu and renders it in the guest's language on their own phone, with dish descriptions and allergen information carried through the translation rather than dropped. Documented here as a concept: the interesting problems are translation quality for food terms and keeping a single source of truth for prices.
Key functionality
What it does.
- One source menu, many rendered languages
- Dish descriptions and allergen information preserved in translation
- Guest access by scanned code, no app install
- Price and availability updated in one place
- Fallback to the source language when a translation is not available
Technology
What it is built on
- Next.js App Router
- TypeScript
- Translation API integration
Process
How it ran
- 01
Discover
Identified the failure modes: food terms, allergens and stale prices.
- 02
Plan
Sketched a single-source model where translation never edits the price.
Services used
The parts of the studio this project needed.
Web Applications
Portals, dashboards, booking and ordering systems built for one business rather than a market of them.
Read about this serviceIntegrations
Connections between your website, applications and the platforms that run your payments, messaging, accounting and point of sale.
Read about this service