Side project

Air Tour

Booking flights doesn't have to be tedious.

Brief

Airtour is an iOS app that helps people book their. 

One day, I was using a local airline app and I struggled when I wanted to book my flight. There were too many steps and a vague design so I wondered... do I have to struggle every time I want to book a flight? 

I wanted to create a concept that helps people buy their tickets easier and make them feel comfortable during the process. I took some decisions based on what would I like to see when I'm using an app like that and what features would be more appropiate to guide me through what I want to achieve. I had the following goals for this first step: make a clean yet intuitive interface and buy tickets faster.

This is not finished as it only contains the booking processs.

user persona

Meet Javier, interested in new world trades, government, new technologies and different kind of cultures.

He's an import and export expert and currently has several meetings and needs to fly over the country to attend them. He’s been asked to host multiple conferences related to his field.

He wants to book several flights per month and make it in the easiest and fastest way possible.

User-Flow

This is the path a user follows to accomplish this first booking feature. This part of the process helped me understand what that local app lacked and what could be improved so that users can meet their goals.

I'd never booked any flights through an app before and didn't like my experience that first time so I wondered if it was just me struggling with that. Well, turns out that 3 out of 6 people I asked use it for the check-in feature but not to live the complete booking experience. Something's wrong then.

User Flow for an easy booking process

architecture

The main goal was simple: how can the booking experience be improve so users don't struggle with it?

I designed a couple of low-fidelity wireframes to help me visualize a little bit better the user-flow I was picturing.

The app should be/have:

  • Easy to navigate.
  • User-Friendly.
  • Trustworthy.
  • A clear step-by-step booking process.
booking options/home - results - summary - payment

design

Now that I had the low-fi wireframes done, the next step of this process was adding an UI design touch so that it could look clean yet intuitive for people to use.

The UI must have the following:

  • Easily understandable design system.
  • Recognizable icons and buttons.
  • Interface elements well-positioned.
  • A clean typeface
booking options

Booking options/home

Users in the home screen can:

  • Select the type of flight.
  • Select origin and destination.
  • Pick the dates.
  • Select whether that's a fixed schedule or they want to know other alternatives.
  • Clarify how many adults, kids and infants are traveling.
  • Search flights.

Booking results

Here users can:

  • Change the dates in order to see other alternatives.
  • Select whether they want to travel in economic, flexible, executive or first class flight.
  • Sort the results by departure time or price.
results
summary
payment
confirmation

Users then have a summary of the options they've picked out in the previous screens.

When they have to pay the tickets, the app offers the three options they've set up in the sign-up screen. They've set the different payments options they like and the app shows them by default. If someone is using it without an account, it simply shows a credit card form.

what's next?

The next steps in this concept are:

  • Itinerary.
  • Check-in process.
  • LifeMiles.
  • Favourites Flights.

Need help with a similar project?

get in touch