Book a call
Schedule a conversation about what you want to build
The onboarding and review steps below are team policy. SDK source verifies the integration primitives, not current curriculum priorities, review availability, or approval.
Why talk to us first
Curriculum gaps exist and must be prioritized. Before you build, we can tell you:- Which subjects and grade levels need coverage
- What content standards to align with
- Which learning approaches fit our model
- How to structure your app for Level 2 integration from the start
What this path looks like
1
Reach out
Book a developer onboarding call
to discuss what you want to build. We will share current curriculum priorities and gaps.
2
Align on scope
Together we define what your app will cover, which standards it aligns to, and how it fits
the Timeback ecosystem.
3
Set up your course structure
The Timeback team will help you create your course structure: courses, QTI content, and
PowerPath configuration. Confirm the currently available setup tooling during onboarding.
4
Build with Managed Lessons
The SDK’s Managed Lessons handle lesson
discovery, question sequencing, scoring, and time tracking. You build the UI; the SDK
orchestrates PowerPath, QTI, and OneRoster under the hood.
5
Iterate with feedback
We review progress and provide guidance throughout development.
6
Launch on Timeback
Deploy directly to Timeback’s distribution channels.
Level 2 Integration
New apps built for Timeback start at Level 2 integration. You use Timeback’s systems instead of building your own: The SDK’s approach to Managed Lessons brings these together into a single lesson runtime, handling lesson requests, sequencing, and activity tracking. Your app renders the returned content and handles the supported QTI interactions.Managed Lessons guide
Full SDK integration guide for delivering Timeback-powered lessons
Get started
Book a call
Schedule a call to discuss building a new app
Join the Discord
Connect with other builders and the Timeback team