Acer reported today that computers running Google’s free Chrome OS accounted for up to ten percent of its US PC shipments since November 13, when the company released its $199 C7 model Chromebook. That’s small in absolute terms, but surprising in light of the nascence of Chrome, as well as the even greater novelty of Chromebooks with the right hardware and design (such as Samsung’s model) for Google’s minimalist operating system. Some have framed the issue as a windfall for OEMs, who now have even more leverage to call out the emperor’s new clothes that is Windows 8, since Chrome represents – at long last – a commercially viable non-Mac alternative to desktop Windows. But I think there are two more pressing questions that the apparent success of Chrome raises:
1) Is Chrome really a “desktop” OS?
2) Does Chrome provide hope for inexpensive laptops to beat back the tide of tablets?
Question 1 seems easy enough to answer on the surface. Chrome doesn’t run any native apps and almost hilariously cordons off your files (the hallmark of all desktop computing for 30 years) in an app called, well, Files. Everything runs side by side in the browser and notifications (Gmail, NYT, Google Talk) for anything come directly to the desktop – I would go so far as to say it dispenses with the very idea of a “browser,” since it is agnostic of the notion of “offline” existence and knows that, anymore, your devices are all doorsteps without a connection. Chrome OS is to the Internet what iOS was/is to file systems – it would rather you just not think about it/them.
And I think that it is this always-online existence – and more specifically, the way in which Chrome takes the Internet for granted – that makes both Chrome and the Chromebook line that runs it a possible foil to the storyline of laptops and especially netbooks completely giving way to mobile devices and tablets. PCs are in a rut for myriad reasons: bad software, price, and inefficiency. Why pay $1000 for an email and Facebook machine, after all? At the other end of the price spectrum, netbooks – cheap, modestly powered laptops running Linux or Windows – have suffered tremendously at the hands of the iPad in particular, which offers basically the same experience but with a better OS. Moreover, the iPad has crushed netbooks because iOS makes it extremely clear exactly what your device can do – your apps are clearly differentiated and displayed in a simple visual interface. What you see is what you get; no complex unfriendly file systems or cumbersome user interfaces.
But iOS, even amid the pain it has exacted on traditional PCs, still clings to the somewhat traditional idea of native apps – in fact, it is (in the user’s eyes) a catalog of native apps tweaked to the OS’s strengths and capabilities. The latter point is important in differentiating the iPad from a netbook – a netbook can theoretically try to run many of the more demanding Windows/Linux apps, but performance is bad, an example of users being given too much freedom which in turn leads to a poor experience. The Chromebook line is by almost any technical standard a “netbook” line. These laptops all use either very simple Intel processors or even ARM chips, have no optical drives, and are extremely cheap, with the C7 in particular available for a basically unmatched price.
But unlike traditional netbooks, the experience is carefully and adroitly managed. All “apps” more or less come from the Chrome Web Store and downloadable executable files are forbidden. An “app” tray simulates a traditional desktop computing environment, but lest you think you’re still in Kansas, note that all browser shortcuts (new tab, new incognito, etc) work directly from said desktop.
Basically, Chrome packages a radical new notion of computing – always online, with the whole Web integrated into or at least in close proximity to your apps – in a highly digestible package, much like iOS did when it debuted. And in doing so, it is redefining what a “netbook” or cheap computer even is and what it can do. While it can’t compete with smartphones, it could grow into a real competitor most tablets, especially if Google actually makes a Nexus-grade Chromebook and further hybridizes Chrome and Android.
-The ScreenGrab Team
A tweet a while back from The Verge’s Joshua Topolsky, about a “nuts” app called AirDroid, inspired me to try out that same app on my Nexus 4. After experimenting with it over the past week, I’ve come to see it as an invaluable, futuristic utility for device management. It feels like something that Google could easily buy and make into a standard service for all Android devices.
AirDroid allows for very nuanced file management and manipulation of your Android phone, but its setup is dead simple. Download the free Android app and start it up. It gives you a URL and an access code. Once you input the code on the Web, the page transforms into a vaguely Linux-like desktop which mirrors (or reinterprets, more nearly) your phone’s entire file structure. You can see all of your text messages, photos, and contacts, as well as apps and what’s currently on your clipboard.
One of the underrated aspects of the Android platform is how independent it remains from traditional PCs and Macs. There’s no syncing or real need for cables (especially now that devices like the Nexus 4 support inductive charging) and the platform had no equivalent of the bloated desktop iTunes 11. Sure, curious users can explore a device’s file system on their PC via cable, or send an app from the Google Play desktop site to an Android device that is using the same Google Account. But these are fringe features. Most Android users have devices that are PC-agnostic.
The flip side of this agnosticism is Android’s unparalleled openness, which lets it be manipulated at a level that iOS (for instance) all but prevents. AirDroid is perhaps the most polished example of remote Android management, such that I think that it may be worth Google’s while to acquire it and make it a standard Android tool, perhaps even as a Chrome extension that would play nicely with the increasingly chic Chromebook line.
A few useful things about AirDroid:
1. Easy file upload of basically any file format or size, without iTunes’ restrictions on folders etc.
2. Send a URL to your phone for later – sort of a like a mini-Pocket.
3. Easily sideload apps from non-Play sources.
Granted, these are niche use cases that appeal mainly to geeks like me. But they have real value since they create what I think is the first real semblance of a coherent multiscreen experience between Google gadgets in particular – it gives me a robust tool for manipulating my Nexus 4, even from the lightweight Web-only world of my Chromebook. It enriches both gadgets – the Nexus 4 becomes an even more flexible device and repository for all sorts of files, while the Chromebook becomes a management tool while sacrificing none of its minimalist appeal.
Google has already stated that it wants to provide a truly seamless multiscreen experience, but so far this has been difficult due to Android fragmentation and Google’s considerable deficit vis-a-vis Apple when it comes to creating fully integrated hardware/software that just works together, like the Mac and the iPhone via iCloud (imperfect as the latter still is). AirDroid is a sleek, sneaky way of experiencing Android on your desktop and having more control over the inside of your phone, which is so often a total black box. Google should buy it and use it to further integrate the experience they provide, especially now that Google is working directly on hardware with Motorola and postulating that someday Chrome and Android will converge.
App rating: 77%
-The ScreenGrab Team