CrossMute is a lightweight iOS and Android SDK that helps apps recognise when a user is approaching a pedestrian or level crossing.
Your app decides what happens next.
That might be a short audio cue, a temporary reduction in competing sound, a vibration or an on-screen prompt.
The user stays inside your app, under your brand, with no separate CrossMute experience to manage.
CrossMute is built around an expanding global database of pedestrian and level crossings.
That database is continually developed through a combination of open mapping, specialist datasets and partnerships with local data providers.
For app owners, this removes a significant part of the complexity.
You do not need to source, combine, clean and maintain crossing datasets market by market.
You do not need to manage multiple local data licences or work out which sources can legally be used in which territories.
CrossMute handles the underlying data relationships, licensing complexity and ongoing maintenance behind the SDK.
Your product receives a consistent crossing-awareness capability through a single integration.
CrossMute is particularly relevant to apps used during walking, running, cycling and public transport journeys.
A fitness app can prompt a runner approaching a road crossing.
A navigation app can add an extra safety cue during the walking part of a journey.
A family-safety app can add crossing awareness for younger or distracted users.
A rail app can recognise approaches to level crossings.
The intervention remains part of the host application rather than sending the user somewhere else.
Crossing detection can take place on the device.
The SDK can therefore provide its core safety function without requiring a continuous central record of the user's movements. Where an organisation needs analytics, consented and aggregated event reporting can be added separately.
CrossMute does not try to redesign the user's journey.
It identifies a moment when greater attention may be useful and gives the host application the opportunity to provide a simple safety nudge. No additional destination app. No separate user account. No new safety interface for your team to maintain.
The SDK licence includes access to the maintained CrossMute crossing database, SDK updates, compatibility maintenance and reasonable implementation support.
New datasets and improvements to the underlying crossing layer can be incorporated centrally, allowing customers to benefit without rebuilding their integration.
Bespoke features, custom data integrations and organisation-specific development can be commissioned separately where required.
CrossMute is designed to be integrated once and maintained with minimal ongoing effort.
The standard commercial model is deliberately simple: annual SDK licence, defined support, maintained crossing data and optional separately scoped development.
This keeps the relationship predictable for product teams and keeps CrossMute focused on maintaining the core safety capability rather than becoming a bespoke development agency.
If your users move through the physical world while using your product, CrossMute can add crossing awareness without asking them to leave it.
Request access to the SDK, technical documentation and evaluation package.