Production Restaurants
The web/backend system is in production for the order and distribution workflow.
CASE STUDY / 02
Sklavounos Restaurants + Driver
ORDER & DELIVERY OPERATIONS
Two distinct surfaces that work together: the production Restaurants system organizes orders and distribution, while the Android Driver client executes assigned routes.
CURRENT STATEIn use · active public Driver listing on Google Play
00 / AT A GLANCE
The project at a glance.
PROBLEM
Order information must remain consistent from intake and preparation through assignment, routing and final delivery.SOLUTION
Restaurants organizes orders and distribution, while the separate Android Driver application executes assigned routes and returns delivery updates.IN USE BY
The operations team and approved drivers within an approved professional-customer order flow.OPERATES ACROSS
The Restaurants web/backend system and a separate Android Driver application.MY ROLE
Product design and UX, web/backend, Android, integrations and deployment.STATUS
Restaurants is in production and Driver has an active public Google Play listing. The exact version currently delivered by the store is not presented as independently verified.01 / THE NEED
Delivery begins before the driver starts the route.
To close a professional order correctly, information must remain consistent from intake and preparation through assignment, routing and final delivery.
- The operations desk needs a clear view of orders, states and assignments.
- The driver needs only the assigned route, stops and permitted actions.
- Location is collected only during an active route and completion returns as a controlled Restaurants state.
02 / IN PRACTICE
What changed in practice.
A shared order-to-delivery flow keeps the operations desk and drivers aligned without merging the two products.
- The operations team organizes orders, states, priorities and assignments without parallel lists.
- Drivers see only their assigned stops and permitted actions, and explicitly start precise location only during an active route.
- Delivery completion returns to Restaurants so the status closes within the same operational trace.
03 / DRIVER DEMO
The route in three clear steps.
These store artworks use synthetic data to present the Android Driver workflow without real customers, addresses or orders.
Illustrative store-listing material — not a capture of real production data.
04 / THE FLOW
From order to closeout.
Restaurants and Driver remain separate products while sharing one strictly defined operational sequence.
- 01
01 / ORDER
Intake and review
Approved professional customers, products, pricing and a clear initial order state. - 02
02 / DESK
Preparation and assignment
The operations team organizes priorities, drivers and next steps without parallel lists. - 03
03 / ROUTE
Route execution
The driver sees assigned stops and explicitly starts precise location for the duration of the route. - 04
04 / CLOSE
Delivery and update
Completion returns to Restaurants so the status closes within the same operational trace.
Sklavounos Orders is a third, customer-facing application and is not conflated with Restaurants or Driver in this case study.
05 / OPERATIONAL PROOF
A real workflow, not isolated screens.
The solution covers the daily transitions and access boundaries required by an actual delivery operation.
Driver 1.3.2 source
The current source version is 1.3.2 / versionCode 10 and the public Google Play listing is enabled.
Controlled access
There is no open driver registration. Assignments, routes and permitted data remain role-scoped.
Privacy by operation
Precise location is explicitly started by the user only for an active route, with a persistent foreground-service notice.
06 / TODAY
In use, with clear next boundaries.
Restaurants is a production system. Driver has an active public Google Play listing; the exact version currently delivered by the store is not presented as independently verified.
NEXT EVIDENCE
- 01Verify the exact version currently distributed by Google Play.
- 02Keep stable release evidence for every Android promotion.
- 03Create a public-safe Restaurants demo with a synthetic order.
- 04Publish reliability measures without real customer data.
Sklavounos Restaurants and Sklavounos Driver retain their independent product identities. Christos Fragoulis is their sole creator and sole legal owner, as well as the owner of the original source code, designs, documentation, assets and deliverables he has created for them. RAW LOGIC serves only as his personal creator/portfolio identity.
07 / CONTACT
Does an operational workflow need a clearer system?
Describe the current process and the point where time, information or control is being lost.