About

Engineer, builder, student of the details.

I'm Yousan, a Staff iOS engineer based in Palo Alto. 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.

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 GitHub

Working principles

How I like to build.

01

Make the system legible

Good architecture should help the next engineer understand what changes, why it changes, and where it belongs.

02

Treat polish as engineering

Responsiveness, motion, accessibility, and failure states are part of correctness—not a layer added at the end.

03

Build for the real environment

Production software lives with poor networks, large datasets, old devices, and humans moving quickly.

Experience

Places and products that shaped the work.

Staff iOS Engineer

Aviation software

Mobile architecture, offline maps, performance, and product direction.

Founding iOS Engineer

Consumer fintech

Built and shipped a SwiftUI product from zero to one.

iOS Engineer

Consumer products

Owned end-to-end mobile delivery across multiple product cycles.

iOS Engineer

ByteDance

Creative tooling, rendering systems, modularity, and app architecture.

Software Engineering Intern

Alibaba & Ant Group

Consumer mobile surfaces, cross-platform UI, and payment experiences.

Toolkit

Deeply mobile, broadly curious.

Apple platforms

Swift · SwiftUI · UIKit · Objective-C · Combine · Concurrency · Instruments

Systems

Offline-first architecture · Rendering · Mapping · Performance · Networking · Storage

Beyond the app

TypeScript · React · Python · C/C++ · Product strategy · Mentorship · Technical writing

Keep exploring

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