When Traccar drops positions, your customers call you.
I build the apps, run the servers and write the protocol support for businesses that depend on Traccar. Apps on this stack are live in the App Store, and the work happens on your instance, so nothing of yours has to move.
The parts that cost you money
The dots stop moving
Trackers are reporting, the map is not updating, and the first you hear of it is a customer asking where their vehicle went. Every hour of that is a support call and a reason to look at another provider.
A device your server does not understand
You have stock of a tracker, or a customer who insists on one, and Traccar does not decode it properly. Hardware that cannot report is money sitting on a shelf.
Still running on the bundled database
H2 is fine for trying Traccar and wrong for a business. As history grows, reports slow down, and a corrupted file with no tested backup is the kind of day that loses accounts.
Alerts reach some users and not others
Geofence, ignition and overspeed alerts are what your customers pay for. When push tokens fail to register, they fail quietly, and only for some people.
The stock app is not your product
You sell tracking under your own name, and your customers open an app with someone else’s on it, missing the reports your business actually sells.
The system that fixes it
Flutter apps on Traccar
Fleet apps for iOS and Android from one codebase: live map, history playback, reports, geofences, alerts and device commands.
Server deployment and rescue
Traccar set up to run as a business: PostgreSQL instead of bundled H2, TLS, backups with tested restores, and monitoring that tells you first.
Protocol support
Custom protocol code for devices Traccar does not handle out of the box, so the hardware you already own can report to the server you already run.
Features your platform lacks
Custom reports, driver behaviour, fuel and sensor views, device commands and your own API endpoints, built around what your customers pay for.
The apps below are public and you can open them. The server and protocol work is not: it runs on clients’ infrastructure, so there is no link to show you. Ask on the call and I will walk through how it was done. Animmza is independent and not affiliated with the Traccar project.
Closest thing I've already shipped
Vision+
GPS tracking with dashcam video, in the App Store
Flutter · Traccar
Read the build →
EcuaGPS
Live vehicle tracking, in the App Store
Flutter · Firebase · Traccar
Read the build →
SmartTrackerz
Second GPS tracking app, same proven stack
Flutter · Traccar
Read the build →Asked before every build
Do I have to move off my current server?
No. The work happens on the Traccar instance you already operate. If it needs changing, that is a separate decision and you will hear why first.
Can you add a device Traccar does not support?
Usually, yes. Send me the device model, its protocol documentation if you have it, and a sample of what it transmits. I will confirm before anything is quoted.
Can you move me from H2 to PostgreSQL without losing history?
That is the point of doing it carefully. The migration is rehearsed on a copy first, and a restore is proven before the live server is touched.
Do you only work on the apps?
No. Server work can be the whole job: self-hosting, a VPS setup, upgrades, backups or running your own instance for the first time.
What does it cost?
Server and protocol work is quoted after I have seen the instance or the device. A focused app is $3,500 – $7,500, and a full platform starts at $9,000.
Twenty minutes, your morning, no pitch deck.
I work 8am – 12pm US Eastern and replies typically land within ~2 hours. Bring the problem, not a spec — the first call is scoping, and it is free.