TwoMore
A training session becomes a record you can build on.
- Year
- 2024
- Discipline
- SaaS
The problem to structure.
A workout plan is only useful when it connects to what actually happens during training. TwoMore brings plans, sets, repetitions and weights into a session log, then makes previous results available for the next workout.
How the pieces connect.
The Next.js application uses Supabase authentication and PostgreSQL, with Zustand and TanStack Query supporting application state and data access. Plans connect to live session logging, exercise history and body measurements. The redesigned public site uses a barbell and training-log narrative to explain how individual sets become a longer record.
Below the interface.
01From a plan to a completed set
The product connects planned exercises with the weights and repetitions actually recorded. Previous-session values sit alongside the current workout to provide context while training.
02A record beyond a single workout
Session history and exercise history answer different questions. Body measurements add a separate record. The public walkthrough shows how these views relate without presenting its example numbers as customer outcomes.
03One application, connected data
The current code uses Supabase for authentication and database access. TanStack Query handles server data, while Zustand manages interface state. The homepage’s scroll storytelling is implemented with GSAP.
The system, made visible.
Workout planning, set-by-set session logging, previous-session comparisons, exercise history, an exercise library and body measurements in one web application.
A similar challenge?
An idea, a bottleneck, a system that has outgrown its tools. Tell us where you are.
Tell us about it