Product1 publisher3 min readPublished
The Googlebook pitch rests on three features that need an Android 17 phone
The Verge's hands-on describes a laptop meant to do for Android phones what the MacBook does for the iPhone. The handoff, app casting and phone file browsing at the centre of that pitch all require a handset already running Android 17.
The Product Desk · Product desk
What happened
- John Maletis, Google's head of laptops and tablets, said at a press briefing that the Googlebooks were designed to "work seamlessly with your Android phone."
- Googlebook OS sits on Android's codebase, so it runs Android apps without emulation and has full access to the Play Store, with a layout that mostly reads like a Chromebook.
- Setup links the Google account and phone to sync contacts, passwords, settings and payment details, and notifications are shared both ways, with inline replies sent from the laptop.
- Continue On handoff, app casting and phone file browsing all need a phone running Android 17, which today means most Pixels and a handful of flagships from Samsung and other makers.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- constraint The handset fleet is the gate on this purchase. An organisation still on older Android buys a competent machine with most of the pitch switched off until phones are refreshed.
- decision Anyone already running Chromebooks or Windows with Phone Link is deciding whether less friction on features they have is worth new hardware. The answer turns on how often their users actually move files and answer messages across devices.
- contradiction The Verge calls these the first laptops built for Android owners. It also reports that ChromeOS and Windows already do notification sync, credential sharing and a version of handoff, so the delta is access and coverage.
- precedent A ten-year support promise on the laptop sets the expectation that a phone bought years from now still hands off to a machine bought in this launch wave. Google has committed to the older half of that pair.
The ritual Google is aiming at is small, and everyone does it. You upload a file to Drive on the phone, then download it again on the laptop, or you mail it to yourself as an attachment. On a Googlebook, The Verge reports, the paired phone shows up in the file browser alongside the hard drives, and you browse, open, edit and copy from there [8].
Phone file browsing is what I would test first, because it replaces something users do by hand every week. App casting is a different sort of promise. Any phone app opens from a dedicated drawer on the laptop, but the app keeps running on the phone and is only cast across into a floating portrait window, and mirroring the whole phone is not offered [9]. The phone has to be awake and nearby for that window to do anything [20].
Most of the rest already exists somewhere. ChromeOS has synced notifications, shared passwords and payment cards, and streamed or emulated Android apps for years, and Windows does notification syncing, screen mirroring and a basic handoff through Phone Link [12][13]. The Verge's claim for the new machines is narrower than the sales pitch: the features are quicker and simpler to reach, and they work on every Android 17 phone instead of Pixels and a handful more [14].
Count the integration behaviours in the briefing and you get five. Account and settings sync at setup, two-way notifications with inline reply, Continue On handoff, app casting, and phone file browsing [6][7][10]. Three of the five need the phone on Android 17 [19]. The Verge expects Android's fragmented update record to throttle immediate demand for the laptops [11].
Google promises ten years of software support on the machines, and says the core integration set should keep working even when the phone software falls behind [16][15]. The Verge notes the laptop will probably outlast the phone it is paired with [17].
Two questions decide this for a fleet. What share of your users' phones will run Android 17 after the next handset refresh, and how often do those users actually move a file or answer a message across the two devices? Where both are high, the integration is the thing you are buying and standardising is defensible. If the phones are old but the cross-device work is constant, the phone budget comes first. Current phones with little cross-device work leaves you buying a laptop, so judge it on keyboard, screen and price and treat casting as a bonus. Low on both, and this pitch is aimed at somebody else.
All of the above comes from a couple of hours with the first five Googlebooks, from Lenovo, Dell, HP, Acer and Asus, and The Verge's writer ended on a conditional: "I really hope Google delivers on it" [3][18].
What to watch
- How fast Android 17 reaches Samsung and other non-Pixel flagships, since that gates three of the five integrations.
- Whether the Continue On compatible-app list grows beyond the handful that support handoff today.
- Whether reviewers with the machines for longer than a briefing find app casting and phone file browsing hold up in daily use.