Flutter MapmyIndia GL
A Mappls sdk for maps, search places, routes navigation, tracking telematics, widgets deep links, offline automotive, capture feedback across Flutter.
Compatibility decision
Do not start a new production build from this evidence. Contain existing use, identify a supported target, migrate with rollback, and retire the dependency.
Repository content, activity, code fragments, and local correspondence are discovery evidence only. They do not establish a supported package coordinate, binary identity, current version, account entitlement, runtime pairing, production compatibility, or approval.Source and identity
- Public source
- Open repository ↗
- Captured document
- Open source documentation ↗
- Default branch
main- Lifecycle risk
- Retire
- Authentication signals
- oauth2 · api-key
Products and prerequisites
- A Flutter project with Android and iOS platform configuration
- OAuth client credentials issued for the intended Mappls project
- A Mappls project key restricted to the intended app, domain, or backend
Install and configuration guidance
These statements are reproduced as normalized repository evidence. Validate coordinates and versions before copying them into a project.
Getting Started
To work with MapmyIndia Map in flutter add this to your package's pubspec.yaml file: yaml dependencies: mapmyindiagl: ^0.3.1
Now in your dart code you need to import this package: dart import 'package:mapmyindiagl/mapmyindiagl.dart';
Source code evidence
Use these fragments to understand integration shape. They may belong to an older toolchain or authentication generation.
List<Symbol> symbol = await controller.addSymbolsFromJson(geojson);
List<Line> lines = await controller.addLinesFromJson(geojson);
List<Fill> fills = await controller.addFillsFromJson(geojson);Connected implementation paths
Exact source paths
Quickstart · FlutterBuild a native-backed Flutter place pickerDownloadable starter · FlutterFlutter place-selection starterAdjacent platform paths
Migration evidence
Direct LineageFlutter map plugin lineageProduction compatibility checklist
A clean demo is the beginning of the decision, not its conclusion.
- 01
Confirm the exact package or artifact identifier and version with the owning Mappls product team; a repository name is not a package contract.
- 02
Verify platform toolchain, operating-system, architecture, host-application, and transitive-dependency compatibility from a clean build.
- 03
Bind only the documented credential class and restriction to its intended client or trusted-server runtime; never commit or log a secret.
- 04
Verify account entitlement, region, quota, endpoint generation, data rights, and applicable commercial terms independently.
- 05
Exercise initialization, ready, denied, empty, offline, timeout, cancellation, background/resume, and teardown paths.
- 06
Pin dependency and native artifact integrity evidence; retain source fingerprint, selected version, lockfile, build provenance, and approving owner.
- 07
For stateful or hybrid behavior, persist application state outside the SDK and prove idempotency, reconciliation, audit, privacy, and recovery.
- 08
Release by a bounded cohort with observable rollback; repository activity or a successful fixture is never production compatibility evidence.
Local repository candidates
Only minimized identity evidence is exposed. Review candidates side by side; do not assume they are the same release line.
contenthub/dochub/flutter-mapmyindia-gllocal-contenthub-dochub-flutter-mapmyindia-gl