Android 1.0: Why Its First Launch Took Three Different Dates

On September 23, 2008, Android reached version 1.0 and the first Android phone was announced. Buying that phone and downloading the platform’s source code still belonged to October. Eighteen years later, those separate milestones explain what Android actually offered.

A birthday is easy to remember. A platform is harder to pin down. The Nerd Calendar marks September 23 as Android’s first release, but that compact label hides three different kinds of arrival: a dependable target for app developers, source code for people building the system, and a phone that customers could take home.

The distinction is more useful than a dispute over which date deserves a cake. Each milestone removed a different obstacle. Looking at them together reveals why a mobile operating system is more than the software inside one handset—and why a product announcement does not mean everyone can participate immediately.

September 23: developers get a target they can build against

Google’s Android 1.0 SDK announcement is unusually helpful about what changed. T-Mobile had just announced the G1; Google released the first version of the 1.0 software development kit. Earlier development releases already existed. This was a transition from preparation toward a supported application target, rather than the first moment anyone outside Google could experiment with Android.

An SDK packages the tools and information used to build applications. An API is the interface through which an application requests a platform’s capabilities. The announcement’s practical promise was that developers could now rely on those interfaces when preparing apps for Android 1.0-compatible devices.

Imagine writing an application while the services it calls keep changing their names or behaviour. Some of your work becomes repair work before a customer ever sees it. A defined release reduces that moving-target problem. It does not promise that every future version will be identical; it gives a developer something concrete to finish against.

October 21: the system becomes available as source code

The September post still described the open-source release as a future event. On October 21, Google announced that Android’s source code had been released with its Open Handset Alliance partners. The same post placed the G1’s retail arrival on the following day.

That is a different door opening. An application developer needs the platform’s interfaces; someone studying or adapting the platform needs its implementation. An SDK and a source release therefore answer different questions: “How do I write something for this system?” and “How does the system itself work?”

This also makes Android’s relationship with earlier computing culture more interesting than a familiar logo. Our account of Linux’s first source release in 1991 explores another moment when making code available created an invitation to participate. The projects and circumstances differ, but the distinction between using software and being able to inspect its construction is central to both stories.

October 22: the phone reaches US customers

The G1 supplied the physical object around which those promises could become everyday habits. A touch screen and a QWERTY keyboard made it a particularly tangible bridge between ways of using a phone. But its announcement and its availability were separate events.

T-Mobile’s launch release states in its dated body that US sales began on October 22, 2008, online and in selected stores nationwide. The archive currently displays October 21 above that text. The October 22 dateline and Google’s independent statement that sales would start the next day make the intended retail date clear.

The geographical qualifier matters too. A US retail launch is not a simultaneous worldwide launch. “Released” without an object or a market can quietly turn several different events into one seemingly precise fact.

A fourth detail: the app marketplace had its own timetable

Android Market opened to users alongside the phone on October 22. Google’s contemporary Market announcement reported more than 50 available applications and set October 27 as the start of general developer registration and uploading. An update confirmed that publishing had opened on that Monday.

So even the marketplace did not arrive in a single indivisible instant. Customers could browse its initial selection before the general publishing entrance opened. Buying software was another developing part of the service: the October announcement presented paid applications as a future addition.

This is a useful corrective to the temptation to project a mature app economy backward onto its first day. A distribution channel needs software, people who can find it, and a route for new contributions. Those pieces can come together at different times while still belonging to one launch.

Open source did not mean every familiar Google app

There is another boundary hidden inside the word Android. In a September 2009 clarification, Google explicitly distinguished the open platform from its own applications. Services such as Gmail and YouTube had Android apps, but those apps were not included as open-source components in the platform’s source repository.

This later explanation helps interpret the earlier promise without turning it into a claim that everything on a phone shared the same terms. A working handset can combine a platform, applications and services that have different owners and distribution arrangements. Seeing them together on one screen does not erase those boundaries.

Three questions make the anniversary clearer

When someone asks when Android launched, first ask which experience they mean. For the 1.0 SDK and G1 announcement, September 23 is the relevant date. For the public source release, it is October 21. For the G1’s US retail availability and the Market’s opening to users, it is October 22.

These dates do not compete so much as describe different participants. Developers needed a stable enough destination for their work. Platform builders needed the source. Customers needed a device and a reason to keep using it. The historical sequence becomes easier to understand once each date has a subject.

The anniversary celebrates an invitation taking shape

September 23, 2026 marks eighteen years since Android 1.0’s SDK release. Its most revealing legacy in this story is the structure of the launch: tools, source, hardware and distribution had to meet before the promise became a usable platform.

The G1 made that future visible. The dates around it show how other people could begin to build, adapt and use it. Keep the birthday—but keep the October pages of the calendar open as well.