public source · Swift

iOS view-ownership starter

A dependency-free Swift feature contract that isolates selected package types behind main-actor lifecycle and restoration.

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

Package.swiftDependency-free contract package

Sources/MapplsStarter/MapFeature.swiftMain-actor SDK seam

Sources/MapplsStarter/FixtureMapAdapter.swiftDeterministic view lifecycle fixture

iOS view-ownership starter

{
  "schemaVersion": "mappls.starter-kit.v1",
  "slug": "ios-native-starter",
  "platform": "iOS",
  "quickstartSlug": "ios-native",
  "readiness": "public-source",
  "liveProviderCallsEnabled": false,
  "sourceGuideSlugs": [
    "mappls-map-ios-distribution",
    "mappls-api-kit-ios-distribution"
  ],
  "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 app credential restricted to the bundle/team context. Keep server secrets and privileged exchanges outside the application bundle.

Evidence boundary

Source before syntax.

Public distribution repositories identify candidate package lines, not a universal version matrix. Confirm SwiftPM products, binary checksums, Xcode/Swift, deployment target, and extension compatibility together.

[Mappls Map SDK]()[MapplsAPIKit (REST API Kit for iOS)]()

Release evidence

What must be true after the scaffold.

The selected place survives intended scene restoration and released views retain no delegates, observers, tasks, or background sessions.

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.

Package/binary lines are compatible

Privacy declarations match behavior

Main-actor and scene ownership are explicit

Release archives are hardware-tested