Samsung Launches the Galaxy S4

Samsung announced the Galaxy S4 on March 14, 2013, at a theatrical event at Radio City Music Hall in New York — 3,000 people attended — and launched it globally in April 2013, priced around $649 unlocked ($199–$249 on two-year contracts in the US). The S4 had a 5-inch Full HD (1920×1080) Super AMOLED display at 441 PPI, up from the Galaxy S3’s 4.8-inch 306 PPI display. Samsung shipped two different chipsets by region: a Qualcomm Snapdragon 600 (quad-core 1.9 GHz) in North America, Europe with LTE, and several Asian markets, and a Samsung Exynos 5410 (octa-core, but only 4 active at once using big.LITTLE) in other markets. Both had 2GB RAM.

Samsung layered TouchWiz extensively over Android 4.2.2: Smart Pause (front camera detected the user’s eyes and paused video when they looked away), Smart Scroll (tilted the screen to scroll), Air Gestures (waved a hand to answer calls or browse photos without touching the screen), Multi-Window (two apps running side-by-side on the home screen), Samsung Hub (music/books/video store), and S Health (step counting and fitness tracking). Air Gestures and Smart Pause received significant marketing attention but required specific conditions to work reliably and were rarely used by most owners. The S Health app predated Apple’s HealthKit by a full year.

Samsung sold 10 million Galaxy S4 units in the first month — reaching that milestone faster than any previous Samsung phone — and approximately 80 million total over the product’s lifetime. The Galaxy S4 briefly displaced the iPhone 5 as the world’s best-selling smartphone in early 2013. The juxtaposition of heavy software differentiation against Android’s fragmentation was visible to developers: Samsung-specific APIs (Multi-Window, S Pen support on Note devices) required testing on Samsung devices separately from AOSP Android, and Samsung’s slow OS update cadence (Android 4.4 KitKat arrived for the S4 nearly a year after Android launch in the US in mid-2014) meant users were often one to two major Android versions behind.

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 technology, computing-history, 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.