Running / cardio tracking with star rating (OpenTracks-style)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start by reading how an existing activity type is modelled, logged and shown across the History, Progress and weekly-goal screens, plus the code that already exports workouts as .fit — the issue names no files, so those screens are the map. The manual-logging-plus-stars slice described under Scope is the smallest shippable version; GPS and GPX/FIT import are explicitly later work behind a Settings › Beta toggle. Done means a run can be logged with distance, duration, pace and a 1–5 star rating, appears in History/Progress/goal, and exports to .fit.
Written by the indexing model from the issue text.
Description
Hi, and thanks for GymMane, I really like the offline, no-account approach.
Idea
Add a simple running (and maybe walking/cycling) activity type, inspired by OpenTracks, that fits GymMane's current style.
What I'd like
- Log a run: distance, duration, average pace
- A star rating (1–5) to rate how the session felt
- Show runs in History, Progress and the weekly goal
- Export runs as .fit for Strava, like workouts already are
Optional / later
- GPS recording (location only, no internet needed), behind a toggle in Settings › Beta so people who don't want the location permission aren't affected
- Import of GPX/FIT files recorded with OpenTracks, so GymMane doesn't have to reinvent tracking
Why
Many lifters also run, and it would be nice to keep everything in one private, offline app.
Scope
I know this could be big, so I'm happy to start with just the manual logging + stars version.
Thanks!
- Dominant language
- Dart
- Stars
- 844
- Forks
- 98
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 11
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from InlitX/GymMane
-
[BUG] JEFIT import fails because # characters are not recognisedPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
KeyboardOpen
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 42/100
InlitX/GymMane#394 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 25/100
InlitX/GymMane#392 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
bug enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
bug from-telegram platform:windows
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hiddify/hiddify-app#2592 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cogwheel0/conduit#1122 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bannzai/shoppinglist#779 ·
Maintainers usually reply within 1 day
-
Android bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PostHog/posthog-flutter#731 · 1 comment ·
Maintainers usually reply within 1 day