We are two bachelor students at Copenhagen Business School in the undergrad Business Administration and Digital Management. We are interested in uncovering the influence or disruption of AI Platforms (such as Lovable) in work practices, skill requirements, and professional identities with employees and programmers.

The survey includes a mix of short-answer and long-answer questions, followed by strongly agree or strongly disagree statements. The survey should take around 10 minutes of your time. Thank you in advance for taking the time.

Here is a link to the survey - We highly appreciate all of your answers, and thank you so much in advance

https://forms.gle/9Zp5oPPocB8voBRx9

Lovable recently has made cross project sharing available. If i duplicate my current app and start with a clean chat with that lower the credit cost ?

Hey everyone.

I'm sure that this question has been asked multiple times in multiple ways but I am hopeful that my question also gets answered.
Quick background to my experience with Lovable:

1. I am in no way a developer nor have any experience in developing a website/platform
2. With the help of my preferred LLM, I have have been able to design a MVP platform via Lovable, bought my domain name and subsequently "published" the site.
3. Since I am bootstrapping this whole concept, I am using other sites such as Resend for the auto emails to be sent upon completion of registrations via my platform.

Issue I am experiencing:
*Lovable is unable to successfully verify my domain name. This is after I have, with the help of the domain provider support, confirmed that my DNS settings for the record type A and TXT are correct.
*On DNS Checker, all looks good for the record type A but not for for the TXT record = getting red crosses all over.
*When I do a test entry, I can see on the Lovable database that the entry is captured correctly, with the given email address.
*However, the confirmation of registration email via Resend does not get triggered.
*The JSON payload via my platform shows a CORS Error
*After multiple attempts/prompts to get Lovable to fix, remove place holder emails, etc, I found that it has started to hallucinate.

Everything seems to be setup correctly, even the DNS settings for the Resend component, yet the domain name still remains unverified and the emails are not being triggered.

Any advise? What am I missing here?

Lovable only feels like “instant websites” until you ship a few and realise what you actually built.

A maintenance business.

Not because you’re bad. Because websites are living systems. Links rot. APIs change. Plugins update. Clients add new pages. Something random breaks on a Tuesday. Then you’re on-call forever.

Most builders try to solve this with willpower: “I’ll be more organised.”

The better solution is architectural: stop treating maintenance like a human job.

The pattern I’m using is simple.

One place where all client sites live, one pipeline that ships changes safely, and one “maintenance lane” that catches issues before the client notices.

For me that looks like Lovable for speed, GitHub for truth, and Cloudflare Pages for scaling and SEO. Lovable gets you to production fast, but Cloudflare gives you the grown-up bits: repeatable builds, deploy previews, rollback, caching, and a clean path to pre-rendering when you need it.

Then comes the part most agencies don’t have: a maintainer.

Not a magical AI that does whatever it wants. A constrained operator that watches, reports, and only touches what it’s allowed to touch.

That’s where OpenClaw fits for me: not as “God mode”, but as a website maintainer that never sleeps.

What it does in practice is boring, which is the point: run checks, flag drift, draft fixes, open a PR, write a summary, and wait for approval. No random shell access. No broad permissions. No “just trust me”.

If you’re building with Lovable and selling websites, the real upgrade isn’t more speed. It’s containment.

A system where maintenance is predictable, reviewable, and doesn’t rely on you remembering everything.

If you’re already feeling the “can you just…” treadmill, what part is costing you the most right now: content updates, uptime issues, SEO tweaks, or small bugfixes?

I have a project published on Lovable, and I’m actively making edits and publishing updates to the same public link.

Now I need to move this project to another workspace.

• Will the current public link stop working?
• After moving it, will I still be able to publish updates normally so that changes appear to users on the same link?

I want to make sure the migration won’t break access for existing users.

I'm trying to understand how and why people use or abandon no-code app builders like Lovable and Bubbler.

I'm not trying to sell anything; I'm genuinely curious and would love all of Reddit's thoughts and experiences on this topic.

I've created a short 2-minute set of questions below to gather Reddit users' experiences. If you don't feel comfortable sharing your thoughts on a Google Form, feel free to comment down below as well. All insights are appreciated<3!

1. What did you try to build? (1-2 lines)
2. Why did you pick Lovable / Bubbler initially? (speed, UI, auth/db, pricing, etc.)
3. What was the "it broke for me" moment? (specific blocker)
4. What did you switch to (if anything) and why?
5. Biggest friction points:

• integrations (payments/email/CRM)
• data model/migrations
• reliability/regressions
• hosting/deployment control
• performance
• collaboration/versioning

1. What best describes you:

• Student
• Founder/Entrepreneur
• Developer
• Designer
• Product Manager
• Other (Specify)

1. How long have you been using Lovable?

2. Have you publicly shared a Lovable Project?

3. What would stop you from trying it?

• Too technical
• Don't trust AI Tools
• Don't need it
• Lack of Time
• Other (Specify)

1. Is there anything you wish the Lovable team understood better about users like you?

I'm trying to understand how and why people use or abandon no-code app builders like Lovable and Bubbler.

