Shared Kotlin API over the native PushPort Android, Apple and Web SDKs. Version 0.0.1 is published on Maven Central. This package delegates token registration, persistence, permissions and delivery to the platform SDK. It creates no extra installation, HTTP client or competing notification handler.

Kotlin/Wasm and desktop notification providers are not implemented.

Add mavenCentral() and google() to your repositories and the dependency to the shared module:

commonMain.dependencies {
    implementation("dev.pushport:kmp-sdk:0.0.1")
}

Android's native AAR is a normal transitive Gradle dependency. iOS hosts additionally link the PushPort Swift Package Manager product. The current stable interop path deliberately keeps Swift package linking in Xcode; there is no dependency on experimental SwiftPM-import Gradle tooling. Web hosts install/import the Web SDK once and pass its module to the adapter.

import dev.pushport.kmp.PushPort
import dev.pushport.kmp.PushPortConfiguration

// Receive the platform-created client through your application DI/constructor.
suspend fun configurePush(client: PushPort) {
    client.initialize(PushPortConfiguration(appId = "YOUR_PUSHPORT_APP_ID"))
    client.setLocale("uk-UA")
}

// From your permission/subscription UI:
// client.requestPermission()
// client.setSubscribed(false)
// client.setLocale(null)
// client.sync()
// val status = client.status()

Call platform-facing operations from the UI/main thread. On Android, requesting permission starts the native permission flow; it does not await the user's decision. Read status after the permission result / on resume. On Apple/Web, the native prompt completes asynchronously. A successful subscription mutation means the native SDK accepted the operation; consult lastSyncedAt/syncError for server synchronization.

val client = createAndroidPushPort(applicationContext) { currentForegroundActivity }

The Activity provider must return a live Activity and must not retain a destroyed one. The SDK retains only applicationContext. Keep the client in your application scope and supply the current Activity from the host lifecycle. Initialization invokes the existing native Android SDK with the same App ID/server.

// iosMain, main thread
val client = createApplePushPort()
client.initialize(PushPortConfiguration(
    appId = "YOUR_PUSHPORT_APP_ID",
    appleEnvironment = AppleEnvironment.SANDBOX,
))

In Xcode link the PushPort SPM product to the iOS application, enable Push Notifications, and forward APNs callbacks as described in the Apple SDK README. Explicitly instantiate PushPortKMPBridge() once in the Swift host during startup to ensure its Objective-C class is linked before the Kotlin factory is called (see example). The common and native initialization must use the same configuration. For images, the extension depends on the Apple extension product directly.

The checked-in Cinterop header declares stable selectors, not a duplicate native implementation. The KMP KLIB alone cannot contain a Swift package added separately through SPM. Test the final linked application, not only compilation of Kotlin metadata.

@JsModule("@pushport/web-sdk")
external object NativeWebSdk

val client = createWebPushPort(NativeWebSdk, serviceWorkerUrl = "/pushport-sw.js")

Add implementation(npm("@pushport/web-sdk", "0.0.1")) to the host's jsMain.dependencies after npm publication and copy the native SDK worker into the site's public directory. SSR import is safe, but initialize the client only in a supported browser. Request permission from an actual user click.

Use the checked-in wrapper, JDK 17, Node.js 24 and Android SDK 36. Portable verification:

./gradlew jvmTest jsNodeTest

For unreleased Android changes, native adapter verification can use an explicit local Maven repository:

./gradlew compileAndroidMain testAndroidHostTest -Ppushport.androidRepository=/absolute/path/to/android-sdk/build/maven-repository

There is no hardcoded dependency on sibling directories. For iOS run compileKotlinIosArm64 compileKotlinIosSimulatorArm64 compileKotlinIosX64 on macOS, then run bash scripts/verify-apple-consumer.sh "$PWD/build/maven-repository" after local publication to link an independent KMP application with the public Swift package. Architecture/API, publishing, security.

The Apple SDK is published/tested first; publish KMP after compatible Android/Apple versions and Web npm package exist. Package availability and provider delivery are separate. Check the platform status in the PushPort console before testing real notifications.

Apache-2.0 В· Oleh Yurkov В· support@pushport.dev

Source: PushPortLibraryKmp · Integration documentation