---
title: Native apps
description: Prepare an Android, iOS or Expo app for the first 1Consent SDK release and verify consent on a device.
url: https://1consent.app/docs/integration/native-apps
---

# Native apps

The first public SDK release is in preparation. You can register your app and check its banner configuration now. Install the SDK once version `0.1.0` is published for your platform. The first release targets GDPR and US banners on Android, iOS and Expo. Native IAB TCF, Flutter and Capacitor have separate release plans.

## Prepare your app in the Dashboard

Select the site and banner your app will use. Register the Android application ID or iOS bundle identifier of the build you plan to test. Development and production builds can have different identifiers. Use an active site on a plan that includes apps. Select a banner published for apps with that exact identifier. To test on Live, verify ownership of the identifier for this site and wait for the published banner to finish deploying. To test on Staging, enable Staging for the site on a plan that includes it. In the downloaded configuration, Live corresponds to `production`, and Staging to `staging`.

For a native Android or iOS project, download the banner's `1consent.json` for that stage. Include it in the Android app's `src/main/assets/` directory or the iOS app target's bundle resources. In an Expo project, the config plugin generates this file from your app ID, banner ID and stage.

## Android with Kotlin or Java

The Android SDK will be distributed from the public 1Consent Maven repository. Customers can download it over HTTPS without a registry account or token. To prepare your project, add this block inside `dependencyResolutionManagement.repositories` in `settings.gradle.kts`. It tells Gradle to use the repository only for the `app.oneconsent` group.

```kotlin
exclusiveContent {
    forRepository { maven { url = uri("https://maven.1consent.app/") } }
    filter { includeGroup("app.oneconsent") }
}
```

If your app resolves from project-level repositories, put the same block in the effective project's `repositories` block. Keep Google's repository and Maven Central for other dependencies.

After publication, pin the released version in your app module's `build.gradle.kts`. Java and Kotlin apps use the same dependency and require Android API level 24 or later.

```kotlin
dependencies {
    implementation("app.oneconsent:oneconsent-android:0.1.0")
}
```

## iOS with Swift Package Manager

After publication, enter `https://github.com/oneconsent/1consent-ios.git` in Xcode under **Add Package Dependencies**, select the released version, and add the `OneConsent` product to your app target. The Swift package delivers the compiled XCFramework for iOS 16.4 or later, on arm64 devices and arm64 simulators. Import `OneConsent` and call `OneConsentSDK.start()` from your app delegate's `application(_:willFinishLaunchingWithOptions:)`. [1Consent iOS releases](https://github.com/oneconsent/1consent-ios/releases)

## React Native with Expo

The first package targets Expo SDK 58 (`expo ~58.0.23`, `react-native ~0.88.1`, `react ~19.3.0`). After the npm release, install `@1consent/react-native` at the released version. Add its config plugin under `expo.plugins` with the `appId`, `bannerId` and `stage` from your selected Dashboard configuration. During prebuild the plugin registers the Android Maven repository and writes the platform configuration. Make a native development or release build to load the SDK. Expo Go cannot load this native module.

Wrap the app in `OneConsent` and place `OneConsentPrivacyChoices` where people can reopen privacy settings. If the same project also ships a browser app, follow the [React web guide](/docs/integration/react) for that target.

## Prepare your privacy disclosures

Use [What to declare for the 1Consent SDK](/docs/integration/native-sdk-privacy) to review the data the SDK handles and prepare your App Store privacy details or Google Play Data safety answers. Include the data handled by the rest of your app and its other SDKs.

## Verify on a device

In a direct Android or iOS integration, call `OneConsentSDK.showPreferences()` from a reachable Settings or Privacy action. On Android the startup provider prepares the process. Call `OneConsentSDK.start(this)` from the host activity to present the notice.

Keep each optional service disabled until the SDK reports a current choice that allows its service ID. Subscribe to choice changes so withdrawal also stops optional processing. Your app controls when its third-party SDKs start.

Start with a fresh install. Check the notice, refuse optional services, reopen settings and grant one service. Confirm the service's actual SDK starts only when its current choice permits it. Withdraw consent, relaunch the app and verify that the saved choice still governs its behavior. For an existing app, also test upgrading a build that already has saved choices.

For an Expo project, a connected assistant can inspect registration, publication and the current installation recipe using the `react-native` target. Keep any reported blockers visible while preparing the integration. [Connect your AI assistant](/docs/integration/ai-assistants)
