3 days, lots of coffee, and many iterations later, hereβs my MVP built with Lovable + Cursor πͺ
It's not perfect, but it works, and I'm very happy with it.
Designers: What would you update here? π
#buildinpublic#SEO#DigitalMarketing
Built the landing + MVP for my new SaaS in 7 days.
What I learned: Use Lovable to focus on nailing the layout + design, then outsource final touches (or use Cursor).
I'm giving 80% off to my next 10 signups - check it out if you want to get featured in Forbes: https://t.co/UuLJMnXxUy
#buildinpublic
@samm_duc Thanks Samuel π Right now I'm experimenting with integrating MCP (Model Context Protocol) into the workflow, mainly testing better defining my static context and syncing with local state. We'll see how it goes!
My new SaaS dev workflow 10x'ing my productivity:
π§ ChatGPT to craft the prompt
π» Paste into Lovable
π Sync with GitHub
π Run locally
π Review changes
π Repeat
Anyone doing something similar, but better?
#buildinpublic
UPDATE on 3-day SaaS build challenge:
β Finished the mobile-ready frontend in 4 hours using Lovable
π Now writing up the backend with a Supabase edge function.
One surprise: Supabase is way more affordable for low-to-mid scale apps.
π Supabase: $25/mo for 100K MAU
π Firebase: $460/mo for similar usage π€―
#buildinpublic
New challenge: Build a brand new SaaS (frontend, backend, AI, payments) in three days.
It is even possible?
I'm starting my build now, planning on going live this Friday (3 days). Watch me π
#buildinpublic
@SangKip4@janetmachuka_@Egline_Samoei Will be interesting to see how this benefits / hurts organic content generation on X, by taking away a large part of the summarization work of emerging trends that many commentators do on this platform.
Will this benefit or hurt X's engagements in the long run?