Planned
π’ Irregular rep sequences β define any reps-per-set pattern
Set up a preset where each set has a different rep target. 6-4-2. 10-8-6-4-2. 5-5-5-3-3-1. Any sequence you want. Current state: Repko already tracks reps per set during a workout β you can edit individual set reps in Rest Editor, Session Summary, History detail, and Manual Entry. CSV export already includes a "Reps Per Set" column with per-set values. What's missing is the ability to plan an irregular sequence upfront in a preset. Today a preset stores one rep target for all sets (e.g. "3 sets Γ 8 reps") β even though I'm logging per-set reps after the fact. What I plan to ship: New preset field: "Reps per set" β accepts a sequence (e.g. 6, 4, 2) Sets count auto-derived from sequence length (no more separate "sets" picker when this is used) Voice cues (VCER/VCFR) adapt to the target rep count for each set Editable on both built-in and custom presets Backward compatible: existing "3 sets Γ 8 reps" presets keep working as-is What this will not include (separate features): Auto-load increase per set (drop sets vs. ascending sets are separate concepts) Tempo changes per set AMRAP last set support Use cases this unlocks: Wave loading: 5-3-1, 5-3-1 Pyramid: 10-8-6-4-2 Reverse pyramid: 4-6-8 Cluster sets: 3-3-3-3 with shorter rest Strip sets / drop sets with rep changes: 8-12-15

Szymon SpΕawski 7 days ago
Low Priority
Planned
π’ Irregular rep sequences β define any reps-per-set pattern
Set up a preset where each set has a different rep target. 6-4-2. 10-8-6-4-2. 5-5-5-3-3-1. Any sequence you want. Current state: Repko already tracks reps per set during a workout β you can edit individual set reps in Rest Editor, Session Summary, History detail, and Manual Entry. CSV export already includes a "Reps Per Set" column with per-set values. What's missing is the ability to plan an irregular sequence upfront in a preset. Today a preset stores one rep target for all sets (e.g. "3 sets Γ 8 reps") β even though I'm logging per-set reps after the fact. What I plan to ship: New preset field: "Reps per set" β accepts a sequence (e.g. 6, 4, 2) Sets count auto-derived from sequence length (no more separate "sets" picker when this is used) Voice cues (VCER/VCFR) adapt to the target rep count for each set Editable on both built-in and custom presets Backward compatible: existing "3 sets Γ 8 reps" presets keep working as-is What this will not include (separate features): Auto-load increase per set (drop sets vs. ascending sets are separate concepts) Tempo changes per set AMRAP last set support Use cases this unlocks: Wave loading: 5-3-1, 5-3-1 Pyramid: 10-8-6-4-2 Reverse pyramid: 4-6-8 Cluster sets: 3-3-3-3 with shorter rest Strip sets / drop sets with rep changes: 8-12-15

Szymon SpΕawski 7 days ago
Low Priority
Planned
π₯ YouTube Shorts embedded per exercise β proper form, one tap away
For each exercise in Repko's catalog (1,083 total), link a curated public YouTube Short showing proper form. One tap from the exercise picker opens the embedded video. What I plan to ship: Curated YouTube Shorts mapped to exercises in Repko's library Tap-to-play inside Repko (YouTube embed β no leaving the app) Curated by me, not user-submitted (quality control) Public, embed-allowed videos only Rollout: I'll start with the most-trained 200 exercises and expand based on demand β covering all 1,083 at launch is unrealistic for a solo founder What this will not include: Hosted videos (no Repko storage cost, no moderation burden) User-uploaded content (no UGC moderation pipeline) Multiple videos per exercise (one good one beats five mediocre) Coach commentary or paid lessons Auto-play (you have to tap) Distribution mechanic: Video links will live in Repko's OTA-distributed exercise database (ex.dat), so I can swap or fix broken links without shipping a new app build. Why this matters: Repko has 1,083 exercises. Most users only know 50 of them by name. A 15-second Short showing proper form removes the "what does this lift even look like?" friction β especially for unilateral variations and eccentric-first lifts where the execution order isn't obvious from the name alone.

