Store app (Android)

What it isCopy Anchor Link

The store app wizard turns your published online store into your own Android app. The app is published under your own Google Play developer account, with your name or your company as the developer. Brivio builds the app file and signs it with your upload key; it never publishes branded apps under its own account.

Open it from Commerce → Sites & stores → Mobile app on a store card, or from the store settings.

Before you startCopy Anchor Link

• A published store. The app opens your public store, so the build starts only once the store is published.
• A Google Play developer account, either:
  • Organization — a company account. Google requires a D-U-N-S number (9 digits, issued free of charge by Dun & Bradstreet).
  • Personal — an account in your own name. Personal accounts created after 13 November 2023 must run a closed test with at least 12 testers for 14 consecutive days before the app can go to production.
• An upload key (a .jks, .keystore or .p12 file), created once with Android Studio or keytool. Keep a copy of it.

The five stepsCopy Anchor Link

1. Developer account — choose organization or personal. For an organization enter the D-U-N-S number; for a personal account confirm the closed-testing requirement.
2. App identity — app name (up to 45 characters), short name (up to 12, shown under the icon), package name (for example ro.yourcompany.store; permanent after the first upload and it must not start with ro.brivio.), main colour and an optional https:// icon. A preview shows how the icon looks. The draft is saved when you leave this step.
3. Data safety — the answers for the Data safety form in your Play Console, generated from what the app actually does. Copy them with one click.
4. Signing key — upload your upload keystore, its password, the key alias and the key password. You confirm your identity with a second factor first.
5. Build — press Build the app. The page refreshes on its own while the build runs; when it is ready, download the AAB file.

The upload key, and why it is stored sealedCopy Anchor Link

The key you upload is the upload key of your own Play app, not the app signing key: Google Play App Signing keeps the real app key, and the upload key only proves that a release comes from you. Brivio stores it sealed (encrypted at rest), uses it only to sign your builds, and never shows it again — not even to you. Uploading or replacing it always requires a second-factor confirmation. If you replace the upload key in your Play Console, upload the new one here.

Uploading the AAB to Google PlayCopy Anchor Link

1. Open Google Play Console and create the app, with the same package name.
2. Go to Testing (closed testing for new personal accounts) or Production and create a new release.
3. Upload the downloaded AAB file and accept Play App Signing.
4. Fill in the store listing and the Data safety form (step 3), then send the release for review.

UpdatesCopy Anchor Link

Changes to your products, prices and pages appear in the app straight away, because the app opens your live store — no new build is needed. Build again only when you change the app identity (name, colour, icon) or when you want a new version in Google Play; upload the new AAB as a new release in your Play Console.