Skip to content
umar✳.devLet’s talk ↗

Writing

A few things worth nerding out about.

Mobile performance, Flutter architecture, and the business cost of technical decisions — written for founders, CTOs, and engineering leads.

Your App Shouldn't Need to Know Everything That Happens

Event-driven communication in Flutter and Android isn't really about sending events. It's about letting the right parts of an app react to change without knowing too much about each other — and knowing when a global event bus is the wrong tool.

When to Modularise a Flutter App (and When Not To)

Splitting a Flutter app into packages won't make it clean — it moves the mess behind package boundaries. A practical guide to when modularity actually pays off, how to structure it efficiently, and the anti-patterns that quietly ruin it.

Your UI Shouldn't Wait for the Network

Most mobile apps don't feel slow because the network is slow — they feel slow because the UI waits for it. A practical guide to Flutter apps that stay fast on 2G, flaky Wi-Fi, and no connection at all: a single source of truth, cache-first data, and skeletons instead of spinners.

Why your app's cold start is quietly costing you users

The users you lose to a slow launch never complain — they just don't come back. A practical guide to measuring cold start, finding where the time goes, and getting it back.

The most expensive bug doesn't crash anything

When a revenue flow breaks, it usually breaks quietly — no error, no ticket, just a number that's lower than it should be. That's where the money hides.