Monday, 6 November 2017

OUGD504 - Studio Brief 02 - Initial Wireframes







































CONSIDERATIONS:
Once you have booked and paid for your journey, how do you stop another customer or person from stealing your taxi?

POTENTIAL SOLUTIONS:
  • Interface needs a step in the process whereby the customer has to input their name or some form of details into the system which can then be given to the taxi driver upon arrival as a form of booking reference.
  • Add a feature which allows users to print out a code to reference to driver or a printed receipt of booking details.

What happens if the taxi is late or for any unknown reason cannot make the booking and has to cancel? If the user has no battery left on their phone (purpose of the interface) then the user has no way of knowing what has happened to their taxi.

POTENTIAL SOLUTIONS:
  • Introduce a login feature whereby users have to create their own user profile - makes the experience more personal to specific users and gives comfort in knowing users can make it to their destination soundly even if their phone has ran out of battery. This also gives users a way of checking for any updates or changes in their journey.
  • Introduce a sidebar which presents live times of the most recent bookings that informs users of any changes in their journey/pick up time - allows other users to book a journey whilst those who have already booked wait and are kept updated on their personal journey at the same time. Feed clears once users have been picked up.

No comments:

Post a Comment