Part 3 reshaped how a set is stored: plates, bodyweight, per-side loads, left and right, warm-ups and tempo. With that data in place, the next question was what the app should do with it during and after a workout.
The guiding idea came from my own training notes. I kept writing "+2 reps compared to last week" by hand. The app should be doing that comparison for me.
DotShredzilla is an Android workout tracker from FreeRave (DotSuite), open source under Apache License 2.0: github.com/kareem2099/Shredzilla.
Workout mode
Logging from a list worked, but mid-workout you want one screen that answers three questions: what's next, what did I do last time, and how long do I rest.
Start workout on a list opens a guided session:
- The current exercise, its target sets (from a program) and the sets done so far.
- Last time: every working set from the previous session of this exercise.
- One big button that logs the next set and starts the rest timer.
- Once the target is reached, the button becomes "Next: Leg Press", with "Log another set" one tap away.
Each new set shows how it compares to the matching set from last time: "+2 reps", "+1 plate", or "Same". When the load changed, the load difference wins over reps, because that's the change that usually matters.
Supersets link the current exercise with the next one. A set of the first exercise jumps straight to the second without rest; a set of the second starts the rest and goes back to the first.
A session isn't stored separately while it runs. It's simply every set logged since you pressed Start, which also means it works offline like everything else. When you finish, a summary is saved to users/{uid}/workouts, with duration, sets, volume, records and each exercise's best set, and it appears on a History page.
A progression hint, not a coach
The record sheet suggests the next step using double progression, a common approach: work up to the top of a rep range at a load, then add load and drop back down.
- Take the top set from the last session (warm-ups excluded).
- Below 12 reps: suggest one more rep at the same load.
- At 12 reps: suggest +2.5 kg (or +5 lb, or one more plate) at 8 reps.
It appears as "Try 60 kg × 11 · last session 60 kg × 10", and Use fills the values in. It's a hint. The app doesn't know if your shoulder hurts today, and the terms of use say so.
Personal records that survive beyond 90 days
History loads the last 90 days, so records calculated from that window would quietly reset over time. All-time bests are therefore stored separately in users/{uid}/records/{exerciseId}, one best per kind, because a plate count and a kilogram value aren't comparable.
Checking a new set looks at both the stored record and the loaded history:
fun checkRecord(history: List<LoggedSet>, stored: PersonalRecord?, entry: SetEntry, unitSystem: UnitSystem): RecordCheck {
val isPlates = entry.plates != null
val load = entry.plates?.toDouble() ?: displayToKg(entry.weight, unitSystem)
if (load <= 0 || entry.bodyweight || entry.setType == SetType.WARMUP) return RecordCheck.NONE
val storedBest = (if (isPlates) stored?.mostPlates else stored?.heaviest)?.load
val historyBest = history.filter { it.isPlates == isPlates && it.countsForRecords }.maxOfOrNull { it.load }
val previousBest = listOfNotNull(storedBest, historyBest).maxOrNull() ?: return RecordCheck.FIRST
return if (load > previousBest + LOAD_EPSILON) RecordCheck.BEATEN else RecordCheck.NONE
}
FIRST means there was nothing to beat yet. It's saved quietly, because celebrating someone's very first set as a "record" feels silly. BEATEN shows a banner and saves the new best.
Records started with this feature, so older bests are backfilled from loaded history. That only happens after the records snapshot has arrived; otherwise every best would look new. A Records page lists the bests, with a reset for the occasional mistyped 600 kg set.
Weekly goal, streak and deload
The weekly goal set during onboarding finally has a home on the Today tab: a progress ring ("3/4 workouts this week") and a streak of consecutive weeks that met the goal. Weeks start on the device locale's first day, which is Saturday on my phone.
I also wanted a reminder I actually follow: a deload week every six weeks or so, lighter loads and about half the sets, to let joints and the nervous system recover. The app counts consecutive training weeks. After six, Today shows a card suggesting a deload, and you can mark the week or dismiss the card until next week. It's advice, never enforced.
Marked deload weeks pause the streak instead of breaking it. Taking the recommended rest shouldn't cost you your streak.
Body measurements, with restraint
I track arms, forearms, thighs and calves on both sides, plus chest, waist and body weight. The Body page stores sessions in users/{uid}/measurements and shows:
- The latest reading of each site, the change since the previous one, and the right-vs-left difference.
- A trend chart for any site or side, including body weight.
- Plain-language insights from simple rules: weight up with the waist steady reads as lean gain; both up suggests some of the gain is fat; both down reads as fat loss.
The app encourages measuring weekly or monthly. If you measure sooner than your chosen rhythm, it gently notes that day-to-day numbers mostly reflect water and food. It accepts past dates, so older paper notes can be entered, and it parses Arabic-Indic digits typed on an Arabic keyboard.
These insights are heuristics on your own numbers. They're useful for spotting a trend and not meant to be anything more.
Sharing a workout
The workout summary is also a share card: brand mark, date, time, sets, volume, records and each exercise's best set. The card is drawn into a Compose graphics layer as it renders, so sharing snapshots exactly what's on screen. The image is framed on an opaque background first, because some apps turn transparent rounded corners black, then handed to the system share sheet through a FileProvider.
What made these features easier
- Most features are queries over the same set data. That only worked because Part 3 got the set model right.
- Warm-ups excluded in one place fixed counts, volume, records and suggestions together.
- Anything that sounds like health advice is phrased as a suggestion, and the legal pages say the same thing.
Part 5 covers getting all of this onto Google Play: a release-only crash, Play policies, legal pages in five languages, and cleaning up the Firebase project.
Which would you use most: last-session comparison, the progression hint, or deload reminders?
Google Play: DotShredzilla
Source: github.com/kareem2099/Shredzilla
Project: DotSuite



Top comments (0)