You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Proposal: full-screen route map, km splits, and GPX export for finished runs #37
Hi, I've been using OpenStrap and it's great. Before I open any PRs, I wanted to check whether you'd want these changes to the finished-run screen.
The Route card on a finished run is a small map. I couldn't open it bigger, see where each kilometre ended, or take the run out of the app, so I built this:
Full-screen map. Tapping the Route card opens the map over the whole screen, with pan, zoom, a Route only toggle (no tile requests) and a Fit route button.
Km markers and split highlight. Each kilometre ends in a numbered marker. A row of chips along the bottom, one per kilometre and matching the Splits list, lets you pick a stretch to highlight and zoom to.
GPX export. An Export button on the Route card shares the run as a GPX 1.1 file through the share sheet, with time, elevation and heart rate. Strava's web upload accepts it.
There are no new permissions or network use, and Strava upload and Health Connect routes are out of scope. I tested on a Pixel 9 Pro XL in portrait and landscape (screenshot below).
It's about 1,300 added lines, so I'd split it into two PRs: the map first (feat/fullscreen-route-map), then the export (feat/gpx-export).
Would you want this in the project, and is there anything you'd like done differently? The commits also include my spec and plan docs. I can drop them if you'd rather not have them in the repo.
I'll hold off on opening PRs until I hear from you.
Hi @ricaezejo , thank you for using my app and im glad you liked it.
Can you please hold it for day or two Im pushing major build so it's better to make sure it will be work with the changes :) I will gladly merge new features and yours seems great that i didn't think of.
ci: scan the release APK's libraries with OSV-Scanner, and raise Guava past an advisory #59: a dependency scan (OSV-Scanner) in CI, plus a Guava bump for an advisory it found in the release APK. Someone recommended more linting and QA tooling, so I tried it here. I kept it small and listed the rest (ktlint, mobsfscan, badges) in the description for you to decide on.
The dependency scan still requires testing. The others were tested on a real device, but before the version bump. The unit tests pass locally, but I haven't checked them on a phone or run them through CI here. I'll mark each one ready once I've done that. No need to look before then, unless you have early thoughts on the approach.
@sayed0am Sorry for the delay. #57 and #58 are ready for review. #58 sits on top of #57, so it's easiest to review #57 first. I fixed the detekt and lint failures and tested both on my phone. CI needs your approval to run on the new commits.
Activity
sayed0am commentedon Nov 6, 2026
Hi @ricaezejo , thank you for using my app and im glad you liked it.
Can you please hold it for day or two Im pushing major build so it's better to make sure it will be work with the changes :) I will gladly merge new features and yours seems great that i didn't think of.
sayed0am commentedon Nov 7, 2026
@ricaezejo now you can do the changes based on version 3 👍
ricaezejo commentedon Nov 8, 2026
Hi! I've opened three draft PRs. They're not ready to review yet, since I still need to review and test them more myself.
The dependency scan still requires testing. The others were tested on a real device, but before the version bump. The unit tests pass locally, but I haven't checked them on a phone or run them through CI here. I'll mark each one ready once I've done that. No need to look before then, unless you have early thoughts on the approach.
ricaezejo commentedon Nov 13, 2026
@sayed0am Sorry for the delay. #57 and #58 are ready for review. #58 sits on top of #57, so it's easiest to review #57 first. I fixed the detekt and lint failures and tested both on my phone. CI needs your approval to run on the new commits.
sayed0am commentedon Nov 13, 2026
@ricaezejo no worries take your time i approved CI again.