Android on Netbooks

[Mason_S]

We've all heard the hype. We've seen the screen shots of Android working on an Asus netbook. Currently in the news, there are discussions of HP possibly jumping on Android as a cheap (read: free) netbook OS solution.

Still, Android "working" on a netbook is a far cry from it being an actual viable solution. There are some inherent problems in using a mobile OS, even one so revolutionary as Android, on an actual computer. I wanted to discuss the issues I see with the community, as well as the possible solutions, and the pros and cons of using Android on a netbook.

Pros:
First and foremost, it's free. This cannot be understated since the netbook market targets the very bottom of the budget barrel. They're meant to be ultra-affordable solutions, so saving $100 or so on OS licensing can be a huge advantage.

Next, it's popular. There's a lot of buzz over Android. The Google branding and tight integration of Google services has a lot to do with that. There are plenty of people out there dying to try Google's new OS. A free OS, surrounded by lots of buzz could never be a bad thing for a netbook manufacturer, right?

Next, and most importantly, Android is very open. This means that it will be possible to address all of the cons. This will come up more as we look at solutions to the problems.

Android's openness also means that there are miles and miles of room for innovation. I'll talk about this more in a moment.

Now let's address the cons. These are some pretty big obstacles, but with some concerted effort and emphasis placed on the netbook segment, either by Google, or by the Open Source community, or preferably both, Android can certainly overcome these due to its openness:

First off is the lack of practical applications for the netbook segment. If you get a Windows based netbook, you can get Microsoft's services, including the office suite. This means you get Power Point, Excel, Word, and Outlook. There is nothing currently available for Android that matches the productivity options of even an ancient Microsoft OS such as Windows XP.

There is a solution to this, of course. Google has its own services to pit against Microsoft's office suite. Google's online Docs is a fairly robust solution. Certainly good enough for composing a quick spreadsheet or a simple text document. Even the presentation suite works well enough to use it in a pinch. And the best part? Those too are free. The problem? None of those are integrated into the current Android build. The solution? Simple: Google needs to integrate their Docs service with Android.

To go along with this is the further fact that, besides Microsoft's own services, there is a HUGE software ecosystem already built around Windows. Granted, much of the software out there for Windows isn't terribly viable on netbook class hardware anyway; you're probably not going to be playing the next Half-Life game on your netbook (well, not very nicely anyway). But older games, other software, such as printshop, photoshop, even the iTunes and Zune players, and even internet plugins such as Flash, already work with Windows, and not with Android.

The solution to this is not as simple. It takes time for such an ecosystem to evolve around a platform. Thankfully, we already have an easy method for software distribution. The Android Market gives developers a means to deploy their software directly to the consumer's device, saving money on publishers' fees, and giving consumers easy access to their product.

Another con is one that most sites I've read have seemed to overlook: the windows of Windows themselves. I think sometimes we take for granted just how easy and seem-less it is to multi-task on a Windows machine. In this area, Android currently doesn't even come close. Though possible, and even somewhat seem-less with certain third party apps (task switcher etc.), multi-tasking on Android is great for a phone, but is miles away, in my opinion, from being on par with even the venerable Windows XP with it's windows and start bar.

The next thing I want to look at could either be a ground-breaking pro, or a serious con depending on how far hardware makers are willing to go in implementation. Simply put, Android is built to be touched. This means any other interface method will fall short. However, if a netbook maker were to incorporate a touch screen into their Android netbook, the result would be ground-breaking.

So, for what it's worth, those are my demands. An Android-powered, touch-controlled netbook costing at least $100 less than comparable Windows machines, with full Google Docs integration, Flash, better multi-tasking implementation within the UI, and, of course, more software to compete with the software ecosystem built around Windows.

I think we could have something big here. What's everybody else think?

[GMemorySolutions]

It's great knowing that Android is becoming more and more popular. Hopefully saving that extra $100 translates to a lowered final cost to us consumers

[happyandyv]

That's a good read. Will come back to it later to discuss with you when I have more time if I remember.. Thanks much.

[gbk1]

Good read.
Any reason to completely pass on the other dude. Apple?

So, for what it's worth, those are my demands. An Android-powered, touch-controlled netbook costing at least $100 less than comparable Windows machines, with full Google Docs integration, Flash, better multi-tasking implementation within the UI, and, of course, more software to compete with the software ecosystem built around Windows.

I'd say your solution would be an Android based OS on Peek.
Shove a bigger touch screen and a more usable keyboard and I'd say it's perfect!

... Twitter, Android Apps(Market access also ), Web, SMS/MMS, and your basic but great Google apps on a more powerful device.
Since it is not phone first, size should not be a huge factor for the target consumer.

[Mason_S]

I mainly steered away from Apple, and even Ubuntu, which is the other real competitor in the netbook space, because Windows XP (and soon, one can only assume, Windows 7) are the standard bearers for the netbook space. Apple has already voiced their disdain for netbooks. And although there are indications currently that Apple may jump into this space, theirs would be boutique type computers with hardware similar to other netbooks but with a price tag that you can bet absolutely will be much higher.

Still, makes for an interesting comparison since I could certainly see Apple incorporating touch into any netbook they make. Still, an Android power netbook might cost around the same as the biggest iPod classic, where any Apple netbook might cost two or three times that much.