My Two-Week Journey with Google Books: Five Major Issues Revealed

The new Googlebooks, a line of laptops powered by Android, have been my mainstay for the last two weeks. My primary focus was on the Acer Googlebook 14, though I also experimented with the Dell XPS Googlebook. Throughout the first week, these devices served as my sole computing tools as I took them on various outings and connected them to external monitors for a range of tasks.

To be frank, the initial experience was less than ideal. Tasks that would typically take a fraction of the time on a macOS or Windows machine proved to demand double the effort on a Googlebook, often leading to frustrating troubleshooting sessions. Several basic features fell short or failed to function altogether. However, my second week brought some changes.

With a series of updates aimed at rectifying early issues with the Googlebook operating system, some of my initial grievances were addressed. I started to integrate the Googlebooks with my other devices while exploring new methods to enhance their functionality. There seems to be potential for this product line, but I’ve identified five significant concerns that would likely deter most users for now.

I want to highlight the “Better Together” functionalities, which stand out as the best aspect of using a Googlebook. These features enhance connectivity between your Android phone and Googlebook. Initially, I faced setup difficulties, especially with Samsung devices. However, I’ve been successfully pairing my Pixel 11 Pro Fold and Samsung Galaxy Z Fold 8 with my Googlebook for seamless use over the past week.

As a frequent user of Google Photos for sharing files, I found Quick Access to be particularly beneficial. This feature allows my phone’s storage to sync automatically with the Googlebook’s Files app, making it easy to access photos, files, and music. It would be even better if this functionality was reciprocal, allowing me to access files from my Googlebook on my phone.

I was impressed to discover the Better Together functionalities work with multiple Android devices. In the Files app, both my Pixel 11 Pro Fold and Galaxy Z Fold 8 appeared as data sources, enhancing usability. Similarly, the Cast My Apps feature lets me stream apps straight from my phone without requiring installation on the Googlebook—something I appreciate.

Most manufacturers don’t develop features with the niche group of tech enthusiasts in mind who regularly use multiple phones. I’m pleased that I can integrate all my Android devices to work seamlessly with my Googlebook. If you’re juggling personal and work devices, this remarkable multi-device integration may significantly influence your buying decision.

Additionally, the Continue On feature is quite impressive. For instance, if I start working in Chrome on my Galaxy Z Fold 8, I can effortlessly transition to my Googlebook to continue without missing a beat.

However, using a Googlebook exposes several limitations. For instance, certain Android apps cannot be accessed via the Google Play Store. I attempted to use the Tesla app through Cast My Apps, but encountered problems with proper rendering, regardless of how I adjusted the app’s window size. The same issue arose with the Best Buy app, which also isn’t available for direct download.

If you’re counting on Cast My Apps for streaming non-optimized applications on Googlebook OS, you might end up feeling let down. Typically, the apps that work well are those that can also be installed natively on Googlebook OS.

As a daily user of Google Authenticator for two-factor authentication, I found it frustrating that the app is unavailable through the Play Store or Cast My Apps on a Googlebook. I needed to resort to my phone, similar to how I would have on a macOS or Windows computer.

One significant drawback of the Better Together features is their dependency on a Wi-Fi connection. While they work flawlessly on a personal network, public or corporate Wi-Fi often blocks peer-to-peer sharing, which can be a hassle when using them outside of home. Typically, people avoid connecting their phones to public networks and prefer to use mobile data.

If utilizing Better Together features requires connecting my phone to public Wi-Fi, the process feels anything but seamless. Apple has addressed this with its Wireless Direct Link technology, which creates a peer-to-peer connection independent of the network, enabling features like AirDrop to function without a Wi-Fi connection.

While I want to fully embrace the Better Together features, they cannot compete with Apple’s integration method until Google resolves this issue.

In light of the incomplete state of Googlebook OS, it would have been prudent for Google to set realistic expectations ahead of its launch. The promotional material claimed Googlebook runs a “desktop-class Chrome browser with extensions.” While this might not be technically incorrect, it’s misleading. The browser used is not the full desktop version but rather an adaptation of the Android app featuring extensions and desktop mode.

Googlebooks operate on a version of Chrome that isn’t comparable to the desktop applications available on macOS, Linux, or Windows. Initial issues with tab management, multi-device synchronization, and the recovering of tasks persisted for quite some time. Although some have been addressed through updates, lingering issues remain for users who adopted them early.

A glance into Chrome settings or the list of Chrome flags quickly reveals that the operating system version of Googlebook is lacking compared to traditional laptop systems. Features like multiple profiles are absent. It’s worth noting that the starting price for a Googlebook is $899, while the highest-end model begins at $1,299.

For years, iPads have offered desktop versions of websites in Safari, and mobile browsers supporting extensions have also existed for a while. Ultimately, the Googlebook OS’s version of Chrome feels underwhelming when placed next to other laptops available within the same price range.

I anticipated solid hardware from Googlebooks, but I was disappointed across the board. Testing the $899 Acer Googlebook 14 and the $999 Dell XPS Googlebook highlighted the inconsistent build quality in comparison to similarly priced MacBooks. The XPS model exhibited creaking sounds and excessive deck flex, while the Acer Googlebook 14 was bulky with outdated bezels.

Inconsistencies were prevalent among the models tested, with both units equipped with mechanical trackpads that I generally avoid. Some Googlebook variants feature haptic touchpads, but this isn’t standard equipment across all models. Additionally, the fingerprint sensors on both laptops were unreliable, often requiring multiple attempts for unlock and frequently timing out, necessitating the use of a passcode. The front-facing cameras fell short of expectations for 2026 as well.

The glowbar’s aesthetic appeal is undeniable, but functionally, it serves little purpose as it always faces away from the user. Its charging indicator lacks any real usefulness beyond being a status light.

Moreover, the chip performance didn’t measure up to expectations. The Qualcomm Snapdragon X Elite in the XPS Googlebook, which I hoped would deliver superior performance based on previous experiences with Windows on Arm devices, turned out to be disappointing with noisy fans and overheating issues. Conversely, the Intel-powered Acer Googlebook 14 unexpectedly delivered a more stable experience, but the Intel Core Ultra 5 is merely a midrange chip.

Over the past two weeks, I found myself restarting these devices far more frequently than I’ve had to restart my Macs in the past year. Clearly, there’s a disconnect between the Googlebook hardware and its Android software.

Given they’re marketed as Android laptops, it’s disappointing that Googlebooks fall short in running Android apps effectively. Perhaps my app choices are unconventional, but many of the applications in my regular use could not be installed through the Google Play Store.

Google categorizes apps based on five compatibility ratings: made for desktop, optimized for desktop, compatible with desktop, better on the web, and built for mobile. So far, I haven’t discovered a single app that genuinely fits the “made for desktop” category.

I attempted to use Luminar, touted as a “made for desktop” photo editing app, but it fails to support basic gestures like pinching and rotating on the trackpad. Adobe’s Photoshop and Lightroom don’t perform at the same level as their iPadOS counterparts, and the Premiere app is not even installable.

Many of Google’s own applications operate as Trusted Web Activities (TWAs) instead of native Android apps. While Google claims that it provides the best experience with this approach, it does not give users the option to choose native apps instead. I am confident that the Android version of YouTube would perform better on the Acer Googlebook 14 in tablet mode than the pre-installed TWA.

The physical function keys of Googlebook keyboards also double as Android navigation buttons. Initially, I thought this was a silly design choice, but I soon realized how essential they became for reliable control of apps via the keyboard and trackpad. The necessity of these keys on a premium device underscores the work that remains for Googlebook OS.

The Linux support within Googlebook OS is a noticeable downgrade from what ChromeOS provides. Currently, Linux apps can only run in the Terminal, without options to save them to the app drawer or taskbar. The Linux Terminal is primarily designed for development purposes rather than running GUI applications. Although it is possible to do so, it offers a far less user-friendly approach compared to Linux support in ChromeOS.

I’m not an avid Linux user—my primary platforms are macOS and Windows 11, and I avoid Linux distros whenever possible. However, with Googlebook OS’s limitations, robust Linux app support is essential to bridge the gaps for applications that lack native compatibility.

My overarching complaints about the lack of app support and compatibility would be alleviated if I could simply install the Linux versions of the problematic applications, as is possible on a Chromebook.

In summary, Googlebooks still feel unfinished two weeks post-release. The straightforward takeaway is that if you have a budget around $1,000 for a laptop, it would be wiser to invest in a MacBook or a Windows device. If you’re contemplating a Googlebook, a Chromebook could potentially meet your needs at half the price.

Ultimately, Googlebooks are more akin to Android tablets with integrated keyboards and trackpads, rather than true laptops. While it is feasible for a Googlebook to replace your laptop, the transition comes with multiple compromises similar to those found with an iPad Pro or Galaxy Tab Ultra.

My sincere hope is that Google continues to refine the Googlebook concept and invests in its future potential, as it’s evident that there is something valuable there, even if it wasn’t entirely ready for launch.