Google Mobile Phones Debut in Feb? 127
SpinelessJelly writes "It appears that Google's Android, criticised by Microsoft as vaporware, has sprung to life. Prototype devices are circulating, software developers are experimenting with the SDK and PC-based Android emulator, and there are rumours of a show-stopping debut at February's Mobile World Congress event in Barcelona. Numerous examples of the Android GUI are also starting to leak out."
Comparisons (Score:5, Interesting)
This ignores the fact that most handset manufacturers will probably include a 3D accelerator to improve graphical performance. Google claims [google.com] that Android has a "highly optimized 3D software rasterizer", but it remains to be seen if a mere 200MHz processor is capable of sustaining the necessary graphical power to provide a smooth experience.
In any case, it's likely that a 3D Accelerator could save on battery power. Application specific chips tend to be able to do more work with fewer cycles and less silicon. Which means that a phone manufacturer can make the choice of a faster CPU + lower battery life, or a slower CPU + 3D accelerator + higher battery life.
I'm pumped! (Score:4, Interesting)
This article doesn't say much of anything new - it mostly uses screen shots and explanations that the folks at Google put in their original announcement videos.
That said, I'm personally very pumped about getting an Android phone. I hear people dissing Google here a lot, but everything that I've used that is made by Google works great - Gmail, Picassa, Google Earth, Google Maps, and the search engine itself. If these guys make something, I pretty much believe it will be cool.
Up till now, I've had very little interest in a "smart phone" - the ones I've had my hands on are clunky, and that includes Blackberries. But if I can get a phone with Android next time my contract is up, I just might do it. If nothing else, the possibility of having features that aren't controlled by the carrier is awesome. And announcements like Android seem to be pressuring carriers to go in that direction, even though Android doesn't specifically prohibit lockdown.
Down with carrier control! Up with open access! :)
Re:Microsoft, Schmicrosoft... (Score:3, Interesting)
All in All (Score:3, Interesting)
Re:Microsoft, Schmicrosoft... (Score:3, Interesting)
Android looks like a really neat platform, but it's a geek platform. It won't have the enterprisey features that business people want (primarily Exchange integration) and from the looks of things, it doesn't have the sleek design that has captured the hip market (like the iPhone has.) It will almost certainly be priced comparably to other smart phones, with nothing to set it apart for the average customer.
I really hope that I'll be proven wrong, but so far, I just don't see anything that makes Android pop.
Re:Screenshot != not vapor (Score:5, Interesting)
Now the individual OEM's/ODP's have to A) integrate telephony (and work out the large number of issues with integrating the Android stuff with that), B) Create the mechnicals, C) Test and certify the phones for a number of different groups (OMA, FCC, etc..), D) Negotiate distribution and availability with carriers, etc... etc... etc...
Building a phone is non-trivial and involves a LOT of 3rd parties. They're on step 1a right now. I'll be duly impressed if they get a phone out before November of 2008.
Neo1973/OpenMoko and Android (Score:3, Interesting)
Google's phone sounds awesome, but this is the kind of thing that hinders the "open phone" market. Too many splinters.
Re:Exchange integration? (Score:2, Interesting)
I used to work for a company that implemented microsoft servers, exchange, and even IIS regardless of the customer's actual needs. It's 'industry standard' to not let hardware control DHCP to these guys! You should see what happens when a server goes down after it's been set up the Microsoft way in a business network. Everything dies, including everybody's connection to the internet.
I think it's time to let Redmond know that we are not going to bend over and take it up the tailpipe on this one. I'd much rather see good integration with Google Aps before people waste time tinkering with Exchange integration.
Re:Comparisons (Score:3, Interesting)
We are talking about lower resolution than Quake with slightly more features.
A 200mhz processor is overkill for that. 486's can do that easily.
The overhead required to power a separate chip and the interface between the two isnt worth it.
Damn Windows users thinking you need a dual core 3ghz processor to type up a document.
A 200mhz processor is freaking fast for most things including low res 3d.