GMS is application for managing and handling gym memberships. Here you can find out what was the basic idea behind it, and how I decided to organize everything and create relationships between different things.

For technical details visit Github repo.

If you’re interested in some design prototypes, check them below. Everything is WIP, so some things or data might seem non-sensical. Most of things are very simplistic and will be refined, but I always like to start with the main features and requirements in my mind.

Here you’ll find screenshots of most of the pages. They are not yet implemented in code.

Some visual concepts:

Main definitions:

• members are the users that are coming to the gym
• team members are the people who are responsible for running the gym (owners, trainers, receptionists, or other staff members)
• plans are programs that allow members to train on their own while using the gym (can be recurring or one-time only)
• groups are programs that allow members to train under the supervision of a trainer (can be recurring or one-session only)

Main requirements

Members:

• members can only be added by team members
  • application is intended for gym owners and their teams, not the end users
• member must have at least one active plan or group program assigned and active in order to have active membership
• freezing member account would suspend all active programs
  • remaining days would be left intact, and could be used after reactivation of the account
  • if selected programs cannot be used anymore after reactivation, remaining days could be transferred to new program
• deleting user account would delete it permanently
  • personal details, memberships… would be removed
  • visitation logs/payment records? (still trying to figure out this one)