The Challenge
As the product grew, there were different needs to tackle. One was the option to select multiple rooms per session.
Research
Benchmarking helped me to decipher the sections I believed should be on the module. However, there were too many options, and it wasn't clear how the user felt about them. Therefore, I decided to run some tests on the competition site. To have an accurate result and the possibility to see how the users interact with those sites.
TripAdvisor is not friendly enough, but users are already familiar with it, so they chose it as the best—Opposite of Tablet.com or Luxuryhotels.com, where the design is much cleaner, but users encounter different problems.
We already had an item page template live for places to stay. I wanted the product to have a consistent feel. Therefore, a lot of the UI, such as iconography, typography, sizing and spacing, remained the same as places to stay.
I needed a new part for the multiroom selection, so that was my main focus.
For this, I worked separately on the calendar first, as it will have different needs for availability or pricing per day.
Then in the room setting: the number of guests, kids, infants, their age, how many rooms, and how many guests per room. How easy it is to edit, delete, or add all this.
Test
I run a series of tests on the designs before implementing them. I tested mobile and desktop, creating a prototype for it. I got excellent feedback, and after some details and adjustments, we moved to the next step.
