Lovable guide

How to get a Lovable app through Google Play's 12-tester closed test

If your Google Play developer account is a personal one created after November 13, 2023, you need a closed test with at least 12 testers opted in for 14 days in a row before you can apply for production. Google then reviews the application, usually within 7 days. Organization accounts skip the test.

Facts checked against Apple's, Google's and Lovable's own documentation.

Do you need the 12-tester closed test?

You need it if your Google Play developer account is a personal account created after November 13, 2023. Until you meet the requirement, Play Console keeps Production and Pre-registration locked for your apps.

You finish your Lovable app, open Play Console, and find the publish button behind a two-week test. It catches a lot of first-time publishers, so check your account type before you plan a launch date.

  • Personal accounts created after November 13, 2023: closed test required.
  • Personal accounts created before that date: not affected.
  • Organization accounts: not affected. They need a registered business and a D-U-N-S number.
New personal accounts run the closed test. Organization accounts go straight to production.

What counts as 12 testers for 14 days?

At least 12 testers must be opted in to your closed test when you apply, and they must have stayed opted in for the 14 days before that, without a break.

  • Opted in means the tester accepted your invite through the opt-in link, not only that you added their email.
  • A tester who opts in, leaves before day 14 and rejoins starts their 14 days again.
  • Google originally asked for 20 testers. Older posts that say 20 are out of date.

How to set up a closed test for a Lovable app

Lovable builds web apps, and Google Play needs an Android app, so the first step is a native build. We convert Lovable apps to React Native and Expo, which gives you an Android App Bundle (an .aab file) for Play and the same app for the App Store.

  1. Create the app in Play Console and fill in the store listing basics.
  2. Open Testing, then Closed testing, and create a track.
  3. Upload your App Bundle to that track and roll out the release.
  4. Add testers by email list or Google Group, choose your countries, and save. The opt-in link appears once the closed test release is published, which can take a few hours.
  5. Send the opt-in link to your testers. They accept it with their Google account, then install the app from Google Play.

Your listing, content rating and Data safety form are needed for production anyway, so fill them in now. The Lovable launch checklist lists everything else the stores ask for.

Where to find 12 testers for Google Play

Start with people who already care about your app: they stay opted in and give useful feedback, which you need for the production application.

  • Friends, family and colleagues with an Android phone.
  • Your own users: the people already using the web version of your Lovable app.
  • Your waitlist, newsletter or social followers.
  • Communities where builders swap testing, such as tester-swap groups and forums. Offer to test their app in return.

Invite 15 to 20 people, not 12. Someone always forgets to accept the invite or uninstalls on day 6, and every drop below 12 delays your application.

The closed test problems nobody warns you about

  • Testers added but not opted in. Adding an email does nothing until that person accepts the opt-in link. Check the count in Play Console, not your invite list.
  • Google Group members who never joined. Testers in a Google Group must join the group before they can opt in. Check the group lets people outside your organization join, then confirm the opted-in count in Play Console.
  • Low engagement. Google can ask you to keep testing if testers didn't use the app. Ask them to open it a few times and send you feedback.

Use the 14 days well: fix what testers report and finish your store listing, so the build you send to production is better than the one you started with.

How to apply for production access

Once 12 testers have been opted in for 14 days, apply from the Play Console dashboard. The form has three parts: your closed test, your app, and your production readiness.

  • How easy it was to recruit testers.
  • How testers engaged with the app.
  • A summary of their feedback and what you changed because of it.
  • Who the app is for and why it is ready for production.

Answer with specifics: the bugs testers found and what you fixed. Review usually takes 7 days or less. If Google asks for more testing, the usual reasons are fewer than 12 opted-in testers or too little engagement.

Can you do the closed test yourself?

Yes. The closed test is free and every step above is something you can do on your own. What it takes is 12 to 20 willing testers and two weeks of reminding them.

If you would rather not, we run it for you with vetted testers as part of getting your app on Google Play, alongside the native build and the store work. You can also skip it with an organization account if you have a registered business.

How we help

We take your Lovable app the last mile.

We convert your Lovable app to a native React Native and Expo app, run the 14-day closed test with vetted testers, prepare the listing and Data safety form, and submit to Google Play and the App Store until approved.

How we ship Lovable apps →

Common questions about Google Play's closed test

Start here

Tell us about your app. We'll handle the rest.

Share your app's link and how to reach you. We'll try out your app and come back within two business days with how we'd get it into the stores.

  • Start with just a link: no source code needed yet
  • NDA before you share code, if you want one
  • Flat fee, no add-ons mid-project
  • Approved or your money back

A project link from Lovable, Rork, Bolt or any builder, or a preview link.

We reply within two business days. No spam, ever.