Train schedules and the UI

Research, ui, ux, prototyping

Train schedules and the UI

This is the project I've presented as the final thesis of my Master. The entire title is “Railway information systems and the graphical interface. Solutions for a less painful relationship with our devices”.

The major aim of this work is to highlight the need of a proper designing process for the current digital services. I tried to show a case study where I designed a mobile app for train search.

Browsing train schedules on smartphones
Buy Ticket within station interface
People use train-search services everyday.

Before facing the design of a new service, I followed the evolution of the train timetable representations, from the first posters in 19th century to the current web services.

Historic train timetables
Posters and charts from late 1800.
Modern train timetables services
Evolution of the most-used digital tool for searching trains: nothing changed in 10 years.

I made a long research about users and their goals. Personas and Scenarios were two fundamental tools to go through this phase. I structured two different interfaces, based on the primary personas: the first one for users who already know the places to move to or from, and the second one for users who have to figure out the space he or she is moving into.

Interface A: inputs+suggestions based on most travelled places (a machine-learning approach I talk about in the thesis) Interface B: map+information

The results–the single trains–are presented in an ideally infinite list, where we can move directly to the period we are interested in with a single click.

Train journey representation
Representations of simple trains.
Train journey representation
Representations of more complex journeys.
First prototypes using Flinto webapp
Sketch+Flinto+Framerjs has been the worflow adopted to build prototypes.
Prototyping using framer.js and Framer Studio