Building reliable apps when connectivity is unreliable
summary
Chrome's network stack is packaged as a library so apps can use Cronet and its user‑space QUIC transport to survive switching between Wi‑Fi and cellular; a demo shows an Assistant query that loses Wi‑Fi and the Cronet path returns results while the unoptimized path stalls. Apps listed using it include Search, YouTube and Maps, it's on iOS and will be distributable via Play Store, updates every six weeks, and it leverages platform Connectivity APIs and Job Scheduler for failure resilience.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:07Who should care?
- 3:07How to Build Network Resilient apps?
- 3:27What is Cronet?
- 4:10QUIC does what TCP cannot
- 4:23QUIC- Performance highlights
- 4:33Android Optimizations
related talks
22mChrome and Android: Past, Present, Future
10mWhat’s new for web apps in Play
29mDealing with Unreliable Networks
09mWhy and how to optimize your app for ChromeOS
13mZoom on Web: getting connected with advanced web technology
12mOptimize your Android games and apps to run on Chrome OS
39mMobile Networking Challenges - Networking @Scale
35mIs your app really connected?