The same app, two completely different products — Swiggy on Android vs iOS
A side-by-side comparison of Swiggy's delivery tracking UI across platforms reveals more than visual differences — it surfaces distinct philosophies about what each user base values. Information density vs. minimalism. Utilitarian control vs. polished simplicity.
↗ Connected to: how platform-native design assumptions shape user expectations — the same feature can need two different UX treatments for two different user segments.
Read on LinkedIn →
A soda can taught me something about SaaS error messages
Most soft drink cans in India are 300ml — but the label says 1 serving = 200ml. Technically correct. Practically useless. The same pattern shows up constantly in SaaS: systems that disclose information but don't actually help users solve the problem.
↗ Connected to: the error translation work in the retail campaign management tool — where every machine error was mapped to plain-language guidance with actionable next steps.
Read on LinkedIn →

8 things most SaaS products get wrong — and how to fix them
These aren't edge cases or nitpicks. They're patterns I've seen repeatedly across B2B SaaS products — including ones I've built myself. Each one is fixable. None require a redesign. They just require someone paying attention.
Onboarding Default settings Edge cases Progress indicators Empty states Error messages In-app copy Contextual help

Open to new opportunities

Senior PM roles, product leadership, and advisory work in AdTech or retail media.

Connect on LinkedIn →

or email dhiraj_sharma00@yahoo.com