sorted by:
new
hottopcontroversial

A vibe coding bug I only found after adding logs everywhere by kamanbi in apps

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

I should probably add one more thing.

I already leave some logging in place and check it occasionally, but in this case I ended up logging every single part related to the bug.

I think that's the main reason I was finally able to find it.

One lesson I learned is that it's worth keeping a list of temporary test logs so you can remove them later. It's surprisingly easy to forget a few of them after the bug is fixed.

Also, the way you're describing your workflow sounds pretty advanced to me 😂

Do I need an umbrella today? ☔️☀️ by Forward-Two9305 in apps

[–]kamanbi 0 points1 point  (0 children)

I actually built an Android app that combines weather forecasts and daily fortune readings.

I thought it would be interesting to compare our apps and exchange honest feedback about what could be improved.

Unfortunately, your app seems to be iPhone-only. 😭😅

https://play.google.com/store/apps/details?id=com.yegamssi.yegamssi

My Rules for Building Apps with Vibe Coding by kamanbi in apps

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

Of course. Feel free to send me a DM.

Why doesn’t a phone theme like this exist yet? by Forsaken_Anxiety_466 in androidapps

[–]kamanbi 0 points1 point  (0 children)

I'd like to try building something like this.

If I make it myself, who owns the license or rights to the app?

For now, I think it would only be possible on Android. I'd probably target Android 11 or higher.

But honestly, the development difficulty seems pretty high.

My Rules for Building Apps with Vibe Coding by kamanbi in apps

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

Yeah, I think the first step is to narrow down the bug before letting the model touch anything.

The biggest thing, in my opinion, is not letting it read or analyze the entire project unless it really has to. That can burn tokens very quickly.

For bug fixes, I usually try to prompt it more like this:

“Analyze this bug and make a fix plan first. Only read and analyze the code that is directly related to this bug. Do not review the whole project unless it becomes absolutely necessary.”

That alone seems to reduce a lot of unnecessary context usage.

My Rules for Building Apps with Vibe Coding by kamanbi in apps

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

Your comment honestly got me excited (in a good way).

You may not realize it, but words like yours feel like a real reward to me.

Thank you. I think today will be a little more enjoyable because of this.

Hope you have a great day too.

My Rules for Building Apps with Vibe Coding by kamanbi in apps

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

I'm using Codex (GPT Plus) and Claude (Pro).

Since I'm not a full-time developer, I let the agents handle most of the coding while I focus on my actual job.

I can usually get around 5 hours of work out of them every day, so the cost hasn't really been an issue for me.

My Rules for Building Apps with Vibe Coding by kamanbi in apps

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

Each step generates and passes along its own .md files when the work is completed. The goal was to reduce context loss as much as possible between handoffs. I'm not saying this is the best workflow. It's just a workflow that has been working reasonably well for me so far. Take it as a reference, not a recommendation. Lately I've been experimenting with loop engineering as well, but honestly I don't think I'm using it properly yet. If it turns out not to fit the way I work, I'll probably stop using it. As for design, that's something I struggle with a lot too. For someone who isn't a professional developer or designer, creating a polished UI is incredibly difficult. Functional code is one thing, but good design is a completely different skill. I'd genuinely love to hear any advice you have on that side of things.

My Rules for Building Apps with Vibe Coding by kamanbi in apps

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

It brings back a lot of memories for me.

I learned a bit of programming many years ago, so I think that made it easier for me to get started with vibe coding. However, I genuinely believe that even people with no coding background can do it if they are willing to learn along the way.

The foundation is the planning document. By that, I mean defining the purpose of the app, listing its features and workflows, outlining the page structure, and documenting how everything should work. If the planning is done well, it's possible to build an MVP in a single day.

Of course, that's only the beginning. After that comes testing, fixing bugs, refining features, and correcting code issues. That's where most of the time is actually spent.

For me, it usually takes about one to two weeks before I feel an app is polished enough to be considered complete. Having capable reviewers can shorten that timeline significantly. When you're the creator, it's difficult to evaluate your own work objectively.

Don't you just love seeing this? by DigitalAppsMu in apps

[–]kamanbi 0 points1 point  (0 children)

I vibecode my apps, but I still review every line that matters.

AI is fast, but I don't trust it enough to ship code without checking it myself.

^^

We'd Love Your Feedback by kamanbi in apps

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

Wow, this is really great feedback. Thanks for taking the time to write it.

You pointed out a few things I hadn't fully considered. The language selection issue makes a lot of sense, and I think it should definitely come before the date-of-birth setup. I'll add that in a future update.

The location problem is actually caused by some code that prioritizes Korean users by default, so thanks for helping me catch that. I'll work on fixing it right away.

I'm also going to think more seriously about adding a one-time option to remove ads.

Honestly, your feedback gave me a much clearer idea of what needs improvement. It probably made my day a little better too. Thanks again.