Build, verify, and operate mobile journeys.

A single documentation path for developers integrating LocusVia and platform teams evaluating or governing it.

Recommended first path

From domain to a verified route.

The quickstart follows the same sequence as the control plane, so each prerequisite and proof step has one obvious owner.

Start quickstart Review architecture

Start with the job in front of you#

Mobile engineering

Build the first verified route

Connect a domain, register the app, issue an SDK key, publish a link, and test it on device.

Start the quickstart

Migration

Move from Firebase Dynamic Links

Map the existing link model, replace the SDK path, and verify destinations before a staged cutover.

Open the migration guide

Journey operations

Diagnose a broken journey

Follow the route decision, fallback, deferred outcome, and SDK receipt in one scoped trace.

Open Flight Recorder

Platform & security

Review architecture and trust

Inspect system ownership, tenant isolation, identity controls, audit evidence, and data boundaries.

Review the architecture

Your first verified journey#

Use one shared sequence from onboarding through production diagnosis.

01
Domain
Serve verified association files.
02
App
Bind iOS and Android identities.
03
SDK key
Scope the correct environment.
04
Link
Set app, store, and web outcomes.
05
Live test
Follow the route and inspect proof.

How a LocusVia link decides#

App installed

Universal Links or App Links open the configured in-app destination directly.

App not installed

The fallback policy sends the user to the correct store or web destination and preserves route context for deferred resolve.

Desktop or unsupported device

The same link resolves to the explicit web fallback instead of a dead end.

Journey diagnostics

Flight Recorder explains the platform decision, matched policy, fallback, and SDK outcome.

One control plane, three working layers#

Build

Domains, app identities, SDK configuration, links, fallbacks, and signed-device verification.

Operate

Readiness, runtime status, journey traces, analytics events, webhooks, and release history.

Govern

Tenant and environment isolation, identity controls, audit evidence, and data boundaries.