Execution-first hierarchy
The next useful action receives priority over secondary analysis.
01 — The problem
The gym floor is an execution environment.
SelfTrainer is built around the active workout — not just planning it beforehand or reviewing it afterward.
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.
02 — 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.
For lifters who already know how they want to train and want a calm, reliable place to run and record it.
SelfTrainer is not primarily a social feed, a generic workout-content library, an entertainment-first fitness product, or a substitute for judgment.
03 — Core gym-floor workflow
From the next action to a record you can trust.
Open the app, see today’s workout, log what you actually did, and keep an honest record that never changes behind your back.
- Up NextThe current program determines what should be trained next.
- Start or ResumeA fresh session begins from planned values; an existing draft returns without starting over from the plan or losing work.
- Execute planned setsPlanned work remains visible while editable logged values reflect what actually happens.
- Adjust honestlyThe session can change without rewriting the original prescription or corrupting historical truth.
- FinishCompletion writes once and hands off to the immutable history record.
- Preserve trustworthy historyCompleted sessions own their facts and do not silently change when routines are edited later.
04 — Selected interface work
The PWA, in daily use.
These screens come from the web version of SelfTrainer in daily use today. The native app is being built from it.
The interface evidence below comes from the mature SelfTrainer PWA, the reference for how the app behaves and saves workout data. The Native rebuild is translating these established workflows into a device-native experience.
05 — PWA-to-Native evolution
Not a visual port alone.
The web app proved what SelfTrainer needs to do. The native app has to do the same things reliably on a phone, mid-workout.
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.
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.
06 — Design and engineering decisions
What the build holds to.
Three rules run through everything: show the next step first, keep what you planned separate from what you did, and never rewrite a finished workout.
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.
07 — Current development state
Native rebuild in progress
The web app works and is used daily. The native app is being tested and hardened, with no release date promised.
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.
08 — Intentionally deferred
What SelfTrainer won’t add until the core is solid.
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
Continue
The proof is the work.
SelfTrainer is still being built. The native product will be shown more fully when the evidence is ready.
Return to garrytipler.com Follow the build in The SignalDevelopment notes and future release information will be added here as the build progresses.