What goes into the app, and why each part matters for Google Play

Identity

Package name

The reverse-domain identifier (com.yourbrand.app) that Google Play uses as the app's permanent ID. It cannot be changed after the first upload — a different package name is a different app with a new listing and zero installs. The builder proposes one from your domain; edit it once, carefully, and never again. Avoid trademarks you don't own; com.google.anything or a competitor's brand in the package name is grounds for rejection under the impersonation policy.

App name and version

The launcher label (keep it under 12 characters or it truncates) and the version name shown to users. The version code — the integer Play compares — increments automatically on each build so you can always upload a newer bundle.

Icon

One upload becomes an adaptive icon (foreground layer plus background colour, so every launcher shape looks right), the legacy PNG set for older devices, and the 512×512 hi-res icon your listing needs. The icon resizer lets you check how your artwork survives circular and squircle masks before you build. Alternatively, generate a lettermark icon from one or two characters and a shape.

First impression

Splash screen

Background colour, optional logo, logo position and app-name colour. Shown while the first page loads. Match the site's colours so the transition is invisible. Android 12+ renders a system splash first; the builder keeps them consistent so users don't see two different screens flash by.

App bar and menu colours

If you enable the native top bar or side menu, these set their colours. Pull them from your logo with the palette extractor; the same values belong in the status bar.

Behaviour — the part reviewers notice

Native navigation, pull to refresh, exit confirmation

A menu button with your chosen label, pull-to-refresh, and a "leave the app?" confirmation on back from the first screen. Individually small; together they are what distinguishes an app from a browser tab in a reviewer's eyes, and they are the cheapest way to satisfy the minimum-functionality policy.

Offline screen

When the device has no connection, the app shows a branded screen with a retry button instead of the WebView's raw error. Reviewers test with the network off; a raw error page is a "broken functionality" finding.

Orientation and screen mode

Lock to portrait, landscape or allow both; choose normal, full-screen or immersive. Lock only what your site's layout genuinely supports — a landscape-locked app showing a portrait-only page will be flagged.

External links

Choose whether links to other domains open inside the app or in the system browser. For a shop or publication, opening payment providers and social links externally is the expected behaviour and avoids trapping users.

Downloads

Enable if your site serves files (PDF menus, invoices, media). The app then routes downloads to the system download manager with the correct permissions declared — undeclared download behaviour is a common pre-launch report warning.

PIN code

An optional 4–6 digit lock screen for internal or kiosk-style apps. Not for public Play listings unless the listing explains it — a reviewer who hits a PIN screen with no way past will reject the app; provide the code in the review notes if you use this.

Engagement and revenue

Push notifications (OneSignal)

Enter a OneSignal App ID and the app registers for push and requests notification permission the correct way on Android 13+ (a runtime prompt, not on first launch). Push is also the single strongest evidence of app functionality beyond a browser. Declare the device identifier OneSignal uses in the Data safety form.

AdMob

Enter your AdMob publisher ID and banner unit ID; pick placement (top or bottom). Two rules that get apps rejected or accounts limited: do not run AdMob banners on screens where your website already shows web ads (stacking networks is prohibited), and never place a banner where it can be tapped accidentally by normal navigation. If your site is AdSense-funded, choose one network for the app. The builder's rewarded and interstitial behaviours respect Google's user-choice requirements.

Contact and social links, About text

Populate the native About screen and side menu with your email, phone, social profiles and a description. Reviewers use the contact details to verify the developer matches the brand; make them real.

Tawk.to chat

Paste your widget code to embed live chat. Declare it in Data safety (name and message content are collected by Tawk).

Compliance fields

Privacy policy URL

Required by Play for every app; the builder puts it in the app's About screen too. It must be a live page on your domain that describes what the site and app collect. The privacy policy guide has a structure that passes.

Output format

The APK is free. The AAB Google Play requires is part of the APK + AAB bundle — US$5 one-time per build (Dodo Payments; both files download instantly and are emailed to you). Upload the AAB to Play; use the APK for your own devices and testers outside Play.

Email backup

Optionally email yourself the generated files. Useful because the build happens in your browser and there is no account to log back into; the files are sent once and not retained.