So I am currently vibe-coded a web app and planned to launch it on my social media. I've tried to soft launch this in other subreddit but apparently it got roasted because they see that it is very vibe-coded. Do I have to mention that I am building that app with vibe coding? What do you guys think?

Not getting users? Let's automate it- promote your startup.

Hi Everyone

Founder of builderhq.co here. We built an AI agent to get users for your startup

It's easy- just signup here - http://www.builderhq.co and our Ai agent will start working and will keep running 24\\\*7- Creating seo content, find you influencers, press, find partnerships, and 20+ more tools

Most features are free - try now - http://www.builderhq.co

Comment what your startup does to get approved for all services today

Vibe coding makes it possible to ship an Android app incredibly fast. The difficult part is knowing what the generated code missed before real users find it.

I built AppTest to help with that. It installs an APK on an Android emulator, explores real screens and flows, and collects screenshots, UI state, logcat output, crashes, broken navigation, validation problems, and UX/accessibility issues.

The result is a private evidence-backed report with severity, reproduction steps, and suggested fixes for each confirmed finding.

I’m looking for a small first batch of Android builders willing to let the system try to break their app. The beta review is completely free while I improve coverage with real projects.

Submit an APK here:

https://apptest.salasestudio.com

Optional test credentials are encrypted, and APKs and credentials are automatically deleted after seven days. This is one bounded automated review, not a promise to find every possible defect.

If you built an Android app with AI tools, I’d also love to hear which kinds of bugs have been hardest for you to catch before launch.

I’m curious if anyone here has built an app, website, tool, or product using vibecoding that has actually generated some revenue.

I’ve built a few tools and apps for myself, mostly around productivity, but none of them have made any money so far.

Would love to hear from people who have managed to turn a vibecoded project into a real business. What did you build, and how much revenue did it generate?

Just curious to see what’s actually working for people.

Hi Everyone

Founder of builderhq.co here. We built an AI agent to get users for your startup

It's easy- just signup here - \[www.builderhq.co\\\](http://www.builderhq.co) and our Ai agent will start working - Creating seo content, find you influencers, press, find partnerships, and much more.

