Make the system legible
Good architecture should help the next engineer understand what changes, why it changes, and where it belongs.
I'm Young, a Staff iOS engineer. My work has moved through consumer video, fintech, and aviation, but the thread is consistent: make a difficult system understandable and make the product feel dependable.
I care about architecture because it changes how a team works. I care about polish because it changes how a user trusts the product. The best mobile work needs both.
Outside of my day job I design and build Usages, an independent iPhone app that puts AI coding quotas, reset windows, tokens, and cost in one private dashboard. It is where I get to own every decision, from the pixel grid to the App Store release.
I also write to make the lessons reusable, especially the mistakes, tradeoffs, and edge cases that disappear from a tidy final diff.
Find me on GitHubGood architecture should help the next engineer understand what changes, why it changes, and where it belongs.
Responsiveness, motion, accessibility, and failure states are part of correctness, not a layer added at the end.
Production software lives with poor networks, large datasets, old devices, and humans moving quickly.
Ascent EFB
Leading iOS for a modern electronic flight bag: architecture, maps, performance, and product direction.
Consumer fintech
Built and shipped a SwiftUI product from zero to one.
Consumer products
Owned end-to-end mobile delivery across multiple product cycles.
Creative editing tools
Creative tooling, rendering systems, modularity, and app architecture.
Alibaba & Ant Group
Consumer mobile surfaces, cross-platform UI, and payment experiences.
Meituan
Shared mobile platform work for the apps built on top of it.
The work is never just the framework. It is the judgment to know what the product needs now, and what the team can keep healthy later.
Read my notes