Products/Embedded
stateful3 platforms8 source families
Location that keeps working

Offline & Automotive

Offline maps, search, routing, guidance, compilers, and embedded navigation runtimes.

Start building Get credentials

Power in-vehicle, industrial, and disconnected experiences with licensed regional data packages and embedded runtimes. This product family includes offline search and route compilers, native SDKs, traffic-event customization, voice guidance, GPS health, and update workflows.

Open the A/B release-control guide

Separate public and local evidence generations, then operate activation, manifests, slots, qualification, interruption, rollback, and retirement.

Open guide

Capabilities

Offline maps, search, and routingProduction guidance, platform support, examples, and operational considerations included.01
Turn-by-turn guidance runtimeProduction guidance, platform support, examples, and operational considerations included.02
Regional data compilationProduction guidance, platform support, examples, and operational considerations included.03
Voice and traffic customizationProduction guidance, platform support, examples, and operational considerations included.04
GPS health and dead reckoning hooksProduction guidance, platform support, examples, and operational considerations included.05
Signed data and software updatesProduction guidance, platform support, examples, and operational considerations included.06

Available platforms

Keep business identifiers and server-side policy portable; use the native surface where device integration or long-lived state matters.

Device activation and licensed data package

Design for activation, entitlement refresh, package compatibility, rollback, and long periods without network access.

  • Use separate projects for development, staging, and production.
  • Apply the narrowest domain, IP, platform, product, and resource scopes available.
  • Never ship a server secret in a browser bundle, mobile binary, prompt, or public repository.

Quickstart

Replace placeholders with credentials from the developer console. Examples include the lifecycle and failure-handling context that short snippets usually omit.

Offline & Automotive quickstart
// Illustrative lifecycle: concrete symbols vary by licensed SDK edition.
NavigationRuntime runtime(configuration);
runtime.installDataPackage(verifiedPackagePath);
runtime.setPositionProvider(vehiclePositionProvider);

auto route = runtime.plan(origin, destination, vehicleProfile);
if (route.ok()) {
  runtime.startGuidance(route.value());
}

// Keep sensor callbacks non-blocking; persist the resumable session safely.
runtime.onProgress([](const GuidanceProgress& progress) {
  tripStore.checkpoint(progress);
});
Before productionRestrict and rotate credentialsHandle timeouts and typed errorsAdd tracing without logging secretsTest quota and degraded-mode behavior

A safe offline navigation lifecycle

Vehicle integrations must survive power loss, partial updates, and intermittent connectivity.

1
State · manufactured

Manufacture

Bind hardware identity, software edition, and regional entitlement.

device.registered
2
State · activated

Activate

Verify license and install a compatible signed base package.

license.activated
3
State · navigating

Operate

Plan and guide locally while checkpointing recoverable trip state.

guidance.started
4
State · updating

Update

Download, verify, stage, atomically switch, and retain rollback data.

package.staged
5
State · recovered

Recover

Restore the last compatible runtime and resume safely after interruption.

runtime.recovered

Operate the complete lifecycle

These blueprints name every state, actor, command, event, invariant, durable record, retry boundary, failure recovery, source contract, and operational signal.

Browse all stateful journey blueprints

Source repositories

Reference content is reconciled against these public and private source families. Version, authentication generation, and maturity are recorded before content is promoted.

Browse all 7 related integration guides