Replace the explicitly obsolete MapmyIndia Flutter plugin with a release-qualified Mappls line while treating Dart, Android, iOS, and native SDK versions as one reproducible compatibility graph.
Brand lineage identifies the current Flutter candidate. Exact plugin, Dart/Flutter, Android, iOS, native SDK, renderer, build, authentication, and entitlement pairings still require release-specific approval.
Legacy sources are fully covered. Candidate links expose the closest public evidence and its maturity; they do not silently upgrade it to an entitlement or support declaration.
flutter-mapmyindia-glmappls-flutter-sdkResolve each dimension explicitly. “It compiled” does not prove identity, lifecycle, failure, privacy, or operational compatibility.
The Dart package and native dependencies can drift independently across old project files.
Lock Flutter/Dart, plugin, Android/iOS SDK, build tools, architecture, and signing as one release decision.
Clean dependency graphs, Android bundle, iOS archive, physical-device launch, and rollback artifact.
Controllers, streams, and callbacks may survive rebuilds or disposal.
Own one controller generation, reject late callbacks, and detach streams deterministically.
Hot/cold launch, navigation, rebuild, rotation, background, memory pressure, process death, restoration, and disposal tests.
Map, camera, annotation, gesture, and API-kit behavior can differ by native platform.
Normalize only application-owned behavior and accept Android and iOS independently.
A shared fixture corpus plus platform-specific visual, accessibility, interaction, error, and performance evidence.
Do not advance on calendar alone. Each stage creates evidence that makes the next one safe and reversible.
Inventory every Flutter map capability, package, host, credential class, callback, and owner before changing production.
Resolve the exact entitled package or endpoint with Mappls and verify its supported toolchain, region, quotas, authentication, and lifecycle.
Move Flutter map capability calls behind a narrow application-owned interface without changing product behavior.
Replay approved fixtures and shadow eligible reads while preventing duplicate writes or user-visible duplicate controllers or native effects.
Release to internal users and bounded cohorts with health gates, ownership, automatic stop conditions, and immutable version evidence.
Remove legacy credentials and dependencies only after rollback and audit retention obligations expire.
These examples deliberately model the seam and verification pattern—not unconfirmed package symbols. Implement the adapters only after the exact target contract is issued.
sealed class MapResult { const MapResult(); }
final class MapReady extends MapResult { const MapReady(); }
final class MapFailure extends MapResult { const MapFailure(this.code); final String code; }
abstract interface class MapPort {
Future<MapResult> mount({required double latitude, required double longitude});
Future<void> showFixture(String featureId);
Future<void> dispose();
}
// One adapter owns each plugin/native generation. Reject callbacks after
// dispose and qualify Android and iOS release graphs independently.The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region.
Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator.
Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences.
A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression.
Stopping traffic is not enough. Recover durable resources, sessions, events, and in-flight commands without duplicates or hidden divergence.
Prepare support packetKeep the previous signed artifact, dependency lock, configuration, and credential valid until the observation window closes.
Make the provider selection server- or release-controlled; define automatic stop signals and one accountable rollback owner.
For durable state, prove backward-readable records or a reversible data migration before allowing candidate writes.
After rollback, reconcile in-flight requests and resources by stable identifiers instead of replaying commands blindly.