TripAdvisor Mason Pomeroy

The evolution of native engineering at Tripadvisor: Part 2

Article Summary

Tripadvisor's mobile team was drowning in nearly-identical UI components. Their server-driven UI framework promised speed but delivered the opposite.

Mason Pomeroy, from Tripadvisor's native engineering team, details their journey rebuilding their SDUI framework from rigid, pre-built 'Sections' into a flexible component system. This is part 2 of a 3-part series on their native app architecture evolution.

Key Takeaways

Critical Insight

By breaking rigid UI Sections into flexible, composable components with server-controlled layout, Tripadvisor achieved 33% faster delivery on UI projects.

Continue reading

What This Article Covers

Problem

Tripadvisor's SDUI framework forced engineers to build 30-40 nearly identical card types. Each small layout change meant writing new API contracts and updating clients, which created a lot of maintenance work and slowed down shipping features.

Solution

Mason Pomeroy's team rebuilt the framework with composable Horizontal and Vertical Stacks that work like SwiftUI and Jetpack Compose. Now the BFF controls layout through smaller atomic components instead of relying on pre-built Sections.

Impact

Within a year, the Design System Flexibility Framework increased throughput by 33% on UI projects. Teams could now build flexible sections for home pages, hotel details, maps, and account tabs without writing new client code.

Part 3 reveals the iOS-specific implementation challenges with The Composable Architecture that made this system actually work in production.

This page summarizes “The evolution of native engineering at Tripadvisor: Part 2” by TripAdvisor, published Aug 8, 2025. All credit for the original work goes to the authors.

Read the original on medium.com (opens in new tab)

AI tools for iOS

Browse all AI tools →