安卓是谷歌图书最令人又爱又恨之处Android is the best and worst thing about Googlebooks


AI free token/AI免费积分
安卓是谷歌图书最令人又爱又恨之处

科技报道:Google Android 是 Googlebooks 最好也最糟的地方

作为一个 Android 忠实用户,我希望爱上 Googlebooks——但它们并没有让我感到轻松。

多米尼克·普雷斯顿,2026年10月12日,下午2:00(UTC)链接分享送给我我一直在测试两款 Googlebooks:这款华硕型号,还有惠普的。

科技报道:Google Android 是 Googlebooks 最好也最糟的地方

作为一个 Android 忠实用户,我希望爱上 Googlebooks——但它们并没有让我感到轻松。

多米尼克·普雷斯顿,2026年10月12日 下午2:00 UTC | 分享 | 礼品 | 多米尼克·普雷斯顿是一位新闻编辑,拥有超过十年的新闻从业经验。他曾任职于 Android Police 和 Tech Advisor。我使用这两款搭载 Android 系统的笔记本电脑的第一周可谓困难重重,和许多人一样磕磕绊绊,但我逐渐开始喜欢它们了,尽管离"真爱"还有一段距离。每一个让我印象深刻的瞬间,都得益于 Android——无论是访问实用应用的原生版本,还是直接从笔记本的用户界面快速查看手机通知。

但说实话,有时候它们真的很糟糕。

手机连接时断时续,应用投屏体验别扭,文件共享功能简直完全坏了。而这还只是Googlebook与手机之间的交互问题——关于在一台1000美元笔记本电脑上运行原生Android应用的种种局限,我还有更多牢骚要发。

如果Googlebook能成功,Android将会因此获益;但如果全盘皆输,Android也难逃其咎。目前看来,成功似乎比失败还要遥遥无期。

Googlebook的设置流程完全基于安卓系统。它的设置同样快速,从头到尾只需几分钟,包括注册生物识别登录、登录Google账号,以及连接到手机以查找应用和备份数据。在我测试的华硕和惠普两款机型之间,具体的设置过程略有差异,但主要区别在于它是默认安装手机上所有应用,还是仅安装桌面优化版的应用。

然而一旦进入操作系统,体验就会变得卡顿。即便使用搭载 Android 17 的手机来设置这台笔记本电脑,之后也很可能无法维持连接,导致文件共享和应用投屏等功能失效。要将我的任一台 Googlebook 与手机完成完全配对,都需要在两台设备上反复切换跨设备设置选项,经历多次重启,偶尔还得祈祷一番,设备才能彼此识别。切换到新的 Wi-Fi 网络会让我再次遇到连接问题,必须重启 Googlebook 才能让设备重新通信——而且它们确实需要处于同一 Wi-Fi 网络下,同时开启蓝牙,所以断网状态下也无法建立连接。

我的华硕谷歌笔记本如今已与一台我一直在评测的OPPO手机建立了相当稳定的连接,尽管它仍然拒绝识别任何其他手机;我的惠普型号则在那台OPPO和vivo X Fold 6之间来回切换,偶尔会同时连接两台。昨天,这是我本周首次成功连接我的Pixel 11 Pro Fold,而这两台笔记本电脑在先前好几天里都顽固地无视这部手机——尽管它本就是谷歌自家的硬件。

我一直很喜欢Googlebook体验中的某些方面。能够以快捷、紧凑的桌面版形式访问我平时只能在MacBook上用网页浏览器打开的那些应用,真是太棒了。更令人惊喜的是,其中一些应用在移动版上还有不同的功能:能够从HBO Max或Netflix下载剧集并离线观看,这意味着一台Googlebook或许就能取代我的Android平板——而目前它基本上只是一台我在飞机上看电影的专用设备。

