Reactive programming for massive mobile multiplayer games
summary
An in-device ad SDK for mobile games combines waterfall sequencing and real-time bidding across about 20 providers using reactive libraries (RxJava/RxSwift via Kotlin/Swift ports). It implements timeouts, retries, and parallel requests with declarative operators, treats the client as a lightweight backend, runs unit and integration/device tests, supports 60+ game titles and millions of daily users, and reports reduced callback complexity while meeting strict latency and battery constraints in production.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:05Wild Life Studios
- 3:14Game architecture
- 5:25Ad SDK challenges
- 7:11Monetization models
- 9:24Combining models
- 10:48Key design principles
- 13:31Multiplatform architecture
- 14:33Mobile technical challenges
- 15:39Reactive programming
- 17:03Reactive tools used
- 18:47RxJava example
- 22:38Benefits of reactive code
- 23:41Architecture layers
- 24:46Game integration
- 26:10Summary
- 27:14Q&A
related talks
17mBuilding a Long-term Gaming App Business: Applying Lessons of the Past to Power Your Success
52mBuilding Reactive Apps
40mReactive programming: lessons learned
41mThe definite guide to reactive programming in Java
24mRefactoring your app in Rx
23mWhy Reactive Programming?
20mHow to run Mobile Games as a Service for Decades? Introducing Beacon
45mReal-Time Multiplayer on Android: Lessons from NYT Crossplay