Platforms/Flutter

Flutter

Use one Dart experience with deliberate native Mappls configuration underneath.

Dart

How the pieces fit

Dart wrappers for native Android and iOS mapping capabilities. Use this boundary as a starting point, then narrow it around the exact Mappls products and trust model your application needs.

01

Dart feature layer

Own widgets, application state, typed models, and platform-neutral business behavior.

02

Flutter platform plugin

Bridge map rendering and native capabilities to correctly configured Android and iOS SDKs.

03

Trusted backend

Issue scoped credentials and own privileged calls, persistence, events, and operational workflows.

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

    Pin the plugin

    Match Flutter, Dart, Android, iOS, and Mappls plugin requirements before resolving dependencies.

  2. 2

    Configure native projects

    Apply repository, manifest, Info.plist, package, and credential steps on both platforms.

  3. 3

    Build a lifecycle-safe widget

    Create controllers once, await readiness, and dispose streams and native resources.

  4. 4

    Exercise release builds

    Test shrinking, signing, permissions, backgrounding, and platform-view performance outside debug mode.

2 product families

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.

  • Android and iOS configuration is version-controlled
  • Controllers are used only after readiness
  • Streams and platform views are disposed
  • Release builds are tested on physical devices