Engineering write-ups, not portfolio cards.

Smaller rebuild surfaces · state the team could actually reason about

Untangling state in a scaling Flutter app — why boundaries beat the library

The team blamed their state management library. The real problem was missing boundaries. Here's how restructuring state — not switching tools — made a growing Flutter app reasonable to change again.

Faster time-to-interactive, globally

Cutting cold-start time on a global consumer app

A slow launch was quietly eroding retention. Systematic profiling of the startup path recovered meaningful time-to-interactive — with no new features and no redesign.

~40% less boilerplate · 99.5%+ crash-free

Modernising a 1M+ user codebase without a rewrite

An app that shipped fast in year one had grown hard to change. A staged architecture migration restored velocity while holding stability — no big-bang rewrite.

Parity gap 50% → 25% · 2-day integration SLA

Architecting a Flutter SDK used by teams worldwide

A developer-facing SDK lives or dies on integration experience. Closing native/Flutter parity and holding a tight support SLA turned friction into adoption.