KMP at Vinted: From mission-team bet to mainstream
Mobile Stage
—
45 minutes
Mobile
Real case studies
Kotlin Multiplatform
At Vinted, we don’t adopt technology for its own sake — we adopt it when it helps us move faster, stay consistent, and scale better. In 2026, Kotlin Multiplatform (KMP) moved from a tactical experiment to one of our key architectural bets in mobile.
In this talk, we'll share how we approached KMP through two very different tracks. For Vinted Go, we went all in, building a full KMP application. For the Marketplace, we took a more incremental path, starting with shared business logic while preserving a premium native experience.We’ll walk through the practical playbook behind these decisions: when full-stack KMP makes sense, when a business-logic-first rollout is the better option, and how to make both approaches work within the same company.We’ll also look at the technical foundations that made this possible, including:The power of one: how our iOS umbrella framework helped us avoid binary bloat by sharing a single Kotlin runtime Interop at scale: how we expose shared Kotlin code cleanly to iOS, Web and Android, and what it takes to make async flows, threading, and API boundaries feel natural on all platforms Modularization as an adoption strategy: how we structure shared modules so KMP works both for a full-app setup in Vinted Go and for incremental rollout in the Marketplace The full-app blueprint: how Vinted Go uses a shared-first architecture to keep business logic, networking, and state management aligned across platforms — dramatically reducing double implementation and logic driftThis is a story about more than shared code. It’s about choosing the right strategy for greenfield and brownfield products, standardizing business rules across platforms, and building toward a future where “write once, run everywhere” is practical at Vinted scale.
Read More...
Mohamed Gamal
Lukas Samuolis