The Jingle demo is a complete, working Android integration - the same plug-in, the full consent flow, and simulated inbound calls routed through the real plugin path, with estimated earnings accruing live.
Every flow in the demo runs on the production plug-in - from consent to call to estimated earnings.
The full consent flow: clear disclosure, then phone verification with a one-time SMS code before anything activates.
Estimated revenue lands the moment each call completes - a per-call feed and session totals, clearly labelled as illustrative.
Every completed call logged with duration, origin country, and USD value - derived from real plugin behaviour, not canned numbers.
For users who have explicitly opted in, simulated inbound calls are routed through the real plugin path - answer in-app and hear a voice endpoint configured by the plugin provider.
Each permission requested in sequence with a plain-language reason - even auto-granted permissions are disclosed up front.
Switch the plugin off at any time - simulation stops instantly. Factory reset returns the demo to a fresh-install state for the next walkthrough.
The journey a user takes - from first disclosure to earnings.
Plain-language disclosure before anything runs - nothing activates until every step is complete.
Three clear steps - permissions, activation, then a test call - each unlocked in order.
Each permission is listed with the reason it exists - users grant it for a real, understood feature, with Jingle disclosed alongside via dual-disclosure.
Activation requires a one-time SMS code - proof of an informed, deliberate opt-in on a real number.
An inbound call delivered and answered inside the app - with a voice endpoint playing the moment you pick up.
Every completed call lands in the event feed with duration, origin country and estimated value - monetisation visualised for the app owner.
The demo is built on the production plug-in - io.minutesnetwork:jingle-fullservice 5.6.0 - with the same integration pattern documented in the CTO brief: permission gating, SMS verification, activation, and call delivery through the real plugin path for users who have explicitly opted in.
Access is credential-gated, and everything you see in the analytics tab is derived from simulation activity and real plugin behaviour. Revenue figures shown in the demo are illustrative, non-binding estimates in USD.
Read the CTO technical brief arrow_forwardAsk your integration engineer for demo access, or apply and we will walk you through it on the intro call.
