SwiftUI & TCA Migration Consulting

That's a core engagement, including the rescue of migrations that stalled around 40%. I led the SwiftUI and TCA rewrite that took Epsy to 99.9% crash-free and a CES Innovation Award, and I pair with your team so they can carry the pattern after I'm out. 6-16 weeks depending on scope, or a few days for just the migration plan.

Yes. About a third of my SwiftUI work is vanilla SwiftUI plus @Observable. TCA fits apps with substantial business logic and multi-person teams. For smaller or UI-focused apps, vanilla is cleaner and often faster.

Yes. UIHostingController at the seams, UIViewRepresentable for UIKit views SwiftUI can't yet do cleanly, and a clear rule about who owns state at each boundary. I document this early so the team doesn't invent conflicting patterns.

Sometimes. TCA has specific strengths around testability, effect handling, and navigation modelling. If those are your current bottlenecks, the adoption cost is usually worth it. If your architecture problems are team-process problems, a new framework won't fix them.

The path out depends on how much of the migrated 40% is worth keeping and what is blocking the team, which is the first thing I work out. Sometimes the answer is to finish the gradual migration module by module, sometimes to rewrite the rest in one go; picking wrong here is what got the project stuck the first time. I have taken this on as a rescue more than once.

TCA fits apps with substantial business logic and multi-person teams. The structure pays for itself in testability and navigation modelling. Vanilla SwiftUI plus @Observable fits smaller apps, UI-focused products, and one-person teams. The adoption cost is only worth paying when the codebase has the state and effects that TCA is designed to organise.

Yes. Most of my migration work is pairing with an internal team: I architect and migrate the highest-risk modules, the team replicates the pattern on the rest. Leaves behind conventions the team can enforce in PR review after I'm out. 6-16 weeks depending on scope.

Directly - you're hiring me, one senior iOS engineer who writes the code, rather than an agency that routes you through a project manager and a team you never meet. For a lot of my clients that's the whole point: one person who owns the work end to end.

A quick call can happen within days. For project work I usually need 1-2 weeks to clear the calendar, though I keep some buffer for urgent firefighting.

Yes, from pre-seed to Series C and beyond. For very early teams, a short advisory engagement often makes more sense than a full build: you get the architecture guidance without committing to a large piece of work before you've validated the product.

Everything: code, architecture decisions, code review, documentation, async Slack availability during working hours. No surprise add-ons. I bill for time spent working on your project, not for "thinking about it in the shower."

I'm currently in Vancouver (PST), with full overlap for North American teams. For UK and Europe, I'm online by their afternoon. For Gulf or APAC, we'd agree on overlap hours and handle the rest async. I've worked with teams from San Francisco to Dubai.