Platforms/Widgets

Widgets

Embed complete Mappls experiences while keeping hand-off, privacy, and fallback deliberate.

HTMLSwiftKotlin

How the pieces fit

Prebuilt UI for places, directions, nearby, geofences, feedback, and rich Mappls content. Use this boundary as a starting point, then narrow it around the exact Mappls products and trust model your application needs.

01

Host product

Own placement, surrounding content, consent, identity, and the moment the embedded experience begins or ends.

02

Mappls widget

Own the focused place, route, feedback, geofence, visualization, or immersive interaction.

03

Event and fallback layer

Capture supported callbacks, provide a useful no-script or blocked-embed path, and keep business state outside the widget.

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

    Select the owned journey

    Choose a widget when its complete supported interaction matches the outcome you need.

  2. 2

    Define the container

    Set responsive dimensions, loading UI, accessibility context, content policy, and failure behavior.

  3. 3

    Pass minimal context

    Provide only documented identifiers, locations, configuration, and callbacks—never privileged credentials.

  4. 4

    Test hand-offs

    Verify completion, cancellation, back navigation, app opening, blocked content, and small-screen behavior.

4 product families

2 of these families include durable or session state. Follow their complete lifecycle guidance rather than integrating only the first successful call.

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.

  • Embedding and content-security policies permit only required origins
  • No sensitive business state lives only inside the widget
  • Loading, failure, and unsupported-browser fallbacks exist
  • Analytics distinguish view, engagement, completion, and hand-off