UX/UI Challenge 1 : Problem Solving

A lot of first for this one, first exercice, first medium page, and first prototype design.

Kevin R.
3 min readDec 15, 2020

Design Thinking

Citymapper is a public transit app and mapping service which displays transport options, usually with live timing, between any two locations in a supported city. It integrates data for all urban modes of transport, including walking, cycling and driving, in addition to public transport

To-Do :

Your task is to create a feature for this app [CityMapper] that solves the pain of having to purchase different public transport tickets by different channels.

For this task, I began to interview some users of the app who live in Paris.

It revealed that users want safety and reliability. Ok with credit card, but better with Apple Pay/Google Pay.

Surprisingly, to buy ticket in advance is not a requirement, the choice of transport can change regarding time available, and weather conditions. They want the choice of buying tickets for public transports and/or a bike or scooter. So the info of a trip can be saved, to buy faster, and just before the trip.

They don’t care about having a physical ticket, but surely need a receipt within the app, or by mail in case they need to write it off as a business expenses.

An important feature is to be able to compare cheapest vs fastest, if possible on a map.

The problem

We have a lot of tickets providers.

When the trip is validate on the app :

  1. They actually have to find the transports websites
  2. re-enter their trip information
  3. enter login for payment/checkout.

/!\ Sometimes multiple time for one trip.

Solution

Users want convenience for this feature, and safety for the paiement.

It must be simple and embedded in the end of the process of looking for a trip.

A few lines must display the available options, and which company you will buy the ticket from with this choice. In the end, all your tickets from one trip will be stored in the app, with paiement done.

The idea here is to add only one extra step for the user, which is payment. He will have the repartition between providers, and tickets in a new category on the homepage.

I particularly enjoyed doing interview because there are things that you will never think of, like the business expenses need, and it really encourages you to asks for more questions as you realise you might have missed a lot of ideas.

It was really hard for me during this process, with my technical background, to try not to think of the feasibility of the features we have to put on paper. I know the nightmare it will be to just be able to checkout with multiple providers, multiple paiement all in one app, to just have one simple paiement. I have to only think of the UX side of things and we (or someone else now) will worry about technicals problems later.

Hope you enjoyed this piece as much as i did.

Kevin.

--

--