Build and customize drinks from structured recipes, bases, syrups, flavors, Lotus options, and coffee types.
Working household app
A home drink shop that grew into a full ordering workflow.
The Drink Shoppe started as a visual drink-menu experiment and now supports structured recipes, household ordering, per-drink names, spoken order-ready callouts, inventory management, reporting, account-aware features, and configurable light and dark themes.
What it does now
Create multi-drink orders while assigning each drink to a different person.
Announce configurable order-ready callouts when individual drinks are completed.
Track household inventory, catalog items, and personal stock while keeping the ordering experience visual and fast.
Key features
Structured drink recipes and categories
Multi-drink ordering with per-drink names
Configurable spoken order-ready callouts
Household accounts and guest access
Order history and reporting
Inventory and catalog controls
Coffee types including brewed and cold brew
Light and dark theme preferences
Progress log
Recent milestones
Major additions that moved the project beyond the original menu-board experiment.
Ordering
- Added multi-drink orders
- Added per-drink “order for” names
- Added configurable voice callouts when drinks are completed
Inventory and catalog
- Added household inventory controls
- Added catalog management for syrups, Lotus, bases, and coffee types
- Improved inventory layout for portrait and mobile use
Accounts and personalization
- Added authenticated and guest entry paths
- Added personal/household inventory behavior
- Added light and dark themes with saved preference behavior
Reporting and operations
- Added order history suitable for usage reporting
- Added configurable administrative controls
- Continued permission and data-access hardening
Behind the Curtain
The Drink Shoppe combines structured recipe/catalog data, local-first browsing behavior, authenticated household workflows, responsive UI components, and database-backed features where persistence or permissions are required. Security and access-control work is summarized publicly rather than documented in implementation detail.