Kawacom’s is a production cross-platform ordering ecosystem designed around the operating model of a coffee franchise—not a generic delivery template. It connects customers, kitchen staff, delivery personnel, dine-in service, and administrators through coordinated mobile applications and a progressive web backoffice.
A complete teamwork delivery
Panayiotis Hiripis created the initial product and solution design. Renos Hiripis implemented the mobile and supporting systems, refined and polished the experience, tested the complete workflow, and carried it through delivery. Product decisions and engineering remained a close collaboration throughout.
A four-application operating ecosystem
Customer ordering
Customers browse the menu, configure drinks and other items, select an address, pay in the application, and follow order progress.
Kitchen management
Orders arrive in a dedicated kitchen application so preparation work can be coordinated without relying on the customer-facing interface.
Driver delivery
Assigned delivery personnel use a companion application for the delivery stage of each order.
Table and waiter terminal
A separate dine-in application supports table and waiter workflows inside the franchise.
Ordering, identity, and payment
The customer application supports a sophisticated menu assembled and managed by administrators in the backoffice. Individual products can receive optional or chargeable add-ons, with separate VAT treatment where required, before the order is finalized.
- Phone-number registration with Firebase OTP verification
- Email registration followed by a six-digit verification message
- Sign in with Apple and Google
- Google Maps services for customer and delivery locations
- Stripe card payments embedded inside the Flutter experience, without sending the customer to an external payment page
- Firebase push notifications sent from the backoffice for order updates
- Multi-language interface content managed centrally from the backoffice
Backoffice and architecture
The progressive web backoffice is implemented with Laravel and PostgreSQL. It manages multi-tier menus, product options, dynamic tax and VAT rules, localized content, administrative access, and the operational flow shared by all four applications. REST APIs connect the Flutter clients with the central business logic and data model.
Production delivery: The customer application is publicly available through both official stores. Store listing artwork and interface screens shown on this page are sourced from the official listings.
