@stephenrobles pretty cool you made it as far as you did!

Not sure if you tried this, but I often find a good way to dig out of a hole when vibe coding is to describe to the LLM what the problem is, then ask it add debug logs that can isolate the issue. Then you run the app, copy/paste the logs back into the conversation.

@stephenrobles Try creating a Product Requirements Document (PRD). It’s an outline that describes your app and its features for AI.

You can use ChatGPT or Claude to help you create it: https://writemyprd.com/

@stephenrobles Appreciate your attempts! Your efforts inspired me to try vibe coding a Swift app. Lots of success creating and tweaking UI, but once I introduced an api to serve as a data source, GPT hit a hard wall.

I’ll be following the comment threads across your channels to see if the community offers you a path forward I could also try. Thanks for sharing your #BuildInPublic journey!

@stephenrobles you’re not alone. I’m an experienced developer (in fact I helped create Pocket Casts) and I think what you found is universal. None of the AIs match the hype. None of them are capable of building a complete app. They are all hype and no substance.

On a more positive note: AI is very good at helping you learn things. I use it almost every day to ask questions. I never get it to code my apps. What if instead of your current approach you use it to slowly learn to code?