Szymon SpΕawski 7 days ago
High Priority
Planned
π₯ YouTube Shorts embedded per exercise β proper form, one tap away
For each exercise in Repko's catalog (1,083 total), link a curated public YouTube Short showing proper form. One tap from the exercise picker opens the embedded video. What I plan to ship: Curated YouTube Shorts mapped to exercises in Repko's library Tap-to-play inside Repko (YouTube embed β no leaving the app) Curated by me, not user-submitted (quality control) Public, embed-allowed videos only Rollout: I'll start with the most-trained 200 exercises and expand based on demand β covering all 1,083 at launch is unrealistic for a solo founder What this will not include: Hosted videos (no Repko storage cost, no moderation burden) User-uploaded content (no UGC moderation pipeline) Multiple videos per exercise (one good one beats five mediocre) Coach commentary or paid lessons Auto-play (you have to tap) Distribution mechanic: Video links will live in Repko's OTA-distributed exercise database (ex.dat), so I can swap or fix broken links without shipping a new app build. Why this matters: Repko has 1,083 exercises. Most users only know 50 of them by name. A 15-second Short showing proper form removes the "what does this lift even look like?" friction β especially for unilateral variations and eccentric-first lifts where the execution order isn't obvious from the name alone.

Szymon SpΕawski 7 days ago
High Priority
π₯ Community comparison β see how you stack up against other Repko users
For a given exercise, tempo, or eccentric stat β see where you land compared to other Repko users. Anonymous. Opt-in. Off by default. What it might include: Per-exercise: average weight Γ reps for your bodyweight category Per tempo signature: how many users train with 3-1-1-0 vs. 4-0-1-0 on a given exercise Eccentric leaderboards: longest single-set TUT, best eccentric ratio across sessions Your percentile within the cohort ("you're in the top 23% on Front Squat eccentric TUT") Why this is "Under Review" rather than "Planned": This is the biggest single change to Repko's identity since launch. Right now Repko is fully local: No account, no backend, no social features Analytics run with no persistent user profile Health-data handling is MHMDA-compliant (Washington state) The privacy policy is built around on-device-only processing Shipping community comparison means undoing some of that on purpose. It requires: A backend (auth, anonymous IDs, opt-in flow) An updated privacy policy that explicitly covers what gets sent Moderation if any user-visible names are shown Data-quality safeguards (one outlier with 500 kg squat at 14yo BW skews the cohort) What I want to hear in the comments: Would you opt in? (yes / no / depends on privacy) What would you most want to compare β weights, tempo, eccentric stats, consistency, something else? Public leaderboards or private percentiles only? If this gets strong signal I promote it to Planned and rework the privacy model. If it stalls below ~20 upvotes after 3 months I keep Repko fully local.

Szymon SpΕawski 7 days ago
Low Priority
π₯ Community comparison β see how you stack up against other Repko users
For a given exercise, tempo, or eccentric stat β see where you land compared to other Repko users. Anonymous. Opt-in. Off by default. What it might include: Per-exercise: average weight Γ reps for your bodyweight category Per tempo signature: how many users train with 3-1-1-0 vs. 4-0-1-0 on a given exercise Eccentric leaderboards: longest single-set TUT, best eccentric ratio across sessions Your percentile within the cohort ("you're in the top 23% on Front Squat eccentric TUT") Why this is "Under Review" rather than "Planned": This is the biggest single change to Repko's identity since launch. Right now Repko is fully local: No account, no backend, no social features Analytics run with no persistent user profile Health-data handling is MHMDA-compliant (Washington state) The privacy policy is built around on-device-only processing Shipping community comparison means undoing some of that on purpose. It requires: A backend (auth, anonymous IDs, opt-in flow) An updated privacy policy that explicitly covers what gets sent Moderation if any user-visible names are shown Data-quality safeguards (one outlier with 500 kg squat at 14yo BW skews the cohort) What I want to hear in the comments: Would you opt in? (yes / no / depends on privacy) What would you most want to compare β weights, tempo, eccentric stats, consistency, something else? Public leaderboards or private percentiles only? If this gets strong signal I promote it to Planned and rework the privacy model. If it stalls below ~20 upvotes after 3 months I keep Repko fully local.

Szymon SpΕawski 7 days ago
Low Priority
π Apple Watch companion with tempo haptics
A native watchOS app that mirrors Repko's 4-phase tempo timer on your wrist, with haptic feedback for each phase transition (eccentric β pause β concentric β pause). Why this is "Under Review" rather than "Planned": Building a great watchOS app is a 4β8 week focused effort for a solo developer. I don't want to commit publicly until I have a clear calendar window. What it would deliver: Start, stop, repeat the timer from the watch Haptic taps for each phase boundary so you can train with the phone in your pocket Phase status (current phase + countdown) visible on the watch face Live Activity / complication support so the timer is reachable from the watch face Why this is genuinely unclaimed territory: No competitor ships tempo haptics on the watch. Hevy and Strong both have watch apps, but they're set/rep loggers β you still need to look at your phone for tempo. A wrist haptic on every phase boundary means you can train with the phone on the bench or on the floor and never look at a screen. If this resonates with you, upvote it and I'll prioritize the timeline. Comment if you're already a watchOS user β that tells me how big the cohort is before I commit the build time.

