Product2 publishers3 min readPublished
Googlebook launches with its Android integration limited to non-Samsung phones on Android 17
Google's Googlebook laptops launch with phone integration that needs Android 17 and leaves out Samsung phones, even the newest models. Many Android owners therefore can't use the main reason to choose one until Samsung support arrives.
The Product Desk · Product desk
Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction
What happened
- Googlebook is Google's latest bid for the premium laptop market, and Ars Technica says tight integration with Android phones is a key part of that effort.
- When it announced the launch window, Google said the laptops were "engineered to work with your Android phone right out of the box."
- The integration covers app streaming from the phone's display, phone file access, notification sync, instant hotspot and continuing phone tasks on the laptop.
- Googlebook also launched without Slack support, and 9to5Google reports apparent optimization problems for apps running on Intel hardware.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- decision A team with Samsung users has to choose between ordering now and waiting, with only an undated "coming weeks" promise to plan the rollout against.
- constraint Samsung phones that cannot run Android 17 stay locked out even after the promised update, so the fix does nothing for older handsets still in service.
- contradiction Google's launch-window promise and its own support page describe different launches, and buyers who planned around the first received the second.
A Z Fold 8 owner opens a new Googlebook and the laptop finds the phone. Then the phone fails to stay connected, according to early adopters whose complaints Ars Technica reported [8]. Ars says the latest Samsung phones shipped with Android 17 [9], so that owner already meets Google's version requirement. Google representatives confirmed to Ars that the Better Together features are not supported on even the newest Samsung phones [5].
Teams buying these will tell themselves they are getting the laptop for Android users [1]. What a given user gets depends on two gates. The first is the operating system: Google's support page rules out every device on Android 16 or earlier [2]. The second is the phone's maker, and Samsung fails it at launch [3]. 9to5Google wrote that at launch "the vast majority of Android users can't use the platform's best features" [15]. Neither outlet published figures for how many Android phones run Android 17 today, so "vast majority" is 9to5Google's estimate.
Google's message to Samsung owners, as 9to5Google published it, is two sentences: "Support for Better Together features will be rolling out across all Android 17-supported Samsung devices over the coming weeks. Sorry for the inconvenience!" [4]. It sets no date. It also limits the fix to Samsung models that support Android 17, so a Samsung phone that cannot run Android 17 stays outside the integration after the update [13]. Google did not say whether it or Samsung has to ship that update, and 9to5Google reasons that Samsung's side might need one [10].
For a rollout, the useful sort is a grid of the phones your people already carry. One axis is whether the phone runs Android 17. The other is whether Samsung made it. Android 17 on a non-Samsung phone is the only cell that works on day one, and Ars's summary is that for now this means a Pixel [14]. Time-to-value in that cell is pairing the phone, after which app streaming, file access and notification mirroring are available [6]. An Android 17 Samsung waits for the coming-weeks update [4]. An older phone from another maker works only once it gets Android 17 [2]. An older Samsung needs both, and gets neither if it cannot run Android 17 [13].
I'd buy Googlebooks on the strength of the phone integration only for staff already in the working cell. For a team that mostly carries Samsung phones, the purchase today is a laptop purchase, and it should be judged on what the laptop does with no phone attached. The tradeoff of ordering now is support load. Pixel users get the features on day one, and Samsung users report a phone that will not stay connected until the update ships [8].
What to watch
- Which company ships the Samsung update, and whether it lands within the "coming weeks" Google gave.
- Any Google figures on Android 17 adoption, or a compatibility list naming non-Pixel phones that work with Googlebook today.
- Whether Slack support and a fix for Intel app performance arrive on a similar timeline to the Samsung update.