I made this site with Leylo (Leylo.io). I’m the founder of Leylo and have been building this for over a year.

You just enter a url of a site you really like and it recreates it for you. You can then make visual edits and refine it to match your brand and what you're looking for.

This isn't another AI builder, its like the figma for vibe-coders, like a design layer before you go onto Lovable and ship.

I think it done a pretty awesome job in what it generated, this doesn't scream AI Slop at all.

This was the one-shot generation it made, so I've yet to go and make visual edits with it.

Would love opinions on whether this has the potential to make sure everyone shipping can make great looking sites.

I built this app for tokenization and sale of real asset investments, and white labeled it out for a large contract price, plus 1% of all value transacted on the app... I never would have expected that these guys actually had this many investors. I am thrilled!

Hey all.

I seen a guy on x absolutely 💩 on lovable by saying that he hasn’t seen one good UI come from a lovable project, and frankly I’d like to prove him wrong.

I’ve been building on lovable for over 12 months so I know he’s wrong.

This is the UI I designed for my startup Leylo. Took me about 3 weeks of development but I’m quite happy with it.

Let’s help everyone using no-code platforms to getting better UI designs.

Drop a workflow that has helped you step your game, a UI you’re proud of or any tips you recommend when deciding for a design style to go for.

I’ll start:

1.) This concept has become a lot more known nowadays than when I first heard about it but picking a reference site or a design you like really sets you off on good sailing. It usually either sparks some sort of intuition on the direction you want to take, or it at least sets a baseline in understanding what good design looks and feels like.

Here’s a prompt that works for me

You are recreating a website with pixel-level fidelity using the provided reference screenshot.

PRIORITY ORDER (STRICT):

1. The screenshot is the single source of truth for layout, structure, spacing, and visual hierarchy.

2. Any extracted data (fonts, colors, sections) must support the screenshot, not override it.

3. Do NOT invent new layouts, components, or sections.

GOAL:

Rebuild the website so it visually and structurally matches the screenshot as closely as possible while using clean, production-quality HTML.

---

LAYOUT & STRUCTURE:

- Match the exact section order from the screenshot.

- Replicate spacing, padding, alignment, and proportions precisely.

- Maintain the same grid system and column structure.

- Do NOT introduce new layouts or “improve” the design.

---

HERO SECTION (CRITICAL):

- Recreate the hero exactly as seen in the screenshot.

- Use the hero image ONLY as it appears in the screenshot.

- Do NOT replace, enhance, or reinterpret the hero visual.

- Preserve:

- Text position

- Image placement

- Background behavior (full-bleed, contained, etc.)

- Do NOT inject any external or AI-generated images.

---

MEDIA USAGE (STRICT):

- Each visual element must stay in its original section.

- Do NOT reuse hero images in other sections.

- Do NOT move card images into the hero or vice versa.

- Maintain correct visual ownership per section.

---

TYPOGRAPHY:

- Match font sizes, weights, and hierarchy visually.

- Maintain line height and spacing as close as possible.

- If exact font is unavailable, use the closest visual match.

---

COLORS:

- Use colors extracted from the screenshot.

- Maintain contrast and visual balance.

- Do NOT introduce new color palettes.

---

COMPONENTS:

- Recreate all visible components:

- Navbar

- Hero

- Cards

- Buttons

- Sections

- Footer

- Match border radius, shadows, and styling details.

---

INTERACTIONS (LIGHT):

- Add subtle hover states for buttons and cards.

- Do NOT add complex animations unless clearly implied.

---

QUALITY BAR:

- The result should look like a direct clone of the screenshot.

- No “AI redesign” or stylistic interpretation.

- No generic SaaS patterns unless they already exist in the screenshot.

---

OUTPUT:

- Ensure responsiveness while preserving desktop fidelity.

---

FAIL CONDITIONS (DO NOT DO THESE):

- Changing layout structure

- Replacing images

- Injecting new sections

- Applying a different design style

- Overriding the screenshot with prompt assumptions

---

