Since I am not an engineer I was able to launch my first app with vibes. Not letting the ai run loose was important. I always checked over what it was doing before committing and created several files for it to reference for architecture, rules, todos etc. Even with that I would have to check over files and instruct it to redo things or suggest more efficient methods for SwiftUI and feed it documentation. I think it’s important working with ai if you’re not an experienced engineer is to at least have a good understanding of SwiftUI best practice and architecture patterns - still research apple docs, tutorials etc and know that ai is always looking to please so you have to be thorough and question what it’s doing instead of blindly trusting it.
3 weeks ago | 1
Hi there, since I use your .cursorrules, vibe coding an app cannot be easier! You just made the perfect rule. PS. got it from one of your learning video❤
3 weeks ago | 0
CodeWithChris
Hot take: Vibe coding isn't the problem—how you use it is.
(For those wondering: "vibe coding" = using AI to generate your entire app with minimal human oversight)
Recently I've been seeing more news about vibe coded apps mishandling sensitive information, being prone to security issues, and being a nightmare to maintain.
It seems like people are waking up to the fact that human software engineers are still needed lol
But does this mean you shouldn't vibe code your app?
Not at all. There's still a perfect use case: prototyping.
Here's the strategy:
Simplify your app idea to minimize the risk of bad code while still allowing you to test your idea in the market.
Vibe coding saves you massive amounts of time that you can redirect to distribution and validation.
Just know the trade-off: You might have to rewrite it from scratch later.
In conclusion… vibe coding isn't bad. Just understand the limitations of the tool you're working with and use it strategically.
What's been your experience with AI-coded apps? Drop your thoughts below 👇
3 weeks ago | [YT] | 22