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 monetises through Google AdMob, serving interstitial, rewarded, and banner ads at key moments in the user journey. The integration uses the play-services-ads:19.6.0 SDK and stores ad unit IDs as string resources so they can be swapped without touching Java source files. An AdsClass helper provides a convenience method for triggering interstitial ads from any Activity.

App ID Configuration

The AdMob App ID is declared as a <meta-data> element inside <application> in AndroidManifest.xml:
<meta-data
    android:name="com.google.android.gms.ads.APPLICATION_ID"
    android:value="ca-app-pub-7520984438935131~4453963759" />
The App ID above belongs to the original developer account. You must replace it with your own AdMob App ID before publishing. Shipping another developer’s App ID violates AdMob policy and will cause revenue to be credited to the wrong account.

Ad Unit IDs

Ad unit IDs are stored as string resources in res/values/strings.xml so they remain outside the compiled bytecode and are easy to update.
String ResourceAd TypeUsed In
R.string.Intusitus_adInterstitialFinalmainScreen, GameMainAct (via AdsClass)
R.string.reward_adRewardedFinalmainScreen, ScoringPage
Banner ad units are configured inline with AdView in the Show_ImagesMain layout rather than through a shared string resource.

Where Ads Appear

Each Activity opts into specific ad formats based on the user action happening in that screen:
ActivityAd TypeTrigger
FinalmainScreenInterstitial + RewardedActivity creation / game completion
ScoringPageRewardedScore screen shown to player
Show_ImagesMainBanner (AdView)Always visible while browsing images
GameMainActInterstitialOn create, via AdsClass.showintertialeAds()

AdsClass Helper

AdsClass is a context-based helper instantiated with an Android Context. Its showintertialeAds() method is called from GameMainAct.onCreate() to display an interstitial at launch.
The Facebook Audience Network code inside AdsClass.showintertialeAds() is currently commented out, making the method a no-op on its own. Interstitial and rewarded ads are wired directly inside each Activity rather than delegated to AdsClass. If you want to centralise ad loading, wire the AdMob calls through AdsClass explicitly.

Development: Test Ad IDs

During development and QA always use Google’s official test credentials to avoid invalid traffic penalties.
ResourceTest Value
App IDca-app-pub-3940256099942544~3347511713
Interstitial unit IDca-app-pub-3940256099942544/1033173712
Rewarded unit IDca-app-pub-3940256099942544/5224354917
Banner unit IDca-app-pub-3940256099942544/6300978111
Never use test ad unit IDs in a production build. Test ads generate no revenue and will result in zero earnings if shipped accidentally.

Steps to Replace with Production AdMob IDs

1

Update the App ID in AndroidManifest.xml

Replace the android:value of the com.google.android.gms.ads.APPLICATION_ID meta-data with the App ID from your AdMob dashboard.
2

Update ad unit string resources

Open res/values/strings.xml and set the correct production values for Intusitus_ad and reward_ad:
<string name="Intusitus_ad">ca-app-pub-XXXXXXXXXXXXXXXX/XXXXXXXXXX</string>
<string name="reward_ad">ca-app-pub-XXXXXXXXXXXXXXXX/XXXXXXXXXX</string>
3

Update the banner AdView unit ID

In the Show_ImagesMain layout (or its Activity), replace the inline banner ad unit ID with your production banner unit ID.
4

Rebuild and test

Do a clean build (Build > Clean Project, then Build > Rebuild Project) and verify ads load on a physical device before submitting to the Play Store.
Enable test devices in your AdMob account for your physical test phone so you receive real-looking ads without generating invalid traffic during QA.

Build docs developers (and LLMs) love