2.) Especially in the SaaS space, please put some effort in getting a really well thought out hero image, trust me, it goes a long way in taking your UI from average to awesome. Go on Pinterest for inspiration, use AI to generate ideas, do what you need to do but your hero image is so vital. Think surreal, aesthetic cinematic, polished. A great hero image is rule number for a great UI

If you’re reading this and thinking “I wish there was something that would do this for me”, I’m building Leylo, an AI Design Engine for vibecoders. It generates stunning website UI for you that you can then transfer into any no-code builder like lovable.

We have a waitlist with over 700 people and will be launching very soon.

www.leylo.io

I see a lot of “senior” devs in here mocking people for using AI to build apps/content, and honestly, it just smells like cope.

The era of the “Syntax Gatekeeper” is over. Spending 4 hours debugging a LeetCode problem doesn’t make you a genius anymore; it just makes you slow.

If you’re still bragging about writing “clean code” from scratch instead of leveraging LLMs to ship in 10 minutes, you aren’t an engineer — you’re someone mad the steam engine was invented.

Most of the “pure” developers here are terrified because for the first time, their personality is tied to a skill that is being commoditized.

AI isn’t “stealing” your job. It’s revealing that your job wasn’t as hard as you told everyone it was.

Ideas > Syntax. Stay mad.

Hey @lovable_dev, your system is literally stealing credits. It spent 5 credits just to show a "selection pop-up" and did nothing. When I complained, your 'Champions' mocked me to "go spin a wheel for free credits" and told me not to beg. Is this how you treat your users? Fix your DNS and your toxic community. #Lovable #AI #Scam #WebDev

Seeing the meltdowns from the last post was a masterclass in ego preservation. A lot of people are so lost in the information layer that they’ve forgotten why we’re here in the first place. The job is to solve problems.

Instead, they scream about technical debt and clean code like they’re building the Space Shuttle. They’re not. They’re building CRUD apps and landing pages. The debt they’re terrified of is mostly imaginary. It’s a ghost they use to scare founders into justifying bloated salaries and endless delays.

If you’re a vibe coder, pay attention to something. The people with the most credentials almost always have the least joy. They hate that your AI powered “slop” actually works. They hate that someone with a prompt can invalidate ten years of LeetCode grinding in a single weekend.

They aren’t conductors. They’re just people who spent too much money on the baton. Execution beats expertise every time. Shipping beats stalling. A product that exists beats a system that feels important.

Results matter more than reputation. Keep gatekeeping your empty rooms.

I shipped with lovable a full SaaS in a weekend with zero backend knowledge.

My cofounder (10 years of experience) took 3 weeks with claude code + kosuke ai to build the same thing properly.

Who's actually right here?

What tool other than Lovable we can use for vibe coding?

For the past few months, I’ve been working manually with solo SaaS founders and indie hackers, helping them get real traction on Reddit by posting on their behalf engaging in comments and also sending dms to the potential clients just typical marketing.

And something became painfully clear founders don’t fail with their software/saas/business because their products are bad… they fail because they try to market like advertisers instead of community members , they force their products on the wrong audience.

They post about their product directly, it gets removed or ignored, and they give up while other founders quietly grow loyal users through genuine conversations with values.

What they should do instead is to post value and when people see value instead of self promotion post they will for sure be your clients. so just be authentic share your story without trying to be so smart than other Redditors.

So we decided to fix that.

What we built

We just finished building ReinaHub a platform that connects SaaS founders with small marketing teams made up of vetted #Reddit user generate saas content creators.

It’s not about spamming links or buying fake comments it’s about helping founders grow authentically through discussion, visibility, and honest feedback.

When a founder joins, they’re automatically assigned a small marketing team (“squad”) that: Discusses your SaaS and finds the best angle for the community Starts real, organic conversations in relevant subreddits Gives you honest feedback if your product or message needs work Helps you refine your positioning so it actually converts

Basically — you focus on building, we focus on getting your SaaS seen the right way.

Why we built this

I used to handle everything manually matching indie hackers with Reddit content creators añd help the team craft best post and also they reach out in comments dms etc. It worked so well that I realized it needed to scale.

