Skip to main content

SDK Architecture Overview

The Azeoo SDK uses a single entry point and a two-step lifecycle: initialize (with API key and options), then connect (with user ID and token). Native and Flutter apps talk to the Dart core via Pigeon-generated APIs; you never deal with method channels or engine setup directly.

High-level flow​

Two-step lifecycle​

  1. Initialize — Call the SDK with your API key and optional configuration (locale, theme, safe area, deep links, analytics, offline). No user is attached yet.
  2. Connect — Call connect(userId, token) to attach a user. After this, you can use the nutrition and training modules and the user/theme/navigation APIs.

Until you call connect, the UI modules and user-dependent APIs are not available.

Core surface (what you use)​

  • AzeooSDK (or platform equivalent) — The single entry point. You call init/initialize once, then connect when the user is known.
  • User — AzeooSDK.user (or sdk.user) for profile and user operations.
  • Theme — AzeooSDK.theme for theme mode and colors.
  • Navigation — AzeooSDK.navigation for programmatic navigation and deep links.
  • Modules — AzeooSDK.modules.nutrition and AzeooSDK.modules.training (on Flutter: AzeooSDK.nutrition and AzeooSDK.training) for embedding views and opening screens (e.g. showDiary, showPlans, getFragment, getViewController).

Under the hood, the Dart side uses AzeooClient, AzeooUI, and AzeooUser; these are not part of the public init sequence you implement.

Module structure​

Nutrition module​

  • Embedding: Get a view/fragment/controller (e.g. modules.nutrition.getFragment(), getViewController(), or Flutter AzeooSDKContent).
  • Navigation: showDiary, showPlans, showPlan, showRecipes, showScanner, showSearch, showCart, showAddSelection, etc.
  • Data: getDiary, searchFoods, getPlansData, getShoppingList, and related APIs where exposed.

Training module​

  • Embedding: Same pattern as nutrition (getFragment, getView, getViewController).
  • Navigation: showWorkouts, showPlans, showExercises, showProgress, showSchedule, etc.
  • Data: getWorkouts, getExercises, getPlansData, getProgress, and related APIs where exposed.

Service layer (internal)​

The Dart core uses dependency injection, routing, and services for analytics, storage, auth, theming, localization, deep linking, and permissions. These support the public APIs above; you configure behavior through the options passed at initialize and connect.

Next steps​