Hotel booking process

background

The hotel booking process inside RoadPlan app was another important process which deserved its own space of presentation. Therefore, I decided to dedicate a page just to this design.

 

 

iterations

1st iteration

In the first iteration, the user journey was overly simplified. Many aspects were not considered, such as how the transaction process would be like, whether users could save a hotel, and whether users can search hotels based on their preferences.

Moreover, the information communication of the UI was not clear enough. Too much information was missing in the process, and the ommissive user experience caused much inconvenience.

 
Wireflow – 2.png
 

2nd iteration

After the first sprint of user testing, I discovered that:

  • Users wanted to be able to review some basic information such as pricing and rating before they wanted to see further details of a hotel.

  • Customer reviews and hotel brands were very important for users in choosing hotels.

  • Being able to search for hotels based on preferences such as budget and location was also crucial in choosing hotels.

  • Users wanted to have clear and explicit confirmation after they have booked a hotel.

However, the transaction process was still not clearly defined because of both technical concerns and booking specifications such as payment type and room type.

 
 

3rd & 4th iteration

I researched and was heavily inspired by the smooth and streamlined hotel booking process on HotelTonight.

After redesigning and another round of user testing, I found out that:

  • Users liked to be able to decide where they wanted to search for hotels sometimes, and it wasn’t necessarily near the last spot of a day.

  • Users didn’t like to jump around between different platforms, and preferred being able to finish booking on one platform.

  • Before even being asked for payment method, users wanted to clearly see all the fees they were being charged for. They expressed having more patience for these steps.

  • The least amount of information needed for charging money the better. Users didn’t like to give their information if not necessary.

  • Users did like to to be able to make changes near the end of the booking before they were about to be charged.

The only part which I would still need further research is the room-type-selecting process. Considering the fact that my app focuses on planning instead of on-the-go searching, allowing users to be able to choose hotel rooms based on their preference is important.

 

 

ui screens

Since the user flow had been mostly sorted out, I jumped into the high-fidelity screen designs. The same UI visual direction of RoadPlan is applied to these screens.