I'm a fitness and neuro professional building a RPG app that teaches you to read your own body — then wants you to leave

There's a gap I've been watching for years in my work as a fitness instructor.

People start. They show up. They do the work. But they don't understand what they're doing to themselves — when to push, when to back off, what sleep and stress are actually doing to their physiology, what their body is asking for the day after a hard session.

That gap isn't a motivation problem. It's a knowledge problem. And I couldn't find a tool that actually tried to solve it.

So I built one. With no development background, using Flutter and a lot of AI assistance — the exercise science and design decisions are mine, the code was a collaboration.

Here's what it actually does.

Every day, after a session or a sleep cycle or a stress spike, the app reads your wearable data — HRV, resting HR, sleep quality, step patterns — and classifies your physiological state in real time.

Then it presents three challenges.

Not hardcoded. Every minigame in the registry gets scored dynamically against your current state using a rule engine built on exercise physiology: system overlap penalties (same system you just stressed = lower score), recovery bonuses, parasympathetic activation value after sympathetic load, time-since-last-session decay, cumulative weekly fatigue. The result is three options that emerge from your actual biology that day:

• One resonant — fisiologically aligned with what your body actually needs right now

• One stable — neutral, safe, no particular signal either way

• One dissonant — working against your current physiology

Take Marco. Wednesday morning. HRV is 18% below his personal baseline. Resting HR up 6 bpm. 5.5 hours of sleep. The scoring engine runs — and the high system-overlap penalty tanks anything strength-heavy, while the recovery bonus lifts breathwork and slow movement to the top. His resonant option might be a slow walk or a breathing exercise. His dissonant option is probably a squat counter.

Marco picks the squats. Because he "feels fine."

His Guardian — Ferrum, the force tied to his strength stat — takes a small resonance hit. Not a punishment. A log. A record of the gap between what his physiology was asking for and what he chose. Over time, those logs become the lesson. His avatar's stats reflect his real training patterns, not his intentions.

A month later, Marco starts recognizing the pattern himself. When his HRV drops like that, pushing doesn't build. It breaks. Nobody told him — his body showed him.

The same logic runs in reverse.

After a sprint session, the engine reads high sympathetic load, CNS strain. Breathwork scores high — parasympathetic activation bonus, promotes recovery, no system overlap. More sprints score low — intensity stacking penalty, same system just stressed. The dissonant option that day might be another sprint. Or something else entirely, depending on Marco's week, his recovery trend, his step count for the day.

The options are never fixed. They're generated fresh each time from the intersection of your biology and every minigame in the system.

The part that gives people pause.

After roughly a year, you should understand your own patterns well enough that you don't need the app to tell you anymore. That's not a retention strategy. That's the explicit design goal.

If you want to stay — the community is there. Weekly duels against real people across five categories (Might, Agility, Vitality, Spirit, Presence). Cooperative Guardian challenges where two players face the same force from opposite aspects — one gets controlled strength, one gets explosive resistance; together they either defeat Ferrum or they don't. New minigames. A system that keeps evolving.

But you could also just leave. And that would mean it worked.

What I'm looking for.

I'm a fitness professional who built this alone. The physiology is solid. The codebase is real — Flutter, HealthKit, Health Connect, Apple Watch + Wear OS + Garmin, Firebase multiplayer, RevenueCat. But it needs someone who knows mobile development to take it further.

Equity and revenue share, no salary. If you've ever thought fitness apps were designed to keep you dependent rather than help you grow — this is the alternative.

Everything runs on your device. No accounts. No ads. No data collection. Your health data never leaves your phone.

Happy to share the codebase, the exercise science documentation, or just talk through the architecture.