Software 2.0 Historical Preview

Archived context for the DTT 2.0 preview, separated from currently verified dashboard and API behavior.

Historical preview, not current setup guidance

This undated preview described planned and staged behavior. Its enrollment promises, prospective features, limits, and channel availability are not treated as current facts. Use the dashboard controls offered to your account and Firmware updates.

Behavior verified in current dashboard/API source

  • The v2 settings API supplies templates as ordered segments and expands configured repeats.
  • The v2 calibration API stores per-toy calibration for the session owner.
  • The v2 completion API accepts Repetition, Endurance, Freeform, and Bounce results.
  • The completion API accepts pass/fail data and contains three-strike processing.
  • The dashboard exposes device-avatar selection for eligible accounts and firmware-channel controls for eligible devices.
  • The server resolves firmware dynamically instead of publishing one hard-coded version here.

These server capabilities do not prove that every firmware version or account receives the same UI.

Claims that remain unverified here

The checked-out repository does not contain the DTT firmware. Exact offline queue behavior, local capacity, retry timing, frame rate, per-version screens, current rollout percentages, and a guaranteed rollback path cannot be verified. See Offline mode for the conservative persistence boundary.

Video

Video transcript and current-status notes

The preview presents cloud-saved toy calibration, larger/repeated templates, depth scaling, toy assignment, pass/fail retries, device avatars, hands-free progression, session summaries, speed-oriented Freeform feedback, unified time-in-target scoring, and cached offline playback. It also presents several dashboard, customization, and offline-sync items as future work. Because the video is a preview, verify each feature in the current dashboard and on your own device before relying on it. The written sections above identify which related server behavior is present in the current repository and which firmware details remain unknown.

Current destinations

Archived and re-reviewed: August 16, 2026.

On this page