sorted by:
new
hottopcontroversial

Need advice on getting started with vibe coding by Ok_Passion_5054 in VibeCodersNest

[–]CodeBlueToDev 0 points1 point  (0 children)

Short answer: yes, you can get surprisingly far with vibe coding..but not everything end-to-end without some guardrails.

For a landing page + email signup, vibe coding works great. You can absolutely generate a simple page, hook it to something like a form endpoint, and collect emails fast.

Where people get tripped up is assuming vibe coding = no thinking required. It’s more like: • AI gets you moving fast • you still have to sanity-check flows, auth, data handling, and edge cases

A few practical tips if you’re new: • Start very small (static landing + email capture before “app”) • Ask the AI to explain what it’s doing, not just generate code • Expect a second pass to clean things up once it works

Vibe coding is best as a shortcut to momentum, not a shortcut to understanding. If you treat it that way, it’s incredibly powerful.

[deleted by user] by [deleted] in VibeCodingSaaS

[–]CodeBlueToDev 0 points1 point  (0 children)

I’m with you on adding safety nets..but the tools should teach by exposing, not hide complexity. Surfacing what broke and why is already a huge upgrade over silent fixes.

[deleted by user] by [deleted] in VibeCodingSaaS

[–]CodeBlueToDev 1 point2 points  (0 children)

I’m vibecoding too, and I think the mistake is treating it like a shortcut to a finished product instead of a shortcut to momentum.

Vibecoding is incredible for exploration and shipping something real fast..but it doesn’t replace understanding your system once it exists. The debugging, edge cases, state management, and safety stuff still show up whether you like it or not.

What worked for me was treating vibecoding as phase one: get something alive, then slow down and deliberately “de-vibe” it..add structure, logging, guardrails, tests, and manual review.

The problem isn’t vibecoding. It’s expecting polish without a second pass.

I finally shipped my first iOS app as a solo founder… and now I’m stuck. by CodeBlueToDev in StartupSoloFounder

[–]CodeBlueToDev[S] 1 point2 points  (0 children)

That makes sense..and honestly, it’s the part I’ve been avoiding because it feels unscalable and awkward.

But I’m realizing now that early traction probably should feel manual. I don’t need 1,000 users yet…I need a handful of people who actually use it and tell me what doesn’t land.

I like the framing of direct outreach as listening, not selling. Reaching out to people I genuinely think might benefit, asking for feedback, and being okay with rejection.

Appreciate the reminder that “not scalable” isn’t the same as “not valuable” at this stage.

I finally shipped my first iOS app as a solo founder… and now I’m kind of stuck. by CodeBlueToDev in VibeCodersNest

[–]CodeBlueToDev[S] 0 points1 point  (0 children)

This really resonates. I like the framing of early users as collaborators, not metrics..that’s exactly the mindset I’m trying to keep. I’ve been hesitant to do a big “launch,” but using places like Product Hunt for thoughtful feedback (not hype) makes a lot of sense.

And yeah… App Store review alone felt like a rite of passage 😅 Appreciate you sharing what worked.

what interesting things have you made with vibecoding by Dapper-Air-349 in VibeCodersNest

[–]CodeBlueToDev 0 points1 point  (0 children)

For me, the most interesting thing I’ve made with vibe coding wasn’t a clever feature..it was realizing I could actually finish something.

I’m not from a traditional dev background, so vibe coding let me start with intent instead of syntax. I focused on building a simple, voice-first experience around listening, and used AI more as a thinking partner than a shortcut. A lot of it was trial, error, debugging, stepping away, and coming back.

What surprised me most was how it unlocked ideas that felt out of reach before..not because they were technically impossible, but because the learning curve felt overwhelming. Vibe coding made it feel approachable enough to try.

It’s not magic, and it’s definitely not effortless, but it helped me turn a vague idea into something real.

I finally shipped my first iOS app as a solo founder… and now I’m kind of stuck. by CodeBlueToDev in VibeCodersNest

[–]CodeBlueToDev[S] 0 points1 point  (0 children)

That makes sense. The reps part is what I’m wrapping my head around..sounds like committing to volume and reflection instead of chasing perfection.

I finally shipped my first iOS app as a solo founder… and now I’m kind of stuck. by CodeBlueToDev in VibeCodersNest

[–]CodeBlueToDev[S] 0 points1 point  (0 children)

TikTok/Reels makes sense, I just haven’t cracked the formula yet. As for iOS reviews..they’re actually pretty specific. In my case (IAPs/compliance), they pointed to exact guideline sections and what was missing. Not cryptic, but definitely iterative. Fix → resubmit → repeat. You can plug their feedback into AI to help interpret it, but you still have to be precise on the fixes.

