At trivago we are working heavily on the web platform and, based on the scale that we need to serve our users, our applications need to cater for many different kinds of environments and conditions.
Mobile at trivago
Insights, experiences and learnings from trivago's tech teams.
What’s the point in downloading the app from the store when you can do the same thing in the browser? I’m a product designer at trivago, and would like to share some insights into one of our biggest projects we tackled in the last period. Designing trivago's new mobile app!
How the Android development team came up with a new architecture based on clean principles and what we learnt along the way.
Concepts like separation of concerns, logic decoupling or dependency injection are things we developers have heard more than a couple of times. At trivago, the Android app is developed using the Model View ViewModel (MVVM) architecture, aiming for views as dumb as possible, leaving the decision making to the view models. This leads to an increased test coverage since testing logic in views is something we can’t do that easily.
When thinking about design patterns and architectures in iOS development, MVC might be the first thing that comes to mind for most of you. But throughout the last years, MVC got a really bad reputation. Probably a lot of you heard about MVC as the massive view controller.