Case study / SelfTrainer

SelfTrainer

Native rebuild in progress

SelfTrainer is an execution-first training system built to keep the lifter close to the planned work, the next honest action, and a trustworthy record of what was completed.

It is not designed to turn training into another dashboard to manage. It is designed to reduce friction before, during, and after the session.

The problem

The gym floor is an execution environment.

Many training tools are strongest before or after the workout. Active training asks for faster comprehension: what was planned, what has been logged, what changed, and what remains.

SelfTrainer reduces the distance between intention and execution, then protects the completed record so later changes cannot quietly rewrite the session.

Who it is for

Serious independent lifters who already train with intent and want a calmer system for planning, executing, adjusting, and preserving their work.

SelfTrainer is not primarily a social feed, a generic workout-content library, an entertainment-first fitness product, or a substitute for judgment.

Core gym-floor workflow

  1. Up NextThe current program determines what should be trained next.
  2. Start or ResumeA fresh session begins from planned values; an existing draft returns without reseeding or losing work.
  3. Execute planned setsPlanned work remains visible while editable logged values reflect what actually happens.
  4. Adjust honestlyThe session can change without rewriting the original prescription or corrupting historical truth.
  5. FinishCompletion writes once and hands off to the immutable history record.
  6. Preserve trustworthy historyCompleted sessions own their facts and do not silently change when routines are edited later.

Selected interface work

The interface evidence below comes from the mature SelfTrainer PWA, the current behavioral and persistence benchmark. The Native rebuild is translating these established workflows into a device-native experience.

SelfTrainer PWA home screen showing Precision Build as session two in the selected rotation, with a start action and a lineup comparing target work with prior performance.
Home / Up Next — PWACurrent-program authority turns the home screen into a clear next action while preserving target and prior-performance context.
SelfTrainer PWA session screen showing the second goblet-squat set, its target and previous result, editable weight and reps, completion controls, and a persistent rest timer.
Active Session — PWAPlanned and logged values remain distinct while completed sets and the persistent rest system support the gym-floor workflow.
SelfTrainer PWA routine editor showing Precision Force, with resistance, set, rep, load, and executable-set controls for two exercises.
Routine Editor — PWAAuthored targets and executable set structure remain related without collapsing into the same data.
SelfTrainer PWA rotation editor showing Ascend: Precision, the next routine, two following slots, drag controls, and routines available to add.
Program Management — PWARotation order, next-workout authority, and routine placement remain explicit rather than inferred.
SelfTrainer PWA completed training record showing session duration, sets, volume, best set, and exercise-by-exercise target and actual results.
History Detail — PWACompleted-session-owned facts preserve the original training record, including target, actual work, volume, and outcome.
SelfTrainer PWA profile showing intentionally published session and volume totals, July adherence markers, recovery adjustments, and accumulated record categories.
Profile / Plan Adherence — PWAConsistency, monthly adherence, recovery options, and accumulated training proof are presented without fabricating unavailable data.

PWA-to-Native evolution

The PWA proved what the product needed to do. Native is proving that the same rules can survive device behavior, interrupted sessions, touch interaction, and the trust demands of a real gym-floor workflow. This is not a visual port alone.

PWA establishedDaily-use product model

Personal use established the rhythm from current program to completed history.

Native is refiningGym-floor ergonomics

Touch targets, keyboard behavior, focus, and layout are tuned for the device in hand.

PWA establishedPersistence and authority

Programs determine sequence, drafts preserve active work, and completed sessions own their facts.

Native is refiningRecovery confidence

Interrupted sessions, resume paths, and navigation protection are hardened against loss or duplication.

PWA establishedExecution rules

Planned values, logged results, routine edits, and historical truth have distinct roles.

Native is refiningPlatform behavior

Gestures, safe areas, audio, haptics, and system behavior are handled where they apply.

PWA establishedPractical proof

The behavioral benchmark came from using the product for real training.

Native is refiningProduction hardening

Device verification, regression protection, and edge-case recovery prepare the core for future release.

Design and engineering decisions

Execution-first hierarchy

The next useful action receives priority over secondary analysis.

Planned versus logged facts

A prescription communicates intent; session data records execution. They remain related but distinct.

Immutable completed-session history

Later routine edits must not rewrite what a completed workout originally contained.

Draft persistence and safe resume

Interrupted sessions return as they were, without duplicated sets, reseeding, or lost edits.

Honest unavailable states

When data cannot be calculated reliably, the interface says so instead of inventing a zero or empty success state.

Restrained visual identity

Black, warm gold, strong typography, and limited motion support focus rather than compete with it.

Current development state

Current status

Native rebuild in progress

The product is mature enough to have a trusted behavioral reference and active native implementation, but it remains under development.

  • The PWA is stable and remains the behavioral reference.
  • The Native core gym-floor loop is built.
  • Routine editing, program behavior, adherence, recovery, and historical trust have substantial implemented coverage.
  • Current work emphasizes device verification, regression protection, recovery behavior, and production hardening.
  • No public release date is being promised.

Intentionally deferred

Deferral is part of the product strategy. SelfTrainer is being completed from the execution core outward rather than broadened before its central promises are dependable.

  • Social features
  • Coaching marketplace behavior
  • Excessive analytics
  • Novelty gamification
  • Broad integrations before the core loop is trusted