🏋️ Training Module (Android)
The Training module's screens are reached through the typed AzeooDestination API:
sdk.navigate(AzeooDestination.Training.Workouts)
Destinations
Every routable training screen, as a subclass of AzeooDestination.Training:
| Destination | Shows |
|---|---|
Home | Training home |
Workouts | Workout plan list |
Exercises | Exercise list |
Progress | Progress |
Schedule | Schedule |
Detail screens are modal sheets
Workout detail and exercise detail are shown as modal sheets inside Flutter, not as routable destinations. The typed API intentionally does not expose Workout(id) or Exercise(id) — there's no Flutter route to navigate to. The previous showPlan(planId) and showExercise(exerciseId) methods accepted IDs but silently ignored them; the typed API makes this limitation explicit.
Examples
Open the workouts list
sdk.navigate(AzeooDestination.Training.Workouts)
Open progress
sdk.navigate(AzeooDestination.Training.Progress)
Go to the schedule
sdk.navigate(AzeooDestination.Training.Schedule)
Embedding the module
Fragment (XML / View system)
val trainingFragment = sdk.modules.training.getFragment(bottomSafeArea = false)
supportFragmentManager
.beginTransaction()
.replace(R.id.flutter_container, trainingFragment, "training")
.commitNow()
Compose
sdk.modules.training.ComposeView(bottomSafeArea = true)
Going back
sdk.back()
sdk.backToRoot() // back to training home
sdk.canGoBack { result -> /* Boolean */ }