During Android’s early ascent, the mobile industry was still fragmented and dominated by tightly controlled platforms. Smartphones were evolving quickly, netbooks were gaining attention, and in-car systems and set-top boxes were beginning to edge into the conversation. In that environment, an in-depth interview with Andy Rubin offered a clear look at how Google envisioned Android’s role in shaping the future of connected devices.

At the time, Rubin was serving as Google’s director of mobile platforms. He had previously co-founded Danger, best known for the Sidekick, and later co-founded Android when it was still an independent startup. His perspective carried weight not only because of his leadership role, but because Android itself had yet to prove its long-term viability against established competitors.

Competing in a Rapidly Shifting Market

When the interview was conducted, Apple’s iPhone was redefining consumer expectations for smartphones, and Palm’s webOS was positioning itself as an innovative alternative. Android was still in its formative stages, competing not just on hardware but on philosophy.

Reflecting on Palm’s webOS and the iPhone, Rubin said:

“You can have spurts of innovation. You can nail the enterprise, nail certain interface techniques, or you can nail the Web-in-the-handset business, but you can’t do everything. You’re always going to be in some niche. What we’re talking about is getting out of a niche and giving people access to the Internet in the way they expect the Internet to be accessed. I don’t want to create some derivative of the Internet.”

At a time when many platforms were optimized for specific use cases or tightly controlled ecosystems, Rubin emphasized scale and openness. The goal was not to refine a single experience to perfection, but to build a foundation capable of reaching beyond niche segments.

A Platform, Not Just a Phone

One of the more forward-looking aspects of the interview centered on Android’s potential beyond smartphones. Rubin referenced the longstanding software ideal of “write once, run everywhere” and suggested that Android could finally bring that idea into practical reality.

“Remember people used to trumpet ‘write once, run everywhere’? Well, I think we’re actually there. When we start talking about the possibility of exploring things like netbooks and car navigation systems, you have potentially different processor architectures. You have Intel, you have ARM, set-top boxes have MIPS. We have all sorts of different processor architectures, and the guys who are steeped in legacy have trouble addressing those markets with a single solution. I actually think Android is the potential single solution that can address all those markets. It’s new, it’s revolutionary. It will change the game.”

At the time, Android’s expansion into cars, TVs, and other connected devices was largely theoretical. The broader industry had yet to fully embrace multi-device ecosystems. Still, Rubin’s comments made it clear that Google saw Android not as a phone OS, but as a scalable software layer adaptable across hardware categories.

Why There Was No “Gphone”

Early speculation about a Google-branded phone was widespread. Rubin addressed the idea directly, explaining why Google’s focus was on the platform rather than a single flagship device.

“It’s funny. If you build one phone, I’d much rather be the guy who creates a platform capable of running on multiple companies’ phones than focusing on a single product. A single product is eventually going to have limitations. Even two products will have limitations. But if it’s a hundred products, now we’re getting somewhere. That’s the scale at which Google thinks people want to access information.”

This perspective underscored Google’s strategic priorities at the time: broad distribution and manufacturer partnerships over vertical integration. Long before Google introduced its own Pixel hardware line, the emphasis was on enabling a wide ecosystem of devices from multiple vendors.

Why It Matters

Looking back, the interview captures a pivotal moment in mobile computing. Android had not yet secured its dominant position, and the outcome of the platform wars was far from certain. Rubin’s comments reveal a deliberate focus on openness, cross-device scalability, and long-term reach rather than short-term product wins.

Many of the platform decisions that shaped Android’s evolution were already embedded in this early philosophy. The commitment to running across different processor architectures, supporting diverse hardware partners, and expanding beyond phones was not an afterthought. It was foundational.

Revisiting these remarks provides a clear snapshot of Android’s original ambitions and the strategic thinking that guided its early development.