Skip to main content

The Rise of Apple, Part 11: 1,000 Songs in Your Pocket

1,000 Songs in Your Pocket

🍎 The Rise of Apple — a 20-part series. See all parts »  |  « Part 10: Think Different

By the start of 2001, Apple had stopped dying. The iMac had sold by the millions, the balance sheet was healthy again, and the four-quadrant product grid had given the company a spine. But Steve Jobs wasn't interested in simply being a profitable computer maker. He had a bigger thesis — one he called the “digital hub.” The personal computer, he argued, would become the center of your digital life: the place where your camcorder footage, your photos, and above all your music would live and be organized. The Mac wouldn't just compute. It would curate.

The problem was that in early 2001, the music part of that story barely existed. And the device that would make it famous hadn't been built yet.

A jukebox called iTunes

The software came first. On January 9, 2001, at Macworld in San Francisco, Jobs introduced iTunes — a free application for the Mac that let you rip your CDs into digital files, organize them into playlists, and burn them back onto blank discs. Apple hadn't written it from scratch. The company had quietly acquired a well-regarded Mac MP3 jukebox called SoundJam MP and brought its developers, including engineer Jeff Robbin, in-house to rework it into something simpler and more Apple. The “i” prefix, borrowed from the iMac, signaled that this was a consumer product, not a hobbyist's toolkit.

iTunes solved half the equation: your music was now organized on your Mac. But a hard drive in a beige tower isn't exactly portable. The MP3 players you could actually buy in 2001 were, in Apple's own blunt assessment, either “big and clunky or small and useless.” Flash-memory players held a dozen or so songs. The hard-drive players that held more were heavy bricks with interfaces Apple described as “unbelievably awful.” Nobody had made a music player you'd actually love to carry. That was the opening.

Nine months to a pocket

Jobs handed the hardware problem to Jon Rubinstein, Apple's hardware engineering chief, who had spotted a crucial enabling part: a tiny 1.8-inch Toshiba hard drive that could hold 5 gigabytes in a package small enough to fit in a shirt pocket. Rubinstein recruited Tony Fadell, a contractor with a background in handheld devices, to lead the project. Working with the chip firm PortalPlayer and a famously punishing timeline, the team went from concept to shipping product in roughly nine months.

The breakthroughs weren't only about the drive. FireWire let the device sync an entire music library in minutes rather than the hours USB 1.1 would have demanded. And the now-iconic scroll wheel let you spin through a thousand songs with your thumb instead of jabbing at buttons. The hardware and iTunes were designed to work as one system: plug in the iPod, and it silently mirrored your library. No file management, no fiddling. It just filled up.

On October 23, 2001 — just weeks after the September 11 attacks, with the tech industry in a nervous crouch — Jobs stood on a small stage and pulled the first iPod from his jeans pocket. Five gigabytes, he said, meant “1,000 songs in your pocket.” It weighed about 185 grams and cost $399. It went on sale on November 10. The reaction was not universal applause: $399 was expensive, and because it required FireWire and iTunes, it worked only with Macs — a tiny slice of the computer market. Skeptics on tech forums joked that iPod stood for “idiots price our devices.”

The flywheel that rewrote the company

They were wrong, but it took a couple of years and two more decisions to prove it. The first was opening the iPod to Windows users — a move Jobs reportedly resisted before relenting, because tying his hottest product to the Mac's small market was leaving the device stranded. The second, and larger, was answering the question iTunes couldn't: where do you legally buy the songs? In an era defined by Napster and rampant piracy, Apple negotiated with the major record labels and, on April 28, 2003, launched the iTunes Music Store — a catalog of songs you could buy individually for 99 cents each, with no subscription and no strings. It sold over a million songs in its first week.

That was the flywheel. iTunes organized your music; the Store sold you more of it; the iPod carried it everywhere; and every step pulled you deeper into Apple's ecosystem. The device that pessimists had written off became a cultural object — the white earbuds turned into a visual shorthand for the whole decade. Over its lifetime, Apple would sell roughly 450 million iPods, and for several years the little music player, not the Mac, was the engine of the company's growth.

More than the revenue, the iPod changed what Apple believed it was. The company had just proven it could design a world-beating consumer electronics device, build the software to run it, and run the service that fed it — all stitched into one seamless experience. That template — hardware, software, and service as a single product — was the exact playbook Apple would soon point at a far bigger target.

Next time: Apple drops the word “Computer” from its name — and bets everything on a phone.


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