JUST GO TRAVEL CONCEPT JUST

The Design Challenge The design challenge is to make little improvement in the UI and UX of the present travel apps, so that the users get to spend less time going through different fields and just concentrate more on the booking process. The Difference This app concept will also help the business to separate out transactions which does not lead to any booking. This app will help support both types of customers with the best possible user experiences. The Similarity To make a walkthrough for my app concept, I have used the Goibibo travel app as a base so that people familiar to it can understand the differennce in it’s usage. This concept is based on an idea where both the user as well as the developer would be benefitted.

Hello! I AM ARUNIM AICH I am here because I love to think and rethink. You can find me at JUST

Competition Analysis The next few slides will show what flow the companies have at present. 1 JUST

“ “A merchant who approaches business with the idea of serving the public well has nothing to fear from the competition.” - James Cash Penney

Makemytrip.com If you notice here, make my trip first shows the user what all services they have and then moves forward towards booking a particular service.

Yatra.com The same thing can be observed here as well.

Goibibo.com The same thing can be observed here as well.

What does the customer think? Users are the most important parameter of any UX design. Let’s see what they have to say on this.

70% Travellers use travel apps to check for fares many times before actually booking the service. 90% Users already have a motive of which service to book before actually opening the app. 65 % Users had a frustrating experience when they had to book tickets in an emergency situation. As they have to go through many screens and at times the responses are slow.

The Big Concept The Wait is over! GO

Goibibo Current UI v/s Revamped UI

Major Observations on the current UI Almost every app have services, such as Flights, Hotel, Bus, Flight + Hotels. Every services in this app has a page to perform all the required transactions. In all the views, the fields are more or less common. E.g Source, Destination, Calendar, If the user needs to plan the travel, he has to enter all the values and go for booking to see the fares. Loading the fare page takes some time. The flow for users who are actually booking and the people who are just looking for fare remains the same.

Revamp Suggestion This screen is selected as home or landing page. This screen is selected as home or landing page. People who need to book near by hotels can skip all the other steps as he does not need to fill any other information. And click on the link to find near by hotels. People who need to book near by hotels can skip all the other steps as he does not need to fill any other information. And click on the link to find near by hotels. Here the source is taken automatically(assumed to be the location where you are actually browsing through GPS or IP) anyways it is editable. Here the source is taken automatically(assumed to be the location where you are actually browsing through GPS or IP) anyways it is editable. The moment the user enters both source and destination, the app makes are request to the backend which responds by sending the cached fare calendar details for the respective cities. The moment the user enters both source and destination, the app makes are request to the backend which responds by sending the cached fare calendar details for the respective cities. Here the users can select the service they want, and fill in the required details. Through this what we can achieve is that the users who only come to check fares can be segregated by showing the fare calendar. Through this only genuine booking will proceed to make request to see the detailed information Here the users can select the service they want, and fill in the required details. Through this what we can achieve is that the users who only come to check fares can be segregated by showing the fare calendar. Through this only genuine booking will proceed to make request to see the detailed information

User Segregation Fare Calendar itself can help in segregating genuine buyers from people who come to see the fares and plan. Fare Calendar itself can help in segregating genuine buyers from people who come to see the fares and plan. As of now, people fill up the fields, and taps on the search button. On the tap the app sends a request to the server to find details of flights or hotels for the given info. As of now, people fill up the fields, and taps on the search button. On the tap the app sends a request to the server to find details of flights or hotels for the given info. Server then connects to third party fare management applications to get the process right. This transactions, plus a lot other similar transactions make the response slow, which we all have observed while booking tickets. Server then connects to third party fare management applications to get the process right. This transactions, plus a lot other similar transactions make the response slow, which we all have observed while booking tickets. Now, if we are able to segregate users on their motive, we can actually reduce the number of requests to a great extent hence providing a better and faster user experience to the genuine buyers. Now, if we are able to segregate users on their motive, we can actually reduce the number of requests to a great extent hence providing a better and faster user experience to the genuine buyers. But, we cannot ignore our prospective buyers to take more care of the genuine buyers, hence the concept of fare calendar has been introduced. But, we cannot ignore our prospective buyers to take more care of the genuine buyers, hence the concept of fare calendar has been introduced. Hence fare calendar can be introduced instead of normal calendars in the screen where user selects the date. Since it Is a mandatory field, the user will open it and he will surely see the fares. Accordingly he can decide to move forward to the next screen i.e. the booking screen or not. Hence fare calendar can be introduced instead of normal calendars in the screen where user selects the date. Since it Is a mandatory field, the user will open it and he will surely see the fares. Accordingly he can decide to move forward to the next screen i.e. the booking screen or not.

Front End-Back End interaction It is suggested that the server makes request to the third party fare management site every 5-10mins (calculated as per requirements), and cache it. When the user enters the source and destination inside the app, the change listener will be called which will make an ajax request to the backend to get the cached information of fares. Now, the user unaware of these processes at the backend, can proceed toward filling up rest of the form. On reaching the fields which has calendar(eg check in, departure date, etc), on users tap, the calendar will be generated with rates at the bottom. Along with the rates there will be a colored marker for the cheap and costly flight dates. This way the users who come with the motive of checking the fight fares get to see rates of that particular dates as well as the other dates. Hence this user may decide to move out of the app and plan his travel or continue with the booking process. Rest of the process goes as usual.

Animated UI presentation

User Interface Description As you can see from the gif in the previous screen, The user is greeted with this screen. If the user, clicks on flights, the fields related to the flight booking comes up.

User Interface Description Now, if the user clicks on the calendar he can see the fare calendar. If the users is satisfied with the prices, he can move forward, select the dates and proceed with the booking in the conventional manner. If the user needs some time to plan or wants to exit the app post this step, he can do it. He will get to know the prices for the required dates as well as the near by dates. The flows are similar for other services as well.

Screens for flight booking

Screens for flight + hotel booking

Screens for hotel booking

Impact Analysis With this idea, the users are expected to have a swifter experience. This concept is true to it’s name, it encourages the user to think less, and just start entering the required information and book the required service. It can reduce the load on the servers to a great extent as we are making use of the caching technique to show the fares. We are also keeping the user in the same screen for all kinds of transactions, even using the same fields. This helps in making sure, the user doesn’t have any distraction of moving forward and backward in an app. The UI was created on goibibo so as to keep the comparison factor always on.

Thanks! ANY QUESTIONS? You can find me at JUST