entitlement required · C#

Xamarin extraction starter

A shared .NET contract extracting business identity and commands from legacy bindings before independent Android and iOS successor selection.

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

MapplsMigration.csprojPortable contract build

MapplsFeature.csBinding-independent contract

MIGRATION.mdCharacterization and replacement sequence

Xamarin extraction starter

{
  "schemaVersion": "mappls.starter-kit.v1",
  "slug": "xamarin-maintenance-starter",
  "platform": "Xamarin",
  "quickstartSlug": "xamarin-maintenance",
  "readiness": "entitlement-required",
  "liveProviderCallsEnabled": false,
  "sourceGuideSlugs": [],
  "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 separately restricted native app credentials and keep privileged service credentials on a backend. Do not move secrets into shared assemblies during extraction.

Evidence boundary

Source before syntax.

No public repository in the snapshot provides a current Xamarin successor. Obtain the existing binding/source and target-platform contract from Mappls and use the migration principles before implementation.

This platform requires an entitled or company-selected distribution before live binding.

Release evidence

What must be true after the scaffold.

Shared tests prove equivalent place identity and errors while no shared state retains a native view, context, delegate, or credential.

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.

Support posture is documented

Both native builds are reproducible

Shared code owns no native resources

Journey parity determines migration