App Store Assistant

The short App Store subtitle shown under the app name.

A concise one-line pitch you may also want on the future Vibe411 Coming Soon draft.

A short product summary for your prep worksheet. If you create a private draft, this can carry into the listing.

Optional longer copy or notes you want to keep with the prep package.

Optional App Store promotional text that can be updated without a new version.

Comma-separated App Store keywords or search terms you want ready before submission.

Your planned App Store primary category.

Optional secondary App Store category if you plan to use one.

Apple treats the marketing URL as optional.

Apple expects a support URL in App Information.

Only fill this if the app is already published on the App Store.

The reverse-DNS bundle identifier used in your iOS project.

The marketing version you expect to submit, such as 1.0.0.

Version-specific release notes you want ready before creating the next build submission.

The copyright or ownership line you plan to use in App Store Connect.

Price tier, territories, phased release, preorder, or other availability notes you want ready.

Does the app require a user account before the core workflow works?

Mark this only if the code or live product clearly includes in-app purchase or subscription flows.

Useful for monetization, privacy, and age-rating prep.

Useful for both App Store prep and a later public listing draft.

Optional if you already have terms or service rules published.

Useful when the app offers tracking or privacy-choice controls and Apple expects that link.

Leave blank unless the code or SDKs clearly indicate tracking-related behavior.

Use strict answers only. If unsure, leave blank and verify manually later.

Use this only when the implementation clearly links collected data to a user identity or account.

Leave blank unless tracking use is clearly visible in the code, SDKs, or app behavior.

If the app requests or depends on location, note it here for later privacy review.

For feeds, comments, uploads, messaging, profiles, or other user-created surfaces.

Mark this when analytics, ads, auth, attribution, or other partners are clearly visible in the implementation.

Summarize what user data the app handles, what third-party services are visible in code, and what still needs manual verification.

Useful for age-rating prep if the app includes built-in browsing or broad internet access.

Useful for age-rating and policy review if the app contains gambling-like mechanics or contests with value.

Flag this when the app includes health tracking, medical content, or regulated wellness claims.

Flag this for violence, adult themes, drugs, or other sensitive material that could affect age rating.

Helpful when the app distributes music, video, books, or other licensed content.

Important when the app uses custom encryption, VPN behavior, or other export-sensitive capabilities.

Summarize anything relevant to age-rating questions, sensitive content, communication, or user interaction.

Summarize ownership, licensing, or rights restrictions for any third-party content in the app.

Summarize encryption use, restricted regions, or anything else you want ready for export-compliance questions.

Apple review contact first name, if already decided.

Apple review contact last name, if already decided.

Email address Apple reviewers can use if they get blocked.

Phone number Apple reviewers can use if they get blocked.

Helpful when the app requires login or gated access.

Test credentials, account setup steps, OTP caveats, or anything else reviewers need to get through the flow.

Anything Apple reviewers should know, such as feature gates, demo content, or special setup steps.

A concise pitch you may also want on the future Vibe411 Coming Soon draft.

Optional short store summary or Play listing description.

Optional longer copy or internal notes for the launch package.

The app or game category you plan to use in Google Play.

Any Play tags or search-facing descriptors you want ready before submission.

Useful for Play Console and for the later Vibe411 draft.

Optional support/help page if you already have one.

Useful for Google Play and can also update your creator support email.

Optional phone number for store or reviewer contact if you keep one available.

Only fill this if the app is already live on Google Play.

The Android package name used in the app project or build configuration.

The user-facing Android version name you plan to submit.

The internal Android version code if it is already known.

Release notes or what's new text you want ready for the next rollout.

Territories, device exclusions, regional caveats, or other availability notes you want ready.

Does the app need an account before the main workflow works?

Useful for pricing and monetization prep before Play Console setup.

Helpful for store, content-rating, and monetization prep.

Useful for Google Play policy prep and a later public listing draft.

Optional if you already have terms or service rules published.

Useful if the app supports account deletion and you want that link ready for Play policy questions.

Use strict answers only. Leave blank if the code does not make this clear.

If the app requests location or background location, note it clearly here.

Important to flag separately if the code shows it.

Use this only when the code, SDKs, or backend behavior clearly indicate data sharing.

Useful for the Play Data safety questionnaire when the app sends data over the network.

Useful when the app uses accounts and you need to prepare the related Play policy answers.

Flag this when users can request deletion through the app, website, or support workflow.

Summarize collected data, SDKs, analytics, authentication, and anything else you will need for Play data-safety review.

Leave blank unless the app is clearly directed at children or families.

For feeds, comments, uploads, profiles, or messaging.

Flag this for built-in browsers or broad web access that could affect content declarations.

Useful when the app includes chat, comments, profiles, or other direct interaction between users.

Flag this when the app could trigger extra Play policy declarations around news or government affiliation.

Summarize anything relevant to content-rating questions, communication, user-generated content, or sensitive themes.

Any notes about ads, news, health, finance, AI-generated content, or other special Play policy areas that still need review.

Summarize notable permissions, what uses them, and any manifest clues you want ready when filling Play questions.

Flag this if the app needs login, OTP, region whitelisting, Bluetooth devices, hardware, or another gate before reviewers see the real flow.

Useful when reviewers need login credentials or a demo account.

Test account details, OTP limitations, region restrictions, or feature gates reviewers must know.

Useful if you plan to use Google Groups for closed testing before production review.

Default Vibe411 group for Exchange users. You can still use other Google Groups at the same time.

Paste the Join on Android link from Play Console when you want testers to install from Android directly.

Optional web join link from Play Console for testers who need the browser flow.

The feedback URL or email address shown to testers inside the closed-testing settings.

Anything testers need to know, such as Google Group setup, supported devices, login requirements, or whether the app still needs more testers.

Anything the Play review flow should know, such as test accounts, feature flags, or gated functionality.