The Slop Wall Is Here: Steam and Apple Have No Filter

The prediction finally paid out — and it paid out on two storefronts simultaneously. In October 2026, Steam's Next Fest featured over 8,000 demos (roughly double the June edition), with players begging Valve for a "No AI" filter as vibe-coded slop buried the catalog. Meanwhile, Apple's App Store absorbed 560,000 new apps in H1 2026 alone — nearly double the prior year — while downloads grew just 2%. Two distribution monopolies, two different failure modes, one shared problem: neither gatekeeper has a quality gate that scales to the volume AI tooling now produces.

📖 Read the full version with charts and embedded sources on ComputeLeap →

This is the slop wall. And nobody has an answer yet.

View original article on Kotaku →

The Numbers Are Not Subtle

Let's be concrete about the scale. According to SteamDB data cited by Kotaku, more games were added to Steam in the first ten months of 2026 than in all of 2025 (which itself set a record at 21,248 releases). SteamPageAnalyzer projects at least 24,000 by year's end. Nearly 20% of 2025 releases disclosed generative AI use — an 800% year-over-year jump — and 2026 is tracking far higher.

On the App Store side, Sensor Tower data reported by The Information shows 235,800 new apps in Q1 2026, an 84% increase year-over-year. The full first half reached roughly 560,000 new submissions. But here's the number that matters most: downloads rose just 2% to 17.6 billion. Supply doubled. Demand didn't move.

That gap — supply growing exponentially while demand flatlines — is the slop wall in one data point. The marginal cost of creating and submitting an app or game just collapsed to near-zero. The marginal cost of getting anyone to care about it did not.

View original article on The Next Web →

Two Gatekeepers, Two Broken Responses

What makes this moment instructive isn't just the volume. It's that Valve and Apple chose opposite strategies — and both are failing.

Valve: Disclose, But Don't Filter

Valve rewrote its AI disclosure rules in January 2026. Developers must declare AI-generated content that ships in the game or appears in marketing, and they retain full liability for copyright and safety. But Valve explicitly carved out an exception for AI coding tools used in development — the exact tools driving the vibe-coding flood.

The result is a disclosure system without a filter. Players can see the AI label but cannot exclude games tagged with it. The biggest community request — a tag-based exclusion filter for generative AI content — remains unimplemented. Meanwhile, Epic Games CEO Tim Sweeney called Valve's disclosure requirement "really irresponsible", arguing it encourages boycotts. Epic then went and built its own launcher with vibe coding, which tells you everything about where incentives point.

View original article on VGC →

Apple: Block the Tools, Not the Output

Apple took the opposite approach. Instead of labeling AI-made apps, Apple cracked down on the vibe coding platforms themselves — removing Anything, blocking updates to Replit and Vibecode, and citing Guideline 2.5.2 (which bars apps from executing code that changes their own functionality). Apple told The Information the issue is about specific rule violations, not vibe coding as a concept.

But this response has a structural flaw: it targets the creation tools while leaving the output untouched. An app built with Cursor, Claude Code, or any desktop-based AI tool doesn't trigger Guideline 2.5.2 — only apps that let users generate code on-device do. So Apple is blocking the most visible vibe coding platforms while the invisible ones (every developer using an AI assistant on their laptop) ship apps unimpeded.

The evidence that this isn't working: review times have reportedly ballooned from 24 hours to as many as 30 days, and enforcement is inconsistent — some vibe-coded apps remain available while others are rejected without clear explanation.

ℹ️ The paradox in one stat: Apple's App Store saw 560,000 new apps in H1 2026. Downloads rose 2%. The average new app is now a rounding error in the store's attention economy.

The Analyst Warning Nobody's Heeding

Circana analyst Mat Piscatella put it bluntly on Bluesky: "Good games will get cloned and buried." His argument is that vibe coding lets developers replicate another studio's game in hours rather than months, and that players will default to established franchises rather than sorting through mountains of near-identical copies.

The cloning problem is already visible. Kotaku reported that recent AI capabilities have made decompile-and-port workflows easier than ever, with people building near-copies of games ranging from indie hits to major franchises. Godot, the open-source game engine, banned AI-generated contributions entirely, stating flatly that "AI cannot take responsibility" for code quality.

This isn't a Steam-only phenomenon. On the App Store, Gizmodo reported that the vibe coding boom has produced an entirely new occupation: "vibe coding cleanup specialists" who fix the broken code AI tools generated. The 404 Media story about Pieter Levels' vibe-coded flight simulator earning $50,000 a month gets cited as a success story — but the subhead tells the real story: "Yours probably won't."

View original article on 404 Media →

Reddit Is Running the Split in Real Time

The most telling signal isn't coming from industry reports — it's on Reddit's front page, where the euphoria and the backlash are running simultaneously.

On r/ChatGPT, a post titled "You can literally just recreate almost any app in a day" hit 2,180 points with 625 comments. The post showcases app cloning as a capability flex — look what I built in a single session. In the same 24-hour window, r/technology pushed "Don't be fooled. The AI that was supposed to save us time is doing just the opposite" to 1,900 points with 294 comments, linking to a Guardian op-ed arguing that AI's time-saving promise is illusory.

These aren't contradictory positions. They're two descriptions of the same phenomenon from opposite sides. Yes, you can recreate almost any app in a day. No, that doesn't mean the output is useful. The people building are thrilled. The people filtering are drowning.

View original analysis on Naavik →

