Device application
Own process supervision, UI or service behavior, hardware integration, storage, and observability.
Kiosks, industrial systems, and embedded navigation
Linux
Run location and navigation reliably on controlled, embedded Linux systems.
CC++
Recommended boundary
How the pieces fit
Native mapping and routing runtimes for controlled devices and embedded systems. Use this boundary as a starting point, then narrow it around the exact Mappls products and trust model your application needs.
Mappls native runtime
Load entitled libraries and compatible map or routing data for the target architecture.
Provisioning and updates
Activate devices, stage signed artifacts, switch versions atomically, and preserve rollback state.
A safe first integration
From empty project to one real journey
Each step produces a testable boundary. Keep the first release deliberately small, then expand from observed product behavior.
- 1
Define the target
Record architecture, ABI, libc, graphics stack, storage, memory, sensors, and connectivity constraints.
- 2
Validate the bundle
Match runtime, compiler, data format, license, and device activation before application integration.
- 3
Build a supervised lifecycle
Handle startup, health, corrupted data, expired activation, resource pressure, and clean shutdown.
- 4
Prove field updates
Test resumable download, signature verification, atomic switch, rollback, and power interruption.
Capabilities on Linux
2 product families
2 of these families include durable or session state. Follow their complete lifecycle guidance rather than integrating only the first successful call.
Auditable implementation evidence
SDKs, APIs, distributions, and samples
Every item below is generated from a public Mappls repository and links to its source-grounded guide. Maturity labels distinguish current material from samples, distributions, legacy sources, and deprecated integrations.
No public repository is classified specifically for this platform.
The product and architecture guidance remains useful, but implementation requires the entitled private distribution and its corresponding local source documentation. The page intentionally does not relabel an unrelated public repository as evidence.
Learn by building
Platform tutorials
Start with one focused result, then move into complete stateful journeys and operational failure handling.
Before launch
Production readiness
Pass these checks in addition to the requirements of the selected product, SDK release, operating system, and security program.
- Runtime and data compatibility is enforced
- Device identity and activation can be rotated
- Updates are signed, resumable, and reversible
- Health and resource telemetry survive application restarts