Driver App

Problem

A common user feedback was that it was too cumbersome for drivers to sign in to the app, as the fleet manager had to generate an access code for each driver and share it with them, being too time consuming. The code expired after 2 weeks, so fleet managers would have to regularly repeat this whole process.

Also, the code was a 6-character random sequence of letters and numbers, which was hard for drivers to remember, so they had to constantly check the message sent by the fleet manager to retrieve it.

This was causing a drop in the app's adoption rates since the whole process took too much time and effort to simply to log in to the app.

Solution

While revamping the sign in flow, I had to make sure the solution would contemplate three constraints:

1. Driver needs to be associated to the fleet in some way, for security reasons
   
2. Log in information must be easy to remember
3. Fleet manager must be able to remove a driver's access if needed

So the proposed enhanced flow would:

• Associate driver <> fleet through a mobile phone number
  
• Drivers would be able to set a password and log in with their phone numbers
  
• Fleet managers would be able to switch the access on or off

Problem

The service Cobli provides depends on a device (OBD) to get data from vehicles and transform them into information and insights available on the dashboard, a web application.

Many leads asked for a free trial, which could only be offered to potential clients with over a determinate amount of vehicles because of the costs involved, mainly: device cost, shipping and the operations team work to send and retrieve (in case the lead didn't convert to customer) devices.

As a way potentialize the go-to-market strategy, the company decided to develop a freemium product – so leads could easily test the web application without the costs and operations team overhead and vehicle's downtime caused by installing hardware.

Solution

The proposed freemium product was a Tracking App, which would track the vehicle position through a smartphone's GPS and limited features on the web dashboard. Users would be able to upgrade to the premium product and gain access to all product features.

The MVP would be tested with a few lost leads (for budget or needs reasons) that would be contacted by the Customer Success team with an offer to test the freemium product and a private link to create an account and download the app.

On the web application end, we would show the premium features as "locked", with hint popups shown on hover briefly explaining the feature's purpose and value with a CTA to upgrade. The driver mobile app would serve only to activate and deactive tracking in the first release.

This showcase presents the UI designed for the mobile app: