This is why Googlebooks will be better than MacBook Neo

Google’s latest attempt at creating premium laptops is here, and they’re called Googlebooks. Silly name aside, Googlebooks looks set to strike the right balance between the versatile ChromeOS ecosystem and the premium design of the now discontinued Pixelbooks.

In short, Googlebooks are mobile computers in premium chassis designed for basic tasks. Where have I heard that before? The same description applies verbatim to Apple’s new MacBook Neo. Considering that Googlebooks are priced the same as the MacBook Neo (I guess they have to be to compete), these brands are set to go up against each other later this year.

I’ve used a lot of macOS and Windows machines over the past few years, powered by Apple, Intel, AMD, and Qualcomm Snapdragon processors at every price point. Budget and mid-tier laptops running macOS and Windows seem to have one thing in common: They provide the illusion of flexibility and versatility by offering full desktop app support. In theory, a cheap MacBook Neo or similarly priced Windows laptop should support plenty of desktop apps. However, this does not mean that the hardware is powerful enough to run them well.

I’m skeptical of the MacBook Neo, and my hesitation has nothing to do with the laptop’s raw performance. By all indications, the Apple A18 Pro chip inside outperforms the M1 chip in single-core tasks. My concern is the minimum 8GB memory and only 256GB or 512GB onboard storage. I used a Mac mini with an M2 chip, 8GB of RAM, and 256GB for a whole year, and it didn’t run properly. My application memory frequently ran out, which meant the operating system would lock up, and I had to force-quit apps to make my computer usable again.

Remember, the M2 chip in the Mac Mini I own is typically faster than the A18 Pro chip in the MacBook Neo. The Mac mini’s chassis is also better for airflow and, unlike the MacBook Neo, it has a fan. In other words, if I had problems with the Mac mini, the MacBook Neo could be even worse.

It’s not just me – many macbook users There have been reports on Reddit about running out of application memory on systems with 8GB of RAM. This is an issue that will get worse over time, as macOS uses free SSD space as virtual memory to compensate for physical integrated memory limitations. When your SSD fills up in a year or two, the MacBook Neo will have less virtual memory to use, and you’ll start to feel the memory limitation.

You may be wondering why macOS and Windows laptops struggle with 8GB of RAM, but Android and ChromeOS devices perform excellent with fewer gigabytes of memory and generally weaker hardware. The simple explanation is that Android and ChromeOS are designed with low-power devices in mind, and ChromeOS in particular offloads processing to the cloud whenever possible. Googlebooks will take a similar approach, and it may help them perform better than similar macOS or Windows laptops with similar or weaker hardware.

Googlebooks are built on the Android technology stack and should have the same software capabilities as Android tablets and Chromebooks. This may seem like a limitation at first, but it doesn’t have to be.

For one, Google wants Android to become the operating system powering your phone, watch, tablet, car, and laptop — it’s billed as an integrated “intelligence system” connected to Gemini Intelligence. Presumably, this means that Google is focused on ensuring that Googlebooks provide a laptop-class computing experience.

It will do this in a few ways, such as enhancing the traditional cursor experience with a Gemini-powered magic pointer that dynamically adapts with contextual suggestions when using Googlebooks. It will also bring Android features to the desktop version of the OS, such as the recently announced Create My Widget tool. Smart connections with your other Android devices is the name of the game, as Quick Access will connect Googlebook’s file browser to your phone’s files without manual transferring or sharing. The integration between Android phones and Windows 11 with Microsoft’s Phone Link is nice, but Googlebooks should make a perfect pairing.

I find Android to be the best feature of Googlebooks. To date, Android apps have not been on par with their desktop counterparts. In fact, many iPadOS apps are more fully featured than their Android counterparts. I’ve found that the default Chrome browser lacks desktop webpage support on foldables and tablets. I imagine some of these limitations will be addressed when Googlebooks launches, but it seems safe to assume that these laptops will primarily run Android and/or ChromeOS apps. Even if Linux app support existed, I doubt Googlebook’s target audience could tinker with it.

Reframe your thinking, and Android on a laptop doesn’t look so bad. A desktop operating system is more versatile when the hardware is powerful enough to handle it. If the Googlebook market is made up of budget and mid-tier laptops, Android may prove to be a more stable and enjoyable OS to use. You can easily overwhelm a MacBook Neo with demanding apps and workflows, but Android apps on the Googlebook are already optimized for low-powered hardware. Running mobile apps designed to run on the hardware you have is usually better than trying to use intensive programs that want more memory or processing power, and that’s why Googlebooks and Android will win.

This is all a bit speculative because we don’t know what hardware Googlebooks will actually introduce until later this year. I’m assuming it will be comparable to the premium Chromebook Plus models and the MacBook Neo in the same class, but that remains to be seen.

The biggest question mark is the price. Googlebooks can’t exceed $700 if they want to capture the budget and midrange segment – ​​the price of a MacBook Neo with 512GB of storage and Touch ID. The emphasis on premium materials confuses me, as it would be difficult to sell an Android-powered laptop at a price close to $1,000.

That said, if Googlebooks lands in the same territory as the MacBook Neo, they’ll become a better choice for students and casual users. The problem with ChromeOS was never really the software, but rather incompatible hardware. Googlebooks is well-positioned to offer more reliable hardware than Chromebooks while maintaining the same solid software approach, and I’m here for it.