Combining strength, cardio, and mobility in one execution log
Learn how to execute and track strength, cardio, and mobility training within a single, structured workout log without losing modality-specific details.
Setline / Journal
Notes from
the product.
Practical guides, observations and updates. Written around what the app actually does.
Designing a Gym Interface for Limited Attention and Sweaty Hands
Learn how Setline designs a mobile-first gym interface prioritizing execution over coaching, optimizing for limited attention, sweaty hands, and offline use.
Designing progression recommendations that never silently change a plan
Explore the technical and design principles behind deterministic, user-controlled progression recommendations that preserve structured workout plans.
How a Do-Later Action Differs From Skipping an Exercise
Understand the mechanical differences between skipping an exercise and using the do-later action in a structured workout session, and how each affects your recorded history.
Offline-first workout execution for unreliable gym connectivity
Discover how an offline-first architecture ensures workout execution remains uninterrupted in gym environments with unreliable network connectivity.
Progressive overload when your workout plan changes week to week
Learn how to manage progressive overload when your training programme changes week to week, using deterministic recommendations and explicit data separation.
Recorded vs Calculated vs Unavailable Workout Values
Learn why distinguishing exact recorded sets from calculated estimates and unavailable data is essential for accurate, structured workout execution.
Safe export and preview-replace import for workout history
Learn how Setline implements versioned JSON export and validated, bounded preview-replace import for local workout history without cloud dependencies.
Scheduling multi-week training blocks with intentionally unplanned days
Learn how to structure 1–16 week training blocks that accommodate life's interruptions using intentionally unplanned days and rigid Monday-based scheduling.
What Useful Local Workout History Should Preserve
Discover why local workout history must preserve authored plans, separate actual execution from targets, and maintain honest measurement principles.
Why a programme-execution app should not pretend to be a coach
Explore the distinction between a dedicated programme-execution layer and algorithmic coaching. Learn why structured training requires precise tracking.
Why rest timing should come from wall-clock timestamps
Explore the technical and practical reasons why relying on wall-clock timestamps for rest timing ensures accurate execution, survives app interruptions, and builds a truthful training history.
Why starting a workout should create an immutable snapshot
Discover why workout tracking apps should use immutable snapshots. Learn how separating the authored template from the recorded session preserves data integrity and honest measurement.