public source · Kotlin

Android lifecycle adapter starter

A Kotlin contract that keeps camera, selection, permission, recreation, and teardown state outside unconfirmed SDK types.

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

src/main/kotlin/MapFeature.ktSDK-independent feature contract

src/main/kotlin/FixtureMapAdapter.ktDeterministic native lifecycle fixture

BUILD_SELECTION.mdAGP, Kotlin, repository, and SDK gate

Android lifecycle adapter starter

{
  "schemaVersion": "mappls.starter-kit.v1",
  "slug": "android-native-starter",
  "platform": "Android",
  "quickstartSlug": "android-native",
  "readiness": "public-source",
  "liveProviderCallsEnabled": false,
  "sourceGuideSlugs": [
    "mappls-android-sdk",
    "mappls-android-compose-demo"
  ],
  "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.

Use only the documented Android credential configuration restricted to the package and signing identity. Server credentials never belong in the APK.

Evidence boundary

Source before syntax.

The public repositories are sample-classified evidence; confirm Maven coordinates, BoM, AGP/Kotlin, min/target SDK, and supported release with Mappls.

Mappls Android SDK Mappls Vector Map Android SDK JetPack Compose

Release evidence

What must be true after the scaffold.

Camera/selection state restores intentionally and no map listener or location request survives the owning lifecycle.

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.

Release dependency matrix is reproducible

Permission denial is a complete state

Process recreation is tested

Native resources detach deterministically