Googlebook Answers Some Questions, Raises Others ⭐️

I’ve been obsessed with Google’s decision to bring Android to laptops since the first rumors, and this week we finally learned key aspects of its go-to-market strategy. But as is always the case with an announcement not accompanied by an actual product to inspect, I have questions.

Note: Everything written here is based on a prebriefing from before today’s GoogleGook announcement. It’s possible that the live show will reveal some additional information. In fact, I’m kind of counting on it, given all the questions I have. –Paul

📜 How we got here

It’s not worth going through the entire history of Google’s client operating systems. But there are two key milestones to understand here: Google essentially has two client OSes today, Android and ChromeOS.

Android is a mobile platform that competes with but is more open than iOS. And ChromeOS is something completely different, a lightweight desktop platform with a Linux core, a full desktop version of Chrome, Android app compatibility, and, perhaps most confusingly, a full but non-native Linux environment that runs in a virtual machine (VM) instead of natively on the deivce.

Android is by far the more popular and more versatile of the two, as it works on smartphones, including foldables, and tablets, and it’s been adapted to run on smartwatches and other wearables (as Wear OS), on smart TVs (as Google TV), in cars (as Android Auto), in virtual/augmented reality (now, as Android XR), and probably other places I’m forgetting.

ChromeOS, meanwhile, typically only runs on Chromebooks, which are laptops, though there is a tiny market for mini-PCs, called Chromeboxes. It has seen some success with education and, less obviously, in business, thanks it part to management simplicity and low costs. But Google has also expanded ChromeOS to premium laptops with Chromebook Plus and, much less successfully, to gaming laptops as well. (There is also a way to install a subset of ChromeOS on existing Windows laptops called ChromeOS Flex.)

Android’s expansion into larger screen devices via foldable smartphones, tablets, and Chromebooks (and Android Auto, actually) led to Google adding (and now requiring) sophisticated adaptive app capabilities from developers. That is, instead of simply “upsizing” a phone app to stretch out and fill the screen on a larger device, Android apps can optimize their look and feel dynamically. This includes adaptive layout capabilities and support for keyboards, mice, touchpads, and other external input devices, among other advances. As is the case with the iPad, especially with iPadOS 26 and newer, Android is becoming a lot more sophisticated and is suddenly edging decidedly into use cases that previously required ChromeOS or some other “real” desktop OS.

Which led to what’s happening now. Google already has ChromeOS, and it’s done an impressive job of keeping that platform simple, capable, and usable. But Android is far more popular, which means it gets faster and broader support from app developers, but also hardware and component makers that require drives for their devices. Given this reality, Google has rethought the relationship between Android and ChromeOS: It’s nice that Android apps can run on ChromeOS, but Google decided to go even further by replacing key core parts of the ChromeOS technology stack with Android. By having a single core technology stack, ChromeOS would benefit from all the driver work that happens on Android immediately.

It wasn’t long before the obvious rumors began, that Google would fully move ChromeOS to Android, meaning it would undergo a multiyear transition of the ChromeOS technology stack to make it yet another Android variant so it could more fully benefit from the advantages of that ecosystem and, hopefully, complete better against Apple’s dominant iPad.

And then something unexpected happened: Google hinted that it was doing just that. And then it confirmed the news, stating multiple times, if vaguely, that it was “combining” Android and Chrome OS. And then, finally, that it was bringing Android to laptops. Given the lack of clarity, this was as confusing as it was fascinating. For now, Google says that it is “super committed” to ChromeOS, but it’s possible, perhaps inevitable, that Android–through an effort codenamed Aluminum OS–will simply replace ChromeOS in time.

Today, we learned more. As noted, I still have questions. And I have a few theories as well.

📢 What Google announced

Today during its pre-Google I/O 2025 “The Android Show” presentation, Google announced Googlebook, which sounds like the name of a new first-party PixelBook laptop but is in fact the go-to-market brand for Aluminum OS. Meaning, we will see third-party Googlebooks, just as we see third-party Chromebooks. And from all five of the top PC makers, Lenovo, HP, Dell, ASUS, and Acer , are onboard.

Googlebook is a “modern OS,” Google says, one that addresses an industry-wide shift to AI by transitioning Android from a mobile platform to being an “intelligence system.” This is, the company says, “an opportunity to rethink laptops again.”

This new category of laptops will be “powered by premium hardware,” Google says, suggesting a Chromebook Plus-like positioning (and pricing). They are built around Gemini Intelligence, Google says, and will “deliver personal and proactive help when you need it.”

There is some interesting innovation here. Google is rethinking the mouse cursor for the AI era in Googlebook, for example, via what it calls the Magic Pointer. You can wiggle this new, more capable cursor to enable the Magic Pointer and then get “contextual suggestions” about whatever you point at. A “Select anything to ask Gemini” pop-up appears, attached to the cursor, and then you can select one or multiple items in turn and type a prompt right there, in-line.

