How I work with mobile teams.

For teams whose Flutter or Android app is getting slower to build and riskier to change.

A structured audit of the codebase and a written findings report: the risks that matter, the order to address them, and what to leave alone. You come away with a plan, not a lecture.

For apps losing users to slowness or instability.

Cold start, jank, memory, app size, battery, and crashes — profiled on real mid-range devices and prioritised by user and revenue impact. Mobile performance optimisation grounded in measurement, not guesswork.

For inherited, stalled, or “someone left” Flutter apps.

I stabilise the build, cut the worst technical debt, and give your team a credible path forward — without the doomed full rewrite that swallows a year.

For startups scaling a mobile product without a full-time lead.

Senior mobile technical direction a few days a month: architecture decisions, code review, hiring input, and delivery process — continuity without a full-time hire.

For teams building or shipping a developer-facing SDK.

I design and build SDKs that are stable, backward-compatible, and ergonomic — the difference between an SDK teams adopt and one they work around.

For teams that want to level up, not just ship.

Architecture, review culture, testing, and estimation — the practices that cut defects and raise velocity, transferred to your team so they outlast the engagement.