Vinted

Vinted is Fully Composed

Article Summary

Vinted just migrated a 15-year-old Android app with 300+ screens to Jetpack Compose in 18 months while shipping features daily. The kicker? Their conversion metrics actually went UP.

The Vinted engineering team shares how they moved their entire Android codebase from XML Views to Jetpack Compose without freezing feature development. They built a custom framework called ProJet, ran over 100 A/B tests, and enforced snapshot testing coverage on every single screen migration.

Key Takeaways

Critical Insight

A full Compose migration on a massive production app is feasible without freezing features, and can actually improve user engagement through better performance.

Continue reading

What This Article Covers

Problem

Vinted had to keep Bloom, its design system, and the testing stack working across both XML and Compose at the same time. This nearly doubled the work needed to build each component and pushed developers toward messy interop hacks.

Solution

Engineers built ComposeProxy, a set of interop wrappers that let Composables sit inside XML screens and XML views sit inside Compose screens. This let teams migrate gradually without blocking feature work.

Impact

The interop layer added overhead that actually slowed down scrolling lists. Vinted didn't feel Compose's real smoothness until the wrappers were removed entirely and migration hit 100%.

Their interop wrappers actually hurt performance during migration, hiding the real wins until screens went 100% Compose.

This page summarizes “Vinted is Fully Composed” by Vinted, published Nov 13, 2026. All credit for the original work goes to the authors.

Read the original on vinted.engineering (opens in new tab)

AI tools for Android

Browse all AI tools →