8.8 KiB

Raw Blame History

Closer — Google Play Store Assets Checklist

Checklist of assets, metadata, and compliance items needed for a Google Play Store submission. Targeting the private MVP / internal launch phase.

1. Store Listing Metadata

1.1 App name

App name finalized: Closer.
App name matches android:label in AndroidManifest.xml (currently @string/app_name).
App name is not trademark-conflicting in target categories/territories.

1.2 Short description

Short description <= 80 characters.
Communicates core value proposition for couples.

Recommended short description:

Private daily questions and gentle connection rituals for couples.

1.3 Full description

Full description drafted and reviewed.
Mentions key features: daily questions, question packs, spin wheel, date planning, bucket list, answer reveal.
Includes value/privacy angle (answers stay private, built for two people).
No misleading claims or guarantees about relationships.

Draft full description:

Closer is a private space for two people who want more intentional conversations.

Answer one daily question, explore deeper question packs, spin a shared prompt wheel, plan date ideas, save bucket-list moments, and reveal answers when you are both ready. Closer is built for quiet connection, not public posting or pressure.

What you can do:

Answer daily prompts and save private reflections.
Reveal answers intentionally when you want to talk together.
Explore question packs for trust, gratitude, home life, conflict repair, intimacy, money, and more.
Use playful connection games like the spin wheel and this-or-that prompts.
Plan dates and keep shared ideas in one calm place.

Closer is not therapy and does not promise to fix a relationship. It gives couples a steady, private rhythm for checking in, listening better, and making time for each other.

1.4 Keywords / tags

Primary category selected (e.g., Lifestyle, Dating, Health & Fitness).
Relevant tags selected in Play Console.

2. Graphic Assets

2.1 App icon

Launcher icon is supplied as an adaptive icon for the app's Android 8+ (minSdk 26) target.
Adaptive icon foreground + background layers present (ic_launcher_foreground, ic_launcher_background).
Android 13+ monochrome layer provided for themed icons.
Icon tested on light and dark wallpapers.
Round icon variant provided (ic_launcher_round).
High-res store icon source is aligned with the Android adaptive mark and palette.

2.2 Feature graphic

Feature graphic 1024 × 500 px (PNG, no alpha): docs/store/feature-graphic-1024x500.png.
Brand name and key tagline legible at small sizes.
Complies with Google Play policy (no device images, no price/calls-to-action like "Buy now").
Leads with privacy + connection and matches in-app purple/pink visual language.

2.3 Screenshots

Phone screenshots: 9 current captures at 1080 × 2400 in docs/screenshots/.
- Current screens:
  - 01-onboarding.png — onboarding / welcome
  - 02-login.png — login
  - 03-home.png — home dashboard
  - 04-daily-question.png — daily question + answer input
  - 05-question-packs.png — question pack library
  - 06-answer-history.png — answer history
  - 07-settings.png — settings
  - 08-play.png — Play hub / spin wheel entry
  - 09-date-builder.png — date planning
- Play Console supports up to 8 phone screenshots per device type. For a store listing, prefer the product screens and omit login unless auth trust is part of the experiment.
Screenshot dimensions are 1080 × 2400 (9:20).
7-inch tablet screenshots if targeting tablets (optional for MVP).
10-inch tablet screenshots if targeting tablets (optional for MVP).
Screenshots do not contain placeholder or hardcoded test data.
Status bar cleaned (no low-battery warnings, demo time 9:41, etc.).

Promo video optional but recommended; if used, YouTube URL added in Play Console.
Video shows real in-app experience, no prohibited content.

2.5 Other assets

512 × 512 px high-res icon ready for Play Console: docs/store/app-icon-512.png.
16:9 promo graphic if running store experiments.

3. Legal URLs

Privacy policy URL defined and reachable: currently https://closer.app/privacy.
Terms of service URL defined and reachable: currently https://closer.app/terms.
Subscription terms URL defined and reachable: currently https://closer.app/subscription-terms.
Action needed: Support URL currently points to https://couplesconnect.app/support in ExternalLinks.kt; migrate to closer.app domain and update store listing support/contact email.
All legal pages load over HTTPS.
Privacy policy accurately describes data collected (answers, FCM tokens, purchase data, couple pairing info).

4. Content Rating

4.1 Rating questionnaire

Content rating questionnaire completed in Play Console.
App declared as targeting couples / adults.
No user-generated content that requires additional moderation declared.
Question content reviewed for mature themes; mark appropriately if intimacy questions are explicit.

4.2 Age-based considerations

Determine if app should be rated Teen or Mature 17+ based on question language.
Ensure ads (none currently) do not affect rating.
In-app purchase disclosure accurate.

5. App Signing Key Checklist

5.1 Play App Signing

Decision made: Play App Signing enabled (recommended) or opt-out (requires justification).
If using Play App Signing, upload key generated separately from signing key.
Upload signing key backed up securely; loss blocks future updates.
App signing key (held by Google) fingerprint recorded.

5.2 Key requirements

Signing key algorithm: RSA, key size >= 2048 bits.
Key validity period covers beyond 22 October 2033 (Google Play requirement).
Keystore file, passwords, and alias stored in team password manager / HSM.
CI pipeline injects signing credentials via environment variables, not hardcoded.

5.3 Verification

Signed AAB/APK uploads successfully to Play Console.
Play Console reports signature valid.
Same signing key used for all future updates.

6. In-App Products / Subscriptions

Subscription products created in Play Console matching RevenueCat product IDs.
Product titles/descriptions match paywall copy.
Base plans and offers configured (free trial if offered).
Subscription terms URL linked.
RevenueCat dashboard product IDs match Play Console SKUs.
Test licensing enabled for internal testers.

7. Compliance & Policy

App complies with Google Play Families Policy (if applicable).
No deceptive behavior, malware, or abuse of permissions.
Permissions declared (INTERNET, POST_NOTIFICATIONS) are necessary and explained if requested.
Data safety form completed and consistent with privacy policy.
Accessibility considerations documented; minimum touch targets and labels reviewed.
No restricted content in screenshots or description.

8. Pre-Launch Checklist

Internal testing track tested end-to-end with closed testers.
Pre-launch report reviewed for crashes, ANRs, security, and performance.
Store listing content spell-checked and approved.
Release notes / "What's new" text prepared for first submission.
Rollout plan: staged release percentage and rollback plan defined.
Monitoring: Crashlytics, Analytics, and RevenueCat dashboards ready.

9. Asset Inventory

Asset	Spec	Status
App name	≤ 30 chars displayed	Draft
Short description	≤ 80 chars	Draft
Full description	≤ 4,000 chars	Draft
Launcher icon	Adaptive + round + monochrome	Ready
High-res store icon	512 × 512 PNG	Ready
Feature graphic	1024 × 500 PNG, no alpha	Ready
Phone screenshots	9 images, 1080 × 2400	Ready; final demo-data review pending
Tablet screenshots	Optional	Ready/Not ready
Promo video	Optional	Ready/Not ready
Privacy policy URL	HTTPS	Ready/Not ready
Terms URL	HTTPS	Ready/Not ready
Subscription terms URL	HTTPS	Ready/Not ready
Support URL	HTTPS	Needs migration

Source SVGs and usage guidance live in docs/store/sources/ and docs/brand/visual-identity.md. Re-export PNGs after any source change; do not edit the raster deliverables independently.

10. Sign-off

Role	Name	Date	Notes
Product
Design
Legal / Compliance
Engineering

8.8 KiB Raw Blame History Unescape Escape