hi 👋
the Apple Watch app is not showing my heart rate in the top right corner where it’s supposed to. I can’t seem to find a setting to make that happen, what an I doing wrong?
In preparation for migrating the app from a webapp (like it is right now) to a native (React Native) app, I had to do a massive rewrite of the whole codebase. But the functionality stays the same. The only difference is graphs look slightly different (had to rewrite the graphs engine from the scratch).
I could introduce new bugs though! So, if you notice something broken/weird - please let me know!
Re Apple Watch integration- the Apple Watch does not recognize Liftosaur sessions as “workouts”. Is there any way to change this?
Is there a way to show time instead of reps on certain exercises, for example planks, dead hangs, etc.
Anyone else noticing the app has been sluggish lately?
Not sure if it's just me, been feeling noticeably slower over the past week or so.
There's a weird lag when logging sets sometimes couple of seconds before the rep/weight registers, when changing exercise the typing takes forever but that's not so new.
I'm on android with the latest version. My phone isn't the issue since everything else runs fine, and im not on battery saving mode.
Is this a known bug? Any fixes in the pipeline? Love the app overall, just hoping this gets ironed out soon because it frustrating standing sweaty after a set and get this crazy lag
I see that the General Gainz in liftosaur is pretty simple, basically increase weight until you can do 6 Volume Drop Sets after the rep max. However I bought the book and I got lost about half way in, the first few chapters are simple but it seems to keep explaining the methodology in different ways. Increase intensity, weight, reps, rest, 3/4 sets. Etc.
Is the program in liftosaur based on the book? Or just on the most simple version of the GG framework? Has u/ashtanov read the book? Maybe you'll know what I mean.
Hello, I am new to the app and was wondering if there is perhaps an easier way to auto-calculate the weight for backoff sets based on the top set weight. This is a fairly common programming strategy in powerlifting programs, where you work to a RPE-based top set and then perform backoffs at a lower intensity calculated based on the top set load (e.g., Squat 1x3 @ 7 RPE, 2x5 @ -16%). I came up with the following update function:
Squat / 1x3 @7 ?+, 2x5 ?+ / warmup: none / update: custom() {~
if (completedNumberOfSets == 1) {
var.repDiff = reps[2] - completedReps[1]
var.extraDrop = 0.03 * var.repDiff // due to rep difference between top set and back offs
var.baseDrop = 0.10 // minimum drop of 10% (if same rep)
var.percentDrop = var.baseDrop + var.extraDrop
var.backOffWeight = roundWeight(completedWeights[1] * (1.0 - var.percentDrop))
weights = var.backOffWeight
}
~}
It seems to be working, but let me know if there is an easier approach like that for absolute percentages.
A 3-day full‑body muscle building routine built with my evidence-based RP Hypertrophy progression logic for Liftosaur.
Goal: Prioritize growing glutes, legs, and defined arms while still training the entire body.
Three days per week. Start and end week with primary Buns & Guns days with 1 Glute Boost + Upper Body day in the middle.
Each day trains a mix of body parts with different emphasis.
All exercises begin at 2 sets, with autoregulated volume changes week to week via ratings feedback.
Rep ranges are 5-10, 8-12, and 10–15 depending on the exercise. Feel free to change to anything in 5-30 rep range based on preferences.
Recommend 1-2 days rest between training days. Good time for light/moderate activity like cardio/yoga.
These days revolve around:
These are your “meat and potatoes” days - the ones that provide most growth to the buns and the guns.
This day is intentionally lower‑fatigue and keeps training balanced:
Think of Day 2 as the “glute pump + upper‑body maintenance” day that keeps everything trained while still feeding the specialization.
This program uses my RP‑inspired autoregulated progression model. Week to week changes will generally be automatically handled by the program.
Here are the basics:
See the full RP Hypertrophy release post for info like basic usage, general features, rating guidelines, and troubleshooting.
Not sure if anyone else has encountered this. But the calendar seems to be stuck in April 2026 while the daily bar up top is correct.
iPhone 17 Pro
iOS 26.4.2
I just saw this ad today which made me wonder: how do you market the app nowadays? Is it still google ads mainly? I heard the reddit ads didnt perform well, are you marketing it elsewhere? Would be interested to know what works the best for you.
If i need to edit the weight for an exercise (different gym/equipment) its cumbersome to tap on every set and change the weight. Is there/ could there be an option to change the weight for every (following) set?
Hi! Long post, but I hope it'll be useful for others too.
My setup: I built my own program and implemented a custom Dynamic Double Progression that analyzes each set independently and determines next session's weight based on rep range completion, RPE, and the difference between completed and programmed weight. Link: https://www.liftosaur.com/p/f5e910d6
THE PROBLEM: Bodyweight exercises and e1RM
Bodyweight-component exercises aren't exotic — they're everywhere: Standing Calf Raise, Weighted Pull Up, Bulgarian Split Squat, Deficit Push Up, etc.
For these, I want to track total load on the muscle, not just added weight, because progression depends on bodyweight changes. I also believe the RPE table at https://www.liftosaur.com/blog/images/rpetable.png that Liftosaur uses under the hood (and presumably for rpeMultiplier) should be applied to total load. Two quick examples:
Bonus: this approach removes the need to split exercises into separate "assisted" and "weighted" versions — you can have band-assisted warm-ups, weighted working sets, and band-assisted drop sets all in one exercise.
I've been estimating the bodyweight fraction from sources like https://exrx.net/WeightTraining/Bodyweight or by direct measurement — for Deficit Push Up I literally put my hands on a scale in the exact position I perform the exercise. It's not perfectly precise, but precise enough for meaningful tracking. It works — but there's one painful UX issue: the app displays total load, while during the workout I only need to see the added weight.
CURRENT WORKAROUNDS — and why none are great
Custom equipment with bar weight = bodyweight × fraction — works, but every time bodyweight changes you have to manually update everything. Painful.
print() in the update block (e.g. print(weights[var.i] - state.bodyweightFraction * bodyweight)) — works for working sets, but warm-up sets are inaccessible in progression code, so those are left out.
Track only added weight, compute total load internally for e1RM — breaks warm-up weight calculations, and for sets where weight is derived from RPE or percentages, you'd get results based on added weight only, which defeats the purpose.
The documentation also shows an approach of modifying weights directly in the update block, something like:
/ update: custom() {~
if (setIndex == 0) {
weights = bodyweight + originalWeights[ns]
}
~}
I consider this unsafe. If you open the app, skip completing sets (where the progression would normally recalculate and reassign the weight back to total load), and then just finish the workout — next session you'd get the wrong weight. Not worth the risk.
If anyone knows a cleaner solution within the current app capabilities, I'd genuinely love to hear it.
SUGGESTIONS
1) Replace the Bodyweight for bar checkbox with a bodyweightFraction percentage field (small change, low risk)
This was already suggested 10 months ago: https://www.reddit.com/r/liftosaur/comments/1lhree7/comment/n3sck8a/
As an Android dev myself, I'd guess this is a relatively small change that wouldn't break anything for existing users. The checkbox behavior would just be a special case of fraction = 1.
2) Make bodyweightFraction an exercise property rather than equipment (more correct architecturally)
Using equipment to encode a bodyweight fraction is really a workaround — ideally equipment should match your actual equipment. If bodyweightFraction is 0, nothing changes for existing users. If set, it gets included in e1RM calculations, and the weight hint shown during workout becomes weights[var.i] - bodyweightFraction * bodyweight. Negative weights for assisted exercises would stay consistent throughout. More work to implement, but cleaner.
3) Add weightsHint / repsHint variables (most flexible)
Decouple the weight used in calculations from the weight shown to the user. weightsHint = weights by default; progression programmer can override it to show whatever makes sense — in my case, just the equipment weight. Would need to be accessible for warm-up sets too.
None of these would affect existing users in any breaking way — they only expand what's possible.
One more thing — a couple of smaller issues I ran into that are worth mentioning separately.
On the bug side: I hit a weird one with using a custom progression inside a template. Here's the example:
t1_moderate[2-7] / used: none / 1x3-5 240s (Top Set), 1x8-10 u/9 120s (Back Off) / warmup: 1x8 50%, 1x5 70%, 1x2 90% / progress: custom(bodyweightFraction: 1) { ...ddp } / update: custom() { ...ddp }
moderate: Triceps Dip[2] / ...t1_moderate
The bug manifested as lines of the program itself swapping places — the custom progression was fine, but the program/template structure got corrupted, causing the program to behave incorrectly and unpredictably, with no syntax error highlighted anywhere. It's possible the issue was with t1_moderate without [2-7] — I don't remember exactly anymore. I also reproduced what seems to be the same bug when adding General Warm-up[0,1-8], which makes me think it might be related to exercise index 0 specifically.
On unexpected behavior: the "Previous Set" tab shows results for the exercise globally across all labels, not per labeled variant. If I have moderate: Triceps Dip, heavy: Triceps Dip, and deload: Triceps Dip, I'd expect to see previous results for the same variant I'm currently doing — not a mix of all three. The global history is already visible by just scrolling down anyway, so the tab feels like it should show something more specific.
u/astashov: is suggestion #1 something we might see at some point? 🙂
I've been trying really hard to get this sort of programming to work:
Day 1: Squat / 1x5 130kg, 2x5 at 90% of topset
Day 2: Squat / 2x5 at 70% of Day 1 topset weight
Day 3: Squat / 3x5 at 80% of Day 1 topset weight
I wont bore you all with failed script that I used AI to build, has anyone had success at this?
As a future feature it would be awesome if you could do % based weights not based on 1RM but based on topset, kinda like the logic in the warmup percentages.
Having issues inputting weight on per sets during workout. I can in put the number but doesn’t let me hit the check mark or anything else. I’ve been able to work around it by hitting the max rep calculator and hitting back.
I’m on iPhone 13 Pro Max so it might just be my outdated phone.
I'm 6'4, 190lbs, 36 y.o. male. Been lifting for about 15 years, a couple years on, 6-8 months off roughly. Finally starting to see some progress over the past 5-6 months and looking to fine tune my program. I've got 4 days a week, 1ish hour per day in the gym. I'm shooting for a reasonable balance of strength and hypertrophy gains.
Nutrition is pretty good. I can easily eat a clean 3k calories a day, 180-200g protein.
Link here: https://www.liftosaur.com/p/735d19ea
I know it's chest and shoulder biased for upper body, those are my low points right now. Any thoughts?
Hi,
is there a way to check the strength increase every month for exercises ? Usually is displayed as % change of 1RM.
Hi,
I'm currently building a personal fitness dashboard that consolidates all my health and workout data in one place. To avoid manual data entry, I want to pull and push bodyweight data programmatically.
Does Liftosaur offer any API endpoints for bodyweight data? Even undocumented ones would be useful to know about.
Thanks!
Hello, currently, if my target reps are say, 10-20, every time I click into the reps input box, it defaults to 20. I prefer it to default to the lower value in the range. Is this possible to configure in any way?