← back to the graveyard
UF-012 Social network · Mixed Media Labs 2017

App.net — The Paid Twitter That Asked Users to Be the Customer

Lifespan
2012–2017 · ~5 yrs
Peak Users
100K+ users (May 2013)
Killed By
couldn't sustain a paid social network
Status
Shut Down

Summary

App.net was the ad-free, subscription-funded "Twitter alternative" that asked a genuinely good question — what if the users were the customers instead of the product? — and then could not find enough of them to keep the lights on. Founded by Dalton Caldwell and Bryan Berg under Mixed Media Labs, it launched on August 8, 2012 on a single, principled premise: members would pay a fee, so the service would answer to them rather than to advertisers, and the perverse incentives that warped ad-funded social networks would simply never apply. It was a real-time microblogging platform with a developer-friendly API at its core, and for a stretch it was the most idealistic thing on the social web.

The founding act was a crowdfunding campaign that became a referendum on whether people would pay for a better social network. Caldwell set a $500,000 goal and a hard deadline, and the campaign cleared it, ultimately raising roughly $803,000 from over 11,000 backers. Paid plans ran $50 a year or $5 a month, and a developer tier targeted the builders Caldwell believed would make the platform indispensable. In May 2013 App.net reported it had passed 100,000 users. The early excitement was real, and so was the affection of the small, technical community that gathered there.

The arithmetic, however, never closed. The thesis depended on a flywheel — paying members would attract third-party developers, whose apps would attract more paying members — and the flywheel never reached escape velocity. Renewals lagged, growth stalled, and on May 6, 2014 the founders conceded that subscription income could no longer fund full-time staff; App.net went into maintenance mode, kept running on autopilot from the revenue it still had. On January 12, 2017 Caldwell and Berg announced the service would close, and on March 14, 2017 it shut down for good, with the platform code open-sourced and user data deleted thereafter.

What App.net lost was not scale — it never had much — but a genuinely better idea, run by people who believed it. Its failure did not disprove the thesis that users should be the customer; it proved how hard that thesis is to fund when the incumbent is free and already has everyone's friends.

Timeline

2012
The grievance
Dalton Caldwell, frustrated by Twitter's tightening clamp on third-party developers, publishes an open letter and floats an ad-free, paid, API-first alternative.
July 2012
The pledge campaign
Mixed Media Labs launches a crowdfunding drive with a $500,000 goal and a fixed deadline — a public test of whether anyone will pay for social.
August 13, 2012
Funded
The campaign clears its goal, ultimately raising roughly $803,000 from over 11,000 backers; paid plans are $50/year or $5/month.
August 8, 2012
Launch
App.net opens as an ad-free real-time microblog built around an open API, pitching members as customers and developers as the growth engine.
February 25, 2013
The free tier
App.net adds a freemium model, letting paid members invite others to limited free accounts in a bid to widen the funnel.
May 2013
100,000 users
App.net reports passing 100,000 accounts — its high-water mark of momentum, modest against Twitter's hundreds of millions.
2013
The developer ecosystem
Third-party clients and apps proliferate around the API, the part of the platform its community valued most.
May 6, 2014
Maintenance mode
Caldwell and Berg announce renewals were too weak to retain staff; App.net continues on autopilot, funded only by remaining revenue.
January 12, 2017
The closing notice
The founders announce App.net will shut down, citing the failure to bridge the developer-and-user chicken-and-egg problem.
March 14, 2017
Lights out
The service shuts down; the platform code is open-sourced and user data is subsequently deleted.

A Better Bargain

App.net began as an argument. In mid-2012 Dalton Caldwell — a founder who had watched Twitter throttle the third-party developers who built its early ecosystem — published a widely read open letter contending that ad-funded social networks were structurally doomed to betray both users and developers, because their real customers were advertisers and their real product was attention. The fix, he proposed, was almost embarrassingly simple: charge the users. If members paid, the company would have to keep members happy, and the whole machinery of surveillance, feed manipulation, and developer hostility would have no reason to exist.

It was a clean thesis, and Caldwell put it to an immediate market test. Rather than raise venture money quietly, Mixed Media Labs ran a public crowdfunding campaign with a $500,000 goal and a deadline, framing the drive itself as proof of demand: if people would not pay up front, the idea was dead before launch. They paid. The campaign closed having raised roughly $803,000 from more than 11,000 backers, and App.net launched on August 8, 2012 with paid plans at $50 a year or $5 a month and a developer-grade API at its heart.

For the technically inclined, it was a breath of clean air — a real-time feed with no ads, no algorithm, no data brokering, and an open platform that welcomed the builders Twitter was busy alienating. The early community was small, sharp, and devoted. App.net had done the hard part: it had shipped a principled product and persuaded thousands to pay for it.

The Flywheel That Wouldn't Spin

The trouble was that "thousands" is not "enough." App.net's business model rested on a flywheel that had to spin fast to survive: paying members would draw third-party developers, whose differentiated apps would draw more paying members, whose fees would sustain the platform. Caldwell himself later named the failure precisely — the company never overcame the chicken-and-egg problem between developers and users. Initial developer adoption, he said, exceeded expectations, but that early enthusiasm never converted into a customer base big enough to make the developers' apps — or the company — viable.