但还有多得多的应用在 Android 笔记本上用起来令人头疼。有些没有桌面优化版本——Slack 的移动版在桌面环境中确实完全不可用,而 Adobe 的 Android 应用只是其桌面版的黯淡影子。另一些在 Play Store 中声称“Optimized for desktop”,但实际上这通常意味着它们只是把界面拉伸以适应桌面尺寸,并加入了基本的鼠标和键盘支持——“基本”才是关键词,因为大多数应用不识别右键点击,或者偶尔会切换到竖屏视图。“Made for desktop”似乎才是 Play Store 中唯一真正有价值的标签,而我只在少数几个应用上见过它。

即便是 Google 自家的应用,也常常受到限制。Chrome 的问题最为严重,因为你很可能会频繁使用它。Google 坚称这是浏览器的桌面版,但它在功能上并不与其他平台对等:不支持切换个人资料、在分屏视图中打开标签页,或创建自定义搜索引擎快捷方式。这些只是我在日常 MacBook 工作流中遇到的遗漏,无疑还有无数其他问题。

尽管谷歌承诺 Chromebook 提供“整个 Play Store 应用库”,但这并不完全属实。我已经遇到了两款根本无法从 Play Store 安装的应用——Bluesky 和登录授权工具 Okta。这也不是 Intel 的问题,正如谷歌周一所暗示的那样:基于 Arm 的 HP Googlebook 同样无法运行这两款应用。

我对笔记本电脑的需求并不复杂:我在办公用 MacBook Air 上 90% 的时间都在 Chrome 和 Slack 中度过,其余大部分时间则用于 Photoshop 或 Lightroom。但目前这四款应用在 Googlebook 上的表现都不尽如人意,而这一切都因为它们本质上都是 Android 应用,无法与真正的桌面版替代品相竞争。

如果笔记本电脑上的 Android 应用还不够,Googlebook 还支持将手机上的 Android 应用投射到笔记本电脑上。

某种形式的 Android 应用投屏或镜像功能此前已在 Windows 和 Chromebooks 上出现过。Google 这一实现方式的不同之处在于,它不是镜像整个手机界面,而是投屏特定应用,既可以通过任务栏中的专用应用抽屉完成,也可以通过点击从手机同步过来的通知实现。这些应用仍在手机本身上运行——手机会收到应用正在投屏的通知——但可以通过 PC 进行控制。

它并不适合流媒体音乐或视频,也不适合同时运行多个应用,但这似乎本来就不是它的设计目标。投屏功能的真正优势在于,无需拿起手机并解锁,就能快速进入某个应用,例如在结算应用 Splitwise 中更新付款信息,或在 WhatsApp 中快速发送消息。我非常享受从笔记本电脑上快速切入和退出手机任务的感觉,同时还能降低被 Instagram 分心的风险。

投屏功能很巧妙,大部分情况下也能良好运行,但我认为它之所以对我有用,是因为我刚接触 Googlebook,还没有把所有应用都设置好。Google 认为,它的设计初衷是让你可以在笔记本上使用某些应用,却不想把它们安装到笔记本上,但这样的应用清单相当短,尤其是考虑到安装 Android 应用通常很快、很轻松,而且对存储空间的占用也很小。从长远来看,我不确定在可以直接安装原生版本的情况下,我会有多频繁地想要投屏移动应用,尤其是在原生应用和投屏版本之间无法复制粘贴,或者投屏时无法访问 Googlebook 文件系统的情况下。

本文来源:https://www.theverge.com/tech/1008750/googlebooks-android-best-worst-notifications-app-cast-file-sharing
若有版权问题,请来信告知:13951431913#139.com 或在右方提交评论。

Dominic Preston Oct 12, 2026, 2:00 PM UTCLinkShareGiftI’ve been testing two Googlebooks: this Asus model, and HP’s too.Tech Report Google Android is the best and worst thing about GooglebooksAs an Android devotee, I want to love Googlebooks — but they don’t make it easy.

