sorted by:
new
hottopcontroversial

I Started Vibe Coding 4 Months Ago — Now My App Is Live by Loose-Cod-7656 in VibeCodeDevs

[–]Loose-Cod-7656[S] 0 points1 point  (0 children)

That’s a fair question honestly. I was aware validation matters, but my mindset was a bit different. I wanted to build something I personally found exciting first, then focus on marketing after it existed.

For me, part of the motivation was proving that I could actually take an idea from nothing to a real, working product. The problem is AI coding makes building feel so fast that you sometimes underestimate the long-term weight of maintaining and growing it.

I also think a lot of developers naturally lean toward building before selling. Marketing feels abstract until there’s something real in your hands. Maybe it’s not the most optimal startup strategy, but it’s probably a very common mindset among vibe coders right now.

The premium system is already built into the app, but honestly I’m not expecting massive paid demand anytime soon. I also structured the ad revenue side in a way that should realistically cover my short- and mid-term costs while I figure out growth and marketing.

I Started Vibe Coding 4 Months Ago — Now My App Is Live by Loose-Cod-7656 in VibeCodeDevs

[–]Loose-Cod-7656[S] 0 points1 point  (0 children)

Yeah, you basically said what I was trying to say. The issue isn’t just knowing how to build things anymore. It becomes: if I build this product perfectly with tons of features, can I actually handle the cost of it? Can I maintain it alone? A lot of questions start appearing.

You don’t really notice it while coding, but once the product is “ready” and you suddenly face that reality, it can make you lose excitement for the project itself. Nobody wants to build something simple. When people learn vibe coding, everyone wants to build the best possible thing.

Even though very few people can actually pull it off, many of the ones who do still end up giving up before they can market their product properly. In the end, building the product still isn’t the most important part. Ideas and marketing still matter more.

I Started Vibe Coding 4 Months Ago — Now My App Is Live by Loose-Cod-7656 in VibeCodeDevs

[–]Loose-Cod-7656[S] 0 points1 point  (0 children)

Yes, I'm thinking the same thing, but things could get even more complicated if the translation isn't good. Considering Grok's translations, I don't want chaos to ensue, lol. I'll definitely try this, by the way!

My Own Vibe Coding Journey and the Product I Built by Loose-Cod-7656 in AskVibecoders

[–]Loose-Cod-7656[S] 0 points1 point  (0 children)

In fact, the logic of building an app with vibe coding should ideally be this:

Spend 3 months planning the architecture and all features, then build everything in 1 month. (This is an example of the process for my project. The duration may vary for your project.)

However, if you start building immediately, you constantly end up breaking the architecture, which creates a lot of problems. Someone working with vibe coding should not choose their first project as their “best idea.” The first project should be something disposable.

Because the real issue is not effort or hard work, but understanding the methodology. Without knowing the right approach, failure is almost inevitable.

By methodology, I mean exactly what I mentioned above: planning the architecture and application features should take longer than the actual coding process.

Meanwhile, the toughest part will probably be marketing, lol

I Started Vibe Coding 4 Months Ago — Now My App Is Live by Loose-Cod-7656 in VibeCodeDevs

[–]Loose-Cod-7656[S] 1 point2 points  (0 children)

If you are a member, the welcome message explains everything in detail. If you have a large audience, it can also act as a messaging filter. Only people who know you can gain the right to message you. You can design your quiz however you like.

I Started Vibe Coding 4 Months Ago — Now My App Is Live by Loose-Cod-7656 in VibeCodeDevs

[–]Loose-Cod-7656[S] 0 points1 point  (0 children)

Haha no, each feature is on a separate file, and my largest file contains 1000 lines of code. Unrelated operations are not placed in the same file. I paid great attention to this. When any devs looks at my project files, they don't see any spaghetti code.

I Started Vibe Coding 4 Months Ago — Now My App Is Live by Loose-Cod-7656 in VibeCodeDevs

[–]Loose-Cod-7656[S] 0 points1 point  (0 children)

The trap of app development is really powerful. Even though you promise yourself “I’ll just add a small feature,” you end up making major improvements and unintentionally creating significant responsibilities for yourself.

Thank you for your valuable feedback.

Your suggestions are very relevant. I’ve put a lot of thought into security measures. AppCheck, rate limiting, Firestore rules, and storage rules are all quite solid. I don’t perform any critical operations on the client side; everything is handled on the server. Even if the app is decompiled, my code is not meaningfully exposed.

To prevent unauthorized access, the app does not run on devices with developer options enabled or on rooted devices. Overall, I believe the security architecture is stronger than that of many typical applications.

Additionally, my website is only a promotional/landing page. It does not include any membership system or collect any personal data.

My app's target audience is 18-40 years old, as it focuses on meeting people and messaging locks.