The huge lift of vibe coding
Every time I vibe code there is always this huge lift that I constantly have to go through. Authentication, billing, password resets, emails, signup, waitlist, landing page and when it’s all said done and the app is ready then comes the marketing, the blogging, the social media automation, the product hunt launch etc etc etc…. So much repetitive crap that I have to do just to get a simple app up and running. How do you guys handle all this?
Since I am a coder and a hammer sees everything as a nail, I decided to create all this code as a template so I can jump into building an app right away. There is actually a lot more than what I mentioned above e.g customer support, chat, roadmap for building in public, email flows and more coming.
I would love to hear feedback and how you do it and what else would be helpful in such a template.
Replies
CuratedLetters
CuratedLetters
@cristian_stoian_urzica you going to open source or sell it or is it just for personal use?
Just gone through your setup, and I must say, you have done something huge here!
Is there a free test scenario, minimal setup and config, not like the entire thing here, so I can test it out.
Would love to test/use it
CuratedLetters
@franklivania thanks man. how did you go through the setup? It's not 100% released yet but if you join the waitlist, you get 50% off and i can give you immediate access as long as you are ok with pre-release code.
@emad_ibrahim I mean I went through the website, and saw the packages you are offering.
Yes please, I am okay with the pre-release code, thank you
CuratedLetters
@emad_ibrahim I am in, email is cfaodigbo@gmail.com
Mocha
We're building Mocha specifically to solve this.
Auth, backend, DB, everything should be very opinionated so you can focus on outcomes. Picking or managing products like supabase makes no sense if you're really non-technical
CuratedLetters
Mocha
@emad_ibrahim I get it. If you're a coder I think the best ones right now are https://codewithfriday.com (underrated), claude code and cursor, in that order.
Our tool is https://getmocha.com.
Releasing our big "backend full stack" version next wekk.
CuratedLetters
You can build up a boilerplate or template for yourself, so you don't have to re-create everything for next products.
CuratedLetters
AdBlur - Hide Ads, Focus on Browsing
Build a boilerplate code and document it, so that your AI agent doesn't have to rethink the wheel again n again. thus less token spent. i update my boilerplate to the latest libraries everytime I start a new project.
create a 3rd party integration requirement checklist. check uncheck which ones you need for a project. most of the time many services are common.
document all apis, ask your agent to document each step, so that you don't lose context.
make a launch checklist. group your tasks based on domains. follow it blindly. plan parallel tasks.
create boilerplate app launch design template with all graphics size requirement rules, based on the respective platform it's gonna be posted in.
This works for me at least! Hope this helps!
CuratedLetters
This is cool! Does it play well with tools like Cursor, like if you pull the whole repo in you can make edits pretty easily?
CuratedLetters
@frederikb it’s built exactly for that. I built it that way because that’s how I build apps now. I don’t know if i can write code without cursor anymore :)
Since all my vibe coded projects are in the same computer, I can tell Claude Code to look into existing implementation of some feature from the other project. Also, I take parts of Claude.md file from other projects. Eventually, I think, I will keep a list of all frameworks/libraries that I prefer and use into a separate file and just initiate new projects with that.
CuratedLetters
@emad_ibrahim that is interesting. With vibe coding, I feel the approach is to use less frameworks and more libraries. It is easy to produce code. In my opinion, it is a great approach to restart using the same guidelines so that each project uses the newest version. Tests will be important. Also, a template will only work for the language/framework it is built on. Prompts or conventions will work more broadly. We can ask Claude Code to write the same end to end tests for any language/framework as long as we know what business case we want to test.
In the end the models are being trained to follow instructions better. A set of libraries + requirements to be met seem to be a superior approach to me.
CuratedLetters
@brainless I agree to a degree, but i got to the point where i know the tools and stack i need to use and set up the template in a way so it's easy to upgrade to the latest version... true, we can build auth code and subscription and payment very quickyl with AI but why spend 20 to 80 hours doing that everytime when i can just hit the ground running.
If you are building one app once a year, this is probably not for you but if you want to crank out one app every 2 weeks to see what sticks and what doesn't then this will save you so much headache.
wow, this is amazing value. For marketing I am handling all ongoing activities on Metaflow AI. I think for foundational stuff, the boiler plate you have built out there is solid. how easy or hard is to swap out let's say if i prefer Firestore vs Supabase?
@emad_ibrahim 100% agree this process should be automated. In fact there should be some classification as well...if you are launching on the day Google or Lovable strikes then all effort goes waste.
In my case we got fantastic reviews/ followers/ website traffic but none of those were considered by the platform in the final evaluation. There were 2 Google product(Opal & Photos tab), Norton AI browser and Golex...how can you stand such competition?