Regimen: A workout progression planning web app


Regimen is a side-project I’ve been building off-and-on for the past few months. It’s a web app that I’d originally created for myself out of frustration for the lack of options in helping me plan my workouts. Specifically, most weightlifting routines offer some form of downloadable Excel spreadsheet, but these are cumbersome to work with when at the gym. I found myself either fumbling with the Google Sheets app on my phone, or printing a paper copy of the spreadsheet – neither was a great solution.

The usability nightmare that is Sheets.

The basic idea behind Regimen is to bring some UX love to these spreadsheets. Just the same as with the spreadsheet, you can customize your “plan”, but instead of entering values into cells on a spreadsheet, you populate a web form tailored to the routine of your choice. Once you’ve created a plan, your workout progression is automatically generated. For each workout, the exercises and sets are clearly itemized, and it’s easy to navigate between workouts and resume from where you’d left off last time.

Here’s an example from my own plan.

While I’d found there are similar apps to mine, the upshot of Regimen is that (a) it’s a web app, so you don’t need to download (or even register) for anything, and (b) most apps target one specific routine, whereas Regimen is meant to be more generic. My preferred weightlifting routine is a bit obscure, hence my initial difficulty in finding solutions.


Of course, Regimen is also open-source:

As with most side-projects, I used this as an excuse to experiment with some new tools I’d been interested in using. Regimen is built as an offline-first single page application. Being offline-capable was important, as I get terrible cell service inside my gym. I also treated Regimen as a playground of sorts for ideas I’d like to consider applying in my day-to-day work.

PouchDB is largely to thank for making offline capability straight-forward to achieve. While it is connected to a remote CouchDB server for storage (via Cloudant), you can continue to use the application offline and it will automatically sync changes once internet connectivity is restored. This empowerment felt very magical (in a good way).

Building an offline-first web app meant to be used in the same way as a native mobile app proved to be quite challenging. Saving a website to the home screen in iOS sounds promising, but I found it to be pretty lacking (always resetting to the bookmarked link, showing only a white screen in app switch mode, cachebusting not taking effect until the next time the app is loaded). Similarly, configuring a web app to be offline capable requires implementing two approaches ([1], [2]), as a new spec have been defined but is not widely supported. Luckily, a Webpack plugin got me most of the way to where I need it to be, but to this day I’m still battling with fully comprehending service worker caching.


Maybe you’ll find the app useful, maybe not 🙂 In either case, it was a fun experience to build. In the future, I hope to add support for more routine options, including a “build-your-own” option that could potentially be used outside the context of weightlifting (e.g. running  distance progression).

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s