Monday, January 6, 2020 [Tweets] [Favorites]

Chrome OS Has Stalled Out

David Ruddock (Hacker News):

Chrome’s problems really became apparent to me when Android app compatibility was introduced, around five years ago. (This also isn’t the first time we’ve pointed out that approach’s failings, Corbin did so in an editorial last year.) Getting Android apps to run on Chrome OS was simultaneously one of the Chrome team’s greatest achievements and one of its worst mistakes. In 2019, two things are more obvious than ever about the Android app situation on Chrome. The first is that the “build it and they will come” mantra never panned out. Developers never created an appreciable number of Android app experiences designed for Chrome (just as they never did for Android tablets). The second is that, quite frankly, Android apps are very bad on Chrome OS. Performance is highly variable, and interface bugs are basically unending because most of those apps were never designed for a point-and-click operating system. Sure, they crash less often than they did in the early days, but anyone saying that Android apps on Chrome OS are a good experience is delusional.

[…]

I say this even as one of the few people who can do 95% of my job on a Chromebook: that 5%, when you really, really need it, is more than enough reason to avoid a platform entirely. And for many others, it’s much more than 5%: it’s their entire workflow.

John Gruber:

The existence of the “Chrome OS can run Android apps” crutch has stunted Google’s motivation to push the platform forward to solve the remaining tasks that the platform isn’t suited for in ways that are truly native to Chrome.

Previously:

Comments

Stay up-to-date by subscribing to the Comments RSS Feed for this post.

Leave a Comment