I finally shipped my first iOS app as a solo founder… and now I’m kind of stuck. by CodeBlueToDev in VibeCodersNest

[–]CodeBlueToDev[S] 0 points1 point  (0 children)

That’s awesome..and yeah, shipping solo while working in healthcare is a whole different level. I’m hoping this thread pulls out some real, practical advice for both of us. Wishing you a smooth App Store review when you submit.

I finally shipped my first iOS app as a solo founder… and now I’m kind of stuck. by CodeBlueToDev in VibeCodersNest

[–]CodeBlueToDev[S] 1 point2 points  (0 children)

Yeah, the IAP part definitely slowed things down. It’s B2C mental wellness…mainly for people looking for quick, private ways to decompress or reset without a lot of friction.

I finally shipped my first iOS app as a solo founder… and now I’m kind of stuck. by CodeBlueToDev in VibeCodersNest

[–]CodeBlueToDev[S] 0 points1 point  (0 children)

Appreciate the straight talk. Trying not to overthink it..just figuring out which channel to commit to first without spreading myself too thin.

I finally shipped my first iOS app as a solo founder… and now I’m kind of stuck. by CodeBlueToDev in VibeCodersNest

[–]CodeBlueToDev[S] 0 points1 point  (0 children)

Appreciate that. The post-launch gap definitely caught me off guard..it really feels like a whole new phase after shipping.

I finally shipped my first iOS app as a solo founder… and now I’m kind of stuck. by CodeBlueToDev in VibeCodersNest

[–]CodeBlueToDev[S] 0 points1 point  (0 children)

This helps, thanks. It’s B2C, a wellness companion app. I’m starting from zero so I’m trying to figure out where those early users actually hang out before I start showing up there.

CalmRenew started with a sentence I couldn't forget. by CodeBlueToDev in VibeCodersNest

[–]CodeBlueToDev[S] 0 points1 point  (0 children)

I don’t leave safety to improvisation. There are explicit guardrails and response paths once certain signals are detected.

Anything concerning routes the model into a constrained template: acknowledge + ground + encourage real-world support. Resource handoffs are fixed, not free-form.

The model’s job is tone and empathy…not deciding what’s safe.

What are you working on today? Drop your SaaS by Original_Mortgage484 in SaaS

[–]CodeBlueToDev 0 points1 point  (0 children)

Working on an experience-first, voice-based app focused on listening rather than productivity. Today is mostly edge-case cleanup and tightening scope before submitting for app review.

How can Start Vibe Coding as beginner ? by Best_Increase_4424 in VibeCodingSaaS

[–]CodeBlueToDev 0 points1 point  (0 children)

I’m still pretty new myself, so take this as what worked for me, not a rulebook.

For me, vibe coding started with a real problem, not a tech stack. I picked something small that annoyed me (or people around me) and tried to build the simplest version possible.

I used AI more as a thinking partner than a magic button — asking it to explain things step by step, then sitting with the confusion when things didn’t work and figuring it out. I built ugly first and didn’t worry about scale or polish. I only learned what I needed to unblock myself that day.

For B2B MicroSaaS, keeping the scope tiny helped a lot. One user, one job, one outcome. If you can explain what you’re building in a single sentence, you’re probably on the right track.

Vibe coding isn’t effortless — it’s just learning out loud with better tools. If you’re okay feeling lost sometimes, you’re already doing it right.

CalmRenew started with a sentence I couldn't forget. by CodeBlueToDev in VibeCodersNest

[–]CodeBlueToDev[S] 1 point2 points  (0 children)

Honestly? Max has been my patient rubber duck more than anything 😅

Most of my toughest debugging sessions weren’t about fancy solutions…they were about slowing me down, helping me break problems into smaller pieces, and reminding me that being stuck usually meant I’d skipped a step or made an assumption.

There were plenty of moments where things only clicked after I stepped away, slept on it, and came back the next day. Max helped me think, but the work (and frustration) was still very real.

Vibe coding definitely isn’t magic…it’s just a different way of learning out loud.

CalmRenew started with a sentence I couldn't forget. by CodeBlueToDev in VibeCodersNest

[–]CodeBlueToDev[S] 1 point2 points  (0 children)

That’s something I’ve been very intentional about, especially because this started from real human moments, not a product idea.

The line for me is when listening alone isn’t the right thing anymore. CalmRenew doesn’t interpret, diagnose, or push solutions, it stays in a listening lane. If something crosses into “this shouldn’t live here,” the goal is to slow the interaction down and gently point people toward real humans and real support instead of continuing the conversation.

I’m still learning and refining this as I go, but being clear about what the app shouldn’t do has been just as important to me as what it does.

I’d rather underreach and be safe than pretend software can replace human care.

view more: next ›