By Google killed ChromeOS this week and replaced it with something Android developers have about five months to prepare for. Googlebook — the new laptop category announced May 12 at the Android Show — runs Aluminium OS, a merger of Android 17 and ChromeOS into one unified platform. First devices from Acer, ASUS, Dell, HP, and Lenovo land this fall. Your Android app will run on them by default. Whether it runs well is entirely on you.
What Googlebook Actually Is
Aluminium OS is not ChromeOS with Android bolted on. It’s the inverse: Android 17 as the base layer with a desktop shell on top. The practical result is that Android apps run natively with full hardware access — no compatibility sandbox, no ARC translation layer. You get keyboard support, mouse input, freeform resizable windows, and multi-window multitasking built directly into the OS.
Gemini Intelligence ships as an OS-layer feature, not an app. The most visible manifestation is Magic Pointer: wiggle your cursor on anything on screen and Gemini surfaces contextual suggestions and actions. Google expects apps to expose structured Gemini Actions for this feature, with developer APIs expected at the I/O keynote on May 19. If you’re reading this before then, the window to be an early adopter is still open.
The hardware launches in fall 2026, targeting MacBook Air buyers with premium specifications and Gemini as the differentiator. Five OEM partners means there will be real units in developer hands soon. That’s your clock.
Most Android Apps Are Not Ready
This is the uncomfortable part. Android has over 3 million apps in the Play Store. The overwhelming majority are designed for portrait orientation, touch input, and phone-sized windows. Put them on a 13-inch freeform-windowed laptop and you get one of two outcomes: letterboxing (app runs in a phone-shaped box in the middle of the screen) or compatibility mode (the OS stretches it, looking terrible). Neither is acceptable for an app you’re proud of.
Google is addressing this with a timeline that amounts to a forced march:
- August 2026: Google Play requires API level 36 for all new and updated apps. API 36 enables the system to override orientation and resizability restrictions — meaning Google can force your app to fill the screen even if your manifest says otherwise.
- August 2027: API level 37 required. At this point, full large-screen support — all orientations, all aspect ratios, full resizability on screens 600dp wide or larger — is mandatory with no opt-out.
The hardware ships months before the first deadline. Users on Googlebook at launch will judge your app by how it looks, not by what the API deadline schedule says.
The Three-Tier Quality System That Determines Your Visibility
Google’s Adaptive app quality guidelines define three tiers, and they are not equally visible in Play Store rankings on large-screen devices:
Tier 3 — Adaptive Ready: The minimum. Your app runs full screen in both landscape and portrait, works properly in multi-window mode, and provides basic keyboard, mouse, and trackpad support. No letterboxing, no compatibility mode. Users can complete every task flow.
Tier 2 — Adaptive Optimized: Where most serious apps should land. Responsive layouts that adapt to all window sizes and foldable states. Freeform windowing support. Keyboard shortcuts and navigation. Proper mouse behavior including right-click and hover. This is a design and engineering investment, but it’s achievable in a focused sprint for most apps.
Tier 1 — Adaptive Differentiated: The full desktop-class experience. Drag-and-drop, stylus input, multitasking support, optimized layouts for every screen size tier. This is the level that earns prominent placement in Googlebook-specific Play Store surfaces.
Being below Tier 3 on a Googlebook is effectively being invisible. Start there, then work up.
The Code Changes You Actually Need
Jetpack WindowManager 1.5.0 introduced Large (1200–1600dp) and Extra-Large (1600dp+) window size classes specifically for desktop and connected displays. Using them requires opting in explicitly:
@Composable
fun MyApp(
windowSizeClass: WindowSizeClass = currentWindowAdaptiveInfo(
supportLargeAndXLargeWidth = true
).windowSizeClass
) {
when (windowSizeClass.widthSizeClass) {
WindowWidthSizeClass.Compact,
WindowWidthSizeClass.Medium -> SinglePaneLayout()
WindowWidthSizeClass.Expanded,
WindowWidthSizeClass.Large,
WindowWidthSizeClass.ExtraLarge -> TwoPaneListDetailLayout()
}
}You also need this in your AndroidManifest.xml:
<activity
android:name=".MainActivity"
android:resizeableActivity="true" />That manifest change plus proper WindowSizeClass handling in Compose gets most apps to Tier 3 in a few days. Tier 2 requires a proper two-panel list-detail layout for expanded and large breakpoints — more design work, less code work. Tier 1 is a deliberate product decision, not a sprint item.
Test It Now, Not in September
Android Studio Canary ships a desktop emulator that accurately simulates Googlebook: window resizing, multi-instance behavior, keyboard and mouse interactions. The stable channel does not have this yet. If you’re waiting until you can borrow hardware, you’re wasting five months of lead time you have right now.
Download Canary at developer.android.com/studio/preview. The emulator is the fastest path to seeing exactly where your app breaks on a desktop form factor. It will break somewhere — the question is whether you find it in May or your users find it in October.
The Opportunity Most Developers Will Miss
The community reacted to Googlebook with the expected mix of skepticism and hardware-failure-of-Android-on-tablets fatigue. That skepticism is reasonable. But it’s also the reason there’s an opportunity here: most Android developers will wait until the last minute, ship the minimum, and fight for visibility on a new platform where nobody has established dominance yet.
The Gemini Intelligence integration surface — apps exposing structured actions to the Magic Pointer — is currently unoccupied territory. The developer APIs aren’t finalized yet, but apps that move fast on adoption will have months of head start on discoverability before the platform is crowded. Google’s official Googlebook developer page already has guidance on adaptive quality tiers and the Canary emulator workflow.
Google has made promises about Android on laptops before. This time the execution is different: five premium OEM partners, direct MacBook Air competition, and Gemini as a genuinely differentiated OS-level feature. The skepticism is understandable. The preparation is still worth doing.
