Services
Mobile work with a clear outcome.
I work directly with product teams on difficult iOS and Android milestones across native apps,
Kotlin Multiplatform and the APIs behind them. The scope is defined around what needs to be
understood, built or released.
Ways to work together
Three bounded engagements.
Each starts with the product and repository you already have. We agree the useful outcome,
the boundaries and how the work returns to your team.
01
Mobile Technical Discovery
Turn an unclear mobile milestone into a concrete technical and delivery plan.
Useful when: An existing product, API or repository with important unknowns to resolve before implementation.
- Product and repository review
- Risks, boundaries and recommended approach
- Delivery sequence and written findings
- Walkthrough with your team
Start a conversation → 02
Mobile Delivery Sprint
Own a defined feature, integration or release milestone through to a shipped outcome.
Useful when: A product team with a bounded piece of difficult work and a real target to hit.
- Hands-on implementation
- Native, shared-code and API integration
- Testing and release readiness
- Clear handover into the existing team
Start a conversation → 03
iOS / Kotlin Multiplatform Support
Improve the iOS side of an existing or actively adopting Kotlin Multiplatform codebase.
Useful when: Kotlin-led or cross-platform teams where the shared code works, but the iOS experience does not.
- Swift-facing API review
- Shared and native boundary decisions
- Xcode, Gradle, testing and release workflow
- Support for iOS engineers contributing to shared code
Explore iOS and KMP support → Starting point
A useful first step when the path is unclear.
Mobile Technical Discovery is fixed-scope. It is designed to surface the important risks and
decisions before a team commits to a larger implementation.
Most fixed-scope discovery engagements begin at £1,800.
If the work is already well defined, a delivery sprint may be the more direct starting point.
Supporting capabilities
The tools follow the problem.
These are the practical areas I can bring into an engagement. They are not separate menu items
or a claim that every project needs every technology.
- Native iOS
- Swift and SwiftUI
- UIKit
- Android
- Kotlin Multiplatform
- Compose
- API and authentication integration
- Testing and code health
- Fastlane and GitHub Actions
- App Store and Play Store delivery
Good fit
Built for products that already exist.
Usually a good fit
You have users, a product, an API, a mobile codebase or a defined milestone. You need an
experienced engineer to clarify the hard parts and own the route to a concrete outcome.
Probably not the right fit yet
You are still testing an unformed app idea with no existing product, technical foundation
or defined milestone. Early product strategy may be more useful before mobile delivery work.
Start a conversation
What exists, and what needs to move?
A short note is enough. Tell me about the current product, the blocked work and the timeframe
you are working towards.