2025 · Full-stack developer
Get Fit!: Mobile Fitness App
A cross-platform iOS and Android fitness app I took from a blank whiteboard to a real release, with a ranking algorithm that turns your data into a workout plan built for you.
Where it started
Get Fit! was my first crack at the entire SDLC, not just “write the code,” but requirements, design, build, ship, repeat. Concept to a working prototype on iOS and Android.
What I actually built
- The personalization engine. This was the part that made me realize I needed to make a dedicated app in the first place, a study showing ideal ratios to train muscles in for improved long term health. USing that study as a basis I created a ranking algorithm in JavaScript that reads a user’s data patterns and spits out a workout plan that’s actually tailored to them, not a generic template with their name slapped on top.
- A real latency win. I profiled the app (properly, not just vibes) and found the slowest thing on the critical path was an external API call I didn’t even need. So I tossed it and moved that state on-device with React
AsyncStorageinstead. Turns out the fastest request really is the one you never make. - Design before code. Before I touched a single component, I mapped out system-flow and interaction diagrams to nail down the business rules and user journeys. Slower start, way fewer “wait, what happens if” moments later.
What it taught me
Shipping something to multiple platofrms is a different animal than shipping a demo with a language you’re comofrtable in, on a platform you constantly work with, with systems that you get to do all the fine-tuning for. But the bigger lesson was that performance work isn’t always about optimizing what’s there, sometimes it’s about deleting the thing that’s slow in the first place. Whether that be refactoring how I brainstorm and how I create my projects or whether that be about actual features in a product that in the moment seem like good ideas, but ultimately end up being more fancy tech than goood features.