legacy maintenance · JavaScript

Cordova stabilization starter

A legacy-safe WebView facade that waits for device readiness, owns teardown, and keeps a web/deep-link fallback available for migration.

Download project Follow the quickstart

Inside the archive

A project you can inspect before installing.

The canonical file manifest is also the archive contract. Common evidence, environment, manifest, and acceptance files accompany platform-specific source.

README.mdSetup and first-success boundary

STARTER_MANIFEST.jsonMachine-readable project scope

.env.exampleBlank non-secret configuration

EVIDENCE.mdSource and selection boundary

ACCEPTANCE.mdSuccess and hostile-path proof

config.xmlMinimal legacy host identity

www/index.htmlWebView host with deep-link fallback

www/js/index.jsDevice-ready lifecycle facade

Cordova stabilization starter

{
  "schemaVersion": "mappls.starter-kit.v1",
  "slug": "cordova-maintenance-starter",
  "platform": "Cordova",
  "quickstartSlug": "cordova-maintenance",
  "readiness": "legacy-maintenance",
  "liveProviderCallsEnabled": false,
  "sourceGuideSlugs": [
    "mapmyindia-map-cordova-ionic-beta",
    "mapmyindia-restapi-cordova-ionic-beta"
  ],
  "credentialRule": "Blank environment placeholders only; enable a live adapter only after account, package, host, auth, region, and entitlement review."
}

Credential boundary

Secrets have one owner.

Treat all client credentials as platform-restricted public credentials and keep privileged REST work on a backend. Never reuse legacy auth with a current host by resemblance.

Evidence boundary

Source before syntax.

Only legacy/beta Cordova sources exist in the public corpus. This quickstart is for stabilizing an existing estate—not recommending Cordova for new development. Use the migration track to select a supported target.

MapmyIndia Map SDK for Cordova/Ionic - Beta 1 MapmyIndia REST APIs for Cordova/Ionic - Beta 1

Release evidence

What must be true after the scaffold.

One legacy journey is reproducible, has a fallback, and can switch to a replacement adapter without changing domain state.

A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result.

No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts.

Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends.

Legacy status is explicit

Every build input is frozen

Facade inputs are bounded

Migration and rollback paths are tested