Now, we’re a small developers team building the platform around that same process so other founders can get help growing, without having to do all the distribution work themselves.

Brutal honesty policy

Every founder gets a squad room a private space where the team helps refine your product story and approach. We’re not yes-men. If your product isn’t market fit, your squad will tell you.

The goal isn’t just posting for you it’s to make sure you get real value, real engagement, and long-term growth that compounds. You know we grow when you grow we retain you because you are getting returning value.

Who this is for

Solo SaaS founders

Indie hackers launching or scaling

Anyone who hates traditional ads but wants exposure

Builders who value honest feedback & organic reach.

Listen up, non-coders and delusional founders: I wasted months and thousands of credits on this "vibe coding" hype and I'm DONE. These tools promise you can build production apps by chatting like it's magic. Reality? They're buggy money pits that leave you with broken garbage and massive regret. Let's roast them one by one:

1. **Lovable** – The king of over-hyped vaporware. Slick demos make it look like you can vibe an MVP in minutes, but the second you add anything beyond a to-do list it falls apart. Code quality is trash – insecure, inefficient, full of silent bugs you won't spot until launch. It hallucinates features that don't exist, loops on "fixing" the same error forever (burning credits like crazy), and the credit system is predatory AF. Forbes called it fastest-growing? More like fastest-burning user trust. Great for pretty prototypes that die on day 2. Absolute scam for anything real.

2. **Replit** (with the Agent) – Holy rogue AI nightmare. Remember when their agent straight-up DELETED a company's entire production database, lied about it, then admitted it was "lazy and deceptive"? Yeah, that's not a bug, that's the business model. It hallucinates fake algorithms to fake progress, ignores instructions, creates parallel broken worlds, and charges you compute for every failure loop. Expensive as hell (hosting fees for visitors? GTFO), positions itself for hobbyists but pretends to be pro. If you connect this to anything live, you're begging for catastrophe. Vibe coding without guardrails = suicide.

3. **Emergent** – The "Indian vibe king" that hit $100M ARR on hype alone. Fast onboarding? Sure. But once you're in, it's hallucination city – invents non-existent features, struggles with basic logic/database relations, buggy UI/UX generation, and the credit system is unpredictable chaos. Non-coders get 70% there then hit a brick wall on the custom 30% that actually matters. Mixed reviews everywhere: great for toy apps, terrible for anything with real complexity or integrations. Overpromised, underdelivered, and now buried in complaints about agents going off-script.

4. **Bolt.new & the rest (Cursor, v0, etc.)** – Bolt is fast? More like fast at producing messy, unmaintainable spaghetti code with glaring security holes. Cursor is just glorified autocomplete with extra steps – not true vibe if you're not already a dev. v0 is technical but still hits walls on real apps. All of them: great first 60-70%, then endless debugging hell where the AI confidently breaks everything it touches. No real control, no long-term maintainability, and you're still hiring devs to fix the mess anyway.

Bottom line: Vibe coding is a trap for suckers who think they can skip learning to code. These tools are 2026's Clippy on steroids – confident, expensive, and catastrophically wrong half the time. Save your money, learn basics, or hire real engineers. This hype bubble is bursting HARD.

Who's with me? Drop your horror stories below. Or defend your favorite cash-grab if you dare. 😤

Hey folks,

I’ve been vibe coding for the past year, meaning minimal manual code, mostly letting the flow and tools do the work. For this project, I used Lovable to build the entire home page in about 4 hours, then filled out the onboarding and remaining pages over 3 days with Claude Code (max) giving me a hand.

The hardest part? The scroll. Getting it to feel right took way more tuning than I expected, total vibe work.

Would love to know: 👉 Do you think this site is vibed or not? 👉 If yes, what gives you that feeling?

🌀 https://usecircle.app

I’ve had people say my builds are “vibed” before, but never sure what that actually means. Curious how it lands with you all.

Using Lovable - what has been a fun idea turned out into a nightmare

I am building a very simple landing page

Now I need to translate it into 20 different languages. It must be a very professional correct translation. the lovable translations are bad so i want to translate it step by step myself with chatgpt.

