Repository navigation
0013 app and open database
Status: accepted · Implementation: planned · Date: 2026-11-17
docs/parity.md lists 'Social and community features' under Won't include, and the website repeats it. Both need a follow-up change to say that contributing data is in scope. The comparison with other projects is in docs/crowd-sourcing.md.
So far LibreLifts is only an app: a free 5x5 tracker (ADR 0003). The app needs reference data to grow past the six lifts of the program: exercises, how they are loaded, instructions, programs. No open source of that data is both large and clean. wger's is CC BY-SA but uneven, free-exercise-db's images have no known origin, and ExerciseDB and MuscleWiki are proprietary.
Projects such as MusicBrainz, Open Food Facts, OpenStreetMap and TheSportsDB show that a community will build and keep up a reference database when the data stays theirs to use.
- LibreLifts is two things under one name: the app, and an open database of lifting reference data that anyone can contribute to.
- The database holds reference data only. It never holds a person's workouts, body weight or any other personal data.
-
Its scope, in the order it is built:
- Exercises: stable ids, names and aliases, variations, muscles, equipment, movement pattern, how load is counted, instructions, translations.
- Media for exercises.
- Program templates that a machine can read, with their progression rules.
- Strength standards, derived from public-domain competition data (OpenPowerlifting).
- The app ships with a snapshot of the database. It works with no server and no account, as ADR 0005 requires.
- Contributing data is the only community feature. There is still no social feed, no following and no sharing inside the app.
- The app's data model has to refer to database records by their stable ids, so a newer snapshot can replace an older one without breaking a workout history.
- The project now has contributors of data, not only of code. They need licence terms (ADR 0014) and a way to contribute (ADR 0015).
- The database is useful to other apps. That is intended: it is how the project grows, and what the hosted API sells access to (ADR 0016).
- A database is a long commitment. Quality, review and moderation become ongoing work for a project with one maintainer.
Generated from docs/ on dev. Edit the docs there; changes made on the wiki are overwritten.
- The open database and the API
- Development
- Parity with StrongLifts
- Workflow
-
Decisions
- 0001 Decisions are recorded as ADRs
- 0002 Apache License 2.0
- 0003 Parity with StrongLifts, everything free
- 0004 iOS, Android and web
- 0005 Local-first; accounts and sync later through Spotcraft
- 0006 openweight for import and export, not for storage
- 0007 One Expo app, wrapped in Electron for desktop
- 0008 A pnpm workspace with app, desktop and core
- 0009 The website is static Astro in apps/website
- 0010 The website is hosted on GitHub Pages at librelifts.app
- 0011 docs/ is for developers and is mirrored to the wiki
- 0012 Changes land on dev by fast-forward; main is the last release
- 0013 LibreLifts is an app and a crowd-sourced open database
- 0014 The database is ODbL, media is CC BY-SA, and neither can be closed later
- 0015 Data contributions start as pull requests; a web editor comes later
- 0016 A hosted API with a free tier is the paid product