LiftTrace

LiftTrace is finally public. The first release candidate is here as a self-hosted Docker image and a signed Android APK, sitting alongside its sister app NutriTrace under the TraceApps umbrella.

This is rc.1, not 1.0 GA. There are going to be bugs. There are going to be UX rough edges. There are going to be edge cases that nobody hit before this hit the open internet. The goal of the rc cycle is to surface those before stamping the final 1.0 tag, and the fastest way to get there is your help.

What’s In It

The full feature surface (see CHANGELOG.md for the complete entry):

• Diary with sets, reps, RPE, warm-up flagging, supersets, rest timer, Smart Add
• Programs & Templates with mesocycles, weekly schedules, starter templates
• Exercise Library seeded from wger and Free Exercise DB, plus your own custom exercises with uploaded images / GIFs / videos
• Statistics for volume, PRs, frequency, weekly heatmap, body weight trends
• Trace AI coach with live workout context (Claude, OpenAI, Gemini, or any OpenAI-compatible endpoint)
• Radio player for Subsonic / Jellyfin / Plex / Emby plus internet stations with now-playing metadata
• Coaching for trainer / athlete prescriptions
• OIDC SSO for Authentik, Keycloak, Pocket ID, Authelia, Auth0, Google, etc.
• Workout History Import from Strong, Hevy, FitNotes, and Jefit CSVs
• Android app with offline-first SQLite, biometric sign-in, native ExoPlayer playback, optional WorkManager reminders

How To Get It

Self-hosted Docker:

docker compose up -d   # pulls ghcr.io/traceapps/lifttrace:latest

Full setup walkthrough lives in DEPLOY.md.

Android: sideload lifttrace-1.0.0-rc.1.apk from the assets below. Release-signed with the TraceApps keystore (SHA-256 3a48b7ac46a2…fbbde4c6). The strict HTTPS-only policy is on by default; if you self-host on plain HTTP, see DEPLOY.md → Connecting from Android for the four supported paths (Let’s Encrypt, Cloudflare Tunnel / Tailscale Funnel, self-signed CA, or building the debug APK yourself).

Help Shape 1.0 GA

The point of the rc series is to ship something usable, find what’s broken, fix it, ship the next rc, repeat until 1.0 feels stable. That loop only works if real users hit real problems and tell me about them. If you find anything off, even small things:

• Bugs: open an issue with the bug-report template, especially anything that loses data, crashes the app, or breaks sync between PWA and Android
• Feature ideas: feature request for anything you wish were there
• Integration reports: if you import from a workout-tracker app or connect a music server, the integration test template helps catch parser quirks fast
• Translations: see CONTRIBUTING.md to add your language; the first pass for a new locale is around 30 minutes

The goal isn’t a perfect 1.0 from one person’s vision; it’s a 1.0 that holds up under real lifting routines, real gyms, real edge cases. Anything you report, even if it’s just “this button feels weird,” moves the date forward.

Thanks for being early.