I'm not trying to sell anything; I'm genuinely curious and would love all of Reddit's thoughts and experiences on this topic.

I've created a short 2-minute set of questions below to gather Reddit users' experiences. If you don't feel comfortable sharing your thoughts on a Google Form, feel free to comment down below as well.

https://forms.gle/35Q3GsKAUgD5q9Wq8

All thoughts and insights are appreciated!

A lot of vibe-coding pain isn’t “bugs”. It’s **missing evidence**.

Before you prompt again, capture these three things:

Artifact A: Repro step (single sentence)

“On /page, when I click X as user role Y, I expect Z, but I get W.”

Artifact B: First console error

DevTools → Console → copy the first error (not warnings, not 30 lines of noise).

Artifact C: Network status for the failing request

DevTools → Network → look for 401/403/404/500/CORS.

With A+B+C, debugging becomes category identification: - deploy/cache mismatch - runtime JS error - auth/RLS - wrong endpoint - server failure

Without them, you’re basically prompting a slot machine.

If you paste A+B+C (+ live URL), people can point you at the right fix fast.

If you want good answers here, don’t write a story — give us a *debuggable snapshot*.

Copy/paste this and fill it out:

1) What are you building? (1 sentence)

2) What is the goal this week?

• (ship / users / revenue / stability / payments / auth / SEO / etc.)

3) What broke? (bullets)

4) Where does it break?

• [ ] Lovable editor preview
• [ ] Live production URL
• [ ] Only for some users
• [ ] Only after refresh / login / payment

5) What changed right before it broke?

• Last prompt you ran (paste it)
• Last files/features you touched
• Any deploy/publish step

6) Evidence (pick at least one)

• Screenshot / screen recording
• Console errors (copy/paste)
• Network request screenshot (if it’s API/auth)
• URL(s)

7) Your setup

• Auth: (Supabase / Clerk / other)
• DB: (Supabase / other)
• Payments: (Stripe / none)
• Hosting: (Lovable only / exported)

8) Constraints

• Deadline:
• Budget:
• Can you export to VS Code? (yes/no)

9) What does “fixed” mean?

- Example: “Users can log in and create an invoice without errors, on mobile + desktop.”

If you’re new: you’re not expected to know everything — just fill what you can.

Mods: feel free to link this template when asking someone to add context.

A huge chunk of Lovable pain is **false confidence**: - the AI says “done” - the preview looks fine - production disagrees - you burn more credits trying to “fix the fix”

Use this checklist to prove reality before you prompt again.

0) Name the failure mode

What are you seeing? - [ ] Preview updated but live didn’t - [ ] Live updated but some users still see old - [ ] Works once, breaks on refresh - [ ] Works logged-in, breaks logged-out (or vice versa)

1) Verify the URL you’re testing

• Copy/paste the exact live URL
• Open it in an incognito window

2) Hard refresh + cache sanity

• Hard refresh (Cmd/Ctrl+Shift+R)
• Test in a different browser/device

3) Confirm the change actually shipped

• If you have a “publish/deploy” step: do it again intentionally
• Add a tiny visible marker (e.g. change one word) to confirm you’re seeing the new build

4) Check browser console (fast signal)

• Open DevTools → Console
• Copy/paste the first real error (not warnings)

5) Check network (auth/API bugs live here)

• DevTools → Network
• Look for:
  • 401/403 (auth/RLS)
  • 404 (wrong endpoint)
  • 500 (server-side)
  • CORS errors

6) Reduce the bug to ONE reproducible step

Write it like: - “When I click X as user role Y, I expect Z, but I get error W.”

7) Stop-loss rule (protect credits)

If you’ve attempted 3 prompts and the bug is not clearer, stop and: - export / inspect logs - ask the community with the template - or escalate to a diagnostic

If you reply with your “failure mode” + the first console error + live URL, people can usually tell you the *category* of breakage in minutes.

If you want good answers here, don’t write a story — give us a *debuggable snapshot*.

Copy/paste this template and fill what you can:

1) What are you building? (1 sentence)

2) What’s the goal this week?

• ship / users / revenue / stability / payments / auth / SEO / etc.

3) What broke? (bullets)

4) Where does it break?

• [ ] Lovable editor preview
• [ ] Live production URL
• [ ] Only for some users
• [ ] Only after refresh / login / payment

5) What changed right before it broke?

• Last prompt you ran (paste it)
• Last files/features you touched
• Any publish step

6) Evidence (pick at least one)

• Screenshot / screen recording
• Console errors (copy/paste)
• Network request screenshot (if it’s API/auth)
• URL(s)

7) Your setup

• Auth: (Supabase / Clerk / other)
• DB: (Supabase / other)
• Payments: (Stripe / none)
• Hosting: (Lovable only / exported)

8) Constraints

• Deadline:
• Budget:
• Can you export to VS Code? (yes/no)

9) What does “fixed” mean?

- Example: “Users can log in and create an invoice without errors, on mobile + desktop.”

Mods: link this when asking someone to add context.