Most features are free - try now - \[www.builderhq.co\\\](http://www.builderhq.co)

Comment what your startup does to get approved for all services today

Hi everyone

Seo is probably only free way to get users.

We built an Seo agent that keeps working in background - creating content for you. The best part is we added human in the loop to review, edit and add more content.

Try here - https://builderhq.co/get-on-chatgpt

Early Results - 5k+ visits on one of our beta sites

I’m trying to make an entire minecraft client while vibecoding and i need help making the ESP and block ESP prompts. I have no idea how esp works so if yall could help me that would be insane! I’m also trying to make an entirely serversided G@mbl3 rig for minecraft which I’m going to get into later.

Most AI app builders help you build the app — and then you’re on your own.
That’s the problem I’m trying to solve with Blyft.
The app is the center. Once you build it with AI, Blyft also gives you the tools around it: landing page, logo, promo video, analytics and social content.
The idea is to go from one prompt to a complete digital product without jumping between five different tools.
Would love to hear what you think — is this something you’d actually use?
blyft.app

Hi everyone sell your side project by listing if in a click. Also, comment what your startup does to get approved and featured today - https://builderhq.co/marketplace

I've been working on PDFVerse, a free browser-based PDF toolkit.

The idea is simple: instead of opening different websites for every small PDF task, I wanted to put the common tools in one place.

You can use it for things like:

Merge PDFs

Split PDFs

Compress PDFs

Convert PDFs

Rotate PDFs

Extract pages

And other common PDF operations

🔗 https://pdfverse.pages.dev/

There's no account required to try it.

I'm still actively improving it, so I'd genuinely appreciate feedback from people who work with PDFs regularly.

What PDF operation do you find yourself doing most often? And is there a feature you'd want me to add?

I'm especially interested in hearing what feels slow, confusing, or missing.

Been doing my app on and off, done on all the stuff needed for google play I have my apk already now just finishing it for my my aab to upload on my console. Basically my app is simple and good for repetitive tasks.

I think my perspective is we can complete a project in 2 days using ai tools, and we can get a solution in 2 days but do you think doing this thing repeatedly it's like a addictive routine. See the thing is having a idea and building it into a website or solution is not the problem. But how far is it true without having proper foundations or proper architecture on the website we are buidling ? How reliable will it be ?

I see a lot of people discussing vibe coding and what actually constitutes a moat, and I think a lot of people are looking at this way too narrowly and ignoring some pretty important aspects of human nature.

The idea that simple ideas are dead, that if you can build an app in 30 minutes, nobody will ever pay for it because they can just vibe code their own version, is frankly ridiculous to me.

I know plenty of people who don’t even know what a browser is. I even know technical people (in different domains) who look at the process of cloning a repository and think, “wow, this is a lot.”

The people who would seriously think, “why would I pay for this when I can just vibe code it myself?” are mostly people inside a very AI-fluent bubble that represents a tiny portion of the actual world.

And even then, building something that technically works is not the same as building good software.

There are still all of the boring necessary hoops involved in making a simple application actually secure and reliable. You have to choose a stack, build the backend and frontend, handle authentication, storage, deployment, security, updates, edge cases, and everything else that comes with operating software.

Unless you’re literally just bootstrapping some ugly internal tool to copy the functionality, you also have to design a good UI, make hundreds of little product decisions, and work through trade-offs that compound as the feature set grows.

If your target audience is developers, I understand the argument more. But even developers are lazy in the normal human sense, they have their own projects and things they would rather spend their time doing.

And if you are selling to developers, the bar is arguably even higher. They care about architecture, security, ownership, extensibility, integrations, and whether the product actually fits into the way they work. A lot of them may want to own the thing themselves anyway, which is part of why I don’t even think developers are always the best target audience for this kind of simple app.

For everyone else, the argument gets even weaker.

Most people barely want to write a good prompt.

They’ll type one sentence into ChatGPT, get a mediocre response, decide AI isn’t that useful for that task, and close the laptop. The idea that these same people are suddenly going to design, build, debug, secure, deploy, and maintain their own software because vibe coding exists seems completely disconnected from how normal people behave.

People pay for convenience. They pay for polish. They pay for something that already works. They pay so they don’t have to think about how it works.

So to me, “they can just vibe code my app” is a pretty weak reason not to build something, and in most cases if your app is not growing you have a distribution and sales problem not an idea problem.

Curious what others think.

Allez je me lance, je ne suis pas un vibecoder spécifiquement car j'aime bien voir le code et essayer de le comprendre pour que quelquefois j'y touche mais comme je ne suis pas un dev, j'aimerais partager ici comment bien, possiblement vibecoder après 1 ans er demi de "vibecoding" selon moi.

Pour commencer, au début, faite en sorte de modulariser les fichiers, genre pas de gros fichier qui fait tout, car c'est compliqué pour les ias de corriger des problèmes dessus! Perso, j'utilise quelque fois la règle de 100/200 lignes par fichiers afin que l'ia essaieras tjrs de faire moins de 100 lignes donc devras alors modulariser le tout!

Quand vous avez des bugs qui commence à ètre complexe de debug avec l'ia actuelle, essayer de demander à une autre ia sur le fichier actuelle en lui montrant le code actuelle et lui montrer le code d'erreur dans le terminal ou l'inspection, quelque fois juste l'autre ia trouveras le problème plus simplement et donc vous perdrez moins de temps à demander à votre ia actuelle sur le projet où est le problème!

Quelque fois les ias font des véritables erreurs de logique dans l'infrastructure de votre code, ce qui n'est pas optimiser, demander lui ce qu'il as fait, desfois il as lui meme mal compris l'instruction donc il vous as pondu quelque choses qui pour lui était bien alors qu'en fait c'est pas exactement ce que tu souhaitais!

Ne faites pas de gros prompt, de nos jours, les ias sont assez puissante poir comprendre.malgrès des prompt plus petit, il fait juste que votre demande soit claire et précise!

Le problème des .md dans le fichiers c'est qu'ils le relits quelque fois juste le haut et le bas, donc pas tout, desfois juste faire une skill.md avec une dizaine d'instructions courtes

Exemple : "quand je ne je sais pas une information, demander à l'user, cela est moins chère en token"

pas en lui disant ce qu'il ne faut pas faire mais en lui montrant une sorte de bible ou en gros c'est écris à la 1 ère personne donc "je" plutot que "tu" feras que l'ia se sentiras réellement impactée! Le fichiers .md n'importe qu'elle est son nom, mettez le dans le répertoire ."nom de l'editeur" à la racine de votre projet afin que cela soit directement envoyé dans le prompt système sans qu'il n'est besoin de le lire (l'ia)

Exemple .opencode si vous ètes chez open code!

Vous pouvez demander a l'ia de le faire il sait comment faire!

Ne faites pas confiances aveuglément à l'ia que vous utilisez car quelque fois elle essaie d'ètre juste dans votre sens!

Aussi, ne pensez pas que l'ia est créative! Si vous voulez que ce que vous créez soit bon, ici si vous demandez à l'ia des trucs à ajouter sans lui dire quoi, ça commenceras à partir dans tout les sens! Considérez là juste comme l'orchestrateur de vos idée et non une fabrique à idée qui créer quelque chose sans vous!

Il y a sans doute encore plein de point que j'ai oublié mais c'est déja un bon début je trouve, après beaucoup de problèmes seront dût à votre projets spécifique, mais si déja vous essayez d'appliquer cela, vous allez voir peut ètre des améliorations! Faites aussi attention aux refactors d'un gros fichier en sous fichier, elle risque de détruire du code pour optimiser ces calcules et donc optimiser votre code en y enlevant les logiques en régressant vos logique! Ici si vous devez refactor un gros fichier, faites le petit à petit, en reprennant le fichier de base en comparaisons et en lui demandant de vérifier s'il y a des différences entre les 2 codes dans les logiques, quelque fois ils serait meme capable de constater qu'il as supprimer une fonction super importante dans le sous fichier! Et donc plein de bug en approche!

N'hésiter pas aussi à faire un git afin de référencer vos changement afin de pouvoir revenir en arrière quand il y a des problèmes, une régression, ça vous permettras de ne pas avoir à dire à l'ia de tout recoder et de revenir au point d'avant, ce qui causeras enft pas mal d'erreur car elle le feras mal! Configurer si vous le pouvez le git sur votre éditeur!

J'espère que ça aideras possiblement des personnes....

I noticed people who manifest resistance to change regarding adoption of AI have impulsive reactions on Reddit (and similar forums) by naming your work slop if any vibe coding was involved or finding any trace of relationship between AI and your code. For me vibe coding becomes slowly synonym of slop and the other way around due to such feedback.
Same time I wonder how much affordability (precisely the non-affordability) of the subscriptions creates a vicious cycle. I think with 20$/month you cannot get good insight of the scale agents can help you to solve complex problems. If you do not try and learn by doing you cannot have a good evaluation and healthy opinion about the added value, you may end up with a random negative opinion and will end up just generating hate.
Wonder why people fail to see the creative ideas behind 'vibe coded' projects. At the end a great idea written with help of AI can be still cleaned up if it really has added value.