Lion Fitness / supervised internship
An entire gym, in perspective.
Plans, payments and workouts connected in one management system. An academic project built from requirements to interface, with a professor’s guidance and review.
Explore the projectAccess to the application requires an account.
Enlarge imageCaptures from the academic environment. Personal and payment data removed; figures do not represent commercial results.
02 / Operations
From membership to payment.
A plan defines the subscription. PIX and card interfaces carry the payment flow forward.
Membership starts here.
Name, type and duration define the offer before payment.
These screens document the implementation. Real production payments have not been verified.
Enlarge image03 / Training
A trainer’s work, organized.
From following a member’s progress to choosing each exercise. Open a step to look inside the workflow.
Manage members
Member status and current workout-sheet access within the trainer’s workspace.
Enlarge imageBuild a workout
Exercises, sets, repetitions and rest brought together in one workout.
Enlarge imageChoose exercises
Search the catalog to choose an exercise for the workout.
Enlarge imageCreate an exercise
A custom exercise gets a category, equipment and execution instructions.
Enlarge image04 / Reports
Data that informs decisions.
System-generated reports make the member base readable by status and time period. These previews use the real documents, with personal data removed.
Enlarge image
Enlarge imageFigures belong to the academic environment, not an operating gym. The original PDFs are not available through these previews.
From specification to delivery.
I was the primary implementer during a supervised academic internship, with a professor providing guidance, reviews and corrections. The work covered requirements, modeling, database design, backend and frontend.
Java / Spring on the backend. PostgreSQL for persistence. Next.js, React and TypeScript for the interface.