How it works
Quick Picks is a set of static pages. There is no server code, no database and no account. A restaurant's whole menu lives in one JSON file.
The menu file
Each dish keeps the restaurant's own number. Three fields drive the picker: protein, kind of dish, and spice from 0 to 2. Stir-fry dishes also get a sauce, which builds the sauce-by-meat grid.
{ "n": "47", "name": "Hunan Chicken", "zh": "湖南鸡",
"section": "chicken", "protein": "chicken", "kind": "saucy",
"sauce": "Hunan", "spice": 2, "price": [8.50, 12.95],
"tag": "popular" }
Design choices
- Menu numbers never change, because regulars and phone orders depend on them.
- The most-ordered list holds up to five dishes and never exactly four, since four sounds like "death" in Chinese.
- Allergen text says what a dish is usually made with. It never claims a dish is free of anything.
- Text size, an easy-read font (Atkinson Hyperlegible), focus mode and no-motion settings are saved on the customer's phone only.
- The page works next to the paper menu and the phone, and opens without a login.
Sources
- Popularity lists: Cai, Chen and Fang, Observational Learning, American Economic Review, 2009.
- Cognitive accessibility: W3C, Making Content Usable for People with Cognitive and Learning Disabilities.
- Easy-read font: Atkinson Hyperlegible, Braille Institute.
Stack
Plain HTML, CSS and JavaScript modules. The picker logic is one file of pure functions with node tests. Hosted on Vercel as static files. A service worker keeps the menu usable on a weak signal.