Design Decision Postmortem: Choosing Mobile-First vs. Feature-First at a Fintech Startup

Design · 6 min read

Early product analytics showed a majority of sessions began on mobile, but power users still relied on a desktop-only CSV export feature. The team faced a crossroads: invest limited resources in a richer desktop feature set or rewire core flows for mobile-first simplicity. They chose mobile-first, arguing that reaching new, less technically committed users would drive volume and network liquidity before deepening power features.

Designers reworked core transaction flows for single-hand interaction, optimized for intermittent connectivity, and reduced screen density to prioritize glanceability. Some advanced features were maintained as web-only beta releases but hidden from default flows. Product leadership used guardrails: a timeline to add top-requested desktop features and a set of success metrics tied to mobile conversion and onboarding velocity.

After six months, mobile DAU rose 42% and new-user activation improved significantly, but power-user churn increased slightly due to the missing desktop capabilities. The team accepted the trade-off and created a roadmap to reintroduce high-impact desktop functionality. In hindsight, they recommend a hybrid early-communication plan to better set expectations for power users while preserving mobile-first momentum.