Back

Trivago native apps

Redesigning Trivago's iOS and Android apps from the ground up, then recovering business KPIs through focused research and design iteration.

Contribution
Product strategy User research Product design
Team
4 product owners 4 product designers 16 engineers
Year
2018
Trivago native app redesign cover

Impact

Click-to-book conversion, against the old app
+5%
Visit-to-book conversion, against the old app
+3%
Clickouts to advertisers, against the old app
+6%

The first release converted well below the old app. After a few rounds of research and redesign on the booking funnel, the new app beat the old one on every booking KPI, even though the old app had been refined for years.

On the verge of failure

After a year of hard work with a radical redesign, we almost reverted to the old version. The business KPIs were way off. With confidence and quick iteration, we managed to fix it and set an example of innovation in the company.

In 2018, I led the redesign of the Trivago iOS and Android apps, used by millions of travelers. The project gave our team the opportunity to build the product from scratch and rethink the complete flow.

The vision

In our pitch , we outlined the direction of the new product. We did a vision discovery exercise for a couple of weeks, which helped us get buy-in from the CEO and CPO.

My specific role was to create a complete flow and high-fidelity prototype that unified feature ideas and visionary ideas from the team. I wrote about it on Trivago's Tech blog .

Trivago's new native apps kickoff workshop

What is Trivago?

Trivago's business model is metasearch: it compares deals from different advertisers, such as Expedia or Booking.com. You do not book on Trivago. In the complete "book a hotel" job, Trivago focuses on the search and compare step, while also exploring the boundaries around it in a smart way.

Goals of the project:

  • Increase Trivago's product offering depth by exploring the quality of advertiser visits and booking conversion, moving from quantity to quality of leads.
  • Improve or maintain business KPIs. The team could deprioritize short-term revenue metrics and click volume, but we still had to stay above a reasonable threshold.
  • Give more value to travelers and answer why someone should download and keep the app instead of using the mobile web version.
  • Integrate well with Apple and Google platforms, respecting native patterns while maintaining the company's brand.
  • Improve the information architecture so future features would not have to be squeezed into the wrong place or the wrong user flow.

The team

Around 40 people worked on the project, divided into cross-functional teams. Each team included a product owner, product designer, user researcher, iOS engineer, Android engineer, and QA.

The main features were already defined during the vision sessions and design sprints. The teams had already:

  • Analyzed the old app and identified product and usability issues using Trivago personas developed by user research.
  • Conceptualized improvements and new features.
  • Taken ownership of individual features and created concepts with realistic technical and timeline constraints.
Trivago native app wireframe

Prototype and user research

We used generative research as the basis for prioritizing content in the flow. The prototype helped the team align on native interaction patterns, information hierarchy, and where the app could provide more value than mobile web.

Research sessions and workshop artifacts gave us a shared view of what mattered most to travelers, where the old app was fragile, and where the new flow needed to be clearer before release.

Usability test for Trivago alpha build

We used that evidence to work through the hotel content hierarchy and translate it into a native prototype that could be tested before the full release.

Trivago brainstorming session on hotel content priority

Booking flow and hotel card

I was the design owner and IC for the booking funnel. It was the crucial flow from a business point of view.

The booking funnel had the following screens:

  • Results with hotel cards
  • Hotel details
  • Child content for hotel details
  • Deals
  • Deal summary
  • Transition to advertiser

In the old app, users struggled with hotel card touch areas that were below the recommended 44 pt. We went in a radical direction and made the whole card tappable, taking advantage of a new hotel details screen that did not exist before.

Alpha build booking funnel screens

Second-level content was exposed in hotel details as an overview: ratings, amenities, location, and more. Granular content had dedicated child screens. We followed our top-level product direction: give users the right information at the right time.

First release

We shipped the new Android app on Google Play with a 5% A/B test. The final design language was not refined and the technical side was not fully optimized, but we wanted to gain quantitative insights as soon as possible.

Trivago pre-alpha build with native design components

Business metrics

We tracked booking conversion as our new reference metric, alongside click conversion and content penetration. The initial KPI numbers were bad.

We forecasted drops in short-term click conversion because the new app no longer sent people immediately to advertisers with a prominent button. To our surprise, booking conversion also dropped far below expectations.

When we analyzed content penetration, we noticed a problem on the search results screen too. Even though the card was one tappable area, fewer people proceeded to the next screen. With each step in the funnel, fewer people converted, dropping by almost half each time.

Fixing with design

The follow-up usability work helped us see where users expected stronger access points and where the new flow was hiding the fastest route to a deal.

Heatmap from a usability test on main access points

The iterations that addressed these issues:

  • Added a stronger tap affordance to the hotel card.
  • Created two paths: one for people who wanted to discover more hotel details, and another for people who just wanted to go to the offer.
  • Made the flow shorter.
  • Removed some steps in the funnel and made others optional. My proposal to make the deals screen optional and integrate it into hotel details was especially successful.

We managed to achieve the same KPI as the old app and surpassed it in some areas, even though the old app had been refined for years around those same goals.

We also had a product tailored to our branded users, flexible enough to add more features, and better able to do justice to the hotel content Trivago had.

Conclusion

The project was successful and was often presented in company all-hands meetings as an example of innovation in product development.

Looking back, I still believe we could have improved a few things:

  • Focus the team only on the main flow for the first MVP iteration, so we could learn more quickly from the things that mattered most.
  • Test earlier in a real-life scenario with our users. It helped tremendously, even if some team members, me included, were skeptical about releasing something unpolished.
  • Cross-functional groups working in parallel made sense, but alignment could have been better. Often, the complete flow was split between teams and adjusted later with compromises.

Download the app from App Store for iOS and Google Play for Android.