I'm in the process of redeveloping a "request seat" page for a taxi sharing application that I am working on. Users can request a seat on a booking made by another user - this page allows them to view the cost implications of having an additional pickup/dropoff on a journey.
The below image is the current iteration:
A couple of issues I have with this screen:
- The manner in which the journey is structured implies that the taxi is going from Great Holm - Shenley Brook End - Central Milton Keynes - whatever the user points in at pickup point B. When really it should be Great Holm - Shenley Brook End OR Pickup point B - Central Milton Keynes. How can make the UX necessary adjustments to have it appear this way? In this example, Great Holm is the pickup point and Central Milton Keynes is the destination.
- Could the fare contribution layout section be improved in anyway? The user can contribute to the Estimated Fare (perhaps this should be reworded to Estimated Total Fare), before requesting a seat. The user is given a set "frozen" price which they can either increase from or decrease to, depending on where they can be picked up from. The +/- buttons currently look out of place, any ideas on how to improve them?
- If I wanted to add a map to this screen - where would it go? Should I make it appear from a dropdown button somewhere on the screen, or have it visible to the user from the get go. The issue here is mainly with bandwidth (so I'm leaning towards having it appear from a dropdown). It would allow for the screen to initially load with the minimum data requirement for the best speed.