Googlebook's Play Store apps will carry three badges showing desktop readiness

The first thing a new owner does is press the button that lists the apps on their phone ^[5]. Most of those apps were written for a phone, and Android Police reports they scale on the laptop in the standard way ^[12]. No developer has to do anything for that to happen.

Google's three badges sit on top of that behaviour. An app can be marked made for the desktop, optimized for the desktop, or better on the web, and Google approves the top tier itself ^[12][13]. For a team with a roadmap that is a concrete choice: ship nothing and live with the scaled phone build, do the layout work and ask for optimized, or commit to a desktop build and wait in Google's queue. The hands-on is silent on what Google requires for each badge and how long approval takes ^[19].

The badge is a label inside the Play Store, which stays the primary source of apps on Googlebook OS, and Android Police says a dedicated space for big-screen apps does not appear likely ^[11]. Even a team that earns the top badge depends on the ranking that surfaces phone apps, and the same piece calls discovery in the Play Store already a big problem and says it doesn't seem likely much will change in Googlebook OS, particularly for newcomers ^[15].

Gaming gets a number: 20,000 compatible games apparently available at launch ^[14]. Compatible is the floor here, and the tier Google reviews is made for the desktop ^[12][13].

The goal Android Police attributes to Google is to "reinvent the laptop for the Android community" ^[1], and the feature carrying that is continuity. Everything on the phone shows up on the laptop, including searchable files, photos and contacts, with Chrome resuming a browsing session ^[6]. The reviewer called it Googlebook OS's "secret weapon" ^[20] and wrote: "I watched it all being demonstrated several times, and switching between your Android phone and the Googlebook looked seamless, powerful, and hesitation-free." ^[7] The session with all five machines ran an hour or so ^[8]. A handoff repeated for press shows the feature exists. The search uses AI to read file contents, and accuracy there only shows against a real archive of somebody's own files ^[6].

On hardware, Google's requirements stop at aluminum, magnesium and carbon fiber construction, an LCD or OLED touchscreen and a backlit keyboard ^[16]. The differences the reviewer found were the Asus matte screen, the only one among the five, leaving four with other panels ^[17][18]; Dell's XPS as the smallest; Lenovo's as the biggest, because of a webcam module above the screen; and Acer's as the only convertible ^[17].

If your feature's value depends on the user's phone being paired and no desktop build ships this quarter, the measurement that helps is how many of your users carry an Android phone at all, because the scaled build is what everyone else gets ^[12]. Phone-dependent with a desktop build: your time to first completed task rides on Google's handoff working outside a demo room ^[7]. Standalone with no desktop build, better on the web is the accurate badge, and the web app had better be fast ^[12]. Standalone with a desktop build: the approval queue is the cost, and Android Police did not report how long it runs ^[13][19].

Week-two return rates among users arriving on a Googlebook, and time to first completed task on the scaled build against a desktop build, are both answerable from your own telemetry before Google says anything more about badges ^[19].