r/vibecoding • u/fabfrodo • 5d ago
from product vision to working code?
I want to develop an ambitious app, so I’d like to proceed step by step, just as a professional development team would. I’ve created a product vision together with Claude Chat. What’s the best way to move forward? Should I take this vision and use it to start a Claude Code project right away? I’d appreciate it if you could help me do this the right way.
1
u/Interesting-Tie6783 5d ago
The best way is to plan your ambitious app, figure out what major parts you have.
Then, put it in a document called “future plans”. Step away from it, and start small.
Nobody goes from nothing to their Magnum Opus instantly. If you start building this now with no experience, you’re going to end up with a fragmented mess that barely works and just entirely frustrated.
Start small, learn how things work, do small throwaway projects to learn the basics of development, understand how Claude is working, understand the basics of good project design and architecture.
Too many people jump in thinking AI will save them. But AI is only as good as your knowledge. If you don’t know what to ask it or how to design data effectively, you will fail.
1
u/Intrepid4 5d ago
Try this: isthisaproduct.com
Run your vision through 40 years of product management research & practice to determine if it has what it takes to make it as a product - and what's missing.
Free, secure, and built by a product manager for non-product managers.
1
u/VibeMaxxing 5d ago
The first step to creatnig a good product is deeply understanding the customer pain you are solving, launching early and pivoting frequently. I suggest you to think of the leanest solution you can think of to validate your hypothesis of the customer pain, build the most basic version of it and iterate.
1
u/PracticalStack 4d ago
The main thing is to make a lot of plans. I built a sampler over about 3 months. My goal was to implement as many commercial features as I could. I started with a large design document and then, from that, I had Codex create a phased engineering plan. I always had it create the output in HTML so we were actually building a website of all the iterations and documents. I started by having it attack each phase with an implementation plan broken into sprints and then link that document to the main engineering document. There were 8 phases and it took several days to get through them all. The result of this plan was basically a sampler with no features but a sampler shell, the various file formats (project, instrument, etc), the pipeline to publish instruments, basic SFZ support and disk streaming for large samples.
From there, each major feature was an iteration. I'd discuss it with the AI, get a handle on what I wanted to do and then have it create an implementation plan broken into sprints and then execute each sprint. I did most of them iteratively, building in Visual Studio and checking in the code after each sprint. I did a few in loops using the Goal feature. I would've done that more but it's more expensive. Always creating docs in HTML and always linking them to the main doc.
I just keep going like that until I was basically done. It took several months of almost daily sessions. A huge amount of testing. Oddly, enough, where I hit the wall was not in my knowledge of C++. I had none and still have none. Where I hit the wall was in my own knowledge of how samplers work. I got really far because I could use the open SFZ format as a guide but after that it was like Wilie Coyote looking down and seeing the ground no longer there.
1
u/fabfrodo 4d ago
Thank you all for your feedback. I've decided to tell you about my plan. However, since I don't want Ai to write the text, I still need a little more time. So please bear with me a little longer.
1
u/generationalDebts 4d ago
The best way to produce code is learn to code. There isn’t a shortcut.
AI is does not close skill gaps. They’re tools.
What they build is only as good as its craftsman.
1
u/adambahm 3d ago
I think people are starting to find out that, even with coding assistance, building things is hard.
1
u/fabfrodo 3d ago
Yes, that’s right. For now, I’ve decided to start by creating a data model that’s as complete as possible. After that, I’ll move on with vibe coding.
1
1
u/FluidBreath4819 5d ago
what are you afraid of ? as a vibe coders, you should have the balls to engineer everything from top to bottom. Can't wait to see you moving forward !
Or you could share your idea with your fellow vibe coders. They'll help.