Forge

Context

What I worked on

Forge is a private gym, nutrition, and physique tracker. I built it to make set logging feel immediate during a workout while keeping plans, food, measurements, photos, and reference media connected in one product.

Challenge

What the project needed

A workout tracker has to stay quick while someone is training, protect private health and media data, and remain honest when the network drops. The core flow could not make a failed save look successful or bury the next set behind desktop-sized navigation.

Approach

How I structured the work

I built Forge as a mobile-first Next.js PWA with Supabase Auth, PostgreSQL Row Level Security, and private Storage. It includes a durable offline queue for workout sets, a rest timer that survives navigation and reloads, reusable routine templates, and signed access to private exercise images and videos.

My contribution

What I was responsible for

• Built workout, nutrition, progress, journal, goals, settings, and routine-template flows
• Protected user data with owner-scoped PostgreSQL policies and private media storage
• Added queued offline set logging with clear waiting and retry states
• Designed and tested responsive workout flows for desktop and 390px mobile layouts

Tools and disciplines

How the work was made

Current status

Where the project stands

Forge is deployed as a live web application. Account access is required for the private tracking experience, and development continues as more real-world flows are verified.