Any system that puts team members on a map looks excellent in a demo. You open the app, the avatar snaps to the right place, the commander is satisfied. The problem starts three hours later, when the phone is in a pocket, the screen is locked, and the app is no longer on screen.
That is precisely when location matters most. And TacOps was built around that moment.
Why this is harder than it looks
Real-time location is not one feature - it is a chain. The device has to know where it is, the operating system has to let it work in the background, the app has to be alive or be woken, and the network has to work. One broken link breaks the whole chain.
And from there comes the real difficulty:
From the server, every kind of failure looks identical. A closed app, a partial permission, a dropped network - all produce exactly the same result: missing data.
That is why in TacOps every position on the map carries its age - and the commander always knows whether they are looking at now or at an hour ago. A picture that tells the truth about itself is the basis of every good decision.
These are the five questions any organization should ask about such a system - and our answers.
"What happens when the user closes the app entirely?"
Operating systems routinely close background apps - correct behavior, designed to protect the battery.
TacOps does not rely on the app staying open. It is built to come back to life in the background even after the app is fully closed, and to keep reporting without the user touching the phone. And we did not test that in a demo - we tested it on real drives, with devices that had been closed for hours, against what the server actually received.
"What happens when a user grants location only 'while in use'?"
iOS and Android distinguish "while in use" from "always". A user who granted the first sees everything approved in settings - but reporting stops the moment the screen locks. In many systems nobody knows, until the incident.
TacOps distinguishes the two states and shows them. Someone under partial tracking gets a clear explanation in the app - and the commander sees it in their force picture. With us, absence does not dress up as presence.
"What happens when a device has not reported for an hour?"
In TacOps every position on the map carries its age - how long ago it was reported - visible to the commander at a glance, with no clicking and hunting. A location record of someone who is no longer active does not linger: it is deleted from the server automatically. The map shows what is known and how fresh it is - not guesses.
"Who controls location publishing - the organization or the user?"
The most important question, and its implications are as legal as they are technical.
Every TacOps user has a location switch under their own control, on the main screen, one tap away. When it is off, the system stops writing their location to the server. Not hidden in the interface, not merely no longer displayed - it stops writing. The organization sets policy; actual control stays with the person. That is what separates a working tool from surveillance.
"Where is the data stored, and for how long?"
TacOps keeps the current position only - it does not accumulate a movement history. The point is replaced with every update, and the record of an inactive user is deleted automatically. Retention periods for every data type are stated in numbers in the terms, the server location is documented there explicitly, and there is a named data protection officer you can write to.
The bottom line
For us this is not a theoretical scenario - it is how the system works every day. Closed devices keep reporting, the commander sees how fresh every position is, and every user controls their own location.
An operational system is not measured by how much data it shows, but by how much of it can be believed. We built that trust first, and the map second.