Dominic Preston Oct 12, 2026, 2:00 PM UTCLinkShareGiftDominic Preston is a news editor with over a decade’s experience in journalism. He previously worked at Android Police and Tech Advisor.My first week with the new Android-powered laptops has been about as rocky as anyone’s, but I’ve slowly learned to like them, even if love still feels a ways off. Every moment that’s impressed me has been thanks to Android, whether I’ve been accessing a native version of a useful app or quickly checking my phone notifications from the laptop user interface.

But man, sometimes it just sucks.

Phone connectivity is flaky, app casting is awkward, and file-sharing seems to be flat-out broken. And that’s just the interaction between a Googlebook and a phone — I have a whole other set of gripes about the limitations of native Android apps on a $1,000 laptop.

If Googlebooks ever become a success, Android is going to get the credit. But if it all goes wrong, that’s exactly where the blame will lie too. So far, success feels a lot further away than failure.

The Googlebook setup process is Android through-and-through. It’s similarly quick, just a few minutes from beginning to end, including time to register biometric logins, log into a Google account, and connect it to a phone to find your apps and backups. There’s a little variation in the exact setup between the Asus and HP models I’ve been testing, but mostly just whether it defaults to installing every app from your phone or only the desktop-optimized ones.

Things get janky once you’re into the OS, though. Even if you use an Android 17 phone to set up the laptop, it’s unlikely to remain connected afterwards for features like file sharing and app casting. Fully pairing either of my Googlebooks to a phone has required toggling cross-device settings on both devices, multiple restarts, and the occasional prayer, until the two devices find each other. Moving to a new Wi-Fi network broke things for me all over again, requiring a restart of the Googlebook to get the devices back talking to each other — and yes, they need to be on the same Wi-Fi network to talk, and to have Bluetooth enabled too, so the connection won’t work when you’re offline.

My Asus Googlebook has now formed a pretty reliable connection to an Oppo phone I’ve been reviewing, though it still refuses to recognize any other phones; my HP model flits between that Oppo and the Vivo X Fold 6, occasionally connecting to both at once. Yesterday, for the first time all week, it connected to my Pixel 11 Pro Fold, after both laptops had stubbornly ignored that phone for days — even though it’s Google’s own hardware.

I’ve loved elements of the Googlebook experience. It’s great being able to access quick, compact, desktop versions of apps I’d normally be stuck using through a web browser on my MacBook. It’s even better that some of those apps have different functionality for being mobile versions: being able to download series from HBO Max or Netflix and watch them offline means a Googlebook could replace my Android tablet, which is mostly just a device for watching movies on planes at this point.

But many, many more apps are a headache to use on an Android laptop. Some don’t have desktop-optimized versions — the mobile version of Slack is truly unworkable in a desktop environment, and Adobe’s Android apps are pale shadows of their desktop selves. Others claim to be “Optimized for desktop” in the Play Store, but in practice that usually means they’ve stretched the UI to fit a desktop scale and included basic mouse and keyboard support — “basic” being the operative word, with most not recognizing right-clicks or occasionally shifting into a portrait view. “Made for desktop” seems to be the only Play Store tag that really counts for much, and I’ve only seen it on a handful of apps.

Even Google’s own apps are often limited. Chrome is the worst offender, since you’re likely to use it so much. Google insists this is a desktop version of the browser, but it lacks feature parity with other platforms: there’s no support for switching profiles, opening tabs in a split view, or creating custom search engine shortcuts. Those are just the omissions I’ve run into from my daily MacBook workflow, and there are no doubt countless more.

And despite Google’s promise that Chromebooks offer the “entire Play Store library,” that isn’t entirely true. I’ve already run into two apps that I simply can’t install from the Play Store — Bluesky and the login authorization tool Okta. It’s not an Intel issue either, as Google alluded to on Monday: the Arm-based HP Googlebook also won’t run either app.

My laptop needs aren’t complex: I spend 90 percent of my time on my work MacBook Air inside Chrome and Slack, and most of the rest in Photoshop or Lightroom. But all four are subpar on a Googlebook right now, and it’s all because they’re fundamentally Android apps that can’t compete with true desktop alternatives.

