Embedded cockpit
OEM-themed map and navigation experience with platform, lifecycle, vehicle signal, audio and display integration.
AutoBuild your programDeveloper docs · SDKs & apps
Own the experience without rebuilding the location stack.
Choose modular SDK composition or a turnkey, OEM-branded application. The integration contract covers platform, HMI, data, vehicle signals, performance, updates and support.
Target surfaces
One route context across every approved screen.
Each target has its own interaction, power, performance and safety constraints. Shared identity and route state prevent the surfaces from disagreeing.
Android & Android Automotive
Map, search, route and navigation components integrated into OEM application and vehicle-service architecture.
iOS companion
Pre-trip planning, send-to-car, vehicle location, charging, service and last-mile continuity.
Web operations
Fleet, dealer, service, charging, engineering and command-center applications on Mappls map and API capabilities.
Projection & phone continuity
Program-supported Android Auto or CarPlay journeys, deep links and cross-device route context.
Cluster & HUD
Approved maneuver, route, speed, hazard and EV guidance rendered through OEM-owned glanceable surfaces.
Experience ownership
Two production patterns.
Both can use the same map, search, route and content foundation while assigning UI and release responsibility differently.
Turnkey OEM application
Start with a complete navigation or connected experience, then configure brand, surfaces, features, vehicle integration and lifecycle.
- ✓Faster coherent baseline
- ✓Defined Mappls application responsibilities
- ✓OEM theme, content and vehicle hooks
- ✓Feature flags and trim entitlement
SDK composition
OEM or Tier 1 owns the application and composes Mappls map, search, routing, navigation and tracking capabilities.
- ✓Maximum UI and application control
- ✓Modular capability attachment
- ✓OEM release train and telemetry
- ✓Explicit binary, API and support boundary
Integration sequence
A practical SDK workstream.
Sequence ownership and platform work before feature polish so the first vehicle build is diagnosable.
Baseline
Confirm SDK release, platform and entitlement; run the official sample on the target hardware.
Identity & content
Configure environments, credentials, region, map style, content version and offline territory.
Location & route
Integrate GNSS, approved dead reckoning, search, route profiles and route-state ownership.
HMI & audio
Apply OEM theme, interaction policy, voice prompts, audio focus, cluster/HUD and accessibility.
Vehicle & EV
Add approved speed, gear, energy, SoC, charging and diagnostic signals under validity rules.
Observe & validate
Capture versions, traces, crash, performance and update state; run weak GNSS, network-loss and proof routes.
Definition of ready
Questions the SDK evaluation must answer.
A demo is not yet an automotive integration.
Platform
Supported OS, SoC/GPU, architecture, display, input, platform services and model-year matrix.
Performance
Cold/warm startup, route time, render FPS, memory, storage, power, thermal and soak behavior.
Offline
Licensed territory, package size, resume, update, rollback and transparent degradation.
Diagnostics
SDK, map and voice versions; GNSS, route decisions, update status, errors and privacy-safe traces.
Release
Compatibility, deprecation, security support, issue intake, field correction and branch strategy.
Ownership
UI, telemetry, data, source/binary access, third-party licenses, support and acceptance.
OEM program workshop
Bring us the vehicle. Leave with the program shape.
Choose the surfaces, modules, deployment and lifecycle that fit your next RFQ. We will turn it into a focused discovery brief.