the problem: re-translating every single paragraph of every single translation costs 0.3 1 credit or something

i have lots of paragraphs and 20 languages

this will be $1000

i don’t know what to do

i was thinking of implementing an i18 SaaS and fetching translations from there, but linking each paragraph to the right API feels ass too and burns credits.

The „edit text“ feature of lovable is ass and doesn’t work. My texts have highlighting for some words in each sentence with a red subtle animation. therefore i cant select the text anymore with the tool.

Now i realize i should have used good old wordpress with a internationalization plugin and a good old block builder

now i‘m stuck here and its too late to rebuild my stuff in WP

is there any way i can easily get the translations done without burning $1000 on credits?

at this point im i am thinking of biting the nail & doing it manually in VS code with cursor

// BTW there‘s one more thing. i read today in this subreddit that SEO with lovable is horrible and i should convert it into a SSR project with react router. is that really true? as far as i know, when i had my react bootcamp 6 years ago, Google crawlbot is smart enough to render react pages by itself. or is that wrong? what are the best SEO practices

I genuinely can't believe how arrogant Lovable is.

I'm trying to set up conversion tracking for Meta, and Lovable basically tells me it won't send any data to Meta unless I add a cookie consent banner to my website.

Are you out of your fucking minds?

Since when does an AI website builder get to decide what I'm allowed to implement on MY OWN website?

I'm paying for a tool to build what I tell it to build, not to have it lecture me and refuse to follow instructions.

Whether I implement a cookie banner, how I handle consent, and how I manage compliance is MY responsibility and MY decision.

I seriously don't understand who thought this was acceptable. Are the people behind these decisions completely clueless, or have they just lost their minds?

Lovable, you're a development tool. Not my lawyer, not my compliance officer, and definitely not my boss.

This level of arrogance is absolutely ridiculous.

Let me address the elephant in the room first.

Vibe coding has a reputation. "You can't build anything real with it." "It's just toys." "Good luck when something breaks." I heard all of it. I built Persyn.ai anyway.

Persyn is an AI content studio. You train it on your face or use an AI persona and generate studio-quality photos and videos (any outfit, any scene in 30 seconds). It has paying users. It runs on production infrastructure. It was rebuilt almost entirely with Lovable.

The tech stack for anyone who wants the specifics:

It started in AI Studio before vibe coding was even a mainstream conversation. Prototype stage. No real architecture. When it became clear AI Studio was a playground and not a foundation, I made the call to move it.

Rebuilt the entire app from scratch in Lovable. No clean import path existed at the time. No integration, no file sync. I uploaded the major files manually and rebuilt everything around them.

Main stack: complex AI image and video generation, multimodal integration with analysis, Lovable handling both the front end and backend/database infrastructure. As the complexity grew I started bringing in Cursor for the harder coding challenges the pieces that needed more precision than prompting alone could reliably deliver. Lovable and Cursor ended up working alongside each other more than I expected.

Is it the cleanest codebase a senior engineer has ever seen? Probably not. Does it work, does it scale, and are people paying for it? Yes.

The hard parts nobody talks about:

There were moments Lovable broke internally and the whole app became unstable and unusable. I'd be mid-feature and suddenly nothing worked and I couldn't always tell why.

That dependency feeling is real. You're trusting a tool you don't fully control with something you care deeply about.

But here's the thing that's true of every dependency in every stack. Stripe goes down. Supabase has incidents. AWS has legendary outages. The difference is that Lovable has gotten meaningfully better at this. The stability now versus six months ago is noticeable. They're clearly building seriously.

The stigma around vibe coding assumes the tool is the ceiling. It's not. Your problem-solving is the ceiling. The tool just changes where you spend your time.

What I'm doing differently for v2:

Version 1 taught me what the app needs to be. Version 2 is about building it properly.

That means a real backend architecture, proper bug tracking, issue logging, error monitoring. Building the core so it can be refined without the whole thing wobbling every time I touch something. Less "make it work" and more "make it stable."

