Replace your interstitials with learning breaks.
Where your game would show an interstitial, show a short learning break instead. When there's no break to show, your ad runs exactly as it does today. You earn a share of revenue from the breaks your game serves.
A pause parents are glad of
Your ad stays as the fallback
The SDK has the same load-then-show shape as an interstitial. Ask for a break first; if there isn't one, load your ad. A player without Learning Breaks sees exactly what they see today.
Earn from breaks served
Families' subscriptions fund a monthly pool, shared among games by the breaks each one gave that family's children. A break counts when the child took part, whether or not they got the answers right. Rates are set out in the publisher agreement.
Practice to earn
Offer "practise to earn" where you'd offer "watch to earn". The reward is given only for a finished break, the child can always stop, and parents set a daily limit for each game.
How integration works
About ten minutes of code for a game that already shows interstitials. Android first.
-
Add the SDK
One Gradle dependency, and your publisher id in the manifest once your app is registered.
-
Load, then show
Load a break when a round starts. At the pause, show the break if there is one, otherwise your ad, otherwise carry on.
-
Carry on
Whatever the outcome, the game carries on. A child is never penalised for how a break went.
-
Test, then register
Debug builds get breaks on a phone with developer mode on. Release builds need your app registered and approved.
What registering involves
Parents trust Learning Breaks to vouch for the games it works with, so every publisher and every app is checked by a person before it gets breaks in a release build.
You sign in to the portal with a passkey. There's no password to set, and a sign-in link comes by email the first time.
-
Publisher verification
Complete your publisher profile: legal name, country, address, support email, privacy policy and your website's domain. We review it.
-
Domain proof
Register your package and SHA-256 signing certificates to get a publisher id. Then serve two files on your domain, which the portal fills in for you:
/.well-known/assetlinks.jsonand/.well-known/learningbreaks.json. Together they prove the app and the domain are yours. -
App approval
We review every app before it goes live. Your dashboard lists every refused break request, with how to fix it. Approved games can add a listing that parents see in the app.
What your game receives, and what it never does
You receive
- The outcome: completed, released, or abandoned.
- An opaque token that means nothing to you.
- A monthly statement of breaks and earnings.
You never receive
- The question, the answer, or whether it was right.
- The subject.
- The child's name, age or profile.
- How long the break took.
Breaks open in Learning Breaks' own screen, so learning material never enters your process. The SDK makes no network calls of its own and collects nothing from the player; it only talks to the Learning Breaks app on the same phone.
Ready to look closer?
The SDK is in early access while the Learning Breaks app gets ready for Google Play. Read the guide, sign in to the portal, or write to us.