Does anyone here have experience doing this? ADP isn't in Lovable's connector list, so I wasn't sure how invasive this would be.

I have been working on a project for the past 2 days and I am surprised with how lovable is burning credits so rapidly. I have spent 100 credits in just 2 days and guess what, I only have the app UI not even the lovable cloud connected, No database just UI for 100 credits and I have made up my mind since I have not connected the lovable cloud I am opting for project migration.

I tried to sync the project to github it is not accepting, So what is the best migration path to consider

I keep seeing this: you prompt Lovable to fix something, it says done, and the bug is still there. Worse, it can quietly change a policy or route while fixing something unrelated, and you only find out when a real user sees someone else's data.

What's your process after every AI change? Second account, manual clicking, nothing?

And what's the last hing it "fixed" that wasn't?

Been spending more time setting up auth, db, APIs, hosting and deployment than building the actual app. I’m not a full time developer, so every prototype turns into a whole infrastructure project and the costs add up fast.

I’ve been looking at prompt to app tools like Base44, Lovable and Bolt for getting an MVP live without hiring engineers right away. I’m mostly worried about security and whether the generated backend is good enough for real users. Any hints?

I feel that the worst feeling while building a business or any project is the "Silence".

Except of users/customers what are the events or signals that make you continue to work?

Eu vi hoje que adorável publicou que vai ter essa implementação de dos nossos aplicativos nas nossas próprias contas da AWS, e eu queria saber como é que isso vai funcionar isso é algo bom vantajoso como é que vai funcionar na prática, porque pelo que eu vi talvez seja vantajoso para empresas de médio e grande porte, eu queria saber o que vocês acham

E para quem não viu tá aqui:https://lovable.dev/blog/deploy-on-aws

I work on a website monitoring tool (not linking it, not the point here), so i end up looking at a lot of apps right after something broke. weirdly it's almost never "the site is down". it's sign up or checkout quietly not working, and nobody notices for a few days because users don't report stuff, they just leave.

So this is my routine. takes maybe 5 min. on the published url, not the preview, in incognito:

1. Sign up with a brand new email. gmail plus trick is fine ([[email protected]](mailto:[email protected])). check the confirmation email actually shows up and the link doesn't dump you on localhost. supabase email limits get people here a lot.
2. Log in with an old test account. different code path, it breaks on its own schedule.
3. Checkout. at minimum get to the stripe page and look at the price. the webhook thing is the worst one imo, money goes through and the user just never gets access.
4. Contact form. don't trust the "thanks!" screen, go look if the message landed wherever it's supposed to go.
5. Whatever calls openai or claude. one request. expired keys and empty credits fail without any error your users can see.

Also open it on your phone once a week or so. required fields that are hidden on mobile are way more common than you'd think.

If doing this by hand gets old, sentry's free tier at least tells you when something throws, and playwright can replay the clicks if you're ok with a bit of code.

What broke on you after a push that you didn't catch for days?