← All projects

Case study

Repps — Fitness App

An offline-first workout tracker: ready-made plans, live set logging, PRs, streaks and muscle-coverage maps.

Product overview

Repps is a gym log for people who lift: follow a plan or log freely, track personal records and streaks, and see which muscles you have trained.

  • Ready-made workout plans and custom workouts
  • Live workout logging with rest timers, PRs and streaks
  • Body-weight tracking and muscle-coverage maps
  • A catalog of nearly 1,400 exercises with images
  • Progress sharing

Problem and solution

The problem

The loggers I tried were either cluttered or put basic tracking behind paywalls and logins. I wanted something fast at the bench that works without a connection and never loses a logged set.

The solution

Repps works fully offline from the first launch, keeps every workout on the device, and gets new plans and content in the background, without waiting on the network.

Design decisions

  • Fast logging between sets, with as little typing as possible
  • Content renders on the first frame from bundled data, with no loading spinners for core screens

Key screenshots

Engineering highlights

  • Offline-first data layer

    Flutter with Riverpod for state and Drift (SQLite) for storage. User data stays on the device.

  • Migrations that never lose a set

    Versioned, guarded schema migrations, because every update runs against real workout history.

  • Bundled content, background sync

    The exercise catalog and plans ship in the binary. Content sync from Supabase (plain PostgREST over HTTP) runs after the first frame and never blocks the app.

  • Admin without app releases

    A separate Flutter Web admin on Supabase publishes plans and content without an app release.

  • Remote config and subscriptions

    Firebase Remote Config for free-tier limits and kill switches, and RevenueCat for subscriptions.

  • Separate environments

    Dev and prod flavors, each with its own Firebase and Supabase project.

Development challenges

  1. Offline, but still fresh

    Keeping the app fully functional offline while still delivering new content.

  2. Never discard workout history

    Schema migrations that keep every logged set across updates.

  3. Store compliance

    Licensing and store declarations for exercise media, ads and tracking prompts.

Release status

Live on the App Store and Google Play.

Want something like this built for your product?

I take on freelance projects and collaborations, and I’m open to engineering roles.