Start building
One honest first success on every platform
Choose your stack and move from an empty project to a verified Mappls boundary. Every quickstart states what public evidence proves, what requires entitlement, where credentials belong, how to run it, how to break it, and what to build next.
The shortest safe path
Copy less. Prove more.
A useful quickstart is not merely the smallest code that can render. It establishes a reproducible source line, credential owner, lifecycle seam, successful outcome, observable failure, and next production decision.
Confirm the exact guide and release line.
Put credentials and provider types in the right place.
Complete one visible or machine-verifiable outcome.
Run the real build path from a clean environment.
Prove denied, unavailable, and teardown behavior.
All platforms
Start where your product runs
13 platform paths
Your first trusted Mappls request
a validated autosuggest result from a credential-safe server boundary
15 minutes1 scaffold1 public guide
Render one accessible web map
a responsive map and text-synchronized selected place
15 minutes1 scaffold2 public guides
Create a lifecycle-safe Android map
a native map screen that survives recreation and permission denial
25 minutes1 scaffold2 public guides
Create a lifecycle-safe iOS map
a native Swift map feature with explicit package and view ownership
25 minutes1 scaffold2 public guides
Bridge one map feature across Android and iOS
a typed shared map feature with separately verified native halves
30 minutes1 scaffold1 public guide
Build a native-backed Flutter place picker
a Dart form that commits one accepted Mappls place identity
30 minutes1 scaffold2 public guides
Stabilize a Cordova map before migration
a reproducible legacy screen behind a replaceable capability facade
35 minutes1 scaffold2 public guides
Extract a Xamarin map integration for replacement
a shared .NET contract with independently owned Android and iOS adapters
40 minutes1 scaffold0 public guides
Boot a supervised embedded map client
a health-checked native process with an atomic data/runtime boundary
45 minutes1 scaffold0 public guides
Simulate one recoverable navigation session
a safety-aware route-to-arrival state machine over an entitled runtime
60 minutes1 scaffold0 public guides
Embed a place journey with an owned fallback
an accessible host that validates one widget result and survives widget failure
20 minutes1 scaffold1 public guide
Ship one zero-SDK Mappls hand-off
a place link that reaches the same intent across app and browser fallbacks
10 minutes1 scaffold1 public guide
Connect a read-only Mappls agent
a grounded documentation query through local stdio or authenticated stateless HTTP
15 minutes2 scaffolds0 public guides
Evidence before installation
Understand the boundaryNo public guide? The quickstart says so.
Embedded, automotive, Xamarin, and locally maintained MCP paths do not borrow unrelated package names. They establish the application boundary and list the exact private distribution or entitlement evidence required before provider-specific implementation.