
MDK: location for mobile applications
Bring indoor and outdoor location into your Android and iOS apps. MDK helps you create experiences that guide people through spaces by combining smartphone sensors and keeping location available when connectivity is limited.
Make location part of the experience
A useful location is more than a dot on a map. It helps an app understand the building and floor, follow movement and deliver the right service at the right place. MDK brings these capabilities into mobile applications, so you can focus on what people need: wayfinding, relevant content or location-aware services.
Explore the MDK overview to see how it fits into your product.

Location that follows the context
Inside a building, MDK updates the position as a person moves and detects floor changes. In projects that also cover outdoor spaces, it can support the transition between indoor and outdoor environments. It combines movement, radio signals, magnetic data and, where applicable, camera input to maintain a coherent estimate across different conditions.
The localization guide explains supported scenarios and the events available to your app.
Continuity when connectivity is limited
Location can keep working offline once activation is complete and the required data is available on the device. This matters in buildings with uneven coverage and in services that need to remain usable as people move.
The data to prepare and the loading strategy depend on your environment. We can validate the choice on the devices and in the spaces your project will use. See the MDK requirements for technical details.
Android
Review the devices and sensors planned for the project.
iOS
Check compatibility with your target devices.
Validation
Test location in the real spaces where it will be used.
Integration shaped around your project
MDK supports Android, iOS and Kotlin Multiplatform projects. We can help you choose a configuration that fits your devices, environments and accuracy needs. The installation guide covers dependencies and setup steps.
Define the experience
Identify the spaces, users and features that need location.
Check the context
Review devices, sensors, maps and connectivity.
Test in the field
Validate the app in real spaces before release.

Prepare the service
Activation, permissions and data availability shape the experience. They should be planned around the devices and spaces where the app will be used. The initialization and permissions guides cover implementation steps.
From position to service
Location updates can drive the app interface or a tracking service, depending on the flow you choose. For data behavior when a connection is available or absent, use the tracking guide.
Bring location into your app
Tell us where it will operate and the experience you want to create. We will help define the integration path.