The deeper obstacle was the one every Twitter alternative runs into: the network effect that cannot be purchased. People go where their friends and the conversation already are, and in 2012 that was Twitter, which was free and had everyone. A paywall, however principled, is a second barrier stacked on top of the cold-start problem — App.net asked newcomers not only to abandon their existing network but to pay for the privilege of doing so on an emptier one. The freemium tier added in February 2013 was an attempt to lower that wall, and it helped push the count past 100,000 in May 2013, but it could not manufacture the critical mass that makes a social network worth joining.

By the spring of 2014 the renewal math had turned decisive. On May 6, 2014, the founders announced that subscription renewals had fallen too far to fund full-time development staff. App.net did not shut down; it downshifted into maintenance mode, running on autopilot from whatever revenue remained — the social-network equivalent of leaving the lights on in a closed shop. It would stay in that twilight for nearly three years.

A Quiet, Honorable Closing

App.net's end, when it came, was unusually candid. On January 12, 2017, Caldwell and Berg posted a closing notice that did not blame users, the market, or bad luck, but named the structural failure plainly: the developer-and-user flywheel had never caught. The service would shut down, the data would be removed, and — fittingly for a platform built around an open API — the underlying code would be open-sourced so that anyone who believed in the idea could carry it forward. App.net went dark on March 14, 2017.

There was no scandal, no fire sale, no value-destroying acquisition — just a good idea that ran out of the one thing it most needed, which was members willing to keep paying. That made App.net a cleaner data point than most of the social graveyard. It did not collapse because it was badly built or badly run; by most accounts it was both well built and run with integrity. It collapsed because a paid social network has to win the network-effects war against a free incumbent before its subscription base can ever reach sustainability, and it never got close.

The irony, sharpened by hindsight, is that App.net's central complaint — that ad-funded social networks would inevitably abuse users and developers — aged extremely well. A decade later, the case against attention-and-advertising platforms had become conventional wisdom, and paid, user-aligned, often open-source alternatives were a live category again. App.net was right about the disease. It simply could not afford the cure.

The Five Factors

01
A network effect cannot be bought, and a paywall makes it harder to earn
People join where their friends and the conversation already are; charging admission stacks a second barrier on top of the cold-start problem. App.net asked users to leave a free network everyone was on and pay to join an emptier one — a near-impossible sell however sound the principle.
02
A two-sided flywheel must spin before the money runs out
The model needed paying users to attract developers and developers to attract paying users, each side bootstrapping the other. Initial developer interest was strong, but the loop never reached self-sustaining speed, and a flywheel that stalls below escape velocity simply coasts to a halt.
03
"Users as the customer" is the right principle and a brutal business
Aligning incentives by charging members fixes the moral problem of ad-funded social and creates a revenue problem in its place: you must convert a mass behavior people expect for free into a paid subscription. The thesis was vindicated in spirit and defeated in arithmetic.
04
Maintenance mode is a managed decline, not a recovery
When renewals could no longer fund staff in 2014, App.net kept running on autopilot rather than dying outright — humane, but terminal. A product frozen to conserve cash stops improving, gives members less reason to renew, and quietly accelerates the very decline it was meant to slow.
05
Being early and right is not the same as being viable
App.net's critique of ad-driven, developer-hostile social networks proved prescient, and paid and open alternatives later thrived. Correctly diagnosing a market before it is ready to pay for the cure is its own way to fail.

Aftermath

App.net's community was small, and its members — many of them developers and early-web idealists — dispersed to Twitter, to the open-source and IndieWeb projects some of them had been building alongside it, and to the federated networks that would follow. Notably, the App.net diaspora seeded a thread of micro-blogging projects, including Manton Reece's Micro.blog, that carried forward the same user-aligned, open principles. The open-sourced code meant the platform's death was a soft one: the idea survived even as the service did not.

App.net's lasting mark is as the honorable failure the next generation of social builders studied. It demonstrated both that thousands of people would pay for a better social network and that thousands were nowhere near enough — a sobering pair of facts for everyone who later attempted a paid or subscriber-funded alternative to the ad giants. When the case against attention-economy platforms became mainstream years later, App.net was remembered less as a flop than as a premature proof of concept: right about the problem, too early and too small to fund the answer.

Lessons

  1. A network's value lives in its members, so a paid social product must win the network-effects fight against free incumbents before subscriptions can ever sustain it — solve distribution first, monetization second.
  2. "Users as the customer" aligns incentives beautifully and monetizes terribly; if you charge for a behavior people expect for free, budget for the conversion to be the hardest part of the whole business.
  3. Don't build a business on a two-sided flywheel unless you can fund both sides through the cold years it takes to spin — a stalled flywheel coasts to zero.
  4. Treat maintenance mode honestly: freezing a product to save cash is a controlled decline, not a turnaround, and members can feel the difference long before the shutdown notice.
  5. Being early and correct is not a moat; the market has to be ready to pay for the cure, not just agree with the diagnosis.

References