0Pricing
React Native Academy · Leçon

Configurer la fiche dans la Play Console

Créez l'application dans Google Play Console, renseignez les détails de la fiche, notamment la description courte, la description complète et le visuel promotionnel, puis téléversez l'AAB signé.

Configurer la fiche dans la Play Console est une leçon React Native Academy gratuite sur CoddyKit. Ceci est la leçon 2 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage React Native Academy, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours React Native Academy comprend 4 leçons au total.

Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.

Google Play Console Overview

Google Play Console (play.google.com/console) is where you manage your Android app's entire lifecycle: from creating the app record to publishing updates, viewing crash analytics, managing in-app products, and tracking installation stats. A one-time developer registration fee of $25 gives you access to publish unlimited apps. The Play Console is more automated and less manual than App Store Connect, with fewer metadata restrictions.

Creating the App in Play Console

In Play Console click Create app. You provide: the app name (up to 50 characters), the default language, whether it is an app or game, and whether it is free or paid (you cannot change free-to-paid later without creating a new listing). You also confirm compliance with Google Play Developer policies and US export laws. The app record is created immediately — no submission needed yet.

// App creation fields:
// App name:      My Awesome App   (up to 50 chars)
// Default language: English (United States)
// App or game:   App
// Free or paid:  Free (can change to paid later if free)
//                Paid (CANNOT change to free later)

// Developer Program Policies:
// Confirm: App meets the Developer Program Policies
// US export laws: Confirm compliance
// Play Console Developer Distribution Agreement: Accept

Main Store Listing

The Main store listing is what users see when they find your app. It requires: an App name (30 chars), a Short description (80 chars — shown in search results), a Full description (4000 chars — shown on the app detail page), screenshots, a feature graphic, and optionally a promo video. The short description is your most important text for Play Store search optimization because it appears in search results without truncation.

// Main store listing field limits:

// App name: 30 characters
// -> 'Recipe Planner: Meal Prep'

// Short description: 80 characters
// -> 'Plan meals, build grocery lists, and prep healthy food all week.'

// Full description: 4000 characters
// -> First paragraph is most important (shown before More)
// -> Use short paragraphs and bullet points
// -> Mention key features in first 167 chars
//    (above the fold on most devices)

Required Screenshots and Graphics

Google Play requires at least 2 screenshots (maximum 8) for phone. If your app supports tablets, add tablet screenshots too. Screenshots can be 16:9 or 9:16 (portrait) and must be PNG or JPEG, minimum 320px on any side, maximum 3840px. The feature graphic (1024 x 500px) is the banner image shown at the top of your listing and in featured sections — it should convey your brand and value proposition at a glance.

// Screenshot requirements for Phone:
// Min: 2 screenshots (max: 8)
// Format: PNG or JPEG
// Aspect ratio: 16:9 or 9:16
// Min size: 320px on shortest side
// Max size: 3840px on longest side
// Recommended: 1080 x 1920px (portrait phone)

// Feature Graphic (required):
// Size: 1024 x 500px
// Format: PNG or JPEG (no transparency)

// Icon:
// 512 x 512px PNG with transparency OK

Uploading the First AAB

Go to Testing > Internal testing > Create new release to upload your first build. Drag your .aab file into the upload area. Google processes the bundle (this takes 2–5 minutes). After processing, you see the app details extracted from the manifest (package name, version code, version name). Add release notes describing what changed, then save and roll out to internal testing.

// Upload flow:
// 1. Play Console > Testing > Internal testing
// 2. Click 'Create new release'
// 3. Drag-drop your .aab file
// 4. Wait for processing...
// 5. Enter release notes:
//    'Initial release for internal testing.'
// 6. Click 'Save'
// 7. Click 'Review release'
// 8. Click 'Start rollout to internal testing'

// Or use EAS Submit:
eas submit --platform android --latest

Localized Store Listings

Play Console lets you localize the store listing into multiple languages. Add translations of the App Name, Short Description, Full Description, and screenshots for each locale. Unlike iOS, Play Console also supports custom store listings for different countries — you can show a different listing to users in Germany versus the US, including different feature graphics and promo videos tailored to each market.

// Localization in Play Console:
// Main store listing > Translations
// > Add language: de (German), fr (French), ja (Japanese)

// For each language, fill in:
// - App name (30 chars)
// - Short description (80 chars)
// - Full description (4000 chars)
// - Upload language-appropriate screenshots

// Custom store listing (per country):
// Main store listing > Manage custom store listings
// > Add countries > Create listing for that country

Category and Tags

Assign your app to the correct category (e.g., Productivity, Health & Fitness, Games > Casual). Apps are ranked within their category for category-based browsing. Add tags (up to 5) that describe your app's content and functionality — these help Google's algorithm match your app to relevant searches. Tags are predefined lists, not free-form text. Choosing accurate tags also affects featured app opportunities.

// App category selection:
// Store presence > Main store listing > App details

// Category examples:
// Education
// Finance
// Health & Fitness
// Lifestyle
// Productivity
// Tools
// Travel & Local
// Games > Puzzle
// Games > Casual

// Tags (up to 5):
// meal planning, grocery list, nutrition tracker,
// recipe organizer, diet planner

Contact Details and Privacy Policy

Under App content, fill in contact information: a support email address, a support website URL, and optionally a phone number. You must also provide a Privacy Policy URL. Play now requires a privacy policy for all apps. The privacy policy page must be live and accessible — Google spot-checks it. If your app targets children (under 13), you must also complete the Families Policy section and your privacy policy must be especially clear about data practices.

// App content > Contact details
// Email: support@yourapp.com (required)
// Website: https://yourapp.com/support (required)
// Phone: Optional

// App content > Privacy policy
// URL: https://yourapp.com/privacy
// Must be:
// - Publicly accessible (not behind login)
// - Specific to your app
// - Describe data collection and usage
// - Available in languages the app is published in

// Free privacy policy generators:
// app-privacy-policy-generator.firebaseapp.com

Pricing and Distribution Countries

Under Monetization, set your pricing (free or a price tier). If the app is free, you can still offer in-app purchases. Under Distribution, choose which countries to publish to. You can publish to all countries or specific regions. Restricting to certain countries is useful for staged launches or compliance with local laws (e.g., some financial apps cannot launch in certain jurisdictions without regulatory approval).

// Pricing:
// Free: No charge to install
// Paid: Set price per region
//   (Google manages currency conversions automatically)

// Distribution:
// All countries and regions: recommended for general apps

// Or select specific countries:
// United States, Canada, United Kingdom, Germany,
// France, Japan, Australia, Brazil...

// Device compatibility:
// Exclude specific devices or Android versions if needed:
// Dashboard > Android vitals > Device exclusions

Play Console Dashboard and Analytics

Once your app is live, Play Console provides rich analytics: Acquire shows install funnel and store listing performance, Financial shows revenue and subscriptions, Android vitals shows crash rates and ANRs (Application Not Responding), and Ratings and reviews lets you respond to user feedback. Monitor Android vitals especially — Google can reduce your app's visibility in search results if your crash rate exceeds the benchmark for your category.

// Key Play Console sections after launch:

// Dashboard > Android vitals
//   Crash rate: < 1.09% is good (Play benchmark)
//   ANR rate: < 0.47% is good
//   If above thresholds: badge of 'poor experience' shown

// Grow > Store performance
//   Store listing conversion rate
//   Search query impressions
//   Install sources breakdown

// User acquisition > Acquisition reports
//   UTM campaign tracking
//   Organic vs paid installs

Release Track Progression

Play Console has four release tracks you progress through: Internal testing (up to 100 testers, instant delivery), Closed testing (alpha, specific invite list), Open testing (anyone can join), and Production (all users in selected countries). Each promotion requires you to create a new release in that track — the same AAB is used. Google review happens when you promote to production for the first time.

// Track progression:
// Internal testing -> Closed testing (alpha)
// Closed testing   -> Open testing (beta, anyone)
// Open testing     -> Production (all users)

// To promote from internal to closed:
// Testing > Internal testing > Promote release
// > Closed testing > Select build > Roll out

// First production release:
// Goes through Google's automated + manual review
// Usually approved within 3 days for first release

Quick Check

Test your understanding of React Native Mobile Development concepts from this lesson.

Lesson Recap

In this lesson you learned: how to create an app record in Play Console and fill in the required store listing fields, how to upload the signed AAB to internal testing and progress through release tracks, and how to localize the listing and configure distribution countries. You also saw how Android vitals affect your app's search visibility. Next up we cover content ratings, policies, and privacy for the Play Store.

Questions Fréquemment Posées

La leçon « Configurer la fiche dans la Play Console » est-elle gratuite ?

Oui — le texte complet de « Configurer la fiche dans la Play Console » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours React Native Academy, passe à CoddyKit PRO. Le cours React Native Academy comprend 4 leçons au total.

Qu'est-ce que j'apprendrai dans « Configurer la fiche dans la Play Console » ?

Créez l'application dans Google Play Console, renseignez les détails de la fiche, notamment la description courte, la description complète et le visuel promotionnel, puis téléversez l'AAB signé. Tu pratiques React Native Academy avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.

Dois-je avoir de l'expérience pour commencer React Native Academy ?

Aucune expérience préalable n'est requise. React Native Academy sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 2 sur 4.

Combien de temps prend la leçon « Configurer la fiche dans la Play Console » ?

La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.

Peux-tu écrire et exécuter du code dans cette leçon React Native Academy ?

Oui. Chaque leçon React Native Academy inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.

Toutes les leçons de ce cours

  1. Créer un keystore et signer l'AAB
  2. Configurer la fiche dans la Play Console
  3. Classification du contenu, règles et confidentialité
  4. Tests internes, déploiement progressif et production
← Retour à React Native Academy