🏗️ SDK Architecture Overview
The Azeoo SDK is a Flutter module embedded in native host apps. You integrate through a single entry point per platform; Pigeon bridges host code to Dart.
High-level flow
Two-step lifecycle
- Initialize — API key, locale, theme, offline, deep links, safe area. No user.
- Connect — User JWT and profile measurements. User id is returned.
See Initialization.
What you use in the host app
| Surface | Purpose |
|---|---|
AzeooSDK / AzeooSDK.shared | initialize, connect, disconnect, dispose |
sdk.modules.nutrition / .training | Embed UI (native) |
AzeooSDKModules | Embed UI (Flutter) |
sdk.navigate(to:) | Typed navigation (Navigation) |
sdk.setModuleContainer(...) | Sync host tab bar with SDK |
sdk.user / sdk.theme | Profile and theme after connect |
Host apps integrate via Pigeon host APIs on each platform, not by calling internal Dart types directly.
Modules
- Nutrition — diary, plans, scanner, search, settings
- Training — workouts, exercises, progress
Each module has embed APIs (getFragment, getView, tabHost, …) and typed destinations.
Repo layout (internal)
| Path | Role |
|---|---|
plugins/core/ (azeoo_core) | Canonical API — AzeooSDK, AzeooSDKInitOptions, Pigeon handlers, native AzeooSDK wrappers |
lib/ | Flutter nutrition/training UI — AzeooSDKModules, AzeooSDKContent |
sdk/android, sdk/ios, sdk/react-native | Distribution packages |
example/ | Sample integrations |
Package split
azeoo_core— initialize, connect, config (all platforms)azeoo_sdk— re-exportsazeoo_core+ Flutter UI modules for pure Flutter or embedded module usage
See Build from source.