Excerpt: How Google bought Android—according to folks in the room

In the beginning, it took a very specialized pitch to connect Android and Google.

In the beginning, it took a very specialized pitch to connect Android and Google.
Dan Sandler

reader comments

52 with 31 posters participating

Androids: The team that built the Android operating system is a new book from longtime Android engineer Chet Haase. Haase has been on the Android team since 2010, and he interviewed dozens of Googlers for this book, which offers a behind-the-scenes look at early Android development. With Haase’s permission, we’re giving readers a look at chapters four and five of the book, “The Pitch,” and “The Acquisition.” That portion covers the independent Android Inc.’s search for venture capital and the team’s eventual meeting with Google. The book is out this weekend in eBook and paperback (Amazon, Google Play), and Haase is donating proceeds to Black Girls Code and Women Who Code.

By mid-2005, Android was acquired and the future looked bright. But just six months earlier, things weren’t quite as rosy. In January of that year, the startup was desperate for cash and their main task was the same as for most startups: getting funding. After the pivot from a camera OS to an open source phone platform, they still had the daunting task of actually building a product, which meant they’d need more money to hire a large enough team to do the work.The original demo, written by Brian Swetland and Chris White and later enhanced by Fadden, showing a home screen and several apps (most of which were not implemented). It’s a far cry from a modern Android home screen.

The original demo, written by Brian Swetland and Chris White and later enhanced by Fadden, showing a home screen and several apps (most of which were not implemented). It’s a far cry from a modern Android home screen.
Chet Haase

So the company focused on three things. First, they needed a demo to show what was possible. Next, they needed to articulate their vision and create a pitch deck to help explain that vision. Finally, they needed to take the demo and the slide deck on the road to pitch their story to potential investors.

Demo time

The first job for Andy McFadden (known to the team as “Fadden”) when he joined was solidifying the demo, a prototype phone system that Brian Swetland and Chris White had been working on. It wasn’t actually functional (for example, it showed a stock ticker on the home screen which used a set of hard-coded symbols and stale data). But the demo represented a vision of what the product could be when it was actually implemented.

One of the apps that Fadden added to the demo was a simple calendar application. This early demo project would come back to haunt him. After many intervening years of working on things throughout the Android platform, he ended up helping out with the Android Calendar app. Time waits for no man… but calendar apps do.

The mobile opportunity

As the team honed their vision, they created a slide deck to explain it. These slides painted a picture of the opportunities that they saw for Android in the marketplace, as well as a picture of how Android would make money for the investors.

Slide 7 diagrammed the potential for an open platform, providing something that was otherwise not available at that time.

Enlarge / Slide 7 diagrammed the potential for an open platform, providing something that was otherwise not available at that time.
Chet Haase

Even more problematic, the systems that were available failed to provide an ecosystem for applications. Symbian provided some of the core infrastructure for an operating system, but the UI layer was left as an exercise for the manufacturer, resulting in an application model for phones where apps written for one flavor of Symbian wouldn’t necessarily run on some other variation, even on phones from the same manufacturer.

The Java programming language, known in the server and desktop PC world as “write once, run anywhere,” could possibly have provided this kind of cross-device application capability, but Java ME fell far short of this in the mobile space. While it did provide at least the same language across devices (much as Symbian provided the same language of C++ for all of its implementations), Java ME addressed the wide variety of form factors and architectures in phones by providing different versions of the platform, called profiles. These profiles had different capabilities, so developers needed to change their applications to run on different devices, and often that approach failed when capabilities were drastically different across devices.

Linux to the rescue!… Almost. Texas Instruments (TI) provided an open platform based on the Linux OS kernel. All manufacturers needed was Linux itself, reference hardware from TI, and then a huge host of other modules that manufacturers had to acquire, license, build or otherwise supply to create their own device. As Brian Swetland put it, “You could use TI’s OMAP chips to build a Linux phone. So you needed TI’s OMAP and then forty components from forty different vendors of middleware. You put all these together and you integrated them all and then you’d have a Linux phone. And that was just absurd.”

TI provided a Linux-based solution, but many of the details of drivers and other components were left as an exercise to the manufacturer, which wasn’t a compelling option.

Enlarge / TI provided a Linux-based solution, but many of the details of drivers and other components were left as an exercise to the manufacturer, which wasn’t a compelling option.
Chet Haase

Android wanted to provide the world’s first complete open handset platform solution. It would be built on Linux, like TI’s offering, but would also provide all of the necessary pieces so that manufacturers would have only one system to adopt in order to build and ship their devices. Android would also provide a single programming model to application developers, so that their apps would work the same across all devices on which the platform ran. By having a single platform that worked across all devices using it, Android would simplify phones for both manufacturers and developers.

Article Tags:
Article Categories:
Technology