Luminax
All docs
Features · Release

Shipping to the App Store and Google Play

Icons, screenshots, store copy, signing, submission and updates — walked through, not left to you.

7 min · Updated Aug 2026

Getting an app built is the part people expect to be hard. Getting it into two stores — certificates, icon sizes, screenshot dimensions, privacy answers, review notes — is the part that quietly kills projects. Luminax treats release as a feature of the product, not homework.

The release path

  1. 1
    Name and identity

    App name, bundle identifier and version are set once and carried through every build.

  2. 2
    Icons and splash

    Generated on brand at every size both stores demand, from your palette and mark.

  3. 3
    Store screenshots

    Captured from your real running app on the required device frames, with captions you can edit.

  4. 4
    Listing copy

    Title, subtitle, description, keywords and what's-new text drafted from what your app actually does.

  5. 5
    Signing and build

    Signed release builds produced for both platforms — you connect your developer accounts, Luminax handles the mechanics.

  6. 6
    Submit and update

    Send it for review, then ship the next version as a new build without repeating any of the above.

What still needs you

Apple and Google require the accounts and the legal identity to be yours: an Apple Developer membership, a Google Play developer account, and honest answers about data use. Luminax prepares everything else, tells you exactly which answers it needs, and keeps them attached to the project.

Rejections

Paste the reviewer's message into the chat. The agent reads it, changes the app or the listing to address it, rebuilds, and resubmits — with the reason recorded in the project's history so the same note never comes back twice.

Still wondering something?

The assistant answers from these pages only.