The Mobile Apocalypse
You shipped a breaking API change. Thousands of mobile users are crashing on launch.
The Scenario
A new API version was deployed that breaks backward compatibility with the mobile app. Unlike web, you can't force users to reload - there are thousands of users on the old app version. The app crashes on launch because it can't parse the new API response format. You need to fix the API without breaking it for users on the new version.
What You'll Learn
Why mobile API versioning is different from web
Diagnosing breaking changes from crash reports and API logs
Implementing backward-compatible API responses
API versioning strategies: URL, header, content negotiation
Tools You'll Use
Real-World Context
Twitter, Instagram, and Uber have all shipped breaking API changes that crashed mobile clients. Mobile API versioning is one of the hardest problems in production engineering.
Ready to debug this?
Free account required - sign up with GitHub or Google in 10 seconds
Play The Mobile Apocalypse