Published SDKs

Built for the stacks mobile teams already use.

Provider-neutral core packages keep AMOS decisioning separate from ad-provider implementation, with dedicated AdMob adapters where needed.

Kotlin Android

Native Android SDK with core and AdMob artifacts published on Maven Central.

com.amostack:amos-sdk:2.0.0com.amostack:amos-sdk-admob:2.0.0Production published

React Native

JavaScript bridge with native Android decisioning and a dedicated AdMob wrapper.

@amos-sdk/react-native 3.0.0@amos-sdk/react-native-admob 2.0.0Production published

Flutter

Dart-first APIs backed by native Android core and AdMob integrations.

amos_flutter: ^2.0.0amos_flutter_admob: ^2.0.0Production published

A consistent model

A familiar AMOS integration across every supported stack.

Public information covers package availability and the onboarding path. Detailed implementation material is available only to authorized publishers.

1

Core SDK

Connect your application to AMOS without requiring an ad-provider adapter.

2

Provider support

Add the supported provider package when it is part of the agreed setup.

3

Secure delivery

Access app-specific configuration and implementation guidance through the publisher portal.

Start integrating

Build the guide for your platform and provider.

Review the sequence publicly, then use the publisher portal for app-specific credentials and ready-to-use files.

Create a guide