✳ Choose your perspective
← Back to projects

03 / FLUTTER · PRODUCT · LOCAL DATA

GYMy

Your training, in perspective

A personal app for planning routines, logging workouts and understanding progress. Built with Flutter, local persistence and an interface that adapts to different screen and text sizes.

MY CONTRIBUTION

Cross-platform product development

DATE

2026 · Ongoing development

DURATION

Personal project

TOOLS

Flutter · Dart · Hive · Provider

01 / CONTEXT

The challenge.

Making workout logging quick while retaining enough detail to review sessions, restore an active workout and compare progress.

02 / PROCESS

My contribution.

The app organises routines, exercises and sessions using Flutter and Hive storage. It preserves workout state, rest timers and sets, then uses the history to calculate records and generate local feedback. The feedback is based on rules and on-device data; it does not require a remote model.

  • Development of routines, session logging, progress and local persistence.
  • History analysis for records, suggestions and post-workout feedback.
  • Accessibility improvements, themes, scalable text and interaction flows.
03 / OUTCOME

What we built.

An app for Android, web and Windows with a calendar, set-by-set logging, timed extra activities and personal records. It includes visual themes, scalable text, accessible labels and a shopping list organised by category.

The value is in the details: restoring a session, reading a card with larger text or finding the reference from a previous workout.
04 / DECISIONS

Development decisions.

Log without starting over

The previous session provides a reference when entering weights and repetitions. The active session preserves exercises, sets, duration and rest so it can be resumed when the app reopens. Interruptions become part of the flow rather than a reason to reconstruct the workout.

Turn records into useful comparisons

History supports four reference values: maximum weight, repetitions, volume per set and an estimated one-repetition maximum. Suggestions consult the previous session and apply local rules. Feedback has a concrete basis in recorded data, and the estimate remains distinct from the weight actually lifted.

Local data and adaptable presentation

Hive stores information on the device while Provider connects state to the screens. The calendar, routines and progress offer different views of the same training history. Five themes and four text sizes adjust readability without changing the workout structure.

05 / WALKTHROUGH

The project in use.

  1. Build a routine from the catalogue and adjust exercises, sets and rest periods to match the training plan.
  2. Start a session, consult the previous reference and log each set. Rest remains visible on the exercise and in the session summary.
  3. Review the session in the calendar and inspect records for the exercises selected for progress tracking.
06 / EXPLORE

What to explore.

A way into the project through its screens, supporting material and, where available, its source code.

  • Restoring an active workout after closing and reopening the application.
  • The distinction between weight, repetitions and volume when reviewing records.
  • How cards adapt when text is enlarged or the visual theme changes.

THE PEOPLE BEHIND IT

Credits.

Laureano Cantó

Personal project · application development

NEXT PROJECT / 04

Horror between lines of C++