Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/SaadAhmed1122/Kids_learnig_App/llms.txt

Use this file to discover all available pages before exploring further.

The Kids Learning App is a standard Android Gradle project targeting API 30 with a minimum supported API of 19 (Android 4.4 KitKat). Building the app requires Android Studio with the Android SDK and build tools installed. This page covers the Gradle configuration, how to compile a debug APK for local testing, and how to generate a signed release Android App Bundle (AAB) ready for Play Store submission.

​
Gradle Configuration

The app/build.gradle file controls SDK versions, versioning, and build behaviour. The key values are summarised below:
ConfigValue
compileSdkVersion30
buildToolsVersion29.0.3
minSdkVersion19
targetSdkVersion30
versionCode6
versionName6.0
applicationIdcom.kidsapp.fiver1
minifyEnabledfalse
Lint is configured to be non-blocking during release builds: 
lintOptions {
    checkReleaseBuilds false
    abortOnError false
}
minifyEnabled false means ProGuard/R8 code shrinking and obfuscation are not applied. For production releases, consider enabling minification and adding appropriate ProGuard rules to reduce APK size and protect your source code.

​
Dependencies

The app relies on the following Gradle dependencies declared in app/build.gradle: 
implementation 'androidx.appcompat:appcompat:1.2.0'
implementation 'androidx.constraintlayout:constraintlayout:2.0.1'
implementation 'androidx.recyclerview:recyclerview:1.1.0'
implementation 'com.google.android.material:material:1.2.1'
implementation 'com.google.android.gms:play-services-ads:19.6.0'
LibraryPurpose
appcompat:1.2.0Backwards-compatible Activity and UI component support
constraintlayout:2.0.1Flexible constraint-based layouts used across screens
recyclerview:1.1.0Scrollable game grid lists in category screens
material:1.2.1Material Design components (CardViews, bottom sheet, etc.)
play-services-ads:19.6.0Google AdMob SDK for interstitial, rewarded, and banner ads

​
Building a Debug APK

Use a debug build for local testing and development. Debug builds are signed with the Android debug keystore automatically.
1

Open the project in Android Studio

Launch Android Studio and select Open (or File > Open), then navigate to the root of the Kids Learning App repository. Wait for the initial project indexing to complete.
2

Sync Gradle

Go to File > Sync Project with Gradle Files (or click the elephant icon in the toolbar). Resolve any dependency download errors before proceeding.
3

Build the debug APK

Navigate to Build > Build Bundle(s) / APK(s) > Build APK(s). Android Studio will compile the project and notify you when the build finishes.
4

Locate the APK

The debug APK is output to:
app/build/outputs/apk/debug/app-debug.apk
Click locate in the build notification balloon to open the folder directly.

​
Building a Release AAB (Android App Bundle)

Google Play requires an Android App Bundle (.aab) for new app submissions. A release build must be signed with your production keystore.
1

Open the signing wizard

Go to Build > Generate Signed Bundle / APK in Android Studio.
2

Select Android App Bundle

Choose Android App Bundle and click Next.
3

Provide keystore details

Enter your keystore path, key alias, and passwords. If you don’t have a keystore yet, click Create new… to generate one. Store the keystore file and credentials securely — you will need them for every future update.
4

Choose release build variant

Select the release build variant and click Finish. The signed AAB is output to:
app/release/app-release.aab
The repository already contains a pre-built app/release/app-release.aab. This is the bundle that was uploaded to the Play Store. Generate a new signed AAB whenever you increment versionCode or versionName before submitting an update.
Keep your release keystore file backed up in a secure location separate from the repository. If you lose the keystore you will be unable to publish updates to the same Play Store listing and will have to create a new app entry.
Before submitting to the Play Store, replace the sample AdMob App ID in AndroidManifest.xml and the ad unit IDs in res/values/strings.xml with your own production IDs. See the AdMob Integration page for the full replacement steps.

Build docs developers (and LLMs) love

Get started for freeTalk to us