Engineer by craft. Builder by design.

Writing / Mobile

What Swiggy-scale mobile actually taught me

Before startup life, I shipped mobile at Swiggy. Scale changes which bugs matter, and how little your happy path predicts production.

Back to writing
MCMukul Chugh
1 min read
x
Four illustrative phones show ready, empty, offline, and low-battery states.
Design for the states beyond the happy path. Illustrative concept.

Before founding-engineer life, I built mobile products at Swiggy. Different pressure: messy networks, old devices, release trains that don't pause for elegant abstractions.

Three things stuck.

Your happy path is a rounding error. Empty states, double-taps, and degraded modes are the feature.

Abstractions layers earn rent or they die. At scale, every unnecessary layer becomes divergent iOS/Android behavior.

A mobile release isn't a deploy: it lives on people's phones. Flags, staged rollouts, and crash analytics aren't "platform work." They're part of shipping.

Startups don't have that traffic. They still have production. Treat the last 5% as the product, not cleanup after the demo.

What should
we make next?

Bring the idea you keep coming back to.
Let’s see where a conversation takes it.

15 minutes.

An idea is enough.