Supercharging App Startup with HTTP/3: Lessons from Foodpanda
summary
Foodpanda (DeliveryHero) moves app startup traffic to HTTP/3 using Cronet and a custom bridge called okronet that keeps OkHttp APIs. Measured results: 51% improvement in connection times, critical home requests start 4.4x faster, and total response P90/P95 improves ~14.5% / 17.9% respectively across markets. Server changes stay at the edge, 0‑RTT and connection migration are enabled, and the OKronet client library is being open sourced in October.
AI-written summary · about
chapters (7)
- 0:00HTTP/3 and app startup
- 8:31Single HTTP request breakdown
- 16:23HTTP/2 vs HTTP/3 performance
- 23:11Adopting HTTP/3 backend
- 27:25Okronet for Android HTTP/3
- 30:40Foodpanda HTTP/3 impact
- 33:53Q&A
related talks
32mDeploying HTTP/3 at Scale on Mobile: A 17% Startup Latency Gain Despite Implementation Constraints
45mSpeeding up Code, Webpages and Teams
27mTurbocharging the UIs
28mFrom Backend Powerhouses to Web-Friendly APIs: Unlocking
45mSpeeding Up VKontakte’s Network Layer with HTTP/3
20mHTTP/3 in Envoy: End to End Acceleration
49mHTTP/3 and Reactive Streaming
35mOn QUIC, HTTP/3 and tech stack unification
