How We Maintain 100 Different Client Versions at Badoo

on YouTube ↗51m

" summary

Badoo runs many projects from a single codebase across iPhone, Android, Web where each platform has a dozen+ concurrent client versions. The talk explains how they handle multiple client versions: evolving the protocol, serving different server-side code per client version, the concept of a “minor feature,” why supporting old clients is acceptable, and how these practices support A/B testing.

AI-written summary · about

" chapters (10)

1. 0:00Badoo introduction
2. 1:29API versioning challenges
3. 8:52Universal API design
4. 13:45Protocol compatibility
5. 20:31Feature toggling benefits
6. 25:51Feature flags vs versions
7. 33:11Development speed impact
8. 40:19Personalized features
9. 44:16Security and flags
10. 47:06Q&A

" related talks

• 31mArchitectural journeyZsolt Kocsi · Android Makers 2019
• 19mVersioning strategy for a complex internal APIKonstantin Yakushev · Nordic APIs Platform Summit 2016
• 24mMobile DevelopmentChad Landis · Product @Scale Spring 2022
• 48mTuenti: From One App to N Apps with the Same CodebaseEduardo González · Codemotion Madrid 2017
• 24mUsing Server Driven UI to rapidly iterate on Android and Across PlatformsLaura Kelly · droidcon Berlin 2018
• 25mFrom 0 to 15 million usersMarcin Pakulnicki · DevWorld 2024
• 43mThe Evolution of Client Development: From the Web to Universal MobilizationPavel Dovbush · HighLoad++ 2015
• 49mWhy developers need statistics, or how to improve product qualityYuriy Lilekov · Backend Conf 2018