Feature idea for Locus Map: hourly low-power group checkpoints

vputewestvie shared this idea 16 hours ago
Gathering feedback

Hello Locus Map team,

I would like to suggest an optional Low-Power Checkpoint mode for Locus Live Tracking.

Locus already has group tracking, member profiles, location accuracy, altitude, chat and custom tracking services. A useful next step would be a mode for long hikes where users want occasional group location updates rather than continuous tracking.

Proposed behaviour:

- A fresh checkpoint is saved whenever the user opens Locus and requests their current GPS position.

- If the app has not been opened, it attempts a background GPS fix every 60 minutes, where the operating system permits it.

- GPS capture is independent of network transmission: the app saves every checkpoint locally but sends a batch to the group/server no more than once per hour.

- When offline, points are kept in persistent local storage and synced after connectivity returns.

- Each point retains its own timestamp and accuracy. The map shows the last known position and age of the fix.

- Sparse checkpoints are displayed as separate markers, not as an invented continuous track. The planned GPX route remains a separate layer.

This would fit well with Locus groups and custom tracking profiles. A configurable frequency (for example 30, 60 or 120 minutes) could make the feature flexible, with 60 minutes as the default.

Because iOS and Android may defer background work, the UI should show the real timestamp and stale status rather than promise an exact execution time.

Would you consider evaluating this feature for a future release?

I have attached an illustrative three-screen mock-up showing a group map, checkpoint history with offline sync status, and the distinction between a planned GPX route and actual saved checkpoints. This is a conceptual visual, not a screenshot of your current app.

Best regards,

Replies (1)

photo
0

Hello Locus Map team,

I would like to add a visual reference to my feature request #41800. I have collected the mock-ups and animations in this Dropbox folder:

https://www.google.com/url?q=https://www.dropbox.com/scl/fo/1lwyzwqbfmgcsfj9w32n8/AET523hYvKJ1yHfkdaIyR8A?rlkey=24mfanks8kfging5vz3aq0zut&dl=0&source=gmail&ust=1795113298762000&sa=E

There are 28 files, including map layouts, interface concepts and GIF demonstrations. A substantial part of the material was originally designed to show how low-power checkpoints and group location sharing could work directly inside Telegram. The same ideas could be adapted to Locus Map and Locus Live Tracking.

For Locus, the most relevant concepts may be a group map with each member's last confirmed position and timestamp, a separate checkpoint history, offline/synchronization status, and a clear visual distinction between a planned GPX route and actual sparse GPS checkpoints.

These are conceptual references, not screenshots of your app. Please feel free to use any of the ideas that fit your product direction.

Best regards

On Wed, Nov 18, 2026 06:55 PM, Locus Map <locus.map@asamm.com> wrote:

Thank You for Your Request


Hi, vputewestvie
Thank you for submitting request to Locus Map - help desk. Our support agents have received it and will review it shortly.
logo

Ticket URL: https://help.locusmap.eu/ticket/41800?access_key=53760-86e00315
Before you get a reply to your inquiry, you might try to find advice or a solution to your problem in the answers to the frequently asked questions of Locus users:

  • Do you need information about the Locus Map installation? Please look here >>

  • Does your request regard subscriptions or in-app purchases? Please look here >>

  • If you need advice on what to do if the app crashes or contains errors, please read >>

  • Do you need information about offline navigation, elevation data or similar topics? See >>

MY REQUESTS
Powered by UseResponse
This comment is in trash! Restore
Leave a Comment
 
Attach a file