The Cycle Everyone Recognizes But Nobody Named

There's a pattern every internet user knows intimately but rarely articulates. A platform launches. It's generous, even delightful — free storage, clean interfaces, organic reach. Users flock to it. Creators build on it. Communities form. Then, slowly, the screws tighten. Features become paywalled. Feeds become algorithmic. Ads multiply. The platform pivots from serving users to extracting from them. The experience degrades. Everyone complains. Nobody leaves — until they do.

This pattern now has a name that's gone viral across developer forums, tech blogs, and social media: enshittification. Coined by writer Cory Doctorow, the term describes the lifecycle where platforms systematically degrade user experience to maximize extraction at every stage. And right now, the internet is having a collective moment of recognition that this isn't accidental — it's the business model.

Why This Concept Is Exploding Now

Several forces have converged to push this conversation from niche criticism to mainstream cultural moment:

• Algorithmic exhaustion: Users across every major platform report that feeds feel manipulative, repetitive, and hostile to genuine connection. The algorithm that once showed you friends' updates now buries them under sponsored content and engagement-bait.
• Creator burnout: People who built audiences on platforms are watching their organic reach collapse to single-digit percentages, forcing them into pay-to-play models that feel like extortion.
• Subscription fatigue: Every service that was once free or affordable now demands monthly payments while delivering less value than before.
• AI content flooding: The platforms that once curated human creativity are now drowning in synthetic content, making the user experience worse while the metrics look great to advertisers.

The result? A pervasive sense that the internet is being actively made worse by the companies that control it. Not through incompetence, but through design.

The Three Stages of Platform Decay

Understanding the mechanics helps you spot the pattern early — and resist it.

Stage One: Be Generous to Users

Platforms start by losing money on users. Free storage, zero fees, powerful APIs, generous terms of service. The goal is acquisition at any cost. Users are the product being built — to be sold later. Think of early social networks with open APIs, early streaming with full catalogs, early cloud services with massive free tiers.

This phase creates dependency. Users invest time, data, social graphs, and creative work. The switching costs compound silently.

Stage Two: Shift Value to Business Customers

Once users are locked in, the platform pivots to extracting surplus from users to benefit advertisers or business customers. Organic reach drops. Algorithms prioritize paid content. User data becomes the commodity sold. The platform becomes a toll booth on the relationships and content users built.

Stage Three: Squeeze Everyone

With both users and business customers dependent, the platform extracts from both sides simultaneously. Ad rates increase. Creator payouts decrease. User experience degrades further. The platform becomes a rent-seeking monopoly on its own decay.

Each stage is rational from the platform's perspective. Each stage makes the next stage more inevitable. And each stage makes leaving harder — until the pain of staying exceeds the pain of migrating.

The Counter-Movement: Users Are Building Exit Ramps

Here's where the conversation shifts from diagnosis to action — and where it gets genuinely interesting for developers and technologists.

A growing ecosystem of projects, protocols, and communities is emerging around the principle that user sovereignty is an architectural feature, not a corporate promise.

Decentralized Protocols

Federation protocols are maturing. Instead of one company controlling a platform, interoperable servers let users choose their host while communicating across the network. If your server enshittifies, you migrate — without losing your identity or connections.

Self-Hosted Stacks

Open-source alternatives to every major platform category now exist. Photo management, note-taking, social feeds, file storage, communication — all deployable on hardware you control. The setup friction has dropped dramatically, and community-maintained guides make it accessible even for non-developers.

Data Portability Tools

Projects focused on standards for data export, identity portability, and cross-platform migration are reducing the switching costs that platforms rely on. When you can take your graph, your content, and your history with you, the lock-in crumbles.

Creator-Owned Infrastructure

Creators are increasingly building on infrastructure they control — personal websites, email lists, payment rails that don't route through platform toll booths. The tools for this have never been better or more accessible.

Practical Takeaways for Developers

If you're building products in this landscape, the enshittification cycle offers both warnings and opportunities:

1. Audit your own incentives. Every product has a business model. Map yours explicitly. Where does extraction creep in? What would it look like to align revenue with user success instead of user dependency?
2. Build for exit. The most ethical products make leaving easy. Robust data export, standard formats, clear migration paths — these aren't features that drive churn. They're features that build trust, and trust is the scarcest resource on the internet.
3. Choose interoperability over moats. Walled gardens accelerate enshittification. Open protocols create resilient ecosystems. If your product only works within your own ecosystem, you're building a future extraction machine.
4. Resist the surveillance dividend. Advertising isn't inherently extractive, but surveillance advertising always is. If your revenue depends on knowing more about users than they'd voluntarily share, your product will inevitably degrade their experience to harvest that data.
5. Invest in community governance. Products governed by their users don't enshittify — because the people experiencing the degradation have the power to stop it. Cooperative models, open-source governance, and community oversight aren't just idealistic; they're structural safeguards.

The Bigger Picture: Infrastructure vs. Ecosystem

The enshittification conversation reveals something fundamental about the internet's current power structure. When infrastructure is owned by companies that profit from user lock-in, degradation is inevitable. The business model demands it.

The counter-movement isn't just about better products. It's about a different relationship between people and their digital infrastructure. One where the tools serve the people using them — not the other way around.

This is why the conversation matters beyond individual platform complaints. The question isn't whether your favorite app will get worse. It will. The question is whether you'll have alternatives when it does — and whether you'll recognize the pattern early enough to act.

The internet is talking about platform decay because they're living through it. But the conversation is shifting. From frustration to understanding. From understanding to architecture. From architecture to alternatives.

The platforms will keep squeezing. The question is whether the next internet they squeeze is one anyone still wants to use.