From manufacture and activation through recovery and retirement.
Offline navigation · automotive release engineering
One bootable map stack at every checkpoint.
Treat runtime, map data, configuration, voice, target compatibility, activation, and qualification as one governed release. Keep public product evidence, local SDK generations, protected artifacts, and vehicle safety proof rigorously separate.
The inactive release is verified and staged before one atomic pointer switch.
Compatibility, power loss, regression, expiry, replay, restart, and retirement.
No credential, key, license, package URL, binary, map data, or artifact body is accepted.
Evidence before syntax
The product family is public. The runtime contract is entitled.
The public Mappls organization advertises NaviMaps SDK APIs for hybrid embedded navigation and the public Android index names NCASE, NaviMaps, and Navigation SDK families. The reviewed public snapshot does not establish the production automotive runtime, package, activation, compiler, vehicle-interface, or safety contract.
Local repositories contain a newer Telecons engine line with map, search, route, simulation, GPS, voice, traffic-event customization, and 2026 release evidence; a separate legacy Hybrid Android SDK; and sparse earlier Linux/navigation repositories. These generations are adjacent evidence, not interchangeable SDK syntax.
Four evidence generations
Do not paste one generation's API into another.
Each row says what the reviewed source establishes—and what remains contract selection.
Public product surface
github.com/mappls-api and developer.mappls.com- NaviMaps embedded/hybrid navigation family
- NCASE and Navigation SDK family names
Product discovery evidence only; obtain the entitled edition and exact contract before implementation.
Telecons engine line
local/mappls-telecons-offline-sdk- Map rendering
- Offline and online route planning
- Search and nearby
- Simulation
- GPS state
- Voice guidance
- Traffic-event customization
Local implementation evidence dated through March 2026; not a public redistribution or compatibility promise.
Hybrid Android line
local/offline-sdk- Region download
- Offline/online mode switching
- Map lifecycle
- Offline map/search/route concept
Legacy MapmyIndia 0.0.1 documentation exposes app-held credential patterns that must not be copied into a current architecture.
Earlier embedded lines
local/linuxsdk-dev1, linuxsdk-dev2, mapmyindia-navigation-sdk- Repository identity
Sparse READMEs do not establish symbols, versions, compatibility, or readiness.
Application-owned release lifecycle
Seven accountable phases. No “installed” shortcut.
Every phase names the owner and the evidence required to advance the durable device-release aggregate.
Manufacturing system
manufacture
Unique hardware, vehicle, edition, target CPU/ABI/OS/graphics, and manufacturing batch identity.
Fleet release manager
activate
Non-secret entitlement reference, edition, regions, expiry, offline grace, and restriction fingerprint.
Package verifier
install
One signed manifest binds runtime, data, configuration, voice, target, component hashes, and observed content digest.
Vehicle runtime
qualify
Versioned startup, render, offline search, offline route, position, voice, and storage suite passes.
Release control plane
update
Inactive slot advances through download, verification, staging, atomic switch, and target qualification checkpoints.
Boot control and watchdog
recover
Power loss or health regression selects a known-good slot without erasing the rejected manifest or incident.
Fleet release manager
retire
Activation and protected-package access are revoked while release and support history remain.
Power-loss-safe update
Switch one pointer, then earn “known good.”
The target advances through a bounded checkpoint sequence while the current release remains bootable. A switch creates a candidate, not an operational release.
- 01Download
Target slot only; preserve resumable progress.
- 02Verify
Match observed SHA-256 identity and approved signature evidence.
- 03Stage
Bind runtime, data, configuration, and voice to the inactive slot.
- 04Switch
Atomically change the durable active-slot pointer.
- 05Qualify
Prove startup, render, search, route, position, voice, and storage.
- 06Promote
Mark the target known good; retain the prior slot for rollback.
Durable records
Persist decisions, not protected packages.
Device identity: hardware, vehicle, product edition, target facts, and lifecycle version.
Release manifest: runtime, data, configuration, voice, target, component digests, and verifier reference.
A/B slot table: active pointer, previous known-good pointer, slot status, and immutable manifest identity.
Update plan: campaign, source/target slots, phase checkpoints, interruption, switch, and qualification evidence.
Qualification and incident ledgers: suite version, results, signal, action, outcome, actor, and time.
Append-only audit and transactional outbox committed with every state change.
Eight operating scenarios
Same control plane, different qualification policy.
Passenger vehicles, fleets, mining, agriculture, emergency response, transit, industrial mobility, and two-wheelers each require target-specific evidence.
Head-unit map and guidance release
Cold boot, local render/search/route, vehicle-signal simulation, voice, HMI policy, and rollback.
Regional truck navigation rollout
Vehicle profile, restricted-road data, cohort health, offline grace, and route-regression threshold.
Disconnected haul-road navigation
Private-region package identity, long offline operation, positioning degradation, storage health, and field recovery.
Farm machinery guidance console
Seasonal regional data, rugged-device target, intermittent activation refresh, operator controls, and rollback.
Resilient in-vehicle map stack
Deterministic boot, offline place/route availability, stale-data disclosure, power interruption, and safe degraded mode.
Bus console release campaign
Route-set compatibility, depot cohorting, audio prompts, driver-distraction review, and watchdog evidence.
Yard and port vehicle terminals
Facility data edition, target GPU/ABI, GNSS shadow handling, restricted zones, and support diagnostics.
Compact offline navigation display
Storage budget, simplified HMI, voice/haptic policy, power cycling, and target-specific qualification.
Downloadable reference
Interrupt the update yourself.
The maintained Offline Release Control app is credential-free and restart-safe. Its ten tests exercise the full lifecycle without pretending fixture manifests are Mappls packages or vehicle certification.