Skip to main content

The Rise of Google, Part 13: Android

Android

🎬 Prefer to watch? Here's the 60-second version:

Watch on YouTube ▶

📚 The Rise of Google — a 20-part series. See all parts »  |  « Part 12: Buying YouTube

In August 2005, Google quietly bought a company almost no one had heard of. There was no splashy press conference, no billion-dollar headline, no analyst frenzy. A two-year-old startup called Android Inc. simply disappeared inside the search giant, and the technology press barely blinked. It would turn out to be one of the most consequential purchases in the history of computing — the deal that decided who would own your pocket.

Four founders and a camera that never sold

Android Inc. was founded in Palo Alto in October 2003 by four engineers: Andy Rubin, Rich Miner, Nick Sears, and Chris White. Rubin was the restless one — a former Apple and General Magic engineer who had already co-founded Danger, the company behind the cult-favorite T-Mobile Sidekick. He had a habit of naming things after robots, and he liked the way “Android” sounded.

The original pitch had nothing to do with phones. Android was first conceived as a smarter operating system for digital cameras — a way to connect them wirelessly to a cloud of photo storage. But the camera market was already sliding as phones began absorbing the point-and-shoot, and the founders saw the writing on the wall. Within months they pivoted to the far bigger, far messier prize: building a free, open operating system for mobile handsets, one that carriers and manufacturers could adopt without paying a licensing toll to Microsoft or anyone else.

It was an audacious plan for a startup running low on cash. Rubin, by his own later account, was scrambling for funding when Google came calling. The two sides had circled each other before — and in August 2005, Google acquired Android Inc. outright. The price was never officially disclosed, but it has been widely reported at somewhere around $50 million, with earn-outs for the founders. Rubin, Miner, and White all joined Google. For a company that would soon spend $1.65 billion on YouTube, fifty million dollars was a rounding error.

Why Google was afraid of a phone it didn’t make

To understand why Google bought Android, you have to remember what Google actually was in 2005: a search-and-advertising company that lived and died by people typing queries into a box. Nearly every one of those queries came through a web browser on a PC. But it was obvious to Larry Page and Sergey Brin that the next great computing wave would happen on phones — and phones, at the time, were controlled by carriers and by a handful of software vendors, chiefly Microsoft with its Windows Mobile ambitions.

The nightmare scenario was simple. If one company controlled the software gateway to mobile, it could decide which search engine came pre-installed, which maps app opened by default, which browser shipped on every device. Google could be locked out of the very future it depended on. The safest way to guarantee an open door was to build the door itself — and give it away for free, so that no single rival could ever slam it shut.

For two years, the Android team worked in near-total secrecy inside Google, building a Linux-based platform aimed at BlackBerry-style keyboard phones. Then, in January 2007, Steve Jobs walked onstage and unveiled the iPhone. The Android team, the story goes, watched the keynote and quietly realized their keyboard-first design suddenly looked ancient. They went back to the drawing board and rebuilt around a full touchscreen. The iPhone hadn’t killed Android — it had shown Android what it needed to become.

The alliance, the G1, and the long game

Google’s answer arrived on November 5, 2007, with the announcement of the Open Handset Alliance — a coalition of 34 companies including handset makers, chipmakers, and carriers, all committing to a shared, open mobile platform. Rather than sell phones itself, Google would hand Android to the whole industry and let a thousand manufacturers compete. It was the anti-Apple strategy: not one perfect device, but an open standard everyone could build on.

The first real Android phone reached customers in October 2008: the HTC Dream, sold in the United States as the T-Mobile G1. It was clunky next to the iPhone — a slide-out keyboard, a trackball, a body only an engineer could love. Reviewers were polite but unimpressed. Yet buried inside was the model that would win: a free OS, an open app market, and a business plan that didn’t depend on selling hardware at all. Google made its money when you searched, mapped, and watched — wherever you did it.

The math played out over the next decade. Because Android was free and open, manufacturers from Samsung to a hundred budget brands adopted it, pushing smartphones to price points Apple never chased. Today Android runs on an estimated 3.9 billion devices and is, by a wide margin, the most-used operating system on the planet. Larry Page would later reportedly call the acquisition one of Google’s best deals ever — and it’s hard to argue. Fifty million dollars, spent quietly in 2005, bought Google a permanent seat in every pocket on Earth.

The quiet acquisition had become the loudest victory in mobile. But owning the phone was only half the battle — next, Google needed to own the browser. In Part 14, we’ll look at how a project code-named Chrome set out to reinvent the web itself.


🔗 Explore more from Syncster

Comments

Popular posts from this blog

Cursor AI Review: Is the AI Code Editor Worth It?

I've been using Cursor as my main code editor for a while now, and enough people have asked whether it's worth switching to that a proper review felt overdue. Short version: for me, yes — but with caveats. What is Cursor? Cursor is an AI-first code editor built as a fork of VS Code. That means every extension, theme, and keybinding you already use in VS Code works here, but with AI woven directly into the editing experience instead of bolted on as a plugin. It's made by Anysphere and can run models from OpenAI and Anthropic under the hood. What I like Tab completion is uncanny. Cursor predicts your next edit — not just the rest of the line, but the next change across the file. Once you get used to hitting Tab, going back to a plain editor feels slow. The Composer / Agent mode. You describe a change in plain language and it edits multiple files at once, showing you a diff to accept or reject. For refactors and boilerplate, this saves real time. It unde...

MacBook Pro M5 vs M5 Pro: Which One Should You Actually Buy?

Apple's latest 14-inch MacBook Pro comes in two very different flavors: the base M5 and the step-up M5 Pro . On paper they look similar — same gorgeous Liquid Retina XDR display, same design — but under the hood the gap is bigger than the names suggest. Here's a clear, no-hype breakdown, with concrete use cases so you can match the chip to your work. Quick spec comparison Spec M5 M5 Pro CPU 10-core (4 performance + 6 efficiency) Up to 18-core (6 performance + 12 efficiency) GPU 10-core Up to 20-core Neural Engine 16-core 16-core Memory bandwidth 153 GB/s 307 GB/s (roughly double) Unified memory 16 / 24 / 32 GB 24 / 48 / 64 GB Max storage Up to 4 TB SSD Up to 8 TB SSD Battery (video playback) Up to 24 hours Up to 22 hours Media engines Single encode/ProRes engine More encode/ProRes engines (higher configs) What actually changes between them More cores — the M5 Pro nearly doubles CPU cores and adds GPU cores, so sustained, multi-threaded work finishe...

How I used Google Sheets and Apps Script

Google Sheet is one of the most powerful spreadsheet application that exists online, rivaling with Microsoft's Excel. One of the main strengths is its strong support for collaboration with other users, much easier and popular than collaboration tools with Microsoft Office. Aside from plain spreadsheet, it also supports extensions such as macro. If you are familiar with macros on other office tools, they work almost the same. However, the most extension I use and tinker with is the Apps Scipt . Apps Script Extension One of the challenges I faced recently is how do I track or monitor reports in our department if they are submitted on time or worst, forgotten due to lack of better monitoring tools. So I thought if there can be simple applications that can be deployed or use by a more general user to allow reminding periodically what reports are approaching due dates or those that are past dues. Then I looked for a way, instead of creating a full blown app from scratc...