Platforms/Cordova

Cordova

Maintain hybrid location experiences with explicit native ownership and a migration path.

JavaScriptObjective-CJava

How the pieces fit

Legacy hybrid bridges for Cordova and Ionic applications. Use this boundary as a starting point, then narrow it around the exact Mappls products and trust model your application needs.

01

Web application shell

Own navigation, UI, business state, and a narrow JavaScript interface to mapping capabilities.

02

Cordova native plugin

Bridge platform permissions, lifecycle, SDK calls, and callbacks across Android and iOS.

03

Compatibility envelope

Pin every toolchain and plugin dependency while planning replacement of unsupported components.

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

    Classify the estate

    Record Cordova, Ionic, plugin, Android, iOS, and Mappls versions plus current release constraints.

  2. 2

    Reproduce the build

    Lock dependencies and prove a clean signed build before adding new location behavior.

  3. 3

    Constrain the bridge

    Keep commands and callbacks small, typed, serializable, and resilient to view recreation.

  4. 4

    Design migration seams

    Separate application state from plugin calls so the UI or native host can be replaced incrementally.

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.

  • Supported status is verified before new development
  • Toolchain and plugin versions are frozen
  • Bridge inputs are validated and bounded
  • A tested migration and rollback path exists