Store Submission Guide

AppForge is designed with Apple App Store and Google Play requirements in mind — but final approval is always determined by the store review process. You are responsible for your website's content, your privacy policy, store metadata and legal compliance, and you must own (or have permission to publish) the website.

Before you submit — use the Compliance page

Admin → Compliance runs a live checklist against your real configuration and links you straight to anything that needs fixing. Get it green first.

Make it more than a website

The most common rejection for website-based apps (Apple guideline 4.2, Google's minimum-functionality policy) is "could just be a mobile website". AppForge gives you real native functionality — use it:

  • Native navigation (bottom bar / drawer) instead of relying on the site's menu
  • Push notifications with real campaigns
  • The native settings page, notification inbox, downloads, offline handling
  • Biometric app lock where it makes sense

Apps that add genuine value beyond the browser pass review far more often.

Google Play checklist

  1. Play Console account ($25 one-time).
  2. Upload the .aab (see android-build.md).
  3. Store listing: title, descriptions, screenshots (min 2), feature graphic 1024×500, icon 512×512.
  4. Privacy policy URL — same one as in your admin panel.
  5. Data safety form — declare honestly: the app talks to your own backend (configuration, push tokens, anonymous counters) and to Firebase if enabled.
  6. Content rating questionnaire, target audience, App content declarations.

App Store checklist

  1. App Store Connect + Developer Program.
  2. Upload the build (see ios-build.md).
  3. Listing: name (30 chars), subtitle, screenshots for required device sizes, description, keywords.
  4. Privacy "nutrition label" — mirror the Data safety answers.
  5. App Review notes: if your website requires login, provide a working demo account — reviews are rejected without one.
  6. Honest usage descriptions for every permission (pre-filled from your admin).

After approval

  1. Paste the live store URLs into Admin → Store Settings.
  2. For every future release: bump the version, rebuild, upload to the store, and publish the version on Store Settings so existing users get the update prompt (use force update only for critical/breaking releases).

If you get rejected

Read the reviewer's message carefully — it cites the exact guideline. The most frequent fixes: add a demo account, improve the privacy policy, strengthen native functionality, or correct permission texts. Fix, rebuild, resubmit; rejections are a normal part of the process.

Previous Troubleshooting Next FAQ