WhatsApp Is Founded

Jan Koum and Brian Acton incorporated WhatsApp Inc. in California on February 24, 2009. Both had recently left Yahoo — Koum after nine years as an infrastructure engineer, Acton after eleven years in various engineering and product roles. They had applied to Facebook in 2009 and been rejected. Koum’s initial concept was for an app that would show a short status beside each contact in your address book — not messaging, but presence: “at the gym,” “on a call,” “battery low.”

Apple’s push notification system, introduced in June 2009 with iPhone OS 3.0, changed the trajectory. WhatsApp could send a notification when a contact updated a status, and users began responding to status updates as if they were messages. Koum rebuilt the app around direct messaging in version 2.0 in August 2009, and downloads jumped from a few thousand to 250,000 within days. The key structural decision was using phone numbers as identity — verification happened via SMS, and the contact list was already populated with everyone the user knew, eliminating the discovery problem that had slowed adoption of earlier mobile messaging apps like BlackBerry Messenger (which required a PIN exchange) and AIM (which required a screen name).

WhatsApp reached 200 million active users by April 2013 and 450 million by February 2014, when Facebook announced its $19 billion acquisition. The team had grown to only about 55 engineers — an unusually small number attributed to their Erlang backend, which handled fault-tolerant concurrent connections efficiently, and a deliberate policy of no advertisements, no games, and no gimmicks that kept the product surface narrow. Acton co-founded Signal Foundation in 2018 after leaving Facebook over disagreements about monetization and data privacy; Koum resigned the same year for similar reasons.

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 software, programming, and 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.