Building Just Got Cheap. Attention Didn't.

Status: draft — pending user review (not approved)

---

The one thing to take away

Before your next launch, run the triage: if you are the only user of what you built, shipping is a pure win — build it, use it, move on. If you need an audience, shipping is table stakes — your buyers can now vibe-code the simple version of your product themselves, so the effort that differentiates you is distribution, trust, and a wedge, not more building. Spend where the constraint actually moved.

---

The pattern: everyone you know just learned how to ship

The r/ClaudeAI thread that kicked this off is titled "the downside of everyone being able to build," and the top-voted read of it is blunt: production is now the cheap part, and getting someone to care about what you built is the expensive one. People put it more pointedly than that. One recurring line: "If you can vibe code it, so can we (your buyers)." Another: "building is becoming the cheap part, and getting someone to care about what you built is becoming the expensive one." r/ClaudeAI — downside of everyone being able to build

Here is the part that looks like a rant and is actually a notification. The same AI that made it trivially easy for you to ship also made it trivial for the person you are trying to sell to. That is not a quality problem or a marketing complaint. It is the cost of production collapsing to near zero, and the scarce resource quietly flipping from supply to attention.

If you build with Claude Code, Cursor, or Lovable, you already lived this. You shipped something in a weekend that would have taken you six weeks a few years back. That felt like the win. The thread's lesson is that it stopped being a win the moment your buyers got the same tool.

---