If Android apps on your laptop aren’t enough, Googlebooks also let you cast the Android apps on your phone to your laptop.

Android is the best and worst thing about Googlebooks

Some version of Android app casting or mirroring has been around before on both Windows and Chromebooks. The difference in Google’s implementation is that instead of mirroring the whole phone UI, you cast specific apps, either through a dedicated app drawer in the taskbar or by tapping into a synced notification from your phone. Those apps still run on the phone itself — which gets a notification that an app is casting — but are controlled via the PC.

It’s not well-suited to streaming music or video, or running multiple apps at once, but that doesn’t seem to be the intent anyway. Where casting shines is in quickly dipping into an app without reaching for your phone and unlocking it, like updating a payment in the settlement app Splitwise or sending a quick message in WhatsApp. I’ve really enjoyed being able to dive in and out of a phone task from my laptop, while minimizing the risk of getting distracted by Instagram.

Casting is clever and mostly works well, but I think I’ve found it useful because I’m new to the Googlebook and haven’t set every app up yet. Google argues it’s designed for apps you might want to use from your laptop but wouldn’t want to install there, but that’s a pretty short list, especially given that installing an Android app is generally quick, painless, and a minimal drain on storage. Long-term, I’m not sure how often I’d want to cast a mobile app when I could just install a native version, especially since you can’t copy and paste between native apps and cast versions, or access the Googlebook file system when casting.

Even when the cross-device connection runs smoothly, some apps — especially secure ones like my authorization app or banking app — won’t run. Others try to open but don’t work: my credit card app breaks on bootup, while Bluesky renders text illegibly. Casting some apps even create rendering issues when I next open them back on the actual phone.

Then there are the other problems.

Continue On lets you start a task on your phone and pick it up on the Googlebook. It’s great when it works, but that’s rare. Only a handful of apps are supported, and even those trigger inconsistently. It works when I open a Google Drive document, but only sporadically in Gmail, and so far never for Calendar.

Notifications are powerful, but messy, with phone and laptop notifications mixed together. Phone notifications open via app casting, but the system gets confused easily. For various reasons, right now my Slack notifications open a casted phone app rather than the native Googlebook app; WhatsApp notifications don’t come through even from my phone; and I can either get notifications for my work Gmail account or my personal one, but not both at once.

File transfer is entirely broken. While I can see my phone’s storage as a drive inside the file manager, accessing those files is near-impossible. It can take minutes to load up the file system, and minutes more to open or transfer a single 5MB photo. It’s completely unusable. This should be fixable, at least. Quick Share — Android’s equivalent to AirDrop — is also supported, and the same files that take minutes over file transfer share in seconds with Quick Share.

It’s the Googlebook in a nutshell: the idea is wonderful, the execution entirely lacking. A week in, I’m learning to work around the kinks and headaches of this odd little OS, finding ways to make the most of it and to maximize those moments when my laptop and my phone just work together. When it clicks, it feels like the payoff to a decade and a half of using Android every day.

Right now, that feeling doesn’t hit nearly as often as it needs to, and certainly not enough to make up for the countless times Android just feels broken in this form factor. The question is whether Google — a company with a deserved reputation for giving up when the going gets tough — has the commitment to see this through and turn things around. It’ll need its own teams to fix what’s broken, third-party developers to pledge support en masse, and a rethink of how to integrate native apps with casting from a phone.

When I first saw the Googlebooks a few weeks ago, I really thought one might be my next laptop. After spending a week with them, I’m not so sure. I certainly wouldn’t buy a Googlebook as they are right now, but I wouldn’t rule out an Android laptop in the future — the execution just needs to catch up to the idea.

Photography by Dominic Preston / The Verge

暂无评论,快来发表第一条评论吧!No comments yet. Be the first!

📮 需求咨询📮 Inquiry