Shared .NET domain layer
Retain portable models, workflows, persistence interfaces, and tests independent of the UI framework.
Existing Xamarin estates planning a migration
Xamarin
Stabilize existing .NET mobile integrations and move forward without losing behavior.
C#
Recommended boundary
How the pieces fit
Legacy .NET mobile samples for SDK-backed maps and REST APIs. Use this boundary as a starting point, then narrow it around the exact Mappls products and trust model your application needs.
Platform SDK adapters
Isolate Android and iOS Mappls bindings, lifecycle, permissions, and rendering behind explicit interfaces.
Migration target
Move screens or features toward a supported .NET or native stack while preserving contract tests.
A safe first integration
From empty project to one real journey
Each step produces a testable boundary. Keep the first release deliberately small, then expand from observed product behavior.
- 1
Inventory dependencies
Capture NuGet packages, native bindings, SDK binaries, build hosts, signing, and entitlement state.
- 2
Freeze observable behavior
Add tests around coordinate conversion, search, routes, state restoration, and native callbacks.
- 3
Extract adapters
Move Mappls-specific calls behind interfaces that a replacement platform can implement.
- 4
Migrate by journey
Move complete user journeys, validate parity, then retire the corresponding legacy surface.
Capabilities on Xamarin
1 product family
These integrations are primarily request-response surfaces; still design authentication, quotas, failures, and data handling explicitly.
Auditable implementation evidence
SDKs, APIs, distributions, and samples
Every item below is generated from a public Mappls repository and links to its source-grounded guide. Maturity labels distinguish current material from samples, distributions, legacy sources, and deprecated integrations.
No public repository is classified specifically for this platform.
The product and architecture guidance remains useful, but implementation requires the entitled private distribution and its corresponding local source documentation. The page intentionally does not relabel an unrelated public repository as evidence.
Learn by building
Platform tutorials
Start with one focused result, then move into complete stateful journeys and operational failure handling.
Before launch
Production readiness
Pass these checks in addition to the requirements of the selected product, SDK release, operating system, and security program.
- The support and security posture is documented
- Build inputs can be reproduced
- Native resources have deterministic ownership
- Migration parity is measured with journey-level tests