🚗 Building a Car Pool App: MVP definition
Following on from my last post, I decided to define the scope of the solution for the problem I had discovered.
Problem:
When it takes longer than normal to be picked up, the driver has no way to express the problem and pickups have no way of knowing.
Things to consider:
- The driver cannot use their phone while driving
- People being picked up may not want to download an app for something they’re not going to use often
For the both the driver and people being picked up, I felt a map-based view would be appropriate. This would provide both with the visual of how far the driver is and what the traffic is like. This should help to answer questions that the person being picked up, might have about why someone is late and when would they arrive.
As inspiration for this (as I said before), I kept Find My Friends and Uber’s interface in mind. Here’s what I came up with:
The driver should be able to:
- See the traffic levels around him and the people to be picked up
- Have the ability to message and call the people
- Request directions to a pickup location
The person waiting to be picked up should be able to:
- Know where the driver is
Given the type of interactions needed from the driver and for future scope, the driver would require to run an app on their phone.
The person waiting to be picked up will have a naturally limited interaction with the service, as they are only likely to check where the driver is when something is unusual or around the time they are meant to be picked up. So a hosted web page would be the most appropriate here.
Next
The next stage is to implement the design in the GIF above into a native app for the driver.
