The 100 hour gap between a vibecoded prototype and a working product

Submit
The 100 hour gap between a vibecoded prototype and a working productmacbudkowski.com
macbudkowski.com

The 100 hour gap between a vibecoded prototype and a working product

AI summary of the linked article

The author argues that the "vibecoded an app in 30 minutes" claims are misleading, based on spending about 100 hours building Cryptosaurus, a simple app where users get a dino styled as their profile picture. The initial prototype took about an hour, but getting the UI, edge-case image outputs, AWS infrastructure, smart contract minting and Farcaster Mini App integration into production took far longer. After launch, a missing nonce check caused some paid requests to fail, and the author refunded affected users $1 extra. The app reached 1,000+ downloads and 180+ paid $2 for a dino, and the author estimates vibecoding gave a 10-100X speed improvement.

Recommended by 2 curators
avatar
Love you’re sharing the whole journey! 👏
avatar
It's been a ride! I def underestimated the time necessary to ship it at the quality level I wanted. At some point I even reached out to Tim and told him how much respect I have for his work at Kiwi given how much complexity there was in a 100X simpler app 😁