Workout Journal

Workout Journal is built for my own use, not as a product for other people. It gives me one place to log workouts, track progress over time, manage custom exercises, follow templates, and look back through previous sessions.

Keeping years of workout history together makes it easier to understand my training without changing the habits and structure that already work for me.

I tracked every workout in Apple Notes for several years. It was a simple system that worked well at first, but eventually it became harder to find previous workouts, compare progress, organize exercises, reuse workout splits, and access everything cleanly across devices.

Rather than search for another workout app, I decided to build one that fits the way I train instead of asking me to adapt to someone else’s system.

The application is built with SvelteKit and TypeScript, using Supabase for PostgreSQL data, authentication, and cloud-backed persistence. Row Level Security keeps each user’s data scoped to that user, while Vercel handles deployment. Git and GitHub provide the version-control workflow behind the private project.

Building Workout Journal gave me practical experience designing relational data, working with PostgreSQL, setting up authentication flows, and applying Row Level Security. It also made cloud deployment and the shape of a larger application feel more concrete than they do in a series of smaller projects.

Because I use it during real workouts, feedback is immediate. Repeated use has helped me make better UX decisions around the details that matter when I am recording a set or checking a previous session.

Workout Journal is actively used and continues to evolve as I notice opportunities to improve it during workouts. Future iterations may explore additional themes, more useful statistics, greater customization, and continued refinements to the experience.