Store Publishing Kit

This page is a publishing checklist for Ball Flip DX by ManbouRockBox. It is not shown as marketing copy inside the game loop.

Store Listing Copy

Long Description

Ball Flip DX is a fast one-touch arcade game built around clean timing and instant retries. Tap to flip gravity, collect crystals to build your combo, grab Charge cells for shields, and dodge red noise hazards as the speed rises. Short runs, clean feedback, and optional rewarded continues make each attempt easy to start and hard to put down.

Screenshot Plan

1. Start screen showing tutorial, missions, and daily challenge.
2. Early run with crystal collection and visible one-touch controls.
3. High-speed hazard moment showing red noise and shield state.
4. Result screen with score, distance, mission progress, and retry button.
5. Skin unlock or progression-focused screen after a strong run.

Required Store Assets To Produce Later

• App icon master: 1024x1024 PNG, no transparency.
• Google Play feature graphic: 1024x500 PNG/JPG.
• Phone screenshots: portrait gameplay captures.
• Optional app preview video: short run from start to result.
• Splash image: Ball Flip DX logo/orb on dark background.

Pre-Capacitor File Structure Plan

New project 6/
  index.html
  manifest.json
  sw.js
  privacy.html
  store-listing.html
  icons/
    icon.svg
    icon-192.png
    icon-512.png
    maskable-512.png
  publishing/
    screenshots/
    store-assets/
    notes.md
  package.json          (future)
  capacitor.config.json (future)
  android/              (future, generated)
  ios/                  (future, generated)

Before Native Wrapping

• Confirm app name, support email, and privacy policy URL.
• Remove placeholder contact text from privacy.html.
• Test PWA install and offline start on Android Chrome.
• Capture real screenshots from the current game, not mockups.
• Include only the rewarded continue ad in the first release; do not add banner, interstitial, analytics, cloud saves, or purchases unless privacy disclosures are updated.

Rewarded Ad Integration Plan

The Android build uses Google AdMob rewarded ads through a small native bridge. Ads must appear only after the player taps “広告を見て続行”, and the game should continue only when the rewarded-ad callback confirms that the user earned the reward. Development and internal testing use Google’s test rewarded ad unit ID.

AdMob IDs To Create Later

• Android AdMob app ID.
• iOS AdMob app ID.
• Android rewarded ad unit ID for continue_once_per_run.
• iOS rewarded ad unit ID for continue_once_per_run.

Implementation Notes

• Use test ad unit IDs during development and internal testing.
• Load rewarded ads before the result screen when possible; if loading fails, hide the continue button.
• Grant the continue reward only from the rewarded callback, not from ad open or ad close alone.
• Keep the current one-continue-per-run rule to avoid misleading or excessive ad prompts.
• Do not add banner ads, interstitial ads, app-open ads, or paid items in the first release.
• Update privacy.html, store privacy forms, and Android/iOS permission declarations before enabling real ads.

Store Review Checklist

• Explain “広告を見て続行” as an optional rewarded ad, not a required ad.
• Do not show rewarded ads before the player explicitly taps the continue button.
• Confirm the app does not imply online ranking unless a real online leaderboard exists.
• Confirm privacy policy URL is live and reachable from the store listing.
• For Google Play, complete Data safety and Ads declarations after choosing the final SDKs.
• For iOS, complete App Privacy answers and review App Tracking Transparency needs if personalized ads or cross-app tracking are used.