Skip to content

For mobile product teams

Reduce legacy drag without pausing the roadmap.

I help mobile product teams reduce legacy drag, introduce shared Android and iOS architecture, and ship difficult features with senior hands-on delivery. The work begins with the smallest change that can prove the direction.

Core services

Start with the mobile constraint

Android modernisation and KMP adoption are the main offers. Embedded delivery is how I can join when the work needs ongoing senior ownership.

Core service

Android app modernisation

Problem
An ageing Android codebase is slow to change, hard to test, and expensive to keep alive.
Good fit
Legacy Java or XML, fragile architecture, slow releases, or rising crash and regression rates.
Deliverable
A prioritised migration to Kotlin and Jetpack Compose, modular architecture, practical test and CI/CD foundations, and a plan the team can continue.
Discuss this service →

Core service

Kotlin Multiplatform adoption

Problem
Android and iOS drift apart because the same business logic is written and fixed twice.
Good fit
A product team wants a shared core without pausing its roadmap or rewriting both apps.
Deliverable
An incremental migration proven on one feature, a shared module structure, native integration boundaries, and a team able to keep going.
Discuss this service →

Core engagement

Mobile architecture and embedded senior delivery

Problem
A mobile team needs senior capacity and architecture decisions that hold while the roadmap keeps moving.
Good fit
A team that needs hands-on delivery, clearer module boundaries, stronger engineering standards, or technical leadership now.
Deliverable
Hands-on senior delivery, architecture decisions, documentation, and knowledge transfer that leaves the permanent team stronger.
Discuss this service →

Specialist capabilities

Used when the product evidence justifies them

These are focused additions to a mobile or product engagement, not broad transformation claims.

Specialist capability

Native and Rust performance work

A latency or CPU-bound mobile problem needs one reliable implementation across Android and iOS.

What I deliver: A focused Rust or native module with clean Kotlin and Swift APIs, tests, benchmarks, and documented ownership boundaries.

Specialist capability

Applied AI product features

An assistant or generation feature demos well but lacks grounding, guardrails, cost controls, and reliable tests.

What I deliver: Tool calling, grounding, model routing, prompt and tool tests, budget controls, rate limits, and retention behavior appropriate to the feature.

Evidence comes from independently shipped products, not client AI engagements.

See the independent-product evidence →

How I work

Clear scope, hands-on delivery, clean handover

  1. 01

    Scope

    Map the codebase, constraints, risks, and the smallest valuable first move.

  2. 02

    Deliver

    Work hands-on inside a fixed scope or alongside the team as an embedded senior engineer.

  3. 03

    Hand over

    Leave decisions, tests, documentation, and enough context for the team to own the result.

Bring the codebase, constraint, and deadline.

I will tell you whether I am a fit and what the smallest useful first step looks like.

Discuss your project

FAQ

Common questions

Do you work remotely?

Yes. I work remotely from London with European and US-East overlap. On-site visits can be arranged for kick-off or key milestones.

Do you take fixed-scope projects or ongoing work?

Both. Modernisation and KMP adoption often begin with a bounded discovery or pilot. Embedded delivery works better when the team needs ongoing senior capacity.

When does native Rust make sense?

When measurement shows a latency- or CPU-bound problem and one implementation across Android and iOS reduces risk. If a native layer does not earn its complexity, I will say so.

What does applied AI mean here?

Contained product features such as tool calling, grounding, guardrails, cost controls, and evaluation. The current evidence is from independently shipped products, not client AI engagements. I do not present model training or MLOps as a service.