Why you keep re-explaining your injury to a fitness app
Most apps ask about your bad knee once, during setup, and never think about it again. Here's what to look for instead — and how to tell within a week.
Kelli and Jordan, Co-Founders, Aion Sculpts ·
Fitness apps forget your injury because the answer you gave during setup was saved as a profile field, not as a rule the programme has to obey. The app knows your left knee is bad in the same way it knows your postcode: it is stored, it is retrievable, and nothing that builds your week ever asks about it.
A setting is not a memory
Almost every app has an onboarding flow that asks the right questions. Any injuries? Any equipment? How many days? The questions are good. The problem is what happens next: those answers usually filter the initial plan, then sit inert while a template generates every week afterward.
You notice it in a specific way. Week one avoids deep knee flexion. Week four quietly contains walking lunges. Nothing changed on your end — the constraint just was not part of the thing doing the generating, so it decayed out of the picture.
What it costs you
Two things, and the second is the expensive one.
The obvious cost is friction: editing the same substitution every week, or mentally skipping an exercise each time it appears. Tedious, but survivable.
The real cost is that you stop trusting the plan. Once you have caught an app prescribing something it should have known to avoid, every session becomes something to audit rather than something to follow — and a plan you audit is one you eventually stop opening. Most people describe that as losing motivation. It is closer to losing confidence in the source.
What persistent memory looks like in practice
The test is not whether an app stores your constraint. It is whether the constraint shows up somewhere you did not put it.
- You mention a cranky shoulder on a Tuesday. The following Monday’s pressing work is already built around it, without you raising it again.
- You say you work nights. The plan stops proposing early sessions, including in weeks you never edited.
- You say you are lactose intolerant but aged cheese is fine. Milk disappears from every future meal; parmesan does not.
That last one is the clearest tell, because it is a rule with an exception. A checkbox can express “no dairy”. It cannot express the shape of how you actually eat, and an app that flattens the exception is one that will keep handing you food you have already said you do not want.
The one-week test
Whatever app you are using, this takes seven days and settles the question.
- Tell it one specific, slightly awkward constraint — not “knee injury” but “left knee, no deep lunges, step-ups are fine”.
- Do not mention it again. Do not edit anything.
- Look at next week’s plan in a slot you never touched.
If the constraint survived into a place you did not point at, the app is carrying it forward. If it did not, you have a settings screen with good manners — which is worth knowing before you build months of training on top of it.
Where Sculpt sits
This is the specific problem AION is built around. Constraints you state — injuries, schedules, food rules, equipment, preferences — are held permanently and applied to everything built afterward, rather than being consulted once at signup. Said once, honoured after that.
It is worth being precise about the limit, though: remembering an injury is not the same as understanding one. AION programmes around what you tell it. Diagnosing why your knee hurts is a professional’s job, and an app that implies otherwise is overselling.
If you are starting or coming back and have a constraint like this in the picture, the five-question planner will size a starting point around it.
Common questions
- Why do fitness apps forget my injury?
- Because most onboarding answers are stored as profile settings rather than as constraints the programme has to satisfy. The app records that you ticked a box, then generates each week from a template that never consults it. Nothing is broken — the answer was simply never wired to the thing that builds your sessions.
- Can any app really work around a bad knee?
- It can select movements that load the joint differently, which is most of what a thoughtful coach does when programming around one. What no app can do is diagnose the knee. Persistent pain, swelling, or anything that changes how you walk is a question for a physio or doctor, and no software should be substituting for that.
- How do I test whether an app remembers things?
- Tell it one specific constraint, then look at next week's plan without repeating yourself. If the constraint is honoured somewhere you did not point at — a different day, a different exercise slot — it is being carried forward. If you have to restate it, it was a setting, not a memory.
- What should I tell an app about an old injury that doesn't hurt anymore?
- Mention it anyway, with the current status: what happened, what still aggravates it, what is fine now. Old injuries change which movements feel good years later, and a plan built without that context tends to rediscover the problem for you.