Why I'm building Rackd

The short version

I wanted a workout tracker for people who follow real programs, not another blank spreadsheet with a timer attached.

Rackd is built around a simple job: keep the program, the session, and the result together. It should tell you what to do today, record what happened, and make the next change understandable.

The thing I kept missing

I had used spreadsheets, notebooks, and plenty of workout apps. Most could log a set. Fewer could keep the program structure visible once training got busy.

A plan is more than exercise names. It has a week, a day, a target, an increment, and a response when the target is missed. Lose that structure and the lifter is back to doing the math between sets.

So I built the tool I wanted at the rack. The selected catalog has 15 programs, 448 exercises, and 11 progression systems. It is meant to give the lifter a real starting point, not make them author a system before the first session.

What Rackd does

Pick a program or bring one you already trust. Set the relevant training inputs. Rackd presents the session, keeps the rest timer and logging in reach, then records the result for the next prescription.

Coach is an anonymous software voice. It reports the program and training data, gives a next action, and stays away from medical or professional-coaching claims.

That is enough product for a workout tracker. The tool should know when to get out of the way.

The deal

Rackd is not a subscription app, and it is free today. Anything paid later will be a one-time purchase.

Referrals remain a viral-growth idea, but no reward is promised until the UI, service, deep link, and deployed state agree.

One more thing

I have made most of the usual programming mistakes. I have changed plans too quickly, logged badly, and lost training history during a phone move. Rackd comes from wanting fewer of those problems between one session and the next.

If you lift and something gets in the way, send it in. I read every reply at support@rackd.fitness.