Kick your 3rd party networking library to the curb
summary
Argues that modern iOS networking can ditch AFNetworking by rebuilding an API client with URLSession and Codable, cutting a 40‑line request to a few lines and estimating the rewrite as a few weeks of work. Claims ownership reduces long‑term cost, shows a bridge pattern to swap hundreds of endpoints over a year, and uses a server-driven toggle to roll back incidents quickly. Cites scale (over 2.5 billion activities, ~45 million athletes, ~25 uploads/sec) as motivation and evidence it works.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:26Connect athletes to what motivates them and help them find their personal best.
- 0:422.5B activities
- 2:38Networking is at the center of the applications we build
- 2:50Would you ever go 5 years without buying a new pair of shoes?
- 3:46Story time Chapters 1. Setting the stage
- 4:09Setting the Stage Chapter 1
- 4:44Last major changes are made to Strava API client on iOS
- 6:56What is the time investment to build and maintain this ourselves?
- 8:21Do we still need a 3rd party library for networking?
- 8:511. Cost of ownership has significantly decreased
- 10:19Simple interface for making a request Usability
- 11:26Many individual components with a single responsibility Extensibility
- 13:50Thoughtful interface design and protocols go a long way Testability
- 15:38Slowly divert traffic from the old bridge to the new one
- 17:16Solution: Server-driven toggle
