P2PSDK lets users share a metered slice of unused connectivity in exchange for a clear in-app reward. Add a consent-first revenue stream alongside — or instead of — ads.
The order matters: each step gates the next, and network activity remains disabled until the user explicitly agrees.
Add the P2PSDK module through your preferred package manager. The integration is designed to stay isolated from the rest of your application stack.
~15 min setupOpen a clear in-app disclosure explaining what is shared, when it runs, and what the user receives. Nothing activates before an explicit opt-in.
Opt-in requiredOnly metered, unused capacity is contributed. Network and device controls cap activity and keep cellular usage disabled by default.
Unused capacity onlyView opted-in users, contributed bandwidth, and accrued revenue in the publisher dashboard once production access is enabled.
Continuous reportingCommercial terms are agreed with each publisher. Eligible opted-in users and contributed bandwidth can both inform the final payout.
A contracted rate for eligible opted-in users during the reporting period. Counting rules and rates are defined in your publisher agreement.
A metered rate based on eligible idle bandwidth actually contributed, adding upside from well-connected opted-in users.
No banners, interstitials, or video pre-rolls. The SDK is designed to use eligible idle connectivity after a clear opt-in.
No creative trafficking, fill-rate gaps, or new interface element competing with your product experience.
Add a separate revenue line without replacing your existing mediation stack on day one.
Customizable consent copy, localization support, and a persistent opt-out are part of the integration model.
A small SDK surface and automatic throttling are designed to minimize CPU, battery, and binary impact.
Review opted-in users, eligible bandwidth, and accrued revenue through a single account dashboard.
Documented permissions and network behavior help product, security, and store-review teams assess the integration.
Share idle connectivity?
This app can share a small, metered slice of unused bandwidth in exchange for a reward. You can turn it off at any time in Settings.
Match the copy, colors, and reward framing to your app while keeping disclosure and opt-out mechanics visible for user and compliance review.
Explain what is shared, when the SDK can run, and what the user receives in return.
Connect opt-in to the coins, unlocks, or other value already used by your product.
Give users a durable setting that disables sharing without waiting for a server round trip.
P2PSDK can run alongside an existing ad stack. The right mix depends on your users, markets, product experience, and commercial terms.
| Dimension | Ads | P2PSDK |
|---|---|---|
| On-screen impact | Visible and competes for attention | No persistent interface element |
| Revenue dependency | Affected by fill rate and market CPMs | Based on contracted eligibility and usage |
| Existing ad revenue | Additional networks can compete in a waterfall | Designed to run as a separate revenue line |
| Predictability | Can vary by season and advertising demand | Commercial rates are defined in the publisher agreement |
| User interruption | May interrupt or displace product content | No interruption after the consent decision |
| Operations | Requires ongoing mediation and creative controls | One SDK, consent flow, and publisher dashboard |
| Market fit | Broad reach across devices and markets | Strongest with connected, retained, opted-in users |
Straight answers about fit, consent, platform review, and network compatibility before engineering work begins.
No SDK vendor can guarantee a store-review outcome. P2PSDK documents its permissions, consent flow, and network behavior so your product and review teams can assess the integration before submission. Final approval always remains with the platform.
There is no universal integration threshold, but commercial impact scales with eligible opted-in users and connectivity. Smaller apps should review expected economics with the P2PSDK team before committing engineering time.
Apps aimed primarily at children, regulated financial products, VPNs, proxies, and products with overlapping network behavior require additional eligibility and compliance review before integration.
Potentially. Multiple networking SDKs may compete for the same capacity or require overlapping platform permissions. Disclose existing networking components during technical review so compatibility can be assessed first.
Availability depends on current demand, compliance requirements, and payout rails. Request the current coverage list during onboarding instead of relying on a static marketing-page list.
Provider terms differ. The integration must clearly disclose bandwidth sharing, obtain an explicit user decision, and apply configured caps. Users remain responsible for agreements with their connectivity provider.
The SDK setup is designed to be compact, but production timing also includes product, security, consent-copy, eligibility, and commercial review. The onboarding team will confirm a schedule for your app and platforms.
Review eligibility, commercial terms, SDK behavior, and consent copy with the team before requesting production access.
Large install base? Include monthly active users so the team can prepare the right commercial review.