From a Simple Rust Gym Log to an Offline-First Gym OS

This is a submission for the GitHub Finish-Up-A-Thon Challenge

What I Built

I built brawnbuild: an offline-first Gym OS designed for people who want to train with consistency, track progression, and not depend on internet or noisy social features.

Before Copilot helped me evolve this project, the idea was very simple:

• Build an app for my own gym sessions.


• Log workouts.


• Track evolution by muscle and exercise.


• Use Rust in the backend.

That was the original scope.

During this challenge, it grew into a polished product demo with:

• A Rust backend (Axum + SQLite) serving a local exercise catalog.


• A local-first data pipeline that consolidates heterogeneous exercise datasets into one unified source.


• Deterministic local import flow so demos are reproducible and resilient.


• Stronger web product narrative and presentation.


• Security and quality engineering upgrades (tests, CI checks, and coverage gates).

Demo

• Repository: https://github.com/lucasrafaldini/brawnbuild
  


• Suggested walkthrough:
  
  
  
  
  1. Run dataset consolidation from local sources.
  
  
  2. Import unified catalog into backend SQLite.
  
  
  3. Start backend and browse exercise endpoints.
  
  
  4. Show test, coverage, and security checks in CI.
  
  
  
  

The Comeback Story

This project is deeply personal.

I was coming back to the gym after an injury: tendonitis in my right arm. I needed something practical and reliable to rebuild consistency, control load progression, and know exactly what to do on the next training session.

The apps I tried had frustrating patterns:

• Many useful features were behind paywalls.


• Some pushed social-network style integrations I did not want.


• Several apps kept pushing products and recommendations instead of focusing on training quality.


• Most were not as detailed as MuscleWiki in terms of understanding exercise impact on each muscle.

MuscleWiki is excellent as a web reference, but it is not a complete tracking app for progressive overload and execution history.

My vision became: combine the best of both worlds.

• A detailed, muscle-aware exercise knowledge base feeling.


• A practical app that logs workouts, tracks load, and helps decide the next set and next session.

That is the comeback story: recovering physically, getting back to training, and building the tool I actually needed.

My Experience with GitHub Copilot

GitHub Copilot helped me go far beyond basic completion.

It supported me across product and engineering fronts:

• Expanded a personal MVP into a structured, demo-ready product.


• Helped redesign architecture toward local-first reliability.


• Supported implementation of catalog consolidation and import workflows.


• Helped improve security validation, including safer data handling and test scenarios.


• Accelerated quality hardening with better tests, coverage, and CI setup.


• Helped improve product communication, branding narrative, and documentation quality.

In practice, Copilot made me faster and more confident in each iteration, from backend internals to storytelling. What started as a simple Rust gym logger became a professional-quality comeback project.