Skip to main content

Integration checklist

Use this list before you write integration code. Check every box.

1. Accounts and keys​

  • You have your SDK API Key from the Azeoo team (platform coming soon — contact Azeoo in the meantime)
  • You have your SDK Secret Key from the Azeoo team (used to sign User JWTs on your backend)
  • Your backend can create a User JWT — see Creating the User JWT for the payload spec and code examples

2. Pick your platform​

  • Flutter — package:azeoo_sdk
  • Android — AAR from Downloads
  • iOS — SPM / CocoaPods; run ./scripts/ios_build.sh if building from monorepo
  • React Native — Bitbucket or downloaded package + Android Gradle line

3. Install the SDK​

  • Dependency added (Gradle, SPM, pubspec.yaml, or yarn add)
  • Android only: ndk.abiFilters added in your app/build.gradle.kts — required step (not applied automatically by the SDK AAR)
  • Android RN only: apply from: ".../azeoolib-dependencies.gradle" in project build.gradle
  • iOS from source: Flutter xcframeworks built (see Build from source)

4. Initialize (once per app launch / process)​

  • Called initialize with API key and config before any UI
  • Waited for success (callback / await / completion handler)
  • Did not call connect inside initialize

5. Connect (when user is logged in)​

  • Your backend creates a User JWT with the required payload (spec)
  • You pass token, gender, height, weight (see Measurements)
  • You did not pass userId as input to connect (it goes inside the JWT)
  • You stored the returned profile id if your app needs it

6. Show UI​

  • Called embed API after connect succeeded
  • For tabbed apps: optional setModuleContainer so cross-module navigation updates your tab bar
  • To open a specific screen from your UI: sdk.navigate(...) — see Destination catalogue

7. Logout and teardown​

  • Logout: disconnect — user session cleared, SDK stays initialized
  • Full reset (rare): dispose then initialize again (native)

8. Production​

  • Deep links configured in host app + SDK deepLinks config
  • Theme / safe area tested on notched devices
  • No hardcoded API keys or secret keys in source control (use env / secrets)

Next step​

Open your platform Quick start.