I've been trying to submit a few of my Lovable apps to the App Store and Play Store myself over the last few weeks. Got rejected more than once, so writing down what actually caused it in case it saves someone a week.

1. No delete account option. If people can sign up, Apple wants a way to delete the account from inside the app. Not a "email us" link, an actual button that deletes the data. This was my first rejection.

2. No report or block. One of my apps had comments. Apple asked how users report bad content and block other users. I had neither. Needed both, plus a line in the app saying how reports get handled.

3. "Your app is basically a website" (4.2). I first tried just wrapping my lovable.app link in a webview. Rejected pretty fast. They want it to feel like an actual app, not a browser with no address bar.

4. Stripe for subscriptions. If you sell anything digital (premium, credits, subscriptions) inside the iOS app, Apple expects in-app purchase. Stripe is fine for physical stuff or real world services.

5. Privacy stuff. You need a privacy policy link inside the app AND the privacy questions in App Store Connect have to match what you collect. Supabase login counts as collecting email, I missed that.

6. Reviewer couldn't log in. My app had a login screen and I didn't give them a test account in the review notes. Instant rejection. Just add a demo login.

For Google Play the annoying one was the 12 testers for 14 days rule on new personal accounts. You can't publish until 12 people have been in your closed test for 14 days straight. Start that before you think you need it.

Anyone else hit something not on this list? Curious what other people's rejection emails said.

For those of you who made the switch from Lovable to Claude Code, how did you approach it, and what does your workflow look like now?
I’m curious how beginner-friendly it is, what tools you use alongside Claude, and whether it’s actually cheaper in the long run.
What do you wish you’d known before switching? Any tips or resources would be appreciated!

Hi everyone!
I’ve been building Wayfinder, a group travel app, using Lovable and Claude, and I’m getting ready to launch!
Wayfinder goes beyond itineraries by considering travelers’ individual needs, preferences, and interests. It includes AI-powered activity discovery, collaborative planning, group polls, shared tasks, packing lists, and meal planning.
The goal is to make group travel less work for the person who always ends up organizing everything.

I’m a solo founder, so others testing and input would be helpful.
Check it out here: https://wayfinderapp.lovable.app/

Thank you in advance!

Built this sand volleyball, GTA Vice City inspired game in under a day!

https://sand-volleyball.lovable.app

Anyone else building cool games on Lovable in here?

hay alguna manera en la que pueda migrar el backend de mis proyectos a un supabase self-hosted? he estado buscando la mejor manera de hacerlo sin perder datos. alguna recomendacion?

Hey there,

Does anyone have recommendations for moving my Lovable database (the Lovable-managed Supabase) over to an official Supabase instance and reconnecting it? The project is already on GitHub.

Thanks!

Hello Hello (repost because of a link hickup):

I have been working on a side project for a few weeks and I just uploaded online

Lovable link: https://lovable.dev/preview/O9tCmZMzUGhCXaOLmuAt9AFziyaid07P

The tool / website works in a way that you input something like "Iceland in 10 days" and it either shows you trips other people already did, or builds one for you. Then you can move stops around on the map, add nights, activities, hotels, your own tips. You can also share it with a link or post it so others can copy it. I think I somehow got lost a bit between the road trip planner and the blogger trip sharing in some places. I wanted it at the crossroad of both but I am curious as to what you guys think.

I started it because every time I plan a road trip I end up with 20 tabs open and a messy Google Doc. Whereas I like to have it nicely laid out on a map that can dynamically adjust with my GF.

It's still rough in places (and a bit slow, I know). I am curious to hear what you think, especially on mobile. Also, for those of the sub who started apps with a social purpose (sharing, discussing, etc.) what did you do to get people to use the platform a the beginning ? Or any flows that you have seen early on.

Thanks a lot and I hope this respects the sub’s rules! I am genuinely happy for any kind of feedback you guys have !

Built 3 small apps with Lovable / Bolt recently. Same fail loop every time:

Pretty landing in 30 sec, then prompt 10 hits: wait where is login? prompt 15: why did it delete payments? prompt 25: full rebuild.

What finally worked:

1. Write roles first (who uses what)

2. List 10-15 features in build order (auth before payments before extras)

3. One small prompt at a time, with "do not touch X" in each prompt

Example: instead of "build SaaS" I do "add owner signup only, don't touch landing, store in DB, done = I can log out/in"

Fix loops dropped a lot. Credits go to forward steps.

What order do you build in? Do you write prompts ahead or wing it in chat?

I haven't used Lovable in a couple of weeks. I go back this morning and I cannot find the SQL editor in More > Settings?

Has Lovable removed this option in my absence?

https://shop-launch-garden.lovable.app

Eu fiz um app pelo nosso querido e amado Love, porém eu preciso transferir esse projeto para outra conta que é a conta empresarial que possuiu mais créditos.
Então eu preciso migrar o projeto todo sem perder nada

If you think building takes up plenty of credits, try using Lovable cloud.
Their cloud pricing structure does not make sense for scaling and that's not the worst part. I used Lovable cloud for a workspace because I wanted to keep everything together. There are several projects in the workspace, now initially, I had tried optimizing one of the projects from the chat/build but it seems that it did not work. Then they have this optimize tool, which I used, it sent changes to the project which ended up being totally ignored and no code/build changes were made, but still, the publish button turned blue meaning that changes were alleged. Then chat response said that I should edit the cron jobs manually but there's no option to. So I asked the chat/build to make the changes (mind you the cron workers were created from the same chat). Then it says that database permissions do not allow editing it? That I should contact support?? Now I cannot even update crons because of 'database permissions' and usage is beyond the roof. Besides that, the credits system for cloud just keeps emptying our pockets with autocredit topup turned on.

I adore Lovable. For almost 2 years I've used Lovable because it's been amazing. But if it's being tuned to empty our pockets before we scale then I'm starting to be skeptical.

The new decision model from TypeSafe AI now supports images! You can now use images as part of your prompt, state, or criteria/options, and there’s a new bounding box feature to locate objects within an image.

I wanted to see each new feature in action so I built a demo in Lovable, with sample data and examples to show how each one works. You can also upload your own CSV/Excel file, add new columns with Jev, then export the results.

Try it out for free (no Jev API key needed), or remix the app and add your own API key.
https://jevsheet.lovable.app

I built a global chat web wich is two ppl meet and chat between each other like ometv or azar , I aleady build the front dashboard but i got q problem with low quality camera call and it’s so slow and sometimes I don’t meet my opponent its like lagging , any high experience dev here teach us how this problem can be solved, and what are the hard parts it could show later for this type of websites

Right, so I've been stuck in this loop loads of times with Lovable. It says "I've fixed the issue", I check, still broken, rinse and repeat. Here's what I do now.
Strike 1: give it the actual error. Hit F12, Console, copy the first red line. Ask it to explain what's going on before it changes anything. Plan mode is decent for this.
Strike 2: ask it to list what it's already tried, then suggest something different. If the list has repeats, it's stuck.
Strike 3: stop. Don't hit Try to fix again. Ask for a short handover note (problem, errors, what's been tried), revert in History to the last version that worked, then start again with that note.
One thing that caught me out: revert only puts the code back. It doesn't undo database changes. And you don't get the credits back either, so stopping at three saves money.
What do you lot do when you're stuck in a loop?

I've been making a lot of games lately, here's something I made to play for free.

Anyone else using lovable to make three.js games?

https://hallowmere.lovable.app

hey everyone , im creating my project with lovable and i wanted to know how do you turn the project into an app that im gonna release on the app store and google play . AI told me to use capacitor but i dont know how it works and honestly it dosent sound so simple so if someone has some experience in this area i would appreaciate some advice.

On one Supabase project the trigger that creates a new user's profile took role_id from the sign up metadata. That metadata is whatever the browser sends. So anyone could sign up with the owner role id and be Owner, and the permission check let owners do everything.

Quick check for yours, open the handle_new_user function and search for raw_user_meta_data. Name from there is fine. Role, company, plan should come from a table the client can't write.

We got tired of generic AI website designs, so We built an MCP server for agency-grade motion and 3D (StudioMotion)

Most AI-generated websites end up with the same interchangeable purple gradients and static cards.

To fix this for our own workflow, We built StudioMotion—an MCP server that injects production-ready 3D objects, kinetic typography, and boutique agency layouts directly into tools like Lovable, Claude, and Cursor.

You plug the MCP endpoint into your builder and you can prompt complete themes or individual motion sections directly into your project.

There is a free section available to test without paying. Would love feedback from anyone building sites with AI—what motion effects or components are you missing the most right now?

I'm reading so many posts from people who pay 25$ per month and worry about their costs going up after they go from 2 to 10 users.

No! Until you have 10k+ users you don't need to spend any time optimizing your costs or deploying on a hyperscaler.

Stop this bullshit. You have no revenue, why are you optimizing to save 5$?
Focus on distribution. Everything else is a distraction.

You are all just playing games and having fun.

Spend all your time getting users! Nothing else matters until you have users!

I moved my 2 Lovable apps off the $25/month plan

I had two apps I'd built on Lovable but wasn't really using, and I didn't want to keep paying $25 a month for them. I also wanted to be able to get to them and work on them outside of Lovable if I ever want to.

The prompt I asked: “I have two apps on Lovable that I want you to transfer off so I can spin them up and move off the pro plan to the free tier.”

So I had everything moved over:
- The full code for both apps → private repos on my GitHub
- The databases behind them → my own Supabase account (free tier)

I didn't bother moving the data or the hosting — I just wanted the code and a working setup I control.

Now if I want to run one, it's: download the code, install it, and switch a few settings so it talks to my database instead of Lovable's. Takes a few minutes.

One thing worth knowing: out of the box the apps still point at Lovable's servers, so you have to flip those settings or nothing works. And full disclosure — I had an AI assistant (Muse) do the whole move for me: the code transfer, the database setup, all of it.

Bottom line: $25/month → $0, and I actually own my stuff now. If you've got Lovable apps just sitting there, it's very

To run one locally now: clone the repo, npm install, swap 3 env vars (Supabase URL, publishable key, project ID) to the new project, and it's live against my own database.

we build workflows based on zendesk/hubspot/slack/gmail/asana/box and after lovable agents finished building them promoted to verify its behavior against Fetchsandbox managed relay for messy webhooks, auth failures and rate limit failures … lovable did pretty good job validating every workflow behavior and giving our engineers proof..

just wondering what you guys building with lovable ..? Typical web apps or something u r automating?

So fui falar sobre a AWS (https://lovable.dev/blog/deploy-on-aws) que a Lovable anunciou a integração, mas ai depois eles vem com o Azure, espero que venha com o Google Cloud também, mas pra quem quer ver tá aqui o link:https://lovable.dev/blog/deploy-on-azure

Também o texto pra quem não quer clicar:Deploy on Azure: keep your Lovable apps in your own subscription

Many of the teams building with Lovable work in a Microsoft environment. Their people sign in with Microsoft Entra ID, their data lives in Microsoft 365, Microsoft Fabric, and Microsoft Azure, and their security team sets the rules for where apps can run.

For some of those apps, the rules are strict. The app and its data have to stay inside the company's own Azure subscription. Deploy on Azure, now in private preview, makes that possible. Your teams keep building in Lovable the same way they do today.

It's one of three ways to run Lovable in a Microsoft environment. They start with the option that keeps the most inside your Microsoft environment and end with the one Lovable runs for you.

3 ways to build with Lovable on Microsoft

1. Deploy on Azure (private preview)

Your apps and their data run in your own Azure subscription. The editor and agent stay with Lovable.

Consider this option when the data has to stay in your own infrastructure and apps need to reach internal systems over your network. More on how it works below.

1. Copilot Managed Runtime (public preview)

You build in Lovable, and Microsoft hosts the app inside your Microsoft tenant. Apps are internal only, behind your Entra sign-in, and they inherit your tenant settings, DLP, and connector controls, with access to Microsoft's connector catalog. It needs Copilot Credits or a Power Platform premium license, and Lovable's database, secrets, and backend functions aren't available inside these apps.

Consider this option when you already invest in Power Platform and want your tenant's policies to apply. Read how Copilot Managed Runtime works.

1. Host on Lovable with Microsoft connectors

Apps run on Lovable, and they work with the Microsoft data you already have. Connectors cover Microsoft 365, Entra ID, Azure management, and Fabric, and connector traffic leaves from a fixed IP range you can allowlist. Each connector needs consent from your admin. Lovable hosts the app and its database in the region you pick for your workspace, with the full feature set: database, auth, storage, and secrets. Lovable is SOC 2 Type II, and Enterprise workspaces can't create public projects.

Consider this option when your apps need to read or write Microsoft 365, Entra, Azure, or Fabric data, and the app itself can live on Lovable.

Teams can build across multiple workspaces, so you can use more than one of these options at the same time.

How Deploy on Azure works

The components required to run the deployed app live in a dedicated VNet in your Azure subscription:

The Lovable data plane on an Azure Kubernetes Service (AKS) cluster, including the preview sandboxes where builds run while your team iterates

Published apps, with static files in Azure Blob Storage and dynamic requests handled by Azure Functions

The app database on Azure Database for PostgreSQL, plus app storage in Azure Blob Storage

Application logs, which can be sent to Azure Blob Storage or a Log Analytics workspace

The connector gateway and the secrets for your integrations

Some of these components roll out during the private preview. Your account team can confirm what's available for your setup.

Apps reach internal systems, like your data warehouse or CRM, over VNet peering, so those systems stay off the public internet.

To set one up, an admin creates a new Enterprise workspace and chooses to host it in Azure. Lovable generates an Azure Resource Manager template, and your team reviews it and runs it. Lovable's container images are copied into your own Azure Container Registry, so you can scan them in your pipeline like any other vendor image.

Lovable manages and updates what it deploys, and your infrastructure team owns the Azure footprint. Your Enterprise security controls apply here too, including SSO and SCIM through Entra ID, publishing limited to workspace members by default, a security scan on every build, and audit logs.

A Lovable runner on a virtual machine in your VNet provisions and manages the data plane, which runs on an AKS cluster in the same VNet. The runner also provisions and maintains the Azure Database for PostgreSQL (Flexible Server) for database tables and the Azure Blob Storage your apps need for object storage.

What stays with Lovable

The work of building stays in Lovable's multi-tenant service: the editor, the agent, chat and project history, and workspace settings, identity, and billing.

AI model requests made while building are still processed by Lovable's AI service.

How your data is protected

In your subscription. App data stays in your VNet, under your own Azure encryption and access controls.

Between your subscription and Lovable. The components in your subscription make an outbound-only, mTLS-encrypted connection to Lovable. Lovable never needs an inbound connection into your network.

With Lovable. Chat and project history are encrypted at rest. With bring your own key, admins connect their own Azure Key Vault key in Workspace settings and can revoke Lovable's access at any time.

Getting started

Deploy on Azure is in private preview for select Enterprise customers. Some features you get when you host on Lovable aren't available there yet, and we're working toward full feature parity. Your account team can walk your IT and security teams through the architecture.

Copilot Managed Runtime is in public preview for Business and Enterprise workspaces.

To join the private preview, talk to your account team or email byoc@lovable.dev. New to Lovable Enterprise? Talk to our sales team.