⚠️ The Contrarian Corner: The "slop flood" panic may be overblown. Most low-effort apps die on the vine within days. Steam's algorithm already buries zero-engagement titles. The real problem isn't volume — it's that critics conflate "made with AI" with "low quality," which punishes developers who use AI tools responsibly. A CodeRabbit analysis found AI co-authored code had approximately 1.7x more major issues than human code — significant, but not the catastrophe the discourse implies. The market may self-correct faster than gatekeepers can regulate.

What Breaks Next: The Discovery Crisis

The immediate crisis isn't creation quality. It's discovery. When the cost of producing and distributing software drops to near-zero, the bottleneck shifts entirely to attention and curation. And the current curation infrastructure wasn't built for this volume.

Steam's discovery is algorithmic — it surfaces titles based on wishlist velocity, engagement metrics, and review scores. In theory, this should bury slop automatically. In practice, the algorithm can be gamed by volume: pump out ten near-identical games, and one might catch enough early engagement to enter the recommendation loop. Circana's Piscatella predicts this drives players toward known franchises and makes indie breakouts rarer.

Apple's discovery is editorial + algorithmic — App Store features are hand-curated, and search results factor in ratings, downloads, and relevance. But editorial curation doesn't scale to 560,000 new apps per half-year. Former App Store chief Phillip Shoemaker warned that the surge could strain Apple's review resources and open the door to malicious actors.

What comes next is third-party curation layers. The pattern is already emerging:

• Steam curators who manually screen for AI content are gaining followers
• Review aggregators that flag AI-generated assets are being discussed on gaming subreddits
• App Store analytics companies like Sensor Tower are building AI-content detection as a service offering
• Community-maintained blocklists, similar to ad-blocker filter lists, are being prototyped

The gatekeeper platforms won't solve this themselves because they're structurally conflicted. Valve and Apple both take a cut of every transaction — more listings means more potential revenue, and filtering too aggressively means killing the growth metrics that Wall Street rewards.

View original interview on Kotaku →

What This Means for Builders

If you're shipping software with AI tools — and most of us are, at this point — the slop wall changes your competitive landscape.

Your moat is no longer "I built it." When anyone can recreate almost any app in a day (as the r/ChatGPT post celebrates), the act of building stops being the differentiator. What differentiates is everything after the build: polish, community engagement, retention mechanics, customer support, and trust. These are exactly the things that AI tools can't vibe-code.

Distribution cost just became your biggest expense. With storefronts flooded, the cost of standing out — marketing, SEO, community building, press outreach — now dwarfs the cost of development. This inverts the traditional software business model, where development was the expensive part and distribution was "just shipping to the store."

Quality signals matter more than ever. Reviews, engagement metrics, user retention data — these are the signals that storefront algorithms will increasingly weight to separate signal from noise. If you're shipping with AI tools, invest in the post-launch experience rather than the pre-launch build.

If you're thinking about getting into vibe coding yourself, our practical guide for founders breaks down what actually works and what breaks. And if you're evaluating the AI coding tools behind this wave, our comparison of the best AI coding assistants covers the current landscape.

💡 The practitioner's playbook: Ship fast with AI, then invest everything saved in polish and community. The first-mover advantage in a slop flood belongs to whoever has the best post-launch retention, not the fastest prototype. Build what vibes can't: trust.

The Historical Parallel: We've Seen This Before

This isn't the first time a distribution channel hit a slop wall. YouTube faced its own version in 2017-2019 with "Elsagate" — algorithmically generated children's content that flooded the platform with bizarre, low-quality videos produced at machine scale. YouTube's response was a mix of algorithmic demotion, human review expansion, and advertiser pressure. It took years and billions of dollars in review infrastructure before the problem was even partially contained.

The App Store had a smaller version in 2012-2013, when template-based app builders flooded iOS with reskinned apps. Apple responded by tightening review guidelines and eventually purging hundreds of thousands of titles. But that era's templates produced dozens of copies per developer. Today's AI tools can produce dozens per hour.

The scale multiplier matters. When YouTube faced Elsagate, the solution — hiring thousands of human reviewers and building content classifiers — was expensive but tractable. The ratio of problematic content to review capacity was manageable. In 2026, the production rate of AI-generated software may already exceed any feasible human review capacity. This is why the filter will almost certainly be AI-powered itself — the only thing that scales as fast as AI generation is AI classification.

Looking Forward: Three Predictions

First, Valve will add an AI content filter within six months. The community pressure is too loud and the implementation is trivial — the disclosure data already exists; Valve just needs to connect it to a user-facing toggle. The question is whether Valve makes it opt-in (users choose to hide AI content) or opt-out (AI content hidden by default). Our prediction: opt-in, because opt-out would crater too many listing metrics.

Second, Apple will shift from blocking tools to rating outputs. The Guideline 2.5.2 approach is a game of whack-a-mole. Apple's long-term play is more likely to be automated quality scoring — using its own AI to evaluate submitted apps for code quality, originality, and security before human review. Think of it as a pre-review filter that catches the lowest-effort submissions before they consume human reviewer time.

Third, third-party curation will become a business category. Just as Wirecutter built a business on curating products from Amazon's infinite shelf, someone will build the equivalent for AI-era app stores. The data inputs exist (reviews, engagement metrics, code analysis, asset originality scores). The demand exists (users drowning in slop). The business model exists (affiliate revenue, premium subscriptions, B2B licensing to enterprises that need to vet tools). The gap is execution.

The slop wall is here. The filter hasn't been built yet. Whoever builds it owns the next layer of software distribution.

Originally published at ComputeLeap