Scopeable capability groups
AutoBuild your programNative application · integration blueprint
Build with Dealer, Service & Roadside.
Native application modules, generated domain clients, platform services and OEM design configuration. This page defines the public integration shape; exact endpoints, artifacts, signals, electronics, entitlement and release versions are program-specific.
Integration boundary
Start with authority, context and capability.
The application renders authoritative domain state and maintains only bounded local/offline state with explicit synchronization.
Adjacent integration domains
Program-selectable forms
Evidence boundaries
Contract families
Interfaces a production program must own.
Names describe the contract boundary. Current Mappls documentation and the signed OEM interface schedule remain authoritative for exact methods and formats.
Domain client
Generated typed models for current state, commands, events, errors and capability negotiation.
Platform adapter
Identity, secure storage, location, background work, notifications, biometrics and accessibility.
Journey handoff
Signed deep links or shared journey/route/trip identities with expiry and compatibility checks.
Experience configuration
OEM brand, modules, territory, role, HMI policy, language, analytics and support.
Delivery journey
From scope to supported release.
Configure
Select surfaces, personas, modules, languages, roles and platform versions.
Prototype
Run against synthetic state and complete every empty, stale, offline, error and unauthorized journey.
Integrate
Connect OEM identity, product APIs/SDKs, notifications, vehicle/partner and support boundaries.
Release
Prove accessibility, security, privacy, performance, lifecycle, store and target-device/vehicle behavior.
Canonical state pattern
Carry the evidence with the value.
The example is illustrative and intentionally product-neutral. It demonstrates version, freshness, quality and correlation behavior that remains stable across Mappls Auto domains.
- ✓OEM CRM/DMS, case, warranty and assistance systems
- ✓Connected vehicle diagnostics and precise location
- ✓Geoanalytics, workforce, route and notification services
- ✓Dealer/service resource and capability master
CapabilityAwareViewModel.kt
data class ProductState(
val capability: Capability,
val freshness: Freshness,
val value: DomainValue?,
val pendingAction: ActionState?
)
// Never map unknown or unsupported to a healthy default.
val canAct = capability.entitled &&
freshness.isWithinPolicy &&
pendingAction == nullUse source-controlled contracts and generated clients for the selected release.
Capability mapping
Turn scope into traceable interfaces.
Each enabled module receives a requirement, owner, contract, test environment, operational measure and lifecycle decision.
Network discovery
Find entitled dealer, service, charger and roadside resources using accurate entrances.
Incident intake
Capture vehicle, location, issue, safety and contact context with consent.
Resource selection
Choose capable resources using proximity, coverage, workload and service constraints.
Dispatch & ETA
Assign, route and track assistance with exceptions and communication.
Closure evidence
Record arrival, action, proof, tow/destination and customer confirmation.
Network analytics
Measure coverage, response, demand, failure and catchment gaps.
Release evidence
Validate the failure path—not only the first success.
Production readiness is attached to the chosen platform, territory, data, vehicle, deployment and lifecycle.
- ✓State-machine and offline reconciliation
- ✓Platform/device and OS compatibility
- ✓Accessibility, localization and large text
- ✓Identity, secure storage and sensitive-action step-up
- ✓Weak GNSS/network, process death and notification races
- ✓Analytics privacy and crash/performance release gates
OEM program workshop
Move Dealer, Service & Roadside from blueprint to integration plan.
Confirm the vehicle, users, territory, source systems, contracts, deployment, lifecycle and evidence. The result becomes a focused technical workshop.