The Brief
A delivery app has more than one interface: customers need to set a pickup point and destination, while drivers need a separate view of the job and its progress. Kang Ojol explores those two journeys as a working Flutter Web prototype rather than presenting a static mockup or claiming to operate a delivery service.
What the Demo Lets You Try
The customer flow collects delivery details, pickup and destination addresses, a vehicle choice and a note about the item. The driver flow includes profile setup, an online toggle and simulated job and delivery stages. The app uses Google Maps for map display and location search; directions depend on the relevant Google Maps APIs being available. Device location is optional and requires browser permission.
How It Was Built
The responsive client is written in Flutter Web and deployed on Cloudflare Pages. Its map integration covers address suggestions, geocoding and route display where the APIs permit it. The public site also includes a readable About/FAQ page that describes how to try the demo and where its limits are, rather than relying on a canvas-rendered app for all of its explanation.
An Important Boundary
Driver assignment and order tracking are simulated; there is no authentication or genuine cross-device, real-time dispatch. Optional Supabase configuration supports basic synchronization, not a production courier backend. Do not use this prototype for real deliveries or payments.
The Outcome
A live, testable demonstration of customer and driver experiences and location-enabled web UI. It shows the interaction design and integration points needed for a future delivery product without misrepresenting the current demo as a working transportation business.