Googlebooks will also use AI for a Create Your Widget feature that looks exciting: Instead of relying on whatever widgets that Google and third-party app makers provide, you can use this feature to create your own custom widgets that do whatever you want, based on information online and the apps in the system. This might be thought of as an entry-level vibe coding solution, and I suspect people will come up with amazing and powerful widgets using it.

Googlebooks will of course integrate deeply with Android phones. Granted, Google already does this with ChromeOS–but not, sadly, with ChromeOS Flex–and some of the features it announced, like the ability to remotely run a phone app on the laptop already exist today. But there is one interesting new feature, Quick Access, which lets you view, search, or use your phone’s files directly from a Googlebook without having to transfer them first.

Google says that the first Googlebooks will come via the PC makers noted above. We don’t have any details yet, but these new laptops will be “built with premium craftsmanship and materials” and “come in various shapes and sizes.” Each will feature a “glowbar” on the outside of the display lid that will serve as a colorful and unique identifier of the platform customers are using.

Speaking of which, while Google’s announcement doesn’t address this, the prebriefing I had and some accompanying photos and videos shed some light on what these laptops will look like. Thin-ish is what I’m thinking.

There’s also a prominent fingerprint reader in one shot, next to the very unlucky F13 key.

Some ports, including a legacy HDMI video-out port, in another.

And, finally, a bit of branding.

⁇ What Google didn’t say

Google’s Googlebook announcement is just a “sneak peek.” But it’s important to put what we know (and don’t know) in perspective.

When you think about ChromeOS today compared to Android, some key differences emerge. Most Chromebooks run on x86 chipsets instead of the Arm-based platforms used by basically all phones and tablets. ChromeOS offers a full-featured Chrome web browser and not the more limited mobile version in Android. ChromeOS and Android are both “based on” Linux, but neither is Linux, and the ChromeOS implementation of Linux is virtual, not native.

When you think about Android replacing ChromeOS, then, some key concerns emerge. And here, we can only read between the lines.

Googlebooks have to run on Arm, not x86. Googlebooks won’t just run Android apps, they will be Android, and thus these new laptops have to be Arm-based and not saddled with all the issues that still dog the x86 platform. This alone makes Googlebook interesting.

It’s not clear which Arm chipset(s) that Googlebooks will use. Qualcomm is dominant in smartphones and has the leading presence in tablets, but MediaTek is big, too, and it’s been evolving its own desktop-class Arm chips for Chromebooks for years. My guess is that we will see Googlebooks based on chips from both companies, and from others. But which ones? On the Qualcomm side, will there be Googlebooks based on phone/tablet chips? Snapdragon X PC chips? Both?

Which version of Chrome will we get? To me, the key usability advantage of ChromeOS is that it runs the full desktop version of the Chrome web browser. And I feel very strongly that Googlebooks need that web browser, too, and not just the Android mobile version. In its announcement post, Google says that Googlebooks will ship with “the world’s most popular browser,” which is Chrome. But that doesn’t mean it will be desktop Chrome. UPDATE: During the live event, Google explicitly said that Googlebooks will get the full Chrome desktop experience with extensions. Nice!

And what about Linux? Another key ChromeOS advantage is that you can install a virtual Linux environment, giving you the ability to run graphical Linux apps in addition to the Linux-based terminal with its command line apps. Google never mentions Linux in its Googlebook announcement, but Android 15 and higher feature an optional Debian Linux-based terminal, just like ChromeOS, so this feels likely. Perhaps it’s something that evolves over time, as it did in ChromeOS.

When will Googlebook replace ChromeOS fully? Googlebook is described as a “premium” experience with “premium hardware and design,” which suggests that its first victim will be Chromebook Plus. But I do expect Googlebook to replace ChromeOS at every level in time, and it’s impossible not to imagine the sub-$200 education laptops of the future running on lower-end Arm chips. This feels inevitable.

How much will these things cost? A year ago or more, a premium laptop experience meant something in the $800 to $1200 range, but given the component crisis it’s difficult to know where Googlebooks will land. Also not clear is whether the minimum system components will be similar to what we see on Chromebook Plus (or, for that matter, Copilot+ PC) at launch.

What about a new PixelBook? Google didn’t announce a new PixelBook laptop running on Googlebook but … come on. It has to happen. Perhaps we will learn about this imagined new product at Google I/O next week or this fall when Google announces its Pixel 11-series devices.

Will there be a Googlebook Flex? ChromeOS Flex is interesting because it can save existing but out-of-support Windows 10-era laptops from landfills, but it’s also too limited, with no support for Android apps or Android phone integration. Will we ever see a Googlebook Flex? If you believe that Googlebook will be Arm only, as I do, then no, certainly not immediately. But if Googlebook also runs on x86, then, yes, that’s a possibility.

Despite the questions, I’m excited about Googlebook and can’t wait to learn more. Hopefully, we won’t need to wait long.