Google speeds up Chrome for iOS by using Apple's WKWebView and reduces frequency of crashes by 70%, and launches Data Saver extension out of beta for desktop
Google speeds up Chrome for iOS with Apple's WKWebView, launches Data Saver extension out of beta
Context & Ripple Effects
Google's iOS browser work has been building toward this: a TestFlight-based Chrome beta arrived last November with 3D Touch, and Chrome Remote Desktop landed on iOS a year before that. The move to Apple's WKWebView is the engine-level payoff — Google is trading its own rendering stack for Apple's native one to fix speed and stability on a platform where it can't ship its own engine.
The second half of the announcement closes a loop on the desktop side: the Data Saver extension, which quietly brought data compression to desktop Chrome last March, is now out of beta and a supported feature rather than an experiment.
First-order effects
- iOS users of Chrome get a measurably more stable browser immediately, with crash frequency down 70% under WKWebView, while desktop users gain a production-ready Data Saver compression option.
Second-order effects
- With Chrome now rendering through Apple's engine, Safari's remaining differentiation on iOS narrows to integration and defaults rather than raw page rendering, pressuring Apple to compete on features like the load-time and AMP improvements Google shipped in its own iOS app months later.
Third-order effects
- If the pattern holds, browser competition on iOS shifts from whose engine renders pages to who layers the best performance and safety tooling on top of the platform engine — a contest Google later claimed outright when it said Chrome 99 on macOS beat Safari on WebKit's own Speedometer 2.0 benchmark by 15%.
The trend: Mobile browsers are converging on platform-native rendering engines while vendors differentiate through speed claims, data-saving features, and safety tooling layered above the shared engine.