Is it better for Wise to focus on improving the mobile app experience or enhancing the web platform?

Introduction

The trade-off between improving Wise's mobile app experience or enhancing the web platform is a critical decision that could significantly impact user engagement, retention, and overall business growth. This scenario requires careful consideration of user preferences, technological constraints, and strategic priorities. I'll analyze this trade-off by examining key metrics, designing experiments, and providing a data-driven recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about Wise's current market position. Could you share how our mobile app and web platform usage compare in terms of transaction volume and user engagement?

Why it matters: Helps understand current user preferences and behavior Expected answer: Mobile app accounts for 60% of transactions, web platform 40% Impact on approach: Higher mobile usage might justify prioritizing app improvements

• Business Context: Based on our revenue model, I assume a significant portion comes from transaction fees. How does the revenue split between mobile and web compare to the usage split?

Why it matters: Aligns decision with revenue generation Expected answer: Revenue split closely mirrors usage split Impact on approach: If web generates disproportionate revenue, it might influence prioritization

• User Impact: Considering our user segments, are there any notable differences in how various groups (e.g., frequent vs. occasional users, personal vs. business) prefer mobile vs. web?

Why it matters: Ensures we're addressing needs of key user segments Expected answer: Business users prefer web, while personal users lean towards mobile Impact on approach: Might lead to a segmented strategy rather than one-size-fits-all

• Technical: Regarding our current architecture, how interconnected are our mobile app and web platform? Are there shared components or APIs that would be affected by improvements to either?

Why it matters: Assesses potential technical dependencies and efficiencies Expected answer: Significant shared backend, but distinct frontend codebases Impact on approach: Could influence decision based on potential for shared improvements

• Resource: What's our current team structure and capacity for mobile app development versus web development?

Why it matters: Determines feasibility of execution for each option Expected answer: Balanced team with slightly more mobile developers Impact on approach: Might favor mobile improvements if resource allocation is easier