Platforms/Deep links

Deep links

Open useful Mappls place and journey experiences from any channel—with no SDK requirement.

URLHTML

How the pieces fit

Universal Mappls URLs for place views, directions, navigation, and app hand-off. Use this boundary as a starting point, then narrow it around the exact Mappls products and trust model your application needs.

01

Link producer

Create documented Mappls URLs from trusted place, Mappls Pin, destination, or route context.

02

Universal hand-off

Let the operating system open the Mappls app when available and a useful web experience otherwise.

03

Campaign measurement

Track link placement and downstream business outcomes without putting private data into the URL.

From empty project to one real journey

Each step produces a testable boundary. Keep the first release deliberately small, then expand from observed product behavior.

  1. 1

    Choose the destination type

    Use a place, map, directions, navigation, or other documented link shape for one clear intent.

  2. 2

    Encode from structured data

    Build and validate URL components with a URL library instead of concatenating user input.

  3. 3

    Provide visible context

    Tell users what opens, show the destination in human-readable form, and preserve a copyable fallback.

  4. 4

    Test every channel

    Verify installed and uninstalled states across mobile browsers, messaging, email, QR, desktop, and in-app webviews.

1 product family

These integrations are primarily request-response surfaces; still design authentication, quotas, failures, and data handling explicitly.

SDKs, APIs, distributions, and samples

Every item below is generated from a public Mappls repository and links to its source-grounded guide. Maturity labels distinguish current material from samples, distributions, legacy sources, and deprecated integrations.

Platform tutorials

Start with one focused result, then move into complete stateful journeys and operational failure handling.

Production readiness

Pass these checks in addition to the requirements of the selected product, SDK release, operating system, and security program.

  • User or confidential data never appears in query parameters
  • All variable values are encoded and length-bounded
  • App and browser fallbacks reach the same intent
  • Redirect and campaign domains are allow-listed and monitored