My first iOS role was on a route-planning app for independent nurses. It taught me to start with the person doing the work: keep the flow clear, preserve state, and make failure recoverable.

At GoodBarber, the scale changed. Server-driven configuration had to produce reliable UIKit apps across thousands of customer projects, including mature code paths that could not simply be replaced. I learned to design for variation, compatibility, and gradual change.

Today I shape architecture, investigate production failures, and help engineers make difficult iOS decisions. Finely adds a different kind of responsibility: I own the product, financial rules, interaction, data, privacy, monetization, and release.

Path

  1. 01 · First product

    Learning from work in the field

    A route-planning app for independent nurses made every interaction concrete: a missed state or unclear step interrupted real work.

    UIKit / workflows / reliable state

  2. 02 · GoodBarber

    Working at platform scale

    One server-driven system had to serve thousands of customer apps. Changes needed to support configuration, legacy behavior, and gradual migration.

    UIKit / Objective-C / configurable UI

  3. 03 · Senior scope

    Taking responsibility beyond implementation

    My work grew to include architecture, StoreKit, WebKit, privacy, lifecycle, SDK migrations, performance investigations, and mentoring.

    Architecture / production diagnosis / guidance

  4. 04 · Finely

    Owning one product end to end

    I make the product and engineering decisions across financial rules, interaction, persistence, privacy, monetization, on-device intelligence, and release.

    Product / domain / UIKit / release

Building an iOS product or platform?

If you are working through a product decision, an architecture problem, or a difficult production issue, I would be glad to discuss it.

Get in touch