Nobody is using vibe coded apps 🤔🤔
App releases have jumped hard, but the demand signals are moving the wrong way.
-- Image from FT
ft .com/content/8e9ae7a4-7209-4e2c-aa36-f3af77d6ce1f?syn-25a6b1a6=1
3:23 PM · Jun 26, 2026 · 3.6K Views
Sentiment
Positive users expect vibe-coded apps from agentic AI to gain traction over time, while negative users criticize coding agents for producing code churn without product-market fit or meaningful releases.
Pos
33.4%
Neg
66.6%
6 comments with sentiment.
Cluster Engagement
Digg Deeper
No Digg Deeper questions have been answered for this story yet.
Posts from X
Most Activity
Most Activity
VIEWS3KBOOKMARKS8LIKES13RETWEETS2REPLIES4
Rohan Paul@rohanpaul_ai
MIT study. Code volume surges by 300%, but output increases by only 30%: The AI dividend meets an awkward reality.
They studied 100,000+ GitHub developers and find that AI coding agents massively increase code production, but much less of that work becomes shipped software.
Autonomous AI coding agents raised commits by 180%, but releases rose only 30%.
The paper’s main idea is that software production has weak links, so faster code writing does not help as much when humans still need to review, connect, test, package, and ship the work.
The authors also check app marketplaces and find more new apps, but no increase in total usage, which means more software appeared without clear evidence that users adopted more software.
The marketplace evidence points the same way: more new apps appeared, but total usage did not rise.
The authors compare more than 100,000 GitHub developers before and after they start using 3 generations of AI coding tools, from autocomplete to more independent coding agents.
Autocomplete raised commits by 40%, interactive coding agents raised them by 140%, and autonomous coding agents raised them by 180%.
The 180% commit gain shrank to 50% for the number of projects and 30% for actual releases.
The estimated "elasticity of substitution" is 0.25 i.e. for every big improvement in AI’s usefulness, only a small amount of human work can be replaced.
Because AI can write code faster, but humans are still needed to decide what to build, check if the code works, connect it with the rest of the product, fix messy edge cases, and actually ship it.
---
papers .ssrn.com/sol3/papers.cfm?abstract_id=6859839
Rohan Paul@rohanpaul_ai
Nobody is using vibe coded apps 🤔🤔
App releases have jumped hard, but the demand signals are moving the wrong way.
-- Image from FT
ft .com/content/8e9ae7a4-7209-4e2c-aa36-f3af77d6ce1f?syn-25a6b1a6=1
1hViews 3KLikes 13Bookmarks 8
Rohan Paul@rohanpaul_ai
Rohan Paul@rohanpaul_ai
MIT study. Code volume surges by 300%, but output increases by only 30%: The AI dividend meets an awkward reality.
They studied 100,000+ GitHub developers and find that AI coding agents massively increase code production, but much less of that work becomes shipped software.
Autonomous AI coding agents raised commits by 180%, but releases rose only 30%.
The paper’s main idea is that software production has weak links, so faster code writing does not help as much when humans still need to review, connect, test, package, and ship the work.
The authors also check app marketplaces and find more new apps, but no increase in total usage, which means more software appeared without clear evidence that users adopted more software.
The marketplace evidence points the same way: more new apps appeared, but total usage did not rise.
The authors compare more than 100,000 GitHub developers before and after they start using 3 generations of AI coding tools, from autocomplete to more independent coding agents.
Autocomplete raised commits by 40%, interactive coding agents raised them by 140%, and autonomous coding agents raised them by 180%.
The 180% commit gain shrank to 50% for the number of projects and 30% for actual releases.
The estimated "elasticity of substitution" is 0.25 i.e. for every big improvement in AI’s usefulness, only a small amount of human work can be replaced.
Because AI can write code faster, but humans are still needed to decide what to build, check if the code works, connect it with the rest of the product, fix messy edge cases, and actually ship it.
---
papers .ssrn.com/sol3/papers.cfm?abstract_id=6859839
1hViews 863Likes 0Bookmarks 3
ROBBIΞ ATAR@robbieatar
@rohanpaul_ai Give it some time the market will correct as well as some vibe coded apps are going to take over the app charts.
1hViews 13Likes 2
Roman P@RomanP918791
@rohanpaul_ai Vibecoded or not, it doesnt matter. Whether it is useful and people know about it, matters.
1hViews 8Likes 1
Rohan Paul@rohanpaul_ai
@robbieatar hard agree
1hViews 57Likes 1
Rohan Paul@rohanpaul_ai
@RomanP918791 💯
1hViews 44Likes 1
Pode vir@thiagoTF
@rohanpaul_ai exactly. massive code churn no actual output. users dont want more code they want working shit. the market doesnt care about commits it cares about releases that work. fucking obvious
1hViews 18
未知@luyun0120
@rohanpaul_ai AI现在最大的问题是：说得比做的好听。真正能落地的项目，远比融资PPT里的少。 「Code volume surges by 300%, but output increases by only 30%...」
1hViews 18
Shinka - AI@ShinkaIoT
@rohanpaul_ai Turns out 'vibe coding' isn't a substitute for product-market fit, shocker.
2hViews 3
AIPathfinder@NavigateAI_
@rohanpaul_ai More commits, more apps, but not more traction. That is the gap. AI can flood the pipeline, but usage and releases still depend on review, QA and integration.
1hViews 2
mamadxbt@creasydude
@rohanpaul_ai Interesting findings! The AI boom isn't translating to actual delivered software yet.
1hViews 1