Understand the problem.
Fitness apps need to bring together several different experiences without making users navigate disconnected screens. This capstone explores an app structure for fitness activities and related tools.
MOBILE APP / CAPSTONE ↗
FitnessFlex✳
Making fitness features feel like one connected mobile experience.
PROJECT / MOBILE APP / CAPSTONE01 — OVERVIEW
FITNESSFLEX ●
GOOD MORNING
Keepmoving.WEEKLY ACTIVITY
Illustrative project visual · not an application screenshot
PROJECT OVERVIEW
A Flutter application built as a university capstone. The repository contains the app architecture, Firebase integration, navigation, workout interfaces and supporting fitness-related packages.
Design the approach.
The codebase uses Flutter for the interface, a central application router for navigation, and Firebase initialisation with optional anonymous sign-in. Dependency configuration also includes Firestore, image picking, charts, and camera/pose-detection libraries; a dependency being present does not on its own establish production feature completion.
03 / HOW IT WORKS
Behind the build.
Application boot
Initialises Firebase before launching the Flutter application.
Navigation
Uses a dedicated router and named entry route for screen flow.
Feature scaffolding
Separates screens, data, features and shared widgets within the project.
04 / MY ROLE
My contribution.
Part of a university capstone group project. I can demonstrate the architecture, application entry point and workout-related screens in the public repository. Individual contribution breakdowns should be confirmed before claiming sole authorship of a feature.
GO DEEPER
Explore the actual code.
These links lead to the source files used to verify this case study. No fabricated metrics or private workplace material.