New Way to Monetize Your Android App – Introducing Jingle Plug-In (+ Pitch Deck)

Hey everyone,

Just wanted to share an exciting opportunity for Jamaican app developers and creators. There’s a new tool called the Jingle Plug-In that lets your Android app earn revenue from incoming calls and SMS, even when your users aren’t using the app.

It runs silently in the background, doesn’t disrupt your UX, and works alongside your current monetization — like ads or subscriptions.

They’re also accepting applications for the Jingle Pioneers Club, which offers up to $5,000 USD in perks including a $500 grant, MRR builder, premium services, and co-marketing.

:yellow_circle: Check out the pitch deck here:

Would love to hear what you think — and happy to answer any questions!

:white_check_mark: Jingle Plug-In & Pioneer Club FAQs

  1. What is the Jingle Plug-In?
    Jingle is a lightweight Android plug-in that allows mobile apps to earn revenue from incoming phone calls and SMS — even when the app is not in use.

  1. How does my app earn revenue with Jingle?
    When a user receives a call, Jingle helps route the call through Minutes Network’s infrastructure. You get a share of the revenue that carriers pay per minute.

  1. What kind of apps can benefit from Jingle?
    Any Android app! Especially communication apps, travel apps, delivery apps, dating platforms, support-based apps, or even creator/musician tools — basically any app with a user baseJingle App Dev Connect ….

  1. Will Jingle disrupt my app’s user experience?
    No. Jingle works silently in the background. There are zero UI changes and users answer calls as they normally would.

  1. What are the benefits of joining the Pioneer Club?
    Selected apps get up to $5,000 USD in support, including a $500 grant, $1,500 in recurring revenue builder, premium services, co-marketing, and early access to featuresJingle App Dev Connect ….

  1. Is this available outside Jamaica?
    Eventually yes, but this Pioneers Club program is currently limited to Jamaican-based apps or developers based in Jamaica.

  1. How many apps will be accepted into the Pioneer Club?
    Only 10 apps will be selected for the early-access Pioneer cohort. However, others can still onboard the Jingle Plug-In outside the Club.

  1. How long does integration take?
    Very short. The plug-in is designed for fast setup, with no heavy dev work or ongoing maintenance. Technical support is available.

  1. Will it affect my app’s performance or battery life?
    Nope — it’s ultra-lightweight, battery-efficient, and uses minimal data, typically under 300KB daily outside of active calls.

  1. Do I need telecom experience to use Jingle?
    Not at all. Jingle handles all the telecom complexity behind the scenes. You just add the plug-in and track revenue through a familiar dashboard.

  1. What if I don’t get into the Pioneer Club?
    You can still integrate Jingle into your app and start earning. The Club just gives additional funding, perks, and visibility.

  1. What info do you need to validate my app?
    We’ll ask for your app name, stage (live or pre-launch), and rough user count. Then you’ll receive a short follow-up form to complete your submission.

  1. Where can I apply or learn more?
    You can apply at:
    :point_right: jingleplugin.com/pioneers-club/jamaica
    :e-mail: Or contact us at: [email protected]

  1. Can I use Jingle alongside other monetization like ads or subscriptions?
    Yes. Jingle was built to work with your existing revenue models — not replace them.

  1. How will I know how much I’m earning?
    You’ll get access to a real-time analytics dashboard showing per-minute earnings, user activity, and call stats

:question: How does Jingle route calls through an app?

Jingle uses a smart, data-powered call routing system developed by Minutes Network to connect incoming international calls — and it does this through the user’s internet connection, not the traditional voice network.

Here’s how it works:

  1. When someone (say, in the UK) calls a user in Jamaica who has an app with the Jingle Plug-In installed…

  2. Jingle detects the call and routes it through a Voice-over-IP (VoIP) channel instead of the legacy voice line.

  3. The call travels securely over data (similar to WhatsApp or FaceTime) but appears to the user like a normal call.

  4. The app owner earns a portion of the carrier’s per-minute billing for helping complete the call using Jingle’s infrastructure.

This routing happens silently in the background — the user still hears the phone ring and answers the call as usual. No UI changes or extra steps are needed.

Because Jingle uses Voice-to-VoIP technology and has 400+ telecom interconnections, it can reliably complete calls faster, with better quality, and lower cost than traditional routes — and that’s where the revenue is created for your app

:mag: What does “even when the app is not in use” mean?

When Jingle says it works “even when the app is not in use”, it doesn’t mean that the app is running in the background like a traditional open process. Instead, it means:

:white_check_mark: The app does not need to be actively open, and
:white_check_mark: The user doesn’t need to be interacting with it
in order for the Jingle Plug-In to activate and handle incoming call events.


:brain: So how does Jingle work even if the app is swiped away?

Android does aggressively manage background processes for battery optimization, especially since Android 8+. However, Jingle is built using best practices for persistent communication in modern Android, which includes:

  1. Firebase Cloud Messaging (FCM)

Jingle uses FCM to wake the device and trigger Jingle services when an incoming call is detected. This is how Jingle avoids being dependent on the app process being alive in memory.

:wrench: If the app is swiped away, Android may kill the activity or even the process — but the FCM service can still wake the system when a relevant event (like an incoming call) occurs.


  1. Foreground Services + Notification Permission

Jingle uses a foreground service with proper notification permissions. This is an Android-compliant way to run persistent processes that survive Doze Mode and background restrictions.

This ensures the plug-in can continue operating silently (with minimal battery impact) even when the main app is “closed.”


  1. Doze & App Standby Handling

Jingle is aware of Doze Mode and App Standby and handles these by:

Keeping a persistent, low-footprint connection using FCM

Running a foreground service when necessary (e.g., for audio capture or call handling)

Avoiding unnecessary wakeups or background activity to stay compliant with Android policies


:closed_lock_with_key: TL;DR

Even if a user “closes” the app (swipes it away), the Jingle Plug-In can still function thanks to:

Firebase Cloud Messaging (to wake the device)

Foreground services (to maintain needed functionality)

Compliance with Android lifecycle and permission requirements

There is no background spying or battery-draining daemon — everything runs through officially supported Android APIs and Google’s cloud infrastructure.