Platform engineering for mobile is the discipline of building and maintaining the internal infrastructure, tooling, and golden paths that enable feature teams to deliver with high velocity and consistent quality. A mobile platform team is not a gatekeeper — it is a force multiplier.
| 1 | Overview | 2 | Golden Path |
| 3 | Shared Platform Capabilities | 4 | Developer Experience Measurement |
| 5 | Anti-Patterns to Avoid | 6 | References |
The mobile platform engineering strategy covers four capability areas: the golden path (opinionated, supported development paths that work out of the box), shared platform capabilities (authentication, analytics, crash reporting, push), internal developer tooling (code generation, scaffolding, build optimization), and developer experience measurement (DORA metrics applied to mobile delivery).
The golden path is the officially supported, documented, and maintained approach to common engineering tasks. Feature teams are not required to use it — but deviating from it means accepting the overhead of unsupported infrastructure. Golden path components for mobile:
Project scaffolding: A CLI or GitHub template that generates a new feature module pre-configured with MVVM + Clean Architecture, Hilt DI, unit test scaffolding, snapshot test scaffolding, and CI integration. A new screen should be commit-ready in under 10 minutes.
API client generation: Given a GraphQL schema or OpenAPI specification, generated Apollo Kotlin/iOS or Retrofit client code. Eliminates handwritten API integration code and the serialisation bugs that come with it.
Shared design system: A versioned :core:ui library with all design system components, tokens, and theming. Feature teams import and use — they do not re-implement Button, TextField, or LoadingState.
Release pipeline: A fastlane configuration and GitHub Actions workflow that any new project can adopt in under 30 minutes, preconfigured with code signing, testing gates, and distribution.
Authentication, push notifications, analytics, crash reporting, and experiment assignment are infrastructure capabilities that should be implemented once and consumed by all mobile applications. Implementing these independently per application creates inconsistent behaviour, multiplied security surface, and duplicated maintenance burden. The platform SDK:
DORA metrics adapted for mobile delivery:
- Deployment Frequency: How often a production release reaches users (target: multiple per week)
- Lead Time: From commit to production (target: under 1 day for bug fixes, under 1 week for features)
- Change Failure Rate: Percentage of releases requiring rollback or hotfix (target: below 5%)
- Recovery Time: From incident to production fix deployed (target: under 4 hours)
Measure and publish DORA metrics to the engineering organisation monthly. Trend analysis identifies platform investments that will move the metrics.
All mobile infrastructure changes require platform team approval and are routed through the platform team's backlog. Feature teams blocked waiting for platform team capacity.
Platform team builds self-service infrastructure. Feature teams are empowered to use and extend it without bottlenecks. Platform team reviews proposals, not every implementation.
One team uses Retrofit, another uses Ktor. One team uses Hilt, another uses Dagger directly. One team uses fastlane, another has custom shell scripts. Every new engineer must learn a different stack for each project.
Opinionated golden path with clear documentation and active support from the platform team. Deviation allowed with architectural justification — but the default is always the golden path.