Status of application development is early closed beta. You find attached the complete screenflows of both roles Driver/customer.
(Sorry, some text is german there)
The most important flow is the creation of a new delivery request. It is currently designed as a 7-step wizard where all informations are entered.
(Generally spoken, all complex data Inputs are designed as n-step-Wizards.)
Second important screens belong to the delivery processing workflow, where the Driver does the daily work.
Which screens we expect for design:
1-2 Dashboard / Welcome screen: For registered users, the app starts directly into this screen. So the user wants all important information and functionality there. (Customer: Create new request, see current Status, check Messages) (Driver: manage deliveries, manage requests, check messages)
The Dashboard can/should differ for Drivers and customers.
1-n. Create a delivery request. This screen(-flow) collects all Information (pickup-source, drop-destination, dimensions, weight, specialities, etc. and is finished by payment process. Your design should tell the whole Story.
Casual users do this proces.
These two Workflows are the most important. If your design-story is told in less than 5 screen, you add these screens:
1. delivery Management
Where the Dashboard is only a summmary of recent data, the "Delivery Management" is the place where all deliveries can be managed. A delivery can be in different states: inactive, Picking up, delivering, delivered, overdue.
The screen should Display Information in a way that express their priority and offer functions to drill down into Details as fast as possible.