Last week TheStreet.com reported that Google had plans to sell a Google-developed phone at retail this year, bypassing carriers with its own Android implementation. But Rubin, vice president of engineering for Android at Google, scoffed at the notion that the company would "compete with its customers" by releasing its own phone.

"We're not making hardware," Rubin said. "We're enabling other people to build hardware."

Now, Google has played a role in designing phones that have emerged with Android, such as the G1. For example, Google advocated the infamous hinge design on the G1 based on its desire to offer a phone with a five-row keyboard, Rubin said. That design was not popular with reviewers, however, and Rubin joked that perhaps that's why Google shouldn't make its own hardware.

But pushing for a design feature is a far cry from designing an entire phone, contracting with a manufacturing partner to build it, and working the distribution channels to get it to market. That would be "a fundamental shift" in Google's business model, Rubin said, and one the company does not seem prepared to make at this time.

Rumors of a so-called "Gphone" date back years, long before Google formally announced Android in November 2007. But Google's strategy to date has been a somewhat traditional volume licensing play, working with hardware and carrier partners to spread Android far and wide as the mobile operating system of choice, rather than following Apple's lead with a complete hardware and software design like the iPhone.

About the author

Tom Krazit writes about the ever-expanding world of Google, as the most prominent company on the Internet defends its search juggernaut while expanding into nearly anything it thinks possible. He has previously written about Apple, the traditional PC industry, and chip companies. E-mail Tom.
See full bio