Evaluation to group 3

User group

Is it clear to whom the service is made for?

The user group is clear. Flags are a good way of indicating that it is available in other languages.

Can also be used by others outside the user group.

Is the functionality well adjusted to the particular user group?

Clever solution. We like that the flags are on the main page. Not too much information on the main page. Main language could be English to clarify that the interface is directed towards tourists.

'The feeling'

What does the first impression tell?

Simple and clear. Minimalistic. The user's mission is to buy a ticket.

The zones are not clear. A? A+B? A+B+C? What does that mean? Is the 'Choose you zone?' function necessary? Maybe a tourist map instead of station map. The tourist could click where he wants to go and the interface could tell the user only the price. It is not necessary to know what zone you are in.

How are blind people going to interact with it?

Interaction and overarching structure

It the flow clear?

'Choose your ticket type'  in clear (good that the ages/limits are there!). The receipt is good, nice to get a confirmation that you have the correct tickets. Great that the app tells you is you have to change bus/tube. Good idea to print line switches on the ticket. The zone function is a bit unclear. Could the ticket be colour coded? This could be a good idea since the subway-lines already are color coded, by this you will create similarity in the design to group the interface with the existing subway map solution.  A suggestion: Minimize the user’s memory load, by always showing the steps and choices he has made.

Is it always clear what options and possibilities the interface provides?

We suggest that you instead of the stations map have an interactive tourist map where the users can click on for example 'Slottet'. That way it will be easier for the tourists to find their stop. Is there any solutions for error prevention? What happens if the user click on the wrong button.

Primary and secondary functions

Is the main functions in focus in the design?

Yes. The main action is to buy a ticket, and that is clear in the interface.

Is the secondary functions valuable?

No. We think that the 'zone' function could be swapped with a tourist map.

Design/composition

Is functions and elements naturally grouped? Design/layout?

The design is clear and easy to comprehend. It might be a good idea to colour code the buttons.

Recover from errors:

What happens if you want to change the trip in the last step. How does it work with the steps, will you have to re-do the steps if you go back or does the already tapped in information stay unchanged?

Sketches

Are they clear enough?

Yes. The prototype is well made and it is easy to understand your concept from the popApp.