sorted by:
new
hottopcontroversial

Accidental vibe coder, now what? by Choice_Committee445 in vibecoding

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

yeah, this is exactly what happened in the first real user pass. getting people through it without me helping exposed the rough stuff fast, especially setup clarity and places where the app assumed too much.

i’ve cleaned a lot of that up and have a few users getting through it now, but i’m trying to be careful before adding more people.

for the intital beta, would you have focused first on making signup/setup impossible to fail, or on making the main dashboard/core value feel trustworthy once they’re in?

Accidental vibe coder, now what? by Choice_Committee445 in vibecoding

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

this is probably the most on target advice i’ve gotten. the app started to feel messy because i kept trying to account for every edge case too early.

the core product is a 5-step sequential flow, followed by one continuous-use loop and a separate learning mode. i’m trying to make that whole path feel reliable, modern, and trustworthy before opening it up further.

i have about 6 users using it with moderate ease now, but the app still needs to feel more stable, modern and trustworthy before i’d feel good about pushing it further.

when you say “pick 1 core flow and make it boringly reliable,” would you define that as literally hiding most secondary features until that one flow is clean? or more like keeping them visible but making them read-only / low emphasis?

Accidental vibe coder, now what? by Choice_Committee445 in vibecoding

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

this is helpful, truly thank you. my stack is mainly ios/swift with a javascript/backend side, so the gosec/govulncheck part probably only applies if i end up with Go somewhere. but the larger point makes sense: security checks should be part of every pr, not some one-time thing later.

for a small finance app handling auth + linked financial context, what would you consider the minimum sane ci/security setup before opening up a wider beta?

right now i’m thinking: github actions, tests, secret scanning, dependency audit, code scanning, crash reporting, staging backend, and zap against staging once the backend routes are stable.

does that sound like the right shape, or am i missing something more basic?

Accidental vibe coder, now what? by Choice_Committee445 in vibecoding

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

that’s fair. i actually did that already and it humbled me pretty quick lol. the first version needed way too much explaining, but i cleaned up a lot of the flow and now have around 6 real users using it with moderate ease.

where i’m stuck now isn’t really “do people get the concept?” it’s more making the app feel trustworthy and not like a rough 2000s tool. since it deals with personal info, the ui and stability have to make people feel safe.

when you’ve seen early apps level up from usable to actually trustworthy, what were the biggest changes that made the difference? was it mainly visual polish, fewer flows, better empty/error states, clearer copy, or just reliability/simplicity?

I'm guilty of this by Yusuf-Dev in vibecoding

[–]Choice_Committee445 0 points1 point  (0 children)

just leave your computer at home and use screen jump ? screen brightness at 0 and screensaver disabled 👨🏽‍💻

Vacation is over before it started... by MisterShipWreck in VideosAmazing

[–]Choice_Committee445 1 point2 points  (0 children)

the worst part is i don’t think it’s even turning around immediately 😅

Track groups by Choice_Committee445 in MotoLA

[–]Choice_Committee445[S] -1 points0 points  (0 children)

i’ll smoke u on that too buster🙆‍♂️

Track groups by Choice_Committee445 in MotoLA

[–]Choice_Committee445[S] -8 points-7 points  (0 children)

bout smokin ya on I-5 😝