Skip to main content

The Rise of Apple, Part 14: The App Store

THE RISE OF APPLE · PART 14The App StoreSYNCSTER· blog.syncster.dev
🍎 The Rise of Apple — a 20-part series. See all parts »  |  « Part 13: The iPhone

When the iPhone went on sale in June 2007, it came with a dozen or so apps, all made by Apple, and no way to add more. Steve Jobs was in no hurry to change that. A phone, he argued, had to be reliable in a way a computer didn't: nobody wanted a call dropped because some stranger's program had crashed the network. Developers who wanted in were offered what Apple called a "sweet solution": write web pages that looked like apps and ran in Safari.

Developers did not find it sweet. Web apps couldn't use the camera, couldn't work offline, and felt sluggish next to Apple's own. Within weeks, hackers had broken into the phone's software, and people were "jailbreaking" their iPhones to install games and tools nobody at Apple had approved. Some of the most talented programmers in the world were spending their nights finding holes in Apple's security, just to make the phone more useful. The demand could not have been clearer.

The change of heart

Inside Apple, the argument had been going on since before launch. Jobs worried about malware, battery life and a cluttered experience; others on the board and in the company pushed for opening the platform. In October 2007, just four months after launch, Jobs gave in, in his own way. In a short note on Apple's website, he announced that a software development kit for native iPhone apps would arrive in February. It would take until February, he wrote, because Apple was trying to do two things at once: give developers an advanced, open platform, and protect users from viruses, malware and privacy attacks.

The kit arrived in March 2008, a few weeks late, at an event that laid out the entire business. Anyone could join the developer programme for $99 a year. Developers would set their own prices, and Apple would keep 30% of every sale for hosting, payments and distribution, passing on the other 70%. Free apps would cost developers nothing beyond the fee. Every app would be reviewed by Apple before it went on sale, and the only way onto an iPhone would be through Apple's store. On stage that day, venture firm Kleiner Perkins announced a $100 million fund just for iPhone start-ups.

The terms were a quiet revolution. Getting software onto a phone used to mean negotiating with each carrier, who took a large cut and decided what customers saw. Apple simply removed the carrier from the deal. A teenager in a bedroom could now reach every iPhone owner in the world on the same terms as a large company.

From "no apps" to a billion downloadsHow the App Store came together, and the deal it offered developersEvery sale, splitDeveloper70%Apple30%Apple's share paid for hosting, payments and review. Free apps cost developers nothing beyond the $99 yearly fee.The road to the storeJun 2007iPhone ships; developers are told to build web appsOct 2007Jobs promises a software kit for native appsMar 2008The iPhone SDK, the $99 programme and the 70/30 splitJul 2008App Store opens with about 500 appsApr 2009One billion apps downloaded

Five hundred apps, and a gold rush

The App Store opened on July 10, 2008, a day before the iPhone 3G went on sale. It launched with about 500 apps, roughly a quarter of them free. Some were serious: an eBay app, a Facebook app, banking and news. Many were games, from Sega's Super Monkey Ball to small titles made by a single person. The iPhone 3G itself fixed the biggest gaps in the first model, adding faster 3G data and GPS, and its price dropped to $199 with a contract. In its first weekend, people downloaded more than 10 million apps.

Stories of overnight success followed. Small games earned their makers more in a month than a year's salary; one developer quit his job after a simple artillery game made him hundreds of thousands of dollars in a few weeks. There were absurdities too, like a $999.99 app called I Am Rich, which did nothing but show a glowing red gem. Apple pulled it within a day, after a handful of people had bought it. By April 2009, the store had passed one billion downloads, less than a year after it opened, and Apple's advertising had a new catchphrase: "There's an app for that."

Gatekeeper

The same control that made the store safe made it controversial. Apple's reviewers rejected apps for duplicating Apple's features, for content it didn't like, or for reasons developers struggled to understand. Rules were written, rewritten and enforced unevenly, and a rejection could wipe out months of work overnight. Developers grumbled, but almost none left. There were too many customers on the other side of the gate.

The store also changed what the iPhone was. It was no longer one device with a fixed set of features but whatever its owner needed it to be that day: a game console, a map, a flashlight, a bank, a camera, a newspaper. Google opened its own Android Market that October, and a phone without a large app store quickly stopped being a serious competitor. BlackBerry and Nokia, who had led the industry a year earlier, would spend the next few years trying to catch up and never did.

For Apple, the App Store was the iTunes Music Store all over again, on a much larger scale: a store that existed to sell the hardware, and that also made a steady stream of money of its own. It also gave Apple a new kind of power, as the toll booth between hundreds of thousands of developers and their customers. That power would make Apple a fortune, and one day land it in court.

Next in the series: 2010 — the iPad, a new category of device, and the start of the post-PC era.


🔗 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...

Running a Server on a Mac Mini: Apple Silicon vs the Home-Server Field

The Mac Mini has quietly become one of the most interesting home-server boxes you can buy. It’s tiny, nearly silent, sips power, and Apple Silicon punches far above its weight. But is it actually the right machine to run your services on — or are you paying an Apple tax for a job a $400 mini PC does better? Let’s put it head-to-head. Why a Mac Mini makes a surprisingly good server Three things make Apple Silicon compelling as an always-on machine: Performance per watt. This is the headline. An M4 Mini idles at just a few watts and rarely pushes past ~35W under load, while delivering multicore performance that embarrasses machines drawing twice the power. Silence. Under typical server loads the fan is inaudible. If your “server” lives in a living room or bedroom, this matters more than any benchmark. Footprint. It’s the size of a coaster and runs cool, so it tucks anywhere. The honest catch It’s not all upside: macOS isn’t...