Android / AAOS packages
Kotlin, Jetpack Compose, Android 35, Java 17 and deterministic domain tests.
AutoBuild your programDeveloper docs · application portfolio
Nine applications. Twenty surfaces. One evidence model.
Mappls Auto applications preserve source authority across cockpit, companion, fleet, field, rider, roadside and developer workflows. Every reference separates local intent, canonical acknowledgement and physical outcome—online, offline and under degraded evidence.
Platform evidence
Native where the lifecycle demands it. Responsive where operations need reach.
The repository binds each canonical APP product to build declarations, deterministic tests and a human-inspectable public flow.
Swift packages
Swift tools 6.0, iOS 17/macOS 14 declarations and XCTest targets.
TypeScript authority
Strict browser-control domain with ephemeral-secret and promotion boundaries.
Responsive public flows
Synthetic, mobile-ready experiences mapped one-to-one to the canonical catalogue.
APP-01 through APP-09
Authority, failure behavior and terminal boundary—product by product.
Each card states what the application may rely on, how it degrades and what the UI can never claim by itself.
APP-01Reference surfaces
Embedded Navigation
PlatformsAndroidAAOS
AuthorityQualified position, entitled content and exactly one active route revision
Offline & degraded- ↘Held position
- ↘Confidence suppression
- ↘Projection unavailable
- ↘Named cached content
Terminal boundary
Selection and projection do not activate a route, play audio, instruct a driver or control a vehicle.
APP-02Reference surfaces
Owner Companion
PlatformsAndroidiOS
AuthorityVerified owner/vehicle binding, effective capability and protected-intent policy
Offline & degraded- ↘Read-only cache
- ↘Intent pending
- ↘Result uncertain
- ↘Capability withdrawn
Terminal boundary
Intent, dispatch and acknowledgement remain distinct from physical vehicle execution.
APP-03Reference surfaces
EV Cockpit & Companion
PlatformsAndroidiOSAAOS
AuthorityFresh BMS evidence, a versioned energy model and one accepted EV plan
Offline & degraded- ↘Stale BMS
- ↘Charger warning
- ↘Reserve failure
- ↘Transfer pending
Terminal boundary
Prediction is not battery fact; plan transfer is not vehicle receipt, activation, reservation or payment.
APP-04Reference surfaces
AI Cockpit Assistant
PlatformsAAOS
AuthorityBound session, signed typed tools, entitlement and consequence confirmation
Offline & degraded- ↘Local grammar
- ↘Tool unavailable
- ↘Moving suppression
- ↘Interrupted
Terminal boundary
Model text and UI confirmation never become vehicle, partner, booking or emergency authority.
APP-05Reference surfaces
Fleet Operations & Evidence
PlatformsAndroid tabletResponsive web
AuthorityCanonical case revision, qualified evidence and accountable human disposition
Offline & degraded- ↘Queued intent
- ↘Revision conflict
- ↘Media unavailable
- ↘Off-duty privacy
Terminal boundary
Acknowledge, assign, review and resolve do not prove contact, dispatch, judgement or physical outcome.
APP-06Reference surfaces
Driver & Field Execution
PlatformsAndroidiOS
AuthorityCanonical assignment, role/duty policy and an acknowledged event journal
Offline & degraded- ↘Pending journal
- ↘Rejected event
- ↘Conflict
- ↘Moving suppression
Terminal boundary
Local intent, arrival and proof never silently advance canonical or physical state.
APP-07Reference surfaces
Rider & Passenger
PlatformsAndroidiOSDevice companion
AuthorityReviewed quote, canonical trip revision and trip-scoped pickup evidence
Offline & degraded- ↘Offline reconfirmation
- ↘Assignment pending
- ↘Pickup mismatch
- ↘Stale guidance
Terminal boundary
Booking, arrival, support and guidance do not prove dispatch, presence, response or rider action.
APP-08Reference surfaces
Roadside Workspace
PlatformsAndroidiOSResponsive web
AuthorityCanonical case, eligible provider, role-minimized data and source proof
Offline & degraded- ↘Queued observation
- ↘Stale revision
- ↘Provider unavailable
- ↘Proof rejected
Terminal boundary
Assignment and arrival evidence do not prove dispatch, repair, notification or emergency response.
APP-09Reference surfaces
Developer Console
PlatformsTypeScriptResponsive web
AuthorityExact project/environment revision, effective entitlement and signed conformance
Offline & degraded- ↘Masked credential
- ↘Trace blocked
- ↘Conformance blocked
- ↘Human approval pending
Terminal boundary
Request, credential intent and readiness do not grant entitlement, production access or promotion.
Cross-platform invariants
The same truth model from cockpit to pocket to control room.
Platform-native interaction never weakens the causal contract.
Causal state
Every transition binds identity, source, revision, policy and evidence before projection.
Offline truth
Pending, acknowledged, rejected, conflicted and uncertain remain separate states.
Source authority
Cache, push, model text, media and display wording cannot promote themselves.
Minimum data
Personal, vehicle and evidence data remain purpose-bounded and role-minimized.
Scoped receipt
A receipt proves only the named system decision—not a downstream physical outcome.
Program acceptance
Device matrix, security, accessibility, signing, HIL and OEM gates stay explicit.
Release boundary
Reference evidence is the beginning of an OEM release case—not its conclusion.
A target program freezes toolchains and contracts, then supplies the device, vehicle, partner, privacy, security and operational evidence this public reference cannot create.
Build & behaviorReference source, deterministic domain tests and declared platform targets
IntegrationApproved identity, credentials, generated clients, vehicle/partner adapters and recovery
Product qualityDevice matrix, accessibility, localization, performance and human-factors evidence
ReleaseSBOM, threat model, signing, distribution, telemetry, support and OEM acceptance
No inferred production outcome
All demonstrations use synthetic data. No screen, test or receipt on this site proves a real booking, dispatch, vehicle action, payment, repair, emergency response, partner action, production entitlement or OEM 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.