timeback.lessons.* and the SDK handles the rest.
When to use
How it works
Your app renders the UI. The SDK manages everything else: discovering available lessons, serving questions, accepting answers, scoring, and tracking time. Under the hood, the SDK orchestrates two Timeback systems:
Time tracking is handled automatically. When a lesson starts, the SDK creates an activity tracker that sends periodic
TimeSpentEvent heartbeats.
The lesson lifecycle
A typical Managed Lesson flow has five phases:
The
LessonSession object returned by lessons.start() is the central runtime. It holds the starting attempt metadata, updates score after submission, and updates finalized after complete().
Caliper behavior
The SDK does not send an
ActivityCompletedEvent for Managed Lessons. PowerPath is the source of truth for completion, XP, and gradebook updates.
These operations delegate to PowerPath and return its progress. For linear lessons, check
finalized before displaying a completed result. The SDK catches finalization errors and re-reads progress, so a resolved promise can still return finalized: false. Adaptive completion returns the current score and marks the SDK result finalized; it does not itself establish that a mastery threshold was reached.Configuration
Managed Lessons require a Caliper sensor URL in yourtimeback.config.json.
See the configuration
reference for sensor
resolution rules and environment overrides.
Next steps
Lesson discovery
List available lessons and start a session
Question loop
Fetch questions and submit answers
Completion
Finalize scoring and interpret results
Attempt history
Review past attempts and per-question data
Reference
Parameters, properties, methods, and return types
Configuration
Full timeback.config.json reference
Getting started
Onboarding guide for building native apps on Timeback