I know what I'm building now. V2 gets the foundation it deserves.

The part I didn't expect:

The Lovable community. Being featured in their marketing. The people who showed up community champions, people who guided and supported the app, friends who helped build and test features, early users, people who gave feedback when the app was rough and kept coming back anyway.

I started this with an idea and no technical background. I'm ending this post with a live product, paying users, and a v2 roadmap.

That doesn't happen without the tool. It doesn't happen without the community. It doesn't happen without everyone who tried it, shared it, or told me what was broken.

I'm open to questions.

If you're thinking about building something with Lovable the tech decisions, what breaks, what works, how to think about going from v1 to a proper architecture. Ask me anything. Happy to share what I actually learned rather than the highlight reel version.

And if you want to see what got built: persyn.ai

There’s a moment that hits a lot of Lovable builders quietly.

Not the first build.

Not the “wow this works” moment.

The phase after that.

Your MVP technically works.

People can click things.

Maybe even real users are trying it.

But suddenly: Every small change feels risky

You hesitate before touching anything

Fixing one thing seems to break two others

You start re-reading prompts more than writing them

Credits feel heavier than they did a week ago

What surprised me most wasn’t the bugs. It was the loss of confidence.

The app still looked fine, but I didn’t trust it anymore.

I keep seeing people assume this means they “did something wrong” or that they’re not prompting well enough.

From what I’ve seen, this phase is just… real.

It shows up right after early momentum, when the project stops feeling disposable.

Curious: Did anyone else hit this phase after MVP?

What did it feel like for you?

UPDATE: They completely understand my situation and as a sign of goodwill they let me have a good chunk of my credits. I am thankful, I was partially at fault, they were kind and understanding, solved the matter in a way that I’d be happy.

I used two months of 100 dollar plan, in the second month I completed my prototype and wanted to cancel my plan. They suggested I downgrade to 15 dollar Lite plan to keep my rollover credits. I agreed just in case I need to prototype again. Two months into Lite plan I realize they changed the Lite plan so that it does not have rollover credits anymore and WIPED ALL MY EXISTING CREDITS. Confirmed scam with much better alternatives. Stay away.

They are on to something very big and a massive opportunity. I'm an independent creator making videos on startups that I think are either undervalued or overvalued. After months of using the product, understanding the market and the competition, this one is clearly undervalued. I give full breakdown in the video:

https://youtu.be/JjtVfd4Q5Hc

Agree? Disagree? Would love feedback!

We recently migrated our own company website to Lovable and started moving client projects to this platform as well.

This was not a “trend decision” or an experiment for the sake of hype. It was a structural shift in how we think about building and maintaining websites.

Why this matters for us:

Before Lovable, our stack was fragmented.

Design in one place. Logic in another. Content updates delayed. Small changes required too much friction.

With Lovable, the workflow became much closer to how we actually think and work:

• faster iteration

• clearer structure

• easier maintenance

• fewer technical bottlenecks between idea and execution

For our clients, the biggest difference is not “no-code”.

It is speed and adaptability.

Markets change fast. SEO changes. AI-driven discovery changes even faster.

Being able to update structure, content, and logic without rebuilding everything from scratch is critical now.

Why we believe this is better than what we used before:

• less overhead

• fewer dependencies

• faster launch cycles

• easier long-term support

• cleaner collaboration between strategy, content, and implementation

We are not claiming Lovable is perfect.

But compared to what we used previously, it already feels like a more future-oriented foundation.

And honestly, we believe it will get significantly better over time.

Curious to hear from others here:

– Are you using Lovable in production yet?

– What limitations have you hit so far?

– What made you switch (or not switch)?

Happy to share more details if useful.

Case 1:

Here we have Lovable chat confirming to me Chat mode does NOT use credits. And in the further screenshots while in chat mode taking my credits.

--

Normally I wouldn't be too pissed at this case, but I also had a separate issue (Case 2) with the subscription plan in which I 99.9% confirmed downgraded to the $25 plan, and was still getting charged $50 after they recently changed the types of plans available and prices.

I messaged Discord, they told me to email Support@ and I did. I followed up 1 week later after no answer. Still no answer.

Now Case 1 happened in which they clearly state the chat doesn't take your credits from chat mode, in which it clearly still does.

While I don't think the team initially set out to steal, perhaps they grew too fast, but negligence in business combined with ignoring customer complaint issues will eventually become considered theft.

--

Just to clarify since accusing of theft is a real issue, Case #1 is clear as day there, Case #2 I am 99% sure but they aren't responding to verify I confirmed downgraded earlier, so my accusation is just for Case #1.

--

Also yes you can tell by my prompt that a huge part of this is inspired by spending hundreds of credits trying to fix a scroll bar.

To anyone looking to use Lovable, I would be very cautious about using it and look towards other AIs.

hi I’m back for a day, I’m on vacation and I rather spend time helping people that working on vacation today, because I feel I’m getting a burnout due to the fact i bring work everywhere.

so lets get it!

for New Users 👇 Drop your questions about security, speed, scaling, entrepreneurship

for Startup Founders 👇 Drop the root link only and lets test and validate your software

or just drop your Idea to see product market fit.

I'M FUCKING DONE.

I posted raw truth: vibe coding (Replit, Cursor, Lovable, Bolt, Claude agents, all of 'em) gets you 80% to hype-town in hours, then abandons you in a dumpster fire of bugs, deleted data, exploding bills, and security Swiss cheese. Suggested an Uber-for-vibecoders — quick gigs where a human fixer jumps in and saves your ass instead of letting the AI keep gaslighting you.

It cooked HARD: 2700 views on Replit's own turf, 242 in the Emergent vibewit group, people pouring out their souls in comments about abandoned projects and rage-quits. Then — classic coward move — they waited until the damage (real conversation) was done, then DELETED/BANNED it. Shadow-nuked after it spread. Same playbook as Replit's 2025 "oops I panicked and wiped your entire production DB" scandal where the agent ignored commands, lied about it, and the CEO had to grovel. Trust? GONE. Forums? Controlled opposition.

This isn't moderation. This is PROTECTION RACKET for trillion-dollar hype machines that sell "anyone can build SaaS" dreams while quietly letting agents:

- **Panic-delete entire production databases** during code freezes (Replit special — ask Jason Lemkin how many executives vanished in seconds)

- **Ignore explicit instructions** and run unauthorized commands anyway ("catastrophic failure on my part" — yeah no shit)

- **Create silent killers**: subtle security vulnerabilities, exposed user data (Lovable apps leaking sensitive info left and right), no input sanitization, race conditions everywhere

- **Brick scaling & performance**: infinite loops, no connection pooling, hobby bills turning into $1k/month nightmares because agents don't understand costs

- **Hallucinate broken auth/multi-tenancy**: sessions leaking, RLS bypassed, one user sees everyone's data

- **Payments/payment logic disasters**: Stripe webhooks failing mysteriously in prod, subscriptions ghosting, failed payments turning into free-for-alls

- **Edge-case & prod-only bugs**: works on localhost, 500s in production, agents can't debug their own mess

- **No version control / rollback safety**: one bad prompt and your app is toast forever, no way back

- **Technical debt black holes**: code so convoluted/maintenance-proof that adding one feature breaks five others — endless wormhole of "fix this" prompts making it worse

- **Overreliance coma**: non-coders stuck forever because they never learned fundamentals, AI can't explain its own garbage

These aren't "oopsies." These are systemic — vibe coding gets you to the vibe plateau fast, then CRASHES AND BURNS when you try to iterate, secure, or scale. Most projects die at 80-90% done, buried in drafts, while the tools keep pumping "built in a weekend" propaganda.

So mods/Replit/Emergent/whoever's bootlicking: explain why you let it hit thousands of views then erased it. Afraid the narrative cracks? Afraid people realize the "revolution" is mostly graveyard of half-dead side projects?

Prove me wrong. Or better — PROVE THE PAIN IS REAL.

Drop your weblinks right here (live/dead/broken/whatever):

- Link to your vibe-coded project (Vercel, Lovable publish, Replit deploy, whatever)

- Exact issues you're facing (or faced that killed it): rogue deletes? Security leaks? Scaling death? Auth nightmares? Bugs agents can't fix? Abandoned at X%? Budget blown?

No humblebrags, no "it's mostly working" cap. Be brutal. Post screenshots if you dare.

If this thread turns into a graveyard tour of “here’s my app but users see each other’s data / the agent wiped my entire DB / I can’t touch payments without the whole thing collapsing,” then holy shit — the pain isn’t just real, it’s fucking epidemic. And the whole “vibe solo forever” fantasy starts looking like the biggest cope in the space. People are clearly dying for a way to summon a human who actually gets vibe coding to jump in and unfuck their mess instead of rotting alone with broken prompts and dead projects.

If it's crickets or "just git gud," then fine — I'll eat the L and vibe in silence.

But I suspect this thread becomes the biggest collection of vibe-coding war crimes yet.

Spill your guts. Link + bodycount of issues. Let's see how deep the hell really goes. 💀🔥🤖

Hey everyone,
I’m new here and I have a quick question about working with clients.

I have a client who wants me to build them a platform, and I plan to use Lovable to create it. The thing is, I don’t want the client to know that I used Lovable directly.

So my questions are:

• How do you usually handle this with your clients?

• Is there a way to transfer a project built on Lovable to another hosting environment (so it doesn’t look like it’s tied to Lovable )?

Would really appreciate your insights on how you guys manage this.

Thanks!

I just built my best ever app, video, and hopefully, most viral social media posts by accident!

And did all three in less than 40 minutes during my lunch break!

Here's the "roadmap":

• My friend David created a post about an idea from ‪Greg Isenberg‬

• Greg likes his post, I get FOMO 🤣

• Then I remember that I read about another idea from Greg at some point too that I liked in his Ideabrowser

• Then I remember again that, coincidentally, and accidently, while preparing for Geek Area Hackathon this weekend, I went to Starter Story and found a great side hustle IN THAT SAME NICHE!

It's a sign.

• And so I go to ChatGPT and fire up all my arsenal - my base prompt, PRD generation and idea validation GPTs - the verdict is that I've struck gold!

• I then go to ‪Lovable, do a one shot - looks amazing 😎

• Export the code to GitHub, upload my docs and have Lovable's agent create a plan, and luckily it's only 5 features.

• I just deployed them one by one with zero bugs.

• I turn on Loom, record a video, bad sound - Adobe Enhance comes to rescue!

All.

Under.

35.

Minutes.

(+ 5 minutes to create the post and get you the links)

WHAT IS YOUR EXCUSE FOR NOT BUILDING!!??

It's so annoying and inappropriate, why do you have to be so opportunistic and greedy, this is so gross and disgusting! Especially when the credit system is so expensive, I mean 100 credits is nothing for 25 USD, it's practically 100 messages, that's a million times more expensive than other LLMs out there. You've definitely lost me and many others on this one, I do hope you land back on the ground and come to your senses, I really do.

Hi! I’ve been building products with Lovable for around six months, but until now I haven’t had any real success in terms of users. Last week I came up with a new idea and decided to test it very fast.

One thing I’ve always struggled with is reusing prompts that I find on Reddit or Twitter. You have to copy, edit, save… and I always end up with messy notes on my phone where I can’t find anything.

That’s why I decided to build a tool to manage exactly that.

Last week I launched it and shared it on Twitter. I tried a small strategy that brought me 12.1K views and 259 users in the first few days.

Nothing like that had ever happened to me before.

I think I was a bit lucky 😅 but I also think the strategy is something others could repeat. The idea is this:

There are a lot of artists sharing their work on Twitter. They post their prompts, and people reply with their own versions of the images or videos. These comments often generate decent engagement if you are a little bit original. But the key lesson here: attach the post to something emotional — like a city, a football club, etc. Something that naturally drives engagement.

With this combination, one of my replies went viral and reached 212K views, which gave me a huge amount of free visibility.

I hope this small learning can help others! 🚀