P2PSDK embeds an opt-in network peer in your application. The supported wrappers own the native runtime, device identity, consent state, callback dispatch, and error mapping. Your application owns when to offer the feature, how to reward the user, and the lifetime of the SDK instance.
SupportedAndroidKotlin / JavaAndroid API 23+, Java 11
com.p2psdk:p2p-sdk-android:1.0.0 SupportediOSSwiftiOS 13+, Swift tools 5.9P2PSdk Swift package SupportedNode.jsTypeScript / JavaScriptNode.js 20+, Linux/Windows x64@p2psdk/[email protected] SupportedElectronTypeScript / JavaScriptElectron 28+, Node.js 20+@p2psdk/[email protected] SupportedWindows / .NETC# / WPF.NET 8, Windows x64P2PSdk.P2P / P2PSdk.P2P.Wpf SupportedLinux nativeC / C++C ABI 1, normally x86_64 GNU/Linuxlibp2p_sdk.so.1 / P2PSdk::p2p_sdk SupportedwebOSTypeScript / Luna serviceLG TV 22+, webOS OSE 2.7+, Node.js 12.14.1@p2psdk/[email protected]Integration path
Section titled “Integration path”SDK runtime sequence
From consent to a connected peer.
CONSENT P2PSDK RELEASEOne owned instance
- 02 / InstanceCreateOne owner per peer
- 03 / SupervisorConnectStart connection setup
- 04 / NetworkOnlineConnected event fires
- 05 / ReleaseCloseRelease exactly once
Consent gateBefore create
Online signalConnected event
Final releaseExactly once
A successful connect call starts the supervisor. Wait for the connected event before treating the peer as online.
- Complete onboarding and receive the package, application API key, consent configuration, and test environment.
- Install exactly one supported wrapper and its matching native artifact.
- Let the SDK-owned consent UI return an accepted SDK instance.
- Attach lifecycle handlers and call
connect(). - Treat the connected event — not the return from
connect()— as the online signal. - Expose consent revoke and release the SDK exactly once during final shutdown.
What these docs cover
Section titled “What these docs cover”- Copy-ready setup for Android, iOS, Node.js, Electron, Windows/.NET, Linux native, and webOS TV/OSE applications.
- Consent, identity, lifecycle, background execution, errors, logging, testing, and release readiness.
- Public wrapper APIs and the stable native C ABI required by application developers.
- Troubleshooting paths and a sanitized support bundle checklist.
Backend signing, discovery implementation, transport protocol, and SDK maintainer workflows are intentionally outside the public application documentation.
Choose your next step
Section titled “Choose your next step”| If you are… | Continue with |
|---|---|
| Evaluating fit | Compatibility and supported platforms |
| Ready to integrate | Integration quickstart |
| Waiting for artifacts | Private package access |
| Integrating the REST API | Control Plane API reference |
| Preparing release | Production checklist |
| Diagnosing a problem | Troubleshooting |