Utility
Every time we revisit Chrome OS we ask ourselves “Can we work with it?” As a writing tool, there's no question. The hardware and software limitations of earlier Chromebooks was like slipping blinders on. No distractions, just you and a writing web app. That’s not all you can do with Chrome OS, though; web apps are becoming more powerful and appeal to users because of their ubiquity. Any modern device with a browser can run a web app and offer the same experience no matter the device context. The appeal is currently primarily for developers who don’t have to worry about keeping separate branches of their code updated and optimized on different platforms. As HTML5 and Java progress, the apps built with them will both be more capable, and better able to tap into local resources for compute and data. You could almost imagine a chart that parallels Intel’s “Compute moves to zero” chart, where instead of measuring size, you’re measuring the limitations of browser-based code. So, once anything can happen in a browser, why not live entirely in the browser? Simply put, because we’re not there yet.
Web app Writer, a very minimalist text editor
Why not Android?
The argument goes something like this: Google has a great browser, and a great app platform, they should combine them in a laptop. Thus, the Chromebook should become the Androidbook. It comes up every time a new Chromebook is announced. It’s an idea not entirely without merit. Android runs on ARM and x86 chipsets. It runs Chrome. It has an enormous stable of apps. But that all misses a key fact: laptops aren’t phones or tablets. Chrome OS works because the PC is an utterly different user experience than mobile. And Google believes the conceits of a desktop environment can be best served by just one app: Chrome.
Google SVP Sundar Pichai, introducint Chrome OS at Google I/O 2011
Despite singing this song since the introduction of Chrome OS in 2009, the recent musical chairs at Mountain View has lead many to revive speculation of a future Android/Chrome OS marriage. Andy Rubin, father of Android, is tucked away in some Google skunkworks, and Sundar Pichai caretaker of Chrome OS now manages both experiences. Bringing all of the user facing software divisions under one leader makes sense to me, and not as a harbinger of fusion. During the last 18 months Google has gone through an extensive redesign of all of their assets, trying to bring a unified style and user experience to every product they offer. That experience has been lead by teams in Rubin’s and Pichai’s divisions, along with teams for GMail, Google+ and Search, and all the other products Google offers. But the only division that handles discrete software, and not just services and websites, were Rubin’s and Pichai’s. Bringing those two groups together for closer collaboration makes sense from a design and philosophy standpoint. Merging the very functions of the two into one monolith does not.
Chrome is about the best web experience possible, no matter the platform. Android is about a mobile software and compute experience that relies on apps and integration with Google services to offer utility. Those are two separate directives, the web and apps, and Chrome OS is the purest distillation of the Chrome experience. Shoehorning Android into the Pixel wouldn’t offer the best of both worlds, it would mean forcing a portrait app designed for a phone onto a really nice notebook. If fragmentation remains an issue for Android developers, imagine what happens if you ask them to design their apps to work on phones, tablets, televisions and notebooks. It wouldn’t be pretty.
Utility Continued
For many of us, browsing is about communication and consumption. We watch movies and listen to music in a browser. We chat with friends, send e-mails, engage with our social networks and even partake in video chats and telephony through our browsers. And, of course, we read and peruse images. If we’re going to get work done, though, we need to do more than just communicate and consume, we need to do produce. That means opening an honest to goodness application. Right?
Writing has always been one of Chrome OS’s strong points, and in earlier reviews we mentioned that the limitations of the OS actually helped make this an excellent writer’s tool. It’s hard to not write when all you have is a text field. Plenty of writing apps are just a click away, like the excellent Google Docs, Microsoft’s Office 365 and the minimalist Writer. The advent of Packaged apps is opening the opportunities for more immersive apps that step outside of the browser window. Txt is an early favorite, simple but adaptive, and it isn't stuck in a tab.
<TXT>, a packaged app
Most publishing, web and otherwise, needs more than just text. A few years ago, there was an explosion of excitement around image editing web apps, and everyone and their mother joined the fray, including Adobe and Flickr. Since then, the hype has died down, and the innovation. There are two factors that limit the appeal of these apps. First, there are limitations regarding file size and type. This is mostly owing to bandwidth concerns, both for the user and for the service host. If we had carte blanc to upload all our massive RAW files into an online editor and then edit them and save multiple copies, as we do on our local apps, we would end up with gigabytes of transferred data. So, even on paid apps you’re often limited to a medium sized JPGs, enough for web publishing to be sure, but given that high DPI content has truly arrived this approach is limiting.
The second limitation is in the apps themselves; they’re just not... enough. Several apps take the wizard approach that you might be used to from the likes of Shutterfly. Upload your images and then make modest edits in an interface that’s simplified and easy to navigate. Great for modest work, not so great if you’re planning on doing some serious editing. Want granular control of an image’s rotation? In Lightroom you grab that rotation slider in the Crop tab and adjust it to your comfort; in several image editor web apps, you’re only option is to rotate by 90 degrees at a time. So, yeah, that’s not going to cut it. There are more feature complete apps, but they come at an almost unbelievable cost: Flash. Pixlr is a great example of a web app with a desktop UI, driven by Flash, though the software itself is still limited to JPGs. So, for now, we’re hopeful for the future of photo editing web apps, but it isn't quite there... yet.
Photo editing app Pixlr, driven by Flash
So, you can write, but not do pictures. Video? Not quite yet. Development? That only requires a text editor, right? We thought about a variety of work flows and almost all ended with users putting the included Chrome Remote Desktop to use, to boot up some missing app or function. Even web developers would find themselves hampered by the inability to test IE or Firefox compatibility, and by the limited number of browser based IDEs rolling out. In the end, what we felt comfortable with remained writing and consumption. Those experiences are great, truly, but utility remains a sticking point. It may be time for Google to step-in and start to develop their own advanced productivity tools. Provide a powerful imaging tool and this becomes a powerful web publishing device. Provide the ability to emulate different browsing environments and we might see developers flock to Chromebooks.
Facebook
Twitter
RSS
74 Comments
View All Comments
Spoony - Friday, May 31, 2013 - link
No way. It must render the page at 1280x800, scale it up, then over the top draw native text. There is simply no way Jason wouldn't have complained bitterly if all of the text was jaggy.lmcd - Friday, May 31, 2013 - link
You realize that text is always available at high DPI as they're usually scalable vectors, right? But regardless of rendered size they're the same size, right?Oh. Yeah, don't forget that!
tuxRoller - Friday, May 31, 2013 - link
Always love hearing what will never be the case for things that don't involve tautologies:)Selden - Saturday, June 1, 2013 - link
Text is razor sharp.jeffkro - Monday, June 3, 2013 - link
You miss the point of the OS, its a no fuss more secure OS. Sure you can do more with windows but for some people its to complicated. I also don't like the idea of some hacker in Russia hacking into windows and getting all my banking info.Selden - Wednesday, August 7, 2013 - link
@JDG1980 : No, you get razor-sharp text, as shown in a screenshot. I just went through cataract surgery, and I have been able to go down a few points in text sizes, and 10-20% on screen magnification with the Pixel, also lower brightness, which increases battery life.cjb110 - Friday, May 31, 2013 - link
One thing they should port is their new Android Studio!lmcd - Friday, May 31, 2013 - link
Well, that's dependent on the moment on their work with NaCl. Hopefully PNaCl final comes out soon (with the performance promised). That, and I hope Dart turns out. Dart + PNaCl looks promising enough to deliver an Android Studio experience.shompa - Friday, May 31, 2013 - link
I try to think of one single reason to buy Chromebook instead of a rMBP (beside the stupid "I hate Apple").Apple have an OS that is designed for retina displays. Apple have solved the issue with non native resolution by render the original screen at 4 times its pixel count and downscale it make it look good on a 2880x1440 screen.
Why have tons of specs when it cant be used? And 4 gig memory?
I hope that Google releases an Android version of Chroomebook. The same day Android can/is preinstalled on PCs, thats the same day that MSFT for the first time have had competition. Something that all consumers would win by.
mavere - Friday, May 31, 2013 - link
I think they should have went with a slightly slower, cheaper Intel chip and spent that extra money on more RAM. It seems like the software offers the expectation of multitasking that the hardware fails to meet.The Chromebook design screams "I do one thing but I do it well". Uhh not at 4GB RAM, you don't.