After years of rumors of a Google phone, the search giant a week ago finally unleashed its mobile play: an alliance of handset makers and an open software platform dubbed Android.
Rubin, director of mobile platforms at Google, talked to CNET News.com about what Android phones will look like, whether they will compete with Apple's iPhone, and why the software took so long to build.
Q: What does Android look like? Rubin: Google has stepped up on behalf of the alliance to do various components of the support from a developer community perspective. We have a user interface team continuing development on the UI, and there will actually be a replacement UI.
We've been building it as a mobile mashup platform. That is a new concept for cell phones. So the developer can now stand on the system platform and take advantage of other developers' work for the first time. So, that just creates more flexibility for the developers, less work, faster turnaround, rapid prototyping, and all that stuff, and we're really, really excited about that concept.
Q: Is there a prototype dubbed Dream? Who has it, and when are we going to see it? Rubin: I actually don't know where that name come from. That's been an internal code name that's been kicked around here, but it changes quite constantly.
A lot of industry efforts just write specifications, and then they expect the rest of the industry to meet those specifications when they build their product.
We have manufacturing partners in the alliance, and they're building products, and Google has been given some of those devices. As part of the SDK, there's a complete hardware emulator that runs on the PC. It runs on Mac, Windows, and Linux. It's literally a hardware emulator of various devices--you know, different screen formats: horizontal, landscape, or portrait and, with the QWERTY keyboard and without a QWERTY keyboard, with touch, without touch.
Q: But consumers won't see devices until next year, right? Rubin: That's right.
Q: So, will there be a Google phone? Rubin: I'm going to say "no comment" on that.
Q: Why did you pick Linux as the foundation for Android? Rubin: One of the advantages of Linux is, it's a pretty prevalent operating system. The portion of Linux that we use for Android is just the kernel portion, and the benefit of kernel, of course, is that it's been already ported to all the varieties of semiconductors that run in cell phones.
Q: Why don't you join an existing Linux phone effort like the LiMo Foundation, or the Lips (Linux Phone Standards) Forum? Rubin: One of the key differences in the Open Handset Alliance with some of the existing consortiums is that we're actually building a product. Every member of the alliance has contributed something to the effort, and it's very product-focused.
A lot of industry efforts just write specifications, and then they expect the rest of the industry to meet those specifications when they build their product.
Q: What were the design goals for the Android project? What do you want Android to do that can't be done with Symbian, Windows Mobile, OS X, Palm OS? Rubin: Openness. The platform is completely open in a variety of ways. Of course it has open APIs, but it's also open source, and it being open source means it's (open to inspection). So expect to have the entire industry crawling all over the source base, trying to make sure that there aren't security issues, and there aren't inefficiencies in how the platform is designed.
Q: Who will do the technical support for Android? Rubin: Within the alliance, there are five categories: semiconductor companies, OEMs (original equipment manufacturers), carriers, software companies, and commercialization partners. The commercialization partners will do the support.
Q: What's Google's business model for Android? Assuming that it's free to use, where is Google's return on investment? Rubin: Google's mission is organize the world's information and make it universally accessible and relevant. This Android project satisfied the universal-access component of our mission. We need to make sure that on cell phones everywhere, consumers who carry them throughout their day have access to Google services.
Q: Does advertising play into this at all? Rubin: There is no direct-advertising component in the platform. (But consumers will be able to) access advertising the same way you're doing on your desktop PC through the browser.
Q: Will the browser in Android be tied to the platform, or can I use any mobile browser I like? Rubin: You can use any mobile browser you like.
Q: What were the primary development challenges for Android? Did you design it with high-end or mainstream hardware in mind, and what are the system requirements? Rubin: When we built the system, we wanted it to be as flexible as possible. We did a lot of work to write our own library, and it's 250 kilobytes, not 3.4 megabytes.
We took a lot of those types of considerations when we were developing the platform. The platform is capable of running, as I said, on kind of mid- to lower-end devices as well.
We feel that one of the platform's distinguishing features is how it handles access to data. I talked about the mashups on the Internet and everything else. So, although the platform can run in a stripped-down fashion on mass-market phones, we think that the initial devices will be mid- to higher-end phones just because of the data access capabilities of the platform.
The minimal requirements are 32 megabytes of RAM, 32 megabytes of flash, and a 200-megahertz online processor. There are companies within the alliance working to bring that to even lower-power phones.
Q: Will there be different versions of Android devices where there will be a commonality, or a basic level of compatibility, that they all must maintain for applications to run on them? Rubin: It's really important that we don't create a fragmented environment, and one of the complaints I think developers have with open source is that there is really no way to guarantee compatibility.
In the SDK, there is a scripting engine that allows remote test scripts to be run on the emulator on a phone. Also, there is a secondary compatibility (test for) support for services.
It's important for third-party developers to make sure that the applications run across different phones. There's not going to be a hard certification requirement. That doesn't make sense in an open environment. But we'll provide the tools necessary to make sure that these applications can be made compatible, if that's what the industry wants.
The platform itself has the ability to be targeted toward all sorts of different screen sizes and input mechanisms--touch devices, trackballs, five-way keypads, portrait displays, landscapes, big displays, small displays, QWERTY keyboards, non-QWERTY keyboards. When the developer writes an app, and that app is on portrait display, the platform also will run that same app on a landscape display.
If something is important to Google, just let it be important - none of this - It's super important to Google - stuff. I've had enough of that with Microsoft, everything is super or "I'm super-enthused about an upcoming product..." Can't anyone think of better descriptors these days?
How about no more useless comments? (after this one)
These TalkBack comments really should be talking about the info given in the interview not how the questions where answered.
Next time think before you post. That way you may think "Wow this is stupid who cares? Best not to waste time on this." or "I am going to get flamed better save my own ass!"
The platform is open and so it seems like an operator or handset vendor could control which APIs are accesible to an Apps developer - kind of like done with JSR's today. They could also insist on certification. If this scenario is possible on Android enabled handsets we will still have a highly fragmented market from an App developers point of view.
Why do you need such a high hardware requirements for? Most of the small phones you buy nowadays probably have much smaller memory and lower power powered processor to conserve battery life.
Most people use phones for text messages, photos, mp3's, and maybe a web surfing. They should just make simple OS and simple applications that people can use. Android's Internet explorer and google maps take too much resource.
Are 32mb and 200 mhz the minimum platform? Guess I better read sdk stuff.
"Most people use phones for text messages, photos, mp3's, and maybe a web surfing. They should just make simple OS and simple applications that people can use. Android's Internet explorer and google maps take too much resource. "
I want a portable internet device, but it doesn't have to be my phone. I don't listen to MP3's just news.
Think we need to wait for system resources and bandwidth high enough to run the droid s/w. Take a deep breath, it has been a while since this "repeated vision of future reality" will take effect, maybe I'm cynical from waiting.
I love the concept, no doubt, but does everyone has to spend the same amount for a "powerful phone" as they do for a Dell portable, or the laptops we get at Fry's. OK, next, ...
Texting on the numpads wastes my time, ~mpov. I call the person and at the worst leave voice mail? Am I nuts (sometimes yes, mpov) ?
The V9m has a 225MHz cpu and the V8 and V9 have 500MHz CPU's. Not sure about RAM. The V9 has 45MB memory (flash,) and the V8 has 420MB. The V9m is in between the other 2. I'm guessing none have 32MB of RAM though. Shouldn't be too much trouble to add to a medium to high-end phone, as PDA's have regularly had 64MB of RAM for years (some have 128.)
I think these minimum specs for Android phones are very nominal. Hardware with these specs is not very expensive to make and it will be even cheaper when the phones are released in second half of 2008.
if I am not wrong , iPhone has 600MHz processor, and looking at the sleek GUI and things it can do, it's worth it
The OVERWHELMING majority of cell phone customers are non-techies who could give a rat zass if the phone they're using is open, closed, or ajar. All they care is if it looks good and--especially--if it's easy to use. If openness doesn't translate to that, it doesn't mean diddly doo!
Why Is Google Dangling a Carrot to Move a Cash Cow?
In response to Google's big-money competition to attract developers to make apps for Android, answer me this...
Why Is Google Dangling a carrot to move a Cash Cow... or is Android really a donkey?
Why is Google offering financial incentives in an open source initiative?
Why are they offering to pay for these apps at such an early stage in the development of Android?
Who... & why would someone put Google into such a disadvantageous position for negotiating future transactions with software app developers?
Seriously, why write open source apps for free when Google is telling us that there are revenue streams to be tapped?
To further wet your appetite, how does revenue-sharing sound? App developers receive a certain percentage of the revenues generated from the apps they write.
Open source doesn't mean free - Patent close doors
As far as I can tell, Openwave, Nokia, Wireless Science, Motorola, Att and a few others control the bulk of patents required to build the real "dream" phone - Open source or not.
Maybe Google's dreamed unwalled garden would open a bit wider if they acquired and included the necessary key licenses with their, so called, open source.
The iPhone maker says that the mobile industry lacks "consistent adherence to Frand principles" and wants the European Telecommunications Standards Institute to step in.
An Internet troll who posts allegedly hateful and racist remarks on Facebook's RIP sites, seems blase about his activities when he is intercepted by a BBC reporter.
California State Teachers' Retirement System, the second-largest pension fund in the U.S., says the social network should add women to its board of directors.
After large numbers of longtime 'Burners' failed to get tickets during the event's recent selection process, many claimed organizers had failed to adopt a sensible system. Now, those organizers are trying to calm community anger.
Fabrication is moving to the nanoscale, aided by a super-hard tip 10,000 times smaller than a pencil point that could be used for microscopic biosensors and optical probes.
Greenpeace tries to cast some light on the energy sources behind data centers and commend IT companies that advance clean energy and efficiency through tech. Facebook and Apple aren't quite there yet, it says.
I've had enough of that with Microsoft, everything is super or "I'm super-enthused about an upcoming product..."
Can't anyone think of better descriptors these days?
Next time think before you post.
That way you may think "Wow this is stupid who cares? Best not to waste time on this." or "I am going to get flamed better save my own ass!"
"Thinking" it makes the internet a better place.
Most people use phones for text messages, photos, mp3's, and maybe a web surfing. They should just make simple OS and simple applications that people can use. Android's Internet explorer and google maps take too much resource.
"Most people use phones for text messages, photos, mp3's, and maybe a web surfing. They should just make simple OS and simple applications that people can use. Android's Internet explorer and google maps take too much resource. "
I want a portable internet device, but it doesn't have to be my phone. I don't listen to MP3's just news.
Think we need to wait for system resources and bandwidth high enough to run the droid s/w. Take a deep breath, it has been a while since this "repeated vision of future reality" will take effect, maybe I'm cynical from waiting.
I love the concept, no doubt, but does everyone has to spend the same amount for a "powerful phone" as they do for a Dell portable, or the laptops we get at Fry's. OK, next, ...
Texting on the numpads wastes my time, ~mpov. I call the person and at the worst leave voice mail? Am I nuts (sometimes yes, mpov) ?
if I am not wrong , iPhone has 600MHz processor, and looking at the sleek GUI and things it can do, it's worth it
The OVERWHELMING majority of cell phone customers are non-techies who could give a rat zass if the phone they're using is open, closed, or ajar. All they care is if it looks good and--especially--if it's easy to use. If openness doesn't translate to that, it doesn't mean diddly doo!
competition to attract developers
to make apps for Android,
answer me this...
Why Is Google Dangling a carrot to
move a Cash Cow... or is Android
really a donkey?
Why is Google offering financial
incentives in an open source initiative?
Why are they offering to pay for these apps
at such an early stage in the development of Android?
Who... & why would someone put Google into
such a disadvantageous position for negotiating future transactions with software app developers?
Seriously, why write open source apps for free when Google is telling us that there are revenue streams to be tapped?
To further wet your appetite, how does revenue-sharing sound? App developers receive a certain percentage of the revenues generated from the apps they write.
Motorola, Att and a few others control the bulk of patents
required to build the real "dream" phone - Open source or not.
Maybe Google's dreamed unwalled garden would open a bit
wider if they acquired and included the necessary key licenses
with their, so called, open source.