📦 Module containers
When Flutter switches from Nutrition to Training (or the reverse), your native tab bar, rail, or drawer should switch too. A module container is the adapter that tells the SDK how to update your chrome.
Platform code & examples
Platform selector → Navigation (module container section) and UI components (multi-tab / bottom nav).
When you need one
| Setup | Container? |
|---|---|
| Single embedded module only | No |
| Two native tabs (nutrition + training) | Yes |
navigate across modules from outside the SDK | Yes |
| Deep link to the other module | Yes |
Without a container, Flutter navigation still works; only the native tab highlight may lag until the user taps manually.
Built-in coordinators
| Platform | Types |
|---|---|
| Android | AzeooBottomNavCoordinator, AzeooNavigationRailCoordinator, AzeooNavComponentCoordinator |
| iOS UIKit | AzeooUITabBarCoordinator, AzeooUINavigationCoordinator |
| SwiftUI | AzeooSwiftUITabCoordinator |
| React Native | setModuleContainer((module) => boolean) |
Install once after connect via sdk.setModuleContainer(...).
Custom hosts implement AzeooModuleContainer / return true from the RN callback when the tab switch was handled.