Apple Releases the iPhone SDK

Apple released the iPhone SDK on March 6, 2008, at a press event where Steve Jobs presented it alongside the announcement of the App Store. The original iPhone had launched in June 2007 with no SDK; Jobs had told developers at WWDC 2007 that the way to build iPhone applications was to create web apps in Safari, arguing that iPhone’s full Safari browser meant web apps could be “as good as any native application.” Third-party developers found this inadequate — web apps had no access to the camera, microphone, accelerometer, GPS, contacts, or phone, and had no presence on the home screen.

The SDK, available as a beta on March 6 and formally released with iPhone OS 2.0 in July 2008, bundled Xcode 3.1, Interface Builder, and an iPhone simulator into a free download for registered Mac developers. Applications were written in Objective-C using Cocoa Touch — a slimmed-down version of the Mac’s Cocoa frameworks — and compiled to native ARM Thumb code for the Samsung-manufactured ARM1176JZF-S running at 412 MHz. Code signing was mandatory: only Apple-signed developer certificates allowed installation on real devices. Distribution required submission through iTunes Connect, Apple review, and pricing in the App Store; Apple would take a 30% revenue share, with 70% going to the developer.

The App Store opened July 10, 2008 with approximately 500 applications. By the end of 2008, over 10,000 apps were available and developers had earned over $200 million. The code signing and mandatory review model was the most commercially and legally significant decision in the SDK announcement: it made the iPhone a curated platform where Apple controlled which software could be installed, setting the template for the iOS ecosystem structure that remained in place through the 2020s, when antitrust regulators in the European Union, the United States, and Japan began requiring Apple to allow alternative app distribution.

Why This Moment Mattered

The event is useful to read as a platform signal, not only as a product announcement. In the short term, it gave users and developers something concrete to react to. In the longer term, it became part of a larger pattern in hardware, computing, history: hardware, software, services, and user expectations were all changing at the same time.

A good technology milestone usually matters for more than one audience. Enthusiasts notice the specifications or the interface first. Developers ask what new assumptions they can make. Companies look at cost, compatibility, and strategy. Ordinary users mostly notice whether the result makes their devices faster, easier, safer, or more useful.

The Broader Context

This period of computing was shaped by several overlapping transitions: faster networks, more capable mobile devices, cloud infrastructure, stronger security expectations, and software that changed continuously after release. Against that background, the milestone was not an isolated headline. It was one piece of a much larger movement away from static products and toward connected platforms.

That context helps explain why some announcements that looked modest at the time became important later. A browser feature, processor change, development tool, or platform policy can alter what future products are able to assume. Once enough users, developers, and vendors adapt, the new assumption becomes normal.

Looking Back

The value of revisiting the moment is that it shows how technology history is built from many medium-sized steps. Some are celebrated immediately, while others become meaningful only after the ecosystem catches up.

Looking back also keeps the story balanced. Progress usually brings tradeoffs: performance against power use, openness against consistency, convenience against control, and speed against stability. The most interesting milestones are the ones that reveal those tradeoffs clearly. This one belongs in that category because it helps explain not just what changed, but why the direction of computing kept moving the way it did.