The Challenge
What Spander Was Facing
Spander needed a navigation and mapping application that could route operators through London infrastructure with awareness of asset locations, restricted access zones, and operational constraints that Google Maps and HERE had no concept of. Generic mapping SDKs required Spander to maintain a costly parallel layer of business logic that constantly fell out of sync with the map data. Every time the underlying map provider changed an API, the integration broke and required emergency engineering effort.
The Solution
What We Built
We built a bespoke navigation application with a custom spatial data layer that held Spander's operational assets, access restrictions, and routing rules as first-class objects — not workarounds on top of a general-purpose map. The routing engine incorporated London-specific constraints including ULEZ zones, permit-restricted streets, and time-of-day access rules. The application synchronised with the operational database in real time so that asset status changes were immediately reflected in routing decisions.
Results