Menu-first customer journey
The customer experience prioritizes reaching the menu and placing an order with minimal friction, particularly on mobile devices used at restaurant tables.
Engineering case study · Restaurant SaaS
ManageMyCafe
A restaurant product that turns physical menus into accessible QR experiences and supports online ordering through a focused customer and operational workflow.
01 · Context
The product problem
Restaurants need a simple way to publish changing menu information and let customers browse or order without installing an application. Static menu files are difficult to maintain and provide no structured ordering workflow.
ManageMyCafe brings menu discovery, restaurant configuration, and ordering into one product experience designed for customers and restaurant operators.
02 · Ownership
My contribution
I designed and built ManageMyCafe as my own product, working across product UX, frontend architecture, backend APIs, database structure, and deployment.
- Product workflow and interface design
- React application architecture
- Node.js and Express API development
- MongoDB data modelling
- Ordering workflows and production deployment
03 · Engineering
Decisions behind the product
Operational data boundaries
Restaurant, menu, category, item, and order concerns are separated so pricing and availability can evolve without destabilizing the complete ordering flow.
API-driven product architecture
The React interface communicates through Express APIs, keeping presentation concerns separate from restaurant and ordering business logic.
Customer QR scan
↓
React menu and ordering experience
↓
Node.js / Express APIs
↓
Restaurant ─ Menu ─ Categories ─ Items ─ Orders
↓
MongoDB persistence and operational workflows04 · Evidence
What can be verified
ManageMyCafe is a live product with a complete customer-facing product surface and full-stack restaurant workflow.
Restaurant count, ordering volume, and conversion metrics will be published only after they are verified from production analytics.