Traccar Client is the reference app for the OsmAnd tracking protocol, available for Android and iOS, free and open source. It is well built and widely used.
It does not work with Geoblip yet. This page explains exactly why, so you can decide whether to wait or use something else today.
Traccar Client’s server URL is not templated. You give it a server address and port, and it constructs a fixed query string of its own:
/?id=<device>&lat=<lat>&lon=<lon>×tamp=<unix>&speed=<s>&bearing=<b>&altitude=<a>&accuracy=<acc>Geoblip’s ingest endpoint expects:
/api/ingest/coordinates?api_key=<key>&lat=<lat>&lng=<lng>&acc=<acc>The values are all there. Two of the names differ — id versus api_key, and
lon versus lng — and because the URL is fixed, there is no way to make the
app adapt. The fix has to happen on our side.
This is exactly the difference from GPSLogger and OsmAnd, which both let you write the whole URL yourself and therefore work today.
Accept id as an alias for api_key and lon as an alias for lng, and
ignore the extra fields. It is a small change to the ingest adapter, and it
would make Geoblip compatible with the entire OsmAnd-protocol client family
rather than this one app.
It is on the roadmap. No date is promised here, because a date on a marketing page is a promise, and we would rather say what is true.
GPSLogger if you are on Android. Free, open source, does one job well, and its named placeholders make the URL hard to get wrong.
OsmAnd if you are on iOS, or want offline maps and navigation in the same app.
Both take about five minutes to configure and work with Geoblip as-is.
Worth being straightforward, because a fair share of people reading this are comparing the two.
Traccar is mature, self-hosted, open source, and supports 200+ device protocols — far more hardware than we do. If you are already running a Traccar server and it works for you, there is no strong reason to switch.
Where Geoblip differs is that it is hosted rather than self-hosted, and it is built specifically around scheduled geofence alerting: per-device, per-zone active hours, and alert state that suppresses repeat notifications from GPS drift while still sending a recovery alert when a device returns. That is a narrower product than Traccar, deliberately.
If you want the protocol breadth and do not mind running a server, Traccar is a genuinely good answer. If you want geofence alerts without maintaining infrastructure, that is what we do.
Recorded now so this page is useful the moment the aliasing ships. Traccar Client exposes:
Set the app to unrestricted background usage on Android, and grant Always location permission on iOS, or reporting stops when the screen locks.
Compatibility last verified 7 August 2026. Manufacturers change firmware and command syntax — if something here is wrong, the device's own documentation wins.
Draw a boundary, assign your device, set the hours it should be active. Seven-day free trial.