Information Architecture IA
To break down further and understand how the app is going to be structured, I drafted a quick breakdown of Information that we will later translate into the app. The target is to make myself aware of possible options, user flow with page breakdown and information with consistency. I broke the information into 2 IA- One for the basic layout with home page and further navigation, and the possible features.
The first illustration is a breakdown of Login/New user, Homepage, Account details, and Vehicle Details. These three will be the guiding sections and will be further broken down.
My entire idea for the app is to be simple so that anyone with minimal to no knowledge of a smartphone can handle the app. Yet, the user flow seems too dynamic and complicated at first glance. So, I thought I would just summarise all the information first and then refine and fine-tune it later.
I had to further write/draft information, but the paper size was restrictive with less space, and I had to draft on a new paper.
It's an extension of the first draft.
Homepage, is further divided in to Driver preferences, Account Details, Vehicle Details.
So the navigation goes ( After downloading the app)
The user is given an option to either log in or register for the app. Registration is as simple as logging in; you just need a registered phone number. If the user is registering, they need a registered mobile number and an ID (driver's license number/photo). Verification for the ID is done later, but the user is navigated to the homepage and is ready for further steps.
Once the user is in, he is given options to put his preferences, such as the Type of vehicle and route that he prefers. He gets a token number and verification of confirmation. That's all—the user is on the list! The driver can be an existing or new user, but it's still the same amount of friction and time taken to get to the listing.
Once there is a match for the driver's preference, he gets a notification request for an order. Once the driver agrees, he gets a detailed breakdown of freight charges and the exact location for pickup. After confirming he the details are shared with the consignee and consignor. WIF, the driver rejects the request? Then the order will be processed to the next waiting person on the list as per the token. This will assure the driver about a strong system in place and guaranteed orders with low commission rates.
On confirming, the driver can either complete his registration with a Driver's licence and vehicle RC or provide his phone numbers. Until the point of order confirmation, both registered and new users only need their phone numbers; the rest can be provided once the order is confirmed.
The homepage is going to be the pilot of the app, which displays driver preferences along side current trip status.
Other key Pages would be Account details and Vehicle Details, which are data stored for the user and vehicle, such as past trips and general info.
