Health, home and travel decision
TollTracker
A technical user can reproduce the core offline camera-alert experience in about a week, but the paid product's live community network, wide European coverage, and platform polish are nontrivial to replicate without the vendor's live data and user network.
View on the App Store↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$50one-off30 h to build
$15/mo3 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Continuously read device GPS, check proximity to known camera/zone geometries, and play a voice alert when approaching a hazard; provide an on-screen map and settings to tune alerts.
What it still won’t have
- Live community reports syncing from other drivers (real-time network updates)
- Automatically updated, centralized coverage across many European countries
- CarPlay, Live Activity deep integrations and polished multi-language voice alert tuning
- Polish, crash-hardened production behavior and App Store distribution history
What remains hard
- Network effects
a live network updated by drivers on the road keeps the map current.
First-year cost
No published price
TollTracker does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal iOS driving-safety app in React Native (or SwiftUI) with a Node.js + Express optional backend. Core features in scope: (1) import a provided CSV/GeoJSON camera & zone dataset into a local SQLite DB with R-Tree indexes; (2) continuous GPS tracking and speed calculation with battery-friendly intervals; (3) geospatial proximity detection that triggers configurable voice alerts and local notifications; (4) a map view showing current location and nearby cameras, plus a settings screen to tune alert distances and languages; (5) background location permissions handling and a basic optional backend endpoint to accept user reports (API only). Out of scope: building a crowdsourced realtime network, CarPlay, advanced localization beyond one language, paid subscription handling. Require error handling for permission denial, GPS loss, and DB errors; include unit tests for proximity logic and an end-to-end test for alert triggering.
How we checked
How the score was reached
- Partly verdict base52
- Hard moats found in the evidence-3
- Evidence score49
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 1
Every page the run actually retrieved.
- official productTollTracker: Speed Cameras App - App Store
Integrity checks
What held up, and what did not.
