Google Play Store ላይ መተግበሪያዎችን እና ጨዋታዎችን ከባዶ ለማተም የተሟላ መመሪያ: ማሸግ, ፖሊሲዎች, የተዘጋ ሙከራ እና የምርት ፈቃድ

Google Play Store Application Publishing and Application Guide (From Zero to Publication)

This guide; It explains step by step the processes of creating a modern Android application (especially .NET MAUI, MonoGame or hybrid C# projects) from scratch on the Google Play Console, packaging it, signing it, resolving any critical errors encountered, and completing the store application steps (App Creation, Privacy Policy, Login Permissions, Advertisements, IARC Age Rating, Data Security, Closed Testing and Open Publication).

---

Contents

1. Introduction and Architectural Preparation
2. Creating a New Application / Game from Scratch in Play Console (Create App)
   • A. Application Details (App Details)
   • B. Application Type, Pricing and Disclosures
3. Keystore Creation and Build/Sign Automation
4. Play Console First Bundle Installation and Critical Errors
   • Error 1: Target API Level 36 (Android 16) Required
   • Error 2: Version Code Significantly Higher Warning
5. Privacy Policy Preparation
6. [App Access / Sign-in Details (#6-app-access--sign-in-details-app-access--sign-in-details)
7. Ads Declaration
8. Content Rating (IARC Content Rating Questionnaire)
9. Target Audience and Age Group Selection (Target Audience)
10. App Content Dashboard
11. Data Safety Form
12. Legal and Regulatory Statements (Government, Financial, Health)
13. Store Settings and Contact Information (Store Settings)
14. Main Store Listing and Visual Assets (Main Store Listing)
15. Closed Testing Setup and Review
16. Advertising ID Declaration
17. Final Submission
18. Final Victory: Production Access (Open Release) Approval
19. Pre-Release Checklist (Completed)

---

1. Introduction and Architectural Preparation

When publishing a new application on the Google Play Store, Google's current security and technical policies must be followed:

• Bundle Format: Only .aab (Android App Bundle) format is accepted. APK files are not valid for store release (but may be generated for testing sideloads).
• Minimum Target SDK: Google Play now requires newly published or updated applications to target at least Android API Level 36 (Android 16).
• Secure Signing: The application must be signed with a v2/v3 schema compatible 2048-bit RSA key.

---

2. Creating a New Application / Game from Scratch in Play Console (Create App)

After logging in to the Google Play Console panel (play.google.com/console), the publishing process is started by clicking the blue "Create app" button at the top right on the main screen where all applications are listed. This form determines the app's digital ID on the console, its package name, and basic store classification.

A. Application Details

1. App Name:
   • It is the first official name that will appear to users in the store.
   • Limited to a maximum of 30 characters (Ex: YourAppName).
   • Recommendation: Avoid unnecessary keyword stuffing (keyword stuffing) or misleading/promotional words ("Best", "Free", "#1") in the title; Otherwise, it may receive rejection from Google Play review.
2. Package Name:
   • Java/Android package identifier that uniquely identifies your application globally within the Android ecosystem (Reverse domain convention, e.g. com.yourcompany.appname).
   • Maximum of 150 characters.
   • ⚠️ Critical Rule: After the application is created on this screen and the first bundle is installed, the package name can never be changed again! The ApplicationId (<ApplicationId>com.yourcompany.appname</ApplicationId>) in the `AndroidManifest.
   • Check availability (Availability Check): By pressing the button, it is instantly questioned whether the package name you specify has been registered by another developer in the Google Play ecosystem.
3. Default Language:

• The primary store listing language of the application (Ex: English (United States) – en-US).
  • Store information will be presented in this default language to users in all countries where no specific localization (translation) has been defined.

---

B. Application Type, Pricing and Disclosures

1. App or Game:
   • The basic type of the product is determined (App or Game).
   • Critical Note: This selection determines the relevant main category of the store (Applications tab or Games tab) and cannot be changed later.
2. Free or Paid:
   • Select whether the application will be available in the store for free or as a paid purchase.
   • ⚠️ Critical Irreversible Rule: According to Google Play policies, an application once published as "Free" can never be made "Paid" in the future! If you want to sell your product directly in the store, you must select Paid initially. In order to publish for free and generate income, In-App Purchase or AdMob ads should be preferred.
3. Automatic Protection:
   • Google Play adds automatic installer check (installer check) to your app's APK/AAB code. If users sideload your app from unauthorized sources outside of Google Play, they will be warned to download the original version from Google Play.
4. Declarations (Legal Declarations and Policies):
   • Developer Program Policies: It is confirmed that the application fully complies with Google Play developer and content policies.
   • US Export Laws: The Software is deemed to comply with US export laws and embargo regulations.
5. Create App:
   • After the form is approved, click the blue "Create app" button at the bottom right. The console processes the application into the system and transfers the developer to the application's main management panel (Dashboard).

---

3. Keystore Creation and Build/Sign Automation

To make the deployment process error-free and repeatable, a Deploy/ folder and automation scripts should be created in the project root.

A. Keystore Generation (1_CreateKeystore.bat)

Using the keytool in the JDK, a key valid for 25 years (10,000 days) is generated:

keytool -genkeypair -v ^
    -keystore "%KEYSTORE_PATH%" ^
    -alias %ALIAS% ^
    -keyalg RSA ^
    -keysize 2048 ^
    -validity 10000 ^
    -storepass "%PASS%" ^
    -keypass "%PASS%" ^
    -dname "CN=SirketAdi, OU=Apps, O=SirketAdi, C=TR"

Tip: Using parenthesized if (...) blocks when obtaining the password from the user with set /p in Windows batch files may cause syntax errors (: was unexpected at this time). Managing the stream with goto tags and enclosing password parameters in quotes "%PASS%" ensures stability.

B. Automatic Versioning and Signed AAB Build (2_BuildAndSign_AAB.bat)

Google Play expects a strictly increasing 'versionCode' with every update. To manage this automatically, a formula based on date and time is used:

# Yılın son hanesi + Ay + Gün + Saat + Dakika (Örn: 2026-10-06 02:42 -> 610060242)
$vc = (Get-Date).ToString('yy').Substring(1) + (Get-Date).ToString('MMddHHmm')

Compilation and signing commands:

dotnet build "Proje.Android.csproj" -c Release -f net9.0-android /p:AndroidPackageFormat=aab /p:ApplicationVersion=%VERSION_CODE% /p:ApplicationDisplayVersion=%VERSION_NAME%

jarsigner -sigalg SHA256withRSA -digestalg SHA-256 ^
    -keystore "%KEYSTORE%" ^
    -storepass "%PASS%" ^
    -keypass "%PASS%" ^
    -signedjar "%SIGNED_FILE%" ^
    "%AAB_INPUT%" ^
    %ALIAS%

When the process is completed, the folder containing the compiled file will be opened directly in Windows Explorer with the start "" "%OUTPUT%" command.

---

4. Play Console First Bundle Installation and Critical Errors

When the signed .aab file is uploaded to the Internal testing or Production channel in Google Play Console, the following screen may appear:

Error 1: Target API Level 36 (Android 16) Requirement

Error Message: "Your app currently targets API level 35 and must target at least API level 36 to ensure it is built on the latest APIs optimized for security and performance."

Solution:

This is bug blocking and cannot be released until it is resolved.

1. Explicitly define the <uses-sdk> tag in the Platforms/Android/AndroidManifest.xml file:

   <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.yourcompany.appname">
       <uses-sdk android:minSdkVersion="24" android:targetSdkVersion="36" />
       ...
   </manifest>

2. Add it to <PropertyGroup> in the project .csproj file:

   <AndroidTargetSdkVersion>36</AndroidTargetSdkVersion>

Error 2: Version Code Significantly Higher Warning

Warning Message:
"This release's version code is significantly higher than your previous version code. Over time, this will result in your app reaching the maximum limit for version codes... Learn more"

Solution:

• Google Play gives this warning when the previous version code of the project is a small number (e.g. 1 or 8) and when you switch to dynamic date format (e.g. 610 million).
• This is not a disabling error. It can be bypassed by clicking the blue Proceed anyway button just below the warning.
• Since this number will be used as the basis for subsequent uploads, the large jump warning will not appear again.

---

5. Privacy Policy Preparation

According to Google Play policies, even if your app does not collect sensitive data, a Privacy Policy link in publicly accessible, standard web page (not PDF) format with an active SSL is required.

Free Hosting on GitHub

A markdown file (blob/main/...) in the GitHub repository is directly recognized by Google as a valid web page.

Basic Headings That Should Be Included in the Policy

1. Ads (Google AdMob): Banner, interstitial and rewarded ads; Use of Android Advertising ID (AD_ID), technical device data and approximate IP location.
2. In-App Purchases & Subscriptions (Google Play Billing): Payments are made entirely within the Google infrastructure, and the developer never accesses card or billing information.
3. Analytics & Telemetry (Firebase Analytics & Crashlytics): Anonymous usage events and crash reports.
4. Consent Management (Google UMP): GDPR and KVKK compliant confirmation windows and the user's right to change their preferences through settings.
5. Legal Exclusions & Special Declarations (E.g. Games of Chance / Prediction Tools):
   • The application is definitely not a betting/game of chance platform.
   • It only offers mathematical coupon optimization and statistics support.
   • When redirecting to official dealers, the usernames and passwords of official sites are never kept, and 2FA/SMS verifications are made directly on the official institution interface.
6. Security Note: Technical links such as the developer's personal GitHub profile should not be included in the privacy policy text; Only corporate email and official website should be included.

---

6. App Access / Sign-in Details

Before Google auditors can review the app, you need to indicate whether the app contains a restricted area:

• Selection: No (No part of the application is restricted).
• Explanation: If there is no membership, user login, e-mail/password or a locked screen in the application, No should be selected. If 'Yes' is selected, Google will ask for your test user name and password.

---

7. Ads Declaration

This is the step where you declare whether ads are shown in your app:

• Selection: Yes, my app contains ads (Yes, my app contains ads).
• Explanation: If the application has the AdMob library or if ads will be opened in the future, 'Yes' must be selected. This selection activates the "Contains advertising" label on the Google Play page and ensures full compliance with the policies.

---

8. Content Rating (IARC Content Rating Questionnaire)

To determine the age limit of the application, you must fill out the IARC (International Age Rating Coalition) survey.

A. Category Selection and Email Entry

• Category: All Other App Types (All other applications that are not games, betting games or social media: Tools, utilities, calculators).
• E-mail: Contact e-mail is entered and IARC conditions are confirmed.

B. Survey Questions (Questionnaire)

Chapter 1: Violence and User Communication

• Downloaded App (Violence, Sexuality, Strong Language): No
• User Content Sharing (Audio, message, media sharing between users): No

Section 2: Content and Age Restricted Products

• Online Content (Music/Video stream or e-commerce catalogue): No
• Promotion of Age-Restricted Products (Tobacco, Alcohol, Gambling): No (Absolutely No as the application does not allow betting)
• Miscellaneous (Precise GPS location sharing): No

Chapter 3: Digital Products and Miscellaneous Features

• Digital Goods (Digital product sales): No (No if active in-store billing is not connected; if active, select Yes and get the Digital Purchases badge)
• Cash Rewards (Cash reward, gift card): No
• Web Browser (Internet browser / search engine): No
• News / Educational (News or educational product): No

When all these questions are answered 'No', the application receives the age rating suitable for the widest audience in the world (PEGI 3, ESRB Everyone).

---

9. Target Audience and Age Group Selection

When determining the target audience of your application, it is vital to accurately declare whether it is intended for children or not in terms of Google's Designed for Families (Family Policy) and COPPA regulations.

Right Choice: 18 and over only

• Why 18+ Only?
  1. Legal Compliance: Spor Toto statistics, odds and coupon analysis tools are intended for an adult audience as they are based on games of chance bulletins.
  2. Protection from Family Policy Restrictions: If under 13 or 13-17 is selected, Google requires the app's ad SDKs to be certified child-friendly, restricts telemetry, and initiates a much more severe review process.
  3. Consistency with the Privacy Policy: It is 100% consistent with the article "The App is intended for audiences aged 18 and older" in our Privacy Policy.
• Second Step (Could your app unintentionally appeal to children?):
  • This question should be answered as No (No). Since there are no cartoon characters, toy themes or children's animations in the application interface, it is not a product that will accidentally attract the attention of children.

---

10. App Content Dashboard

Google Play Console tracks the legal and content readiness of your app with a step-by-step checklist under the Policy and programs -> App content tab in the left menu.

Green check icons (✓) will appear as the privacy policy, login permissions, ads and content rating are completed. The remaining sections of the list (Data Security, Government Agencies, Financial Features, Health) must be completed in order.

---

11. Data Safety Form

It is one of the most strictly controlled areas of Google Play. You must declare what data the application and its libraries collect or share with third parties.

Question: Does your app collect or share any of the required user data types?

• Selection for First Release: No (No).
• Technical Reason: Since AdMob SDK or Firebase SDK is not yet directly integrated in the first loaded .aab package and user ID / sensitive data is not collected, the form is completed cleanly by selecting No.
• Note for Future: When AdMob or Firebase SDKs are activated and coded, you should return to this form and update the "Approximate Location", "App performance" and "Device or other identifiers (AD_ID)" items to Yes.

After checking the preview, it is saved.

---

12. Legal and Regulatory Statements

A. Government Apps

• Selection: No (The application does not represent an official government agency).

B. Financial Features

• Selection: My app doesn't provide any financial features at the bottom.
• Confirmation: In the pop-up window that opens, it is confirmed that there is no need to submit any financial licenses or documents:

C. Health Apps

• Selection: My app does not have any health features at the bottom.
• Confirmation: In the pop-up window you confirm that regional health documentation is not required:

---

13. Store Settings and Contact Information

The category in the store and the communication channels through which users can reach the developer are configured:

• App Category: Sports or Utilities / Tools.
• Tags: Relevant keywords can be selected (Ex: Sports, Utilities).
• Store Listing Contact Details:
  • Email Address: destek@sirketadi.com (Corporate support e-mail is mandatory).
  • Website: https://company.com
• External Marketing: Left checked to allow Google to promote your app on platforms outside Google Play:

---

14. Main Store Listing and Visual Assets

The storefront is the most important area that directly affects users' download decision:

A. Texts

• App Name: Maximum 30 characters (Ex: 15te15 - Spor Toto Assistant).
• Short Description: Maximum 80 characters (Ex: Formula optimization, probability calculation and smart Spor Toto coupon assistant.).
• Full Description: Detailed description including features, algorithmic advantages and legal notices.

B. Visual Size Standards

• App Icon): Exactly 512 x 512 px, 32-bit PNG, 1 MB maximum.
• Feature Graphic: Exactly 1024 x 500 px, JPG or 24-bit PNG, maximum 15 MB.
• Phone Screenshots:
  • Minimum 2, maximum 8 screenshots.
• Minimum size: 1080 px (Ex: 1080 x 2340 px).
  • Aspect ratio: 16:9 or 9:16.

C. Generative AI Content Declaration

• Even if AI-powered tools are used to create store images, Don't label assets is selected as long as photorealistic human/public faces are not produced that mislead the user.

---

15. Closed Testing Setup and Review

For newly created personal developer accounts in Google Play Console, it is mandatory to complete the Closed Testing process before moving directly to production.

A. Submitting Changes for Review (Publishing Overview)

When all store settings and forms are completed, the publishing overview lists pending changes:

However, in order for the "Send changes for review" button at the top right to be activated, the application must be configured in at least one test channel (Closed Testing) version.

B. Closed Test Steps

There are 3 mandatory steps to complete closed testing:

1. Select countries and regions:

• The countries where the application will be tested are selected (by default, the whole world or Türkiye can be selected) and Save is made from the bottom right.

2. Select testers:

• In the Testers tab, an e-mail list (Email List) is selected or a new list is created.
• In order to obtain production permission on personal Google Play accounts, Google requires at least 20 test users to be involved in the testing for 14 days. Therefore, it is important to have a sufficient number of users included in the test list.
• After selecting the list, click Save changes from the bottom right.

3. Create a new release:

• When Countries and Testers are completed, "2 of 4 complete" appears as above.
• Click on the blue Create new release button on the top right to proceed to the version creation phase.

• The signed .aab package is loaded. Once the installation is complete, Google analyzes the package:

• As seen in the image, Target SDK: 36 is detected successfully, Version: 610060410 and architectures are verified.
• When Next is clicked, a warning screen appears due to version code jumping:

• Solution: Click on the blue Proceed anyway link just below the "This release's version code is significantly higher than your previous version code" warning.
• After the error confirmation is removed, the version is saved successfully by clicking the blue Save button at the bottom right.

When these steps are completed, you can return to the Publishing overview screen and start the Google approval process with the Send changes for review button.

C. Common Situation: "App not available" Warning on Test Connection

The most common screen that developers see when opening a closed testing opt-in link (play.google.com/apps/testing/com...) is this:

"App not available - A testing version of this app hasn't been published yet or isn't available for this account."

Causes and Solution to This Warning:

1. In Review: Even if the closed test version is created and sent for review, this link will not be activated until the Google review team approves the package. The link will be opened when the status is "Available to testers" in the Play Console.
2. Google Account Mismatch: The Google login active in the browser must be exactly the same as the email address added to the Testers list in the Play Console. A different or anonymous Google account cannot access this link.
3. Server Propagation Time: Even if Google approves the review, it may usually take 1-2 hours for the closed test link to propagate to store servers worldwide.

D. Participating in the Testing Program (Become a Tester - Opt-in)

Once the review is approved and the link is activated, the following official invitation screen opens:

• The page includes the application's icon, developer name and invitation text to the test version.
• When the blue Become a tester button is clicked, the account is included in the test.
• The application can be downloaded directly from the Google Play Store application on the Android device by clicking the "Download it on Google Play" link on the next screen.

---

16. Advertising ID Declaration

For all apps targeting Android 13 (API 33) and above, Google Play requires explicit declaration of Advertising ID (AD_ID) usage.

Question: Does your app use advertising ID?

Google's critical rule on this page is this:

"If you say that your app uses advertising ID, we will block releases that don't include the com.google.android.gms.permission.AD_ID permission in the manifest file when targeting Android 13."

• Option 1 (Recommended): No (No).
• In the closed test package we have currently installed, AdMob SDK or cross-promotion libraries have not been actually compiled yet and there is no AD_ID permission in the AndroidManifest.xml file. Therefore, when No is selected and saved, there will be no manifest conflict.
• Option 2 (If Yes Selected):

• If Yes is selected, [x] Advertising or marketing should be selected as the intended use and the "Turn off release errors" box at the bottom of the page (I understand the ramifications of not including the com.google.android.gms.permission.AD_ID permission...) must be checked since the permission is not yet added to the manifest.

In both cases, after making the selection, click Save from the bottom right.

---

17. Submission for Review (Final Submission)

Once all the store listing, privacy policy, security forms, legal declarations, target audience and closed test version are completed, you will be returned to the Publishing overview screen:

• Submit 14 changes for review: Google Play collects all statements and the test version into a single review package (14 changes awaiting approval as seen in the image).
• The official Google approval process is started by clicking the blue Submit 14 changes for review button.
• Google's automatic quality checks (Quick checks) run in the background and then the application is placed in the evaluation queue of the Google Play Review Team. The review is usually completed within 24-72 hours on personal accounts.

---

18. Application for Production Permit After Closed Testing (Apply for Access to Production)

When the closed testing process (uninterrupted testing for at least 14 days) required by Google for personal developer accounts is completed, the **"Apply for production" button will be activated in the Play Console main control panel. By clicking this button, Google offers a comprehensive 3-step application form to check whether the application has actually been tested and is ready to go live:

Form Steps:

1. About your closed test: You are asked how you find test users, how you collect feedback, and what improvements you make in the application based on the feedback you receive.
2. About your app: The target audience of the application and the main benefits it provides to the users are explained.
3. Your production readiness: It is declared how you will track errors and manage user comments when it goes live.

Critical Questions and Sample Application Answers (English & Turkish)

1. "How did you recruit users for your closed testing? For example, did you ask friends and family, or use a paid testing provider?"

How did you find users for closed testing? (Ex: Family and friends or paid testing provider?)

Important Rule: Google does not like bots or paid artificial test farms. It is safest to state that the testers are real organic users, close circle and relevant social media communities.

I recruited testers organically through friends, family, and colleagues interested in sports analysis. Additionally, I invited active football prediction fans from targeted social media groups (Reddit & sports communities). No paid services were used; all were real, active users.

2. "How easy was it to recruit testers for your app?"

How easy was it to find testers for your app?

• Recommended Choice: Neither difficult or easy or Easy. This option indicates that the process is carried out organically and balancedly and that artificial bot networks are not used.

3. "Describe the engagement you received from testers during your closed test"

Describe the engagement you received from testers during closed testing:
(Google's tip: Indicate whether users are using all features and whether the usage is consistent with the behavior of a real user)

Testers actively used all core features: match fixtures, filters, and coupon generation. Their engagement matched real user behavior, logging in regularly around weekly match days to create coupons and review predictions. All tester activity closely mirrored real-world football fan usage.

4. "Provide a summary of the feedback that you received from testers. Include how you collected the feedback."

Provide a summary of the feedback you received from testers. Include how you collected feedback:

Feedback was collected via Google Play internal feedback, emails, and tester messaging groups. Testers appreciated the fast coupon generator but suggested improving font readability on small screens, adding clearer filter descriptions, and optimizing fixture loading on slow mobile networks.

---

Step 2: About your app

This step asks about the target audience of the application, the added value it offers, and the expected number of downloads for the first year:

1. "Who is the intended audience of your app?"

Who is the target audience of your application?

The intended audience includes adult football fans, sports enthusiasts, and Toto players seeking analytical tools to plan predictions. It is designed for users aged 18+ who want structured match fixture insights, mathematical coupon filtering, and systematic statistical analysis.

2. "Describe how your app provides value to users"

Describe how your app adds value to users:

The app provides value by automating complex coupon filtering and Toto calculations, saving users substantial time. It offers clean weekly fixture overviews, probability statistics, and intuitive mathematical tools that help sports fans make well-structured, data-informed prediction plans.

3. "How many installs do you expect your app to have in your first year?"

How many downloads do you expect your app to reach in your first year?

• Recommended Choice: 0 - 10K (An organic and realistic indie developer goal).

---

Step 3: Your production readiness

This final stage of the application asks about improvements made based on what was learned during closed testing and how the application is deemed ready for live production:

1. "What changes did you make to your app based on what you learned during your closed test?"

What changes have you made to your app based on what you learned in the closed test?

Recommendation: The response should be fully consistent with the feedback you specified in the previous steps (small screen compatibility, font size, filter labels and data caching).

Based on tester feedback, we adjusted font scaling and spacing for smaller screens, added descriptive labels to filter options, and optimized fixture caching for slower network connections. We also streamlined the coupon generation interface to make navigation smoother and more intuitive.

2. "How did you decide that your app is ready for production?"

How did you decide your app was ready for live production?

Recommendation: Google vitals metrics (zero crashes, zero ANR), 14-day testing period and stability across different Android versions should be emphasized.

We confirmed production readiness through 14 days of closed testing with zero crashes and zero ANRs in Android Vitals. All core workflows (fixture browsing, filtering, and coupon generation) executed smoothly across diverse devices, and testers confirmed high stability and complete features.

After all fields are filled in, the official production permit application is completed by clicking the blue Apply button at the bottom right.

Application Sent Screen (Review Process)

Pressing the 'Apply' button returns you to the Play Console main control panel and the following official review card appears on the Production page:

"We have your application for production access"
"We're reviewing your application form. We'll email the account owner with an update. This usually takes 7 days or less, but may occasionally take longer."

Things to Know About This Phase:

1. Review Time: Although Google officially states on the screen that it is "7 days or less", for apps with consistent form responses and a zero crash rate, this approval usually results within 24 to 72 hours.
2. Result Notification: When the evaluation is completed, an official acceptance notification is sent to the account holder's email address (See Chapter 19).
3. What to Do During the Waiting Process: There is no need to take any additional action; The closed test channel can remain active, it is enough to wait for the decision of the Play Console review team.

---

19. Final Victory: Production Access (Open Broadcast) Confirmation

When the Closed Testing (14 days of active testing with at least 20 test users) process, which is the most challenging stage of Google Play Console for new personal developer accounts, is successfully completed and the open store application is made, the following official acceptance e-mail is received from the Google Play Console team:

"Congratulations! Your app has been granted Google Play production access"
"You applied for Google Play production access for your app, and this has now been granted. Production is where you make your app available to billions of users on Google Play."

What Does This Email Mean?

1. Public Release: Your app is now eligible to be released to billions of Android users around the world, not just to invited closed testers.
2. Exceeding the Personal Account Threshold: Google's 20 tester / 14 day test requirement has been officially satisfied, and the developer account has moved to trusted status.
3. One-Click Go Live: By going to the Production channel in the Play Console panel, the proven package in closed testing can go live to the storefront directly or with a new version.

---

20. Pre-Release Checklist (Completed)

All control items at the application stage:

• Have the app ID and unique bundle name been generated in Play Console?
• Is the signed .aab package compiled with targetSdkVersion 36?
• Is the versionCode greater than previous versions? (Was Proceed anyway clicked on the warning?)
• Is the Privacy Policy URL active and opened with HTTPS?
• Is App Access recorded as No?
• Is the advertising statement marked Yes?
• IARC Age Rating completed and certified?
• Is Target Audience selected as 18 and over?
• Has the Data Safety form been filled out?
• Have Government, Financial and Health declarations been recorded as No?
• Are Store Assets (512x512 Icon, 1024x500 Feature Graphic, Screenshots) loaded?
• Closed Test: Have the countries/regions been selected and saved?
• Closed Testing: Has the testers list been selected and saved?
• Closed Test: Is the signed .aab package loaded and versioned?
• Advertising ID: Saved as No for initial release?
• Publishing Overview: Have the changes been submitted for Google review?
• Has Closed Test Process & Production Access been received?

---

21. Arar Games and Our Games

You can visit our store pages to experience live all the games, game mechanics and updates we have developed within our independent studio:

🎮 Our Games:

• 🛡️ Blocked: Pixel Panzer:
  Retro pixel tank action, ColorWheel elemental shells, dynamic weather, Boss battles, global leaderboards and Google Play achievements!
  👉 Download on Google Play (Android & PC) | Microsoft Store (Windows PC)
• 🎨 Paint Trek:
  Reflex-focused arcade experience in colorful pixels and space atmosphere. 👉 Google Play | Microsoft Store (PC & Xbox)
• 🚀 Space Dodger:
  Fast-paced retro arcade obstacle avoidance in deep space.
  👉 Download on Google Play

📢 Social Media and Communication:

To follow our new technical guides, devlogs and game updates:

• 🎵 TikTok: @arargamesstudio
• 📸 Instagram: @arargamesstudio
• 🐦 X (Twitter): @arargamesstudio
• 📺 YouTube: @koreaaria
• 🧵 Threads: @arargamesstudio
• 📘 Facebook: arargamesstudio

---

Prepared by: Arar Games Developer Documentation Archive