Mobile platforms that keep shipping while the architecture changes.
I work across application architecture, Design Systems, Backend-Driven UI and cross-platform migration—turning one-off product work into mechanisms other teams can reuse.
Selected engineering cases
Five independently framed case studies. Company or product appears as provenance; the engineering specialty is the entry point.
Move one surface. Keep the product shipping.
Production add-to-app architecture with Pigeon, multiple engines, feature flags and native fallbacks.
Design decisions that ship as code.
A governed Compose system designed for incremental adoption across a mature fintech product.
Portable product flows, native rendering.
Contract governance, Universal Card and platform-owned Android/Flutter presentation.
EV charging state the driver can trust.
Maps, reservations, queues, payments and a guided physical charging lifecycle.
Short films, social discovery, one Android product.
Playback, casting, local data and a working MVP 40 days after starting from scratch.
Architecture is useful when it improves delivery.
My work spans mature applications and early-stage products: modernising Android without rewrite freezes, embedding Flutter behind explicit host boundaries, building reusable UI systems and integrating mobile clients with backend-owned physical or media state.