Szymon SpΕawski 7 days ago
Low Priority
π Apple Watch companion with tempo haptics
A native watchOS app that mirrors Repko's 4-phase tempo timer on your wrist, with haptic feedback for each phase transition (eccentric β pause β concentric β pause). Why this is "Under Review" rather than "Planned": Building a great watchOS app is a 4β8 week focused effort for a solo developer. I don't want to commit publicly until I have a clear calendar window. What it would deliver: Start, stop, repeat the timer from the watch Haptic taps for each phase boundary so you can train with the phone in your pocket Phase status (current phase + countdown) visible on the watch face Live Activity / complication support so the timer is reachable from the watch face Why this is genuinely unclaimed territory: No competitor ships tempo haptics on the watch. Hevy and Strong both have watch apps, but they're set/rep loggers β you still need to look at your phone for tempo. A wrist haptic on every phase boundary means you can train with the phone on the bench or on the floor and never look at a screen. If this resonates with you, upvote it and I'll prioritize the timeline. Comment if you're already a watchOS user β that tells me how big the cohort is before I commit the build time.

Szymon SpΕawski 7 days ago
Low Priority
π― Per-exercise drilldown β full history, PR, TUT per single lift
Tap any exercise name from any screen β open a dedicated screen showing its full history, PRs, TUT progression, and tempo discipline trends β for that one lift only. Context: what Repko already has Repko v1.0 already ships extensive analytics: Charts tab: TUT Trend, Weekly Sets, Weekly Volume, Muscle Distribution, Volume by Muscle, Personal Records Your Data tab: Tempo, TUT, RIR, Consistency (lifetime) Per-session detail with full per-set breakdown (reps, weights, RIR per set) History filter with multi-select by exercise + cross-filtering with muscles So technically you can already filter History by "Front Squat" and see every session. What you can't do is open one curated screen per exercise that pulls all of that together. What's missing β and this fixes: A dedicated per-exercise view. This screen would give you: All sessions where you did this exercise, sorted by date PRs for this exercise specifically: max weight, max single-set TUT, max volume, longest set Weight Γ reps trend across all sessions of this exercise only TUT trend for this exercise only Your favorite tempo for this exercise + tempo-adherence average Lifetime totals: times trained, total volume, total TUT Why "Under Review": The data is already captured in HistoryProvider β this is a new view layer, not new infrastructure. Build cost is moderate (1β2 weeks for a polished version). The question is whether this beats Apple Watch and CSV Import on demand before I commit. Comment with which lift you'd open first β that tells me which exercises I should optimize the drilldown for (compound barbell lifts, isolation work, bodyweight progressions, etc.).

Szymon SpΕawski 7 days ago
Low Priority
π― Per-exercise drilldown β full history, PR, TUT per single lift
Tap any exercise name from any screen β open a dedicated screen showing its full history, PRs, TUT progression, and tempo discipline trends β for that one lift only. Context: what Repko already has Repko v1.0 already ships extensive analytics: Charts tab: TUT Trend, Weekly Sets, Weekly Volume, Muscle Distribution, Volume by Muscle, Personal Records Your Data tab: Tempo, TUT, RIR, Consistency (lifetime) Per-session detail with full per-set breakdown (reps, weights, RIR per set) History filter with multi-select by exercise + cross-filtering with muscles So technically you can already filter History by "Front Squat" and see every session. What you can't do is open one curated screen per exercise that pulls all of that together. What's missing β and this fixes: A dedicated per-exercise view. This screen would give you: All sessions where you did this exercise, sorted by date PRs for this exercise specifically: max weight, max single-set TUT, max volume, longest set Weight Γ reps trend across all sessions of this exercise only TUT trend for this exercise only Your favorite tempo for this exercise + tempo-adherence average Lifetime totals: times trained, total volume, total TUT Why "Under Review": The data is already captured in HistoryProvider β this is a new view layer, not new infrastructure. Build cost is moderate (1β2 weeks for a polished version). The question is whether this beats Apple Watch and CSV Import on demand before I commit. Comment with which lift you'd open first β that tells me which exercises I should optimize the drilldown for (compound barbell lifts, isolation work, bodyweight progressions, etc.).

Szymon SpΕawski 7 days ago
Low Priority
Planned
π Workout Plans β save session as template & replay last workout
Two simple actions, not a full program builder. I want to make it trivial to repeat a workout you liked or save a session as a template β without turning Repko into a programming app. What I plan to ship: "Save as template" button in Session Summary β reusable template appears on your home screen "Replay last session" β one tap to start the same session you did last time "Replay" pulls from your last completed session in History (with logged weights and RIR), not the last setup state β so you replay what you actually did, not what you planned Templates store: exercise, muscle group, tempo, sets, target reps, rest, direction, unilateral flag Templates live alongside your existing presets in the Exercise Library panel (not a separate section) What I am explicitly not building: A full program builder (5/3/1, PPL splits, nSuns, etc.) Multi-exercise workout chains (template = one exercise configuration, not a full session sequence) Periodization, deload weeks, automatic progression Pre-built programs from coaches Calendar-based scheduling Programmed load progression (no auto-increase of weight session-to-session) If you need full programming, Hevy and JEFIT do that well. Repko stays focused on tempo-driven sessions and quick replayability.

Szymon SpΕawski 7 days ago
High Priority
Planned
π Workout Plans β save session as template & replay last workout
Two simple actions, not a full program builder. I want to make it trivial to repeat a workout you liked or save a session as a template β without turning Repko into a programming app. What I plan to ship: "Save as template" button in Session Summary β reusable template appears on your home screen "Replay last session" β one tap to start the same session you did last time "Replay" pulls from your last completed session in History (with logged weights and RIR), not the last setup state β so you replay what you actually did, not what you planned Templates store: exercise, muscle group, tempo, sets, target reps, rest, direction, unilateral flag Templates live alongside your existing presets in the Exercise Library panel (not a separate section) What I am explicitly not building: A full program builder (5/3/1, PPL splits, nSuns, etc.) Multi-exercise workout chains (template = one exercise configuration, not a full session sequence) Periodization, deload weeks, automatic progression Pre-built programs from coaches Calendar-based scheduling Programmed load progression (no auto-increase of weight session-to-session) If you need full programming, Hevy and JEFIT do that well. Repko stays focused on tempo-driven sessions and quick replayability.

Szymon SpΕawski 7 days ago
High Priority
Planned
π₯ Import workout history from Strong & Hevy (CSV)
Bring your training history with you when you switch to Repko. Upload a CSV export from Strong or Hevy and I'll map your past workouts β exercises, weights, reps, dates β into Repko's history view. What this will include: Strong CSV format (the standard export) Hevy CSV format (Hevy itself only supports Strong imports β I plan to handle both) Exercise name matching against Repko's catalog of 1,083 exercises, with a fallback to map unknown lifts manually Unit handling (lbs / kg) and timezone-aware dates Per-set weights and reps preserved (Repko already tracks this granularity in CSV export) What this will not include (at least initially): Importing tempo data (Strong and Hevy don't track it β there's nothing to import) Importing RIR (same reason β neither competitor exports it consistently) Importing bodyweight percentage on calisthenics Reverse export from Repko back to Strong/Hevy formats Honest note on what gets lost: Strong and Hevy don't track tempo, eccentric/concentric phases, or RIR per set the way Repko does. Your imported history will have weight, reps, dates, and exercise names β but you'll start fresh on the tempo-discipline metrics in Repko's Your Data tab. If you're migrating from another tracker, comment with what app you're coming from β that helps me prioritize edge cases in the import (custom exercises, supersets, drop sets, etc.).

Szymon SpΕawski 7 days ago
High Priority
Planned
π₯ Import workout history from Strong & Hevy (CSV)
Bring your training history with you when you switch to Repko. Upload a CSV export from Strong or Hevy and I'll map your past workouts β exercises, weights, reps, dates β into Repko's history view. What this will include: Strong CSV format (the standard export) Hevy CSV format (Hevy itself only supports Strong imports β I plan to handle both) Exercise name matching against Repko's catalog of 1,083 exercises, with a fallback to map unknown lifts manually Unit handling (lbs / kg) and timezone-aware dates Per-set weights and reps preserved (Repko already tracks this granularity in CSV export) What this will not include (at least initially): Importing tempo data (Strong and Hevy don't track it β there's nothing to import) Importing RIR (same reason β neither competitor exports it consistently) Importing bodyweight percentage on calisthenics Reverse export from Repko back to Strong/Hevy formats Honest note on what gets lost: Strong and Hevy don't track tempo, eccentric/concentric phases, or RIR per set the way Repko does. Your imported history will have weight, reps, dates, and exercise names β but you'll start fresh on the tempo-discipline metrics in Repko's Your Data tab. If you're migrating from another tracker, comment with what app you're coming from β that helps me prioritize edge cases in the import (custom exercises, supersets, drop sets, etc.).

Szymon SpΕawski 7 days ago
High Priority