GPhone — If I Built It (Part 1)
If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

The internet is buzzing with rumors about a possibility of a phone from Google. I too have posted some thoughts in the past. It is being said that Google isn’t developing a phone but an operating system. That kinda sounds right as Google is known for its software and not for its hardware capabilities. Although Andy Rubin (possibly the main guy running the GPhone operation) did create the SideKick, which was an awesome phone.
Based on this latest rumor, the threat could be more towards the likes of Microsoft, Symbian and other mobile OS providers. The OS play is interesting as Google will have to depend on OEM vendors and carriers to some extent for getting its service to the market. This is in contrast to Apple who has all or nothing mentality (of course excluding the RF infrastructure).
My intent with the post is not really to spread more rumors. It is more around analyzing how Google could solve this problem. They probably have the best armory of services and applications, which can be extended to a Mobile ecosystem. This post delves into the approach from my perspective. I will try and break my analysis down in various horizontal components, which comprise the ecosystem. This post will be in three parts covering:
- Base operating system and mobile features
- Messaging, Productivity and Media features (live now)
- Application Ecosystem and Revenue Enablement (live now)
So without further ado, let’s look at part one.
Comments(9)