What the flood numbers actually show (and what they don't)

The backdrop is real, and you should use it as exactly that — a backdrop, not the argument.

  • New App Store submissions jumped roughly 84% in a single quarter as vibe coding went mainstream — the largest surge in a decade — with approval times ballooning from about 24 hours to 7–30+ days. The Next Web — vibe coding flooding the App Store
  • Appfigures logged roughly 557,000 new apps submitted to Apple's App Store in a year, up 24% year over year, with the store described as an "AI dump." Over 20% of the top 100 apps in South Korea's Google Play were simple PDF-reader clones. Chosun — app stores become "AI dump sites"
  • At WWDC 2026, Apple updated its App Review Guidelines and said it may remove apps in saturated categories that are not "updated, improved, or attracting customers." Tim Cook said developers submit over 1,000 apps to the store every hour. TechCrunch — Apple low-engagement removal policy
  • Reviewers of vibe-coded software keep finding the same security-debt patterns — exposed secrets, weak input filtering, placeholder logic that ships — often invisible from the store page. AppleMagazine — vibe-coded apps' invisible security debt

Now the part the numbers do not prove. The volume flood is well sourced. The claim that "users can tell the apps are lower quality" is not something the sources demonstrate — and the thread's own consensus pushed back on that framing. The top comments' counter was sharp: "You think if you built some random app before Claude people would have noticed?" The hard part was always distribution; AI just amplified it. r/ClaudeAI thread — TL;DR of top commentary

So do not build a piece of your strategy on "app stores are full of slop." That is a true-ish backdrop, but it is not a moat, it is not a wedge, and acting on it alone gets you a review badge nobody asked to buy. The operationally useful reading of the flood is different and simpler: the platform gatekeepers can no longer keep up, so the curator's job is moving to human networks you can actually reach. When 1,000 apps land in an hour, the reviewer is nobody's guardian — the recommendation is. More on that below.

---

The inversion: production got cheap, attention didn't

Take the two sides of the trade and price them.

Production — turning an idea into a working app — just went from months and an engineering hire to a weekend and a subscription. That is real, and it is the side every "I shipped it" post celebrates.

Attention and trust — getting a specific person to find, believe, and pay for what you built — did not get cheaper. If anything it got harder, because the denominator (a weekend) now applies to everyone, including your prospective customer who can build the simple version of their own problem.

The inversion is this: when production cost trends to zero, the binding constraint stops being making software and becomes being noticed and trusted. You cannot out-produce the problem by shipping more apps into a saturated store, because attention is not produced by volume — it is drained by it. The scarce resource flipped from supply to attention.

This is inference, not measured fact — say it plainly. The numbers above confirm the volume. The observation that attention is now the constraint is a practitioner reading the same situation the way the thread's top comments did. It is the frame this article runs on, and you should treat it as a frame, not a law.

---

The substitution you cannot outbuild

The sharpest consequence is the one most build-focused posts miss: your buyers can now vibe-code the simple version of your product themselves.

Read the thread's version carefully, because it is the whole game in one line: "If you can vibe code it, so can we (your buyers). It's going to be even more necessary now to have a real wedge. Maybe it's data... or novel implementation... The bar to clear is higher now." r/ClaudeAI thread — buyer-can-build-it substitution

Here is what that means concretely. The value you could once capture by owning the act of building — "I can make software, therefore I get paid" — is gone, because the act of building no longer costs anything scarce. What people pay for instead is the part they cannot prompt their way to:

  • Data** a buyer doesn't have, you do. A proprietary or hard-won data asset is a wedge no one can vibe-code into existence.
  • Distribution** a buyer doesn't have, you do. A channel, an audience, a relationship with the person who recommends — that transfers, and it does not show up in a code prompt.
  • Novel implementation* that is hard to replicate. Actual engineering depth, integrations, performance, or a workflow tuned over real usage — the parts that are not* one prompt away.

A simple utility app in a crowded category has none of these, which is why cloning it is now free. A PDF reader clone was buildable before; now your prospective user can ask a model to make one. The bar to clear is higher, as the thread put it — not because the code is harder, but because the moat moved out of the code.

---

The triage: build-for-myself vs compete-for-attention

Here is the reusable decision rule, and the part to actually keep after reading. It answers the reader's question — where do I spend effort now? — per project, rather than once for "founder strategy."

Ask, honestly: am I the only user?

  • If you are the only user — shipping is a pure win.** You built it, you use it, your life is better, no one else needs to know. Vibe code to your heart's content. This is the territory where cheap building is unambiguously good, and you should not feel guilty about it. Shipped-for-yourself tools are the free wins of this era.
  • If you need an audience — shipping is table stakes.* It does not differentiate you, it does not get you noticed, and it does not justify the effort by itself. The instant you need someone else to find you, your margin moves to distribution, trust, and a wedge. Spend there*, not on more building.

Examples, so you can see which bucket you are in:

  • A personal prompt-library you use for your own writing pipeline → build-for-myself. Ship it, iterate, done.
  • A nice notes app into a saturated store, hoping people find it → compete-for-attention. Shipping the app was the easy, useless half. Without a distribution angle or a data wedge, this clone gets you nothing.
  • A tool that pulls your own business's orders into a report format HR needs weekly → build-for-myself (or a small, known user). Pure win.
  • The same tool offered to every small business in your city with no channel → compete-for-attention. Your effort should be on finding the first ten users and the recommendation path, not on polishing a feature nobody has discovered.

The mistake this triage catches is specific: reaching for more building when the actual constraint is attention. If you are stuck in compete-for-attention territory and your instinct on hitting a plateau is "ship another feature, or another app," you are optimizing the half of the game that just stopped paying.

---

Where the effort actually goes now: distribution, trust, and a wedge

So what does "spend where the constraint moved" look like in practice?

Distribution. The platform gatekeepers are drowning — that's the durable read of the flood. When Apple can't meaningfully curate 1,000+ apps an hour and discusses removing low-engagement ones TechCrunch, the person who decides what a buyer tries is a human: a recommended post, a newsletter mention, a colleague's tip, a search result that actually surfaces you. The curator's job moved from the store reviewer to the network. That is reachable by a solo operator in a way a platform policy is not. Your distribution asset is a channel where the right people trust you — and building that is slow, concrete, and unglamorous, which is exactly why it's a moat.

Trust. Trust is the transferable asset of the network era, and its scarcity is why it compounds. A person who recommends you once is worth more than a store ranking, because their audience already believes them. The evidence that trust is scarce, not plentiful: the quality of recommendation is now the thing that decides attention, and recommendations are finite and slow to earn. A solo operator can build a small, credible, specific audience that no clone can buy. (This is our editorial inference — a framework for where to spend effort, not a measured outcome — and we won't pretend the numbers exist to confirm the conversion.)

A wedge. This is the change inside the product itself. Your product needs at least one thing a vibe-coder — including your customer — cannot trivially reproduce: data, distribution, or a novel implementation. Thin utility apps have no wedge by construction. Products with a wedge are where "competition" stops being a volume game.

The three are not optional extras bolted onto a build. They are the new definition of building, because building-the-code no longer differentiates anyone.

---

What to do first

A single next step, not a list.

Before your next launch, write down one sentence each for three things — and refuse to market (not ship) until all three have at least something real in them:

  • Who exactly needs this?** (A named person/role, not "everyone.")
  • How will they hear about it?** (Your channel, your network, your reach — not a hope and a store.)
  • What wedge do I hold that a vibe-coder and a buyer can't reproduce?** (Data, distribution, or a novel implementation.)

A useful answer to all three means you are honestly in or moving toward compete-for-attention territory and you know where the effort goes. Empty answers across the board are your signal: this is actually a build-for-myself tool, so stop marketing it and just use it.

Run the triage per project. Keep shipping for yourself freely. Stop spending the week of your life on the compound-flavored illusion that another clone, another feature, or another "I shipped it" is the moat. The moat is the trust and the reach and the wedge around the thing — and those are the only parts of building that are still expensive.

If you want to go deeper on the signal that started this, the full thread is worth reading for its commentary, not just its premise: r/ClaudeAI — downside of everyone being able to build

---

Sources

Claims in this draft that are inference, labeled as such in the text: the attention-constraint inversion is a practitioner frame grounded in the thread's own consensus, not a measured outcome; the curator-moves-to-human-networks read is our analysis of the Apple review-delay facts; "trust moves conversion" is not supported by any source and is presented only as a framework for where a solo operator should spend effort.

---

X entryway list (per the approved angle brief — not written yet)

Each hooks independently; the article link is a bonus, never the whole point.

  • Hook: sharp claim* — "Building just got cheap. Attention didn't. The AI that made it easy to ship also made shipping worthless as a differentiator." Links to article — why:* the claim earns the read; the article holds the triage framework.
  • Hook: mechanism* — "The substitution you can't outbuild: your buyers can vibe-code the simple version of your product now, so a real wedge (data, distribution, novel implementation) is the only moat left." Links to article — why:* the mechanism stands alone; the article has the triage.
  • Hook: result* — "Apple's reviewers can't keep up — 1,000+ apps/hour, 84% single-quarter surge — and the curator's job is quietly moving from the platform to human networks you can actually reach." Links to article — why:* the platform fact is the hook; the article is what to do about it.
  • Hook: build sequence* — "Run the triage before your next launch: if you're the only user, shipping is a pure win. If you need an audience, shipping is table stakes — spend the effort on distribution and a wedge, not more building." Links to article — why:* the triage is the actionable bit; the article explains the why.

(These mirror the angle brief's distribution_entryways exactly. I have not drafted the actual posts — that happens after the draft and the entryways are approved.)