Overview Process
Studying internal processes of the system and defining its structure.
Deciding to break down the website into three global sections: Ticket Office, Information Desk and My Order. The first section deals with ticket sales, the second will provide useful travel information and in the third the users will be able to print out guides with useful tips custom tailored for their journeys. Assembling a prototype to test all scenario hypotheses.
The client likes the approach. Moving on to the design concept. The first idea is to make a calendar with visual information on prices.
Art director: Not bad. It would probably be difficult for the client to implement, but it doesn’t mean we can’t suggest it.
Adding everything we need to create the main page. Using a color scheme similar to the colors of the logo.
Visually separating the filters from the flight list. Making the expanded filter fill the entire page which allows us to easily fit all the parameters.
Adding the ability to change destination in the collapsed filter with a simple text input.
The date can also be changed without expanding the filter.
Working on the style.
Assembling a presentation and showing to the client.
The client likes it but asks to choose a different color scheme, further from the sky and air travel and closer to railroads.
When inverted, the original color scheme doesn’t look dissimilar to rail travel.
Client: All right, you’ve proven you’re right. You also need to think about the cases where price information would not be available.
Creating two views of the calendar.
To make building the website is easy, creating a small site map with ready pages.
Finalizing the rest of the pages.
Simultaneously assembling a generic page.
The client typesets the pages that will be launched first. There are a couple of things that need to be fixed.
Working on the dynamics.