Google announces Chrome for iPhone and iPad, available today
On stage at Google I/O, Brian Rakowski, Vice President of the Chrome division at Google has just announced Chrome for iPhone and iPad. It's something iOS users have been asking for for a very long time, and plenty of people will be happy.
Context & Ripple Effects
Chrome for iOS lands as one piece of a coordinated Google I/O 2012 push to put Google software on Apple hardware: the same stage saw [[a:none|native Google Drive apps]] promised for iPhone and iPad, and reviewers naming the $200 Nexus 7 the best tablet available at its price point. Brian Rakowski's announcement answers a long-standing request from iOS users who wanted Chrome's sign-in and sync experience outside the desktop.
The story traveled widely on day one — BuzzFeed, AnandTech, Business Insider, AllThingsD, VentureBeat, PC World, ZDNet and Mashable all picked it up — but the framing was already split: AnandTech went straight to benchmarks, while BuzzFeed led with 'The Problem With Chrome For iOS,' signaling that the debate would center on what a Google browser can actually change inside Apple's app-store rules.
First-order effects
- iPhone and iPad users get Chrome's synced bookmarks, tabs and sign-in experience the same day it is announced, ending a long-standing gap between Chrome's desktop footprint and Apple's mobile platform.
- Immediate reviewer scrutiny splits along predictable lines: AnandTech benchmarks performance while BuzzFeed frames the port's limitations, making the launch's success contingent on execution rather than availability alone.
Second-order effects
- With the browser shipping through Apple's App Store under Apple's terms, Google's differentiation against Safari has to come from account-level features like sync rather than anything the platform's rules don't permit — shifting the competitive battleground to services layered on top of the browser.
- The launch sits inside Google's broader cross-platform offensive at I/O 2012 — Drive for iOS, the Nexus 7, the Jelly Bean fragmentation fix — so each Apple-platform client reinforces the others, raising the cost to Apple of keeping Google services second-class on its devices.
Third-order effects
- If the pattern holds, mobile browsers stop competing as engines and start competing as service layers over whatever rendering stack the platform owner allows — leaving Apple holding the structural levers over what 'an alternative browser' can mean on iOS.
- A web-services company building first-party clients on a rival's closed platform tests the limits of nominal versus usable openness: presence in the App Store is not the same as parity with the built-in option, a distinction regulators and competitors alike will keep returning to.
The trend: Google is extending its browser and services beyond Android onto Apple's platforms, probing how much of its ecosystem can function inside a closed app-store regime.