I've been having a lot of fun exploring AI and using tools like @Cursor, @bolt.new, @Lovable, and @Warp to learn how to build and make some apps for myself! I'm also noticing a tremendous amount of growth in folks creating their own apps using these same tools which has me wondering... if a company wanted to acquire someone's app or tool that was built via vibe coding, would it matter how it was built? Does the method of how it was built impact the valuation? In my idealistic eyes, I'd like to think it doesn't. As an acquisition is often much more than just the tech but also the user base, brand, and even team behind the product. If anything I think that acquiring a product that has been "vibe coded" and putting them into capable engineering hands would only enhance the product...or a least make the code base cleaner. I also believe that talent that is able to create stunning products with AI is currently a small percentage of folks, and that companies should be investing in acquiring that talent (either independently or via product acquisition) so that they can stay ahead in innovation while learning how to implement AI tools more efficiently in their orgs. Very curious to hear what you all think!
Hi Makers! Post your product in this thread if you are: (1) launching soon or recently launched (2) looking for feedback on your landing page
(3) looking for someone to beta-test your product and give feedback on the product before launch I believe in giving before asking. Start by helping someone who have posted their product, help them with their question, give a suggestion, write a review or a comment on their launch page. Once you have helped someone else out, share your product link here and clearly state what kind of help you need.
In my case, building my startup Selftalk - an app for self-therapy, transformed my character big time.
1. I became much more grounded, and connected to reality.
2. I discovered so many things about myself, good and bad, which significantly deepened my self-awareness.
3. I ve developed immense respect and compassion for fellow entrepreneurs, creators, and doers. It s easy to critique from the sidelines, but it s an entirely different experience to be in the arena, facing the challenges head-on.
I run an offensive security firm (SDX Shadow Labs), and we spend a lot of time pentesting early-stage startups and MVPs. I love the speed at which indie hackers ship, but I see the exact same 3 critical vulnerabilities in almost every new product.
If you are building an MVP right now, check your codebase for these:
1. The "Hidden" API Endpoint You built a feature, decided not to launch it, and hid the UI button. But you left the API endpoint live (/api/v1/export-users). Attackers don't need UI buttons; they just query your API directly. Delete dead code.
In the beginning, everything feels fast and exciting. You have an idea, people start trying it, feedback comes in. But what happens when that energy slows down?
There s often a quiet middle stage less feedback, fewer new users, and more questions in your head:
