Place identity, navigation, point-on-map, and the signed-in Pin flow.
Zero-SDK handoff lab
Build one Mappls deep link. Prove every fallback.
Choose a source-documented intent, validate its identity, and copy platform-shaped code. This lab never accepts a credential, private payload, or invented Mappls route.
All outputs are bounded public hand-offs, never a secret transport.
HTML, JavaScript, Kotlin, and Swift from the same validated result.
Installed state, browser, messaging, offline, and accessible recovery.
India Gate at 28.612964,77.229463
Primary HTTPS
https://mappls.com/navigation?places=28.612964,77.229463,India%20Gate&isNav=true&mode=drivingOpen test target Installed-app URI
mappls://navigation?places=28.612964,77.229463,India%20Gate&isNav=true&mode=drivingUse only from a native mobile host with the HTTPS fallback retained.<a href="https://mappls.com/navigation?places=28.612964,77.229463,India%20Gate&isNav=true&mode=driving" rel="noopener noreferrer">
Open in Mappls
</a>Observable fallback contract
A click is not an arrival.
Record only the hand-off stage your application can prove. A downstream navigation session remains outside your authority unless Mappls supplies an entitled callback.
User action
A visible, accessible link or button owns the hand-off.
Click event and exact generated intent version.Universal link
HTTPS opens an associated Mappls app where supported or remains useful in the browser.
Observed outcome class by OS, browser, and installed state.Explicit app URI
A native mobile host may try the documented Mappls URI and retain the HTTPS fallback.
App-open callback or caught unavailable-handler result; never inferred downstream arrival.Recovery
The user can copy the HTTPS URL, retry, or continue in a browser without a redirect loop.
Visible recovery control and fallback-loop test.Release matrix
Test the real hand-off surface.
Android: installed and uninstallediOS: associated-link and browser behaviorDesktop: primary and private browsingMessaging/email clients that rewrite linksOffline and captive-network statesScreen reader, keyboard, and copy-link recovery
Safety properties
Keep URL intent bounded.
Only mappls.com HTTPS and the documented mappls URI are emittedEvery variable segment is validated and encoded exactly onceNo credential, precise user location, or private payload is acceptedClick evidence is not represented as navigation arrivalMappls Pin remains the place identity when availableDevice and entitlement behavior remains an explicit acceptance test
Evidence boundary
Official path shapes, repository-backed product family.
The current official Mappls deep-link page documents the exact HTTPS and app-URI shapes. The public repository establishes the credential-light widget family but does not contain those path contracts. Installed-app association, regional availability, and downstream arrival still require device evidence.