Google Play

What it takes to list your app on the Play Store, which parts Mistflow does, and which parts are yours.

Direct installs cover testers and small audiences. Reaching the general public on Android means a Play Store listing.

What is yours and what is ours

	Who
A Google Play developer account, one-off fee, identity verification	You
The app itself, built and signed	Mistflow
Store listing: title, description, screenshots, category	You
Privacy policy, data safety form, content rating	You
Uploading the build and submitting for review	You
Responding to review feedback	You, with changes built in Mistflow

Mistflow does not submit to Google Play on your behalf. It produces the app; the account and the listing are yours.

If you have not already, upload a release keystore in the project's App tab. Play requires a consistently signed app, and losing the key means losing the ability to update the listing. See Build and share an Android app.

Create a Google Play developer account

Sign up at the Play Console. There is a one-time fee and an identity verification step that can take a few days. Start it before you need it.

Get the listing material ready

Google asks for more than the app:

Title and short description
Full description
Screenshots on several device sizes
A feature graphic and an icon
A privacy policy at a public URL
The data safety form, which asks what data you collect and why
A content rating questionnaire

The data safety form is the one people get wrong. Answer it against what your app actually does: accounts mean you collect email, uploads mean you collect photos, and so on.

Build and upload

Build the Android app in Mistflow, download it, and upload it in the Play Console.

Note that Play wants an app bundle (AAB) for new listings, while the build here is an APK that installs directly. If Play refuses the file, that is why. Ask in the build chat and this can be looked at for your project.

Submit and wait

Review takes anywhere from hours to about a week for a first submission. Later updates are usually faster.

Common rejection reasons

Reason	Fix
Data safety form does not match app behaviour	Correct the form to match what the app collects
Missing or unreachable privacy policy	Publish one at a public URL and link it
Screenshots that do not show the actual app	Take fresh ones from a real device
Broken sign-in during review	Give reviewers test credentials in the review notes
Paid digital content outside Play billing	See Payments

The sign-in one is worth planning for. Reviewers get a fresh account and no context. If your app needs an account, provide working test credentials in the review notes.

After you are live

Updates to a Play listing follow the same rule as anywhere else: interface and logic changes can reach installed apps directly, while anything that changes what the app is made of needs a new build submitted through Play. See Shipping updates.