Overview
What the project is designed to do
A privacy-first restaurant discovery and ordering demo with six fictional kitchens, thirty-six menu items, filters, favourites, local distance estimates, and an expiring one-restaurant cart.
Visitors browse menus, configure items, estimate distance locally, and prepare an order through an accessible cart.
Checkout and the session receipt are demonstrations: no restaurant receives an order and no payment occurs.
Problem
What needed to change
The original API-dependent finder relied on discontinued data paths and could not demonstrate ordering without implying real transactions.
Solution
How the release responds
Use a fictional Ottawa catalogue and local-only state so discovery and ordering remain reliable, private, and honest.
Key features
What visitors can use
- Six kitchens and thirty-six items
- Search, filters, and favourites
- Local distance estimate
- Configurable expiring cart
- Local-only checkout
Implementation
How it was built
- 01
A dependency-free build generates restaurant routes.
- 02
Scoped local and session storage preserve state.
- 03
PWA assets provide an offline-capable shell.
Architecture
Delivery shape
The experience is static and browser-local with no runtime server, database, restaurant API, or transactional backend.
Product boundary
What this release does not claim
- All restaurant and order data is fictional
- No real order, payment, reservation, account, or delivery service
Collaborators named in the source data
Ziyong He, Natallie M’bayo
