iOS work gets difficult when a change stops being local.

I work with teams as they start a new iOS product,
untangle a mature app, or bring a migration into production.

Where I can help

Starting a new product

Set the iOS architecture, delivery approach, and early technical boundaries before they become expensive to change.

When a mature app resists change

Trace why work spreads beyond the feature, decide what deserves attention first, and work through it with the team.

When a migration has stalled

Choose what moves first, what stays in place, and how the team keeps releasing while it moves.

How work can begin

It should make the next piece of work clearer.

Starting with the work at hand

When a team needs a second technical view, I look at the relevant code and product context, then say what I see and where I would begin.

Joining the work

When the direction is clear, I work with the team on the architecture, implementation, reviews, and release work that gets it finished.

We talk first. If the problem or the fit is unclear, that should be obvious early.

Selected background

Point-of-care retinal imaging — iOS platform ownership through clinical studies and clinical builds.

FDA-cleared ultrasound platform — iOS connectivity, SwiftUI, and device/data delivery.

Prior experience, not Apps Done Wright client work.

Writing

Writing about the parts of iOS work that become difficult as a product grows.

Read the essays