Event Flow Examples
Typical orders. Every flow can include error_occurred at any point, and events you did not opt into are left out.
Workout or Plan workout:
1. kinestex_loaded - Page ready: send your launch payload
2. kinestex_launched - Payload verified
3. plan_opened (plans) and workout_opened - Detail page loaded
4. workout_started - The run begins
5. camera_selected, then person_in_frame (or check_frame_skipped) - Camera on, user positioned
6. left_camera_frame / returned_camera_frame - Whenever the user leaves and returns
7. exercise_completed then workout_progress - After each exercise
8. workout_ended - Session ends (exit_type says how)
9. workout_overview, then exercise_overview - Results screen
10. workout_session_saved and the upload events - Only when saving is on
11. workout_completed then plan_workout_exit_request - User leaves the results; KinesteX goes back to the workout or plan page
12. exit_kinestex - User closes KinesteX from that page
With includePoseData containing "events", each exercise also sends exercise_setup when it starts, then the real-time motion events (start_position_reached, successful_repeat and action per rep, feedback, mistake, presence and the rest) while it runs.
Custom Workout:
1. custom_workout_ready - Page waiting for your data
2. kinestex_launched - Payload verified
3. commit_screen_shown - Loading screen visible
4. speech_fetch_complete, then all_resources_loaded - Everything downloaded
5. workout_committed - Only with showCommitScreen
6. You send { workout_activity_action: "start" }
7. workout_started, then the workout events as above, up to exercise_overview (and custom_assessment_completed with isAssessment)
8. workout_completed then workout_exit_request (location: "statistic") - Close your view
Challenge Flow:
1. challenge_started - User tapped Start
2. workout_started - The run begins
3. exercise_completed then workout_progress - Exercise finished
4. workout_ended - Run over
5. workout_overview, challenge_completed, exercise_overview - Results screen
6. workout_completed then challenge_exit - User leaves the results
Camera Component:
1. kinestex_loaded, then kinestex_launched
2. models_loaded (and speech_fetch_complete) - Models for exercises ready
3. model_warmedup, then camera_selected - Pose tracking and camera ready
4. exercise_setup - For currentExercise
5. framing_hint (opt-in) and person_in_frame - Positioning check
6. start_position_reached, successful_repeat + action, feedback, mistake, presence, activity and the rest - While the user exercises
7. You switch currentExercise: exercise_change (totals of the previous one), then exercise_setup
8. You send "Workout Overview": exercise_overview, then workout_overview
9. You send "Stop Camera": stop_camera
Assessment Flow:
1. kinestex_launched - Application starts
2. camera_selected - Camera on; the user follows the on-screen instructions
3. assessment_overview - Results page loads with all metrics
4. assessment_completed - User taps Finish (or assessment_restart if they tap Restart). Close your view: Finish does not send exit_kinestex
If the user quits mid-test, you get assessment_exit instead, or assessment_exit_results followed by the results events above when the assessment shows what it recorded so far.