For Wish's mobile app, should we optimize for faster load times and performance or add more features and functionality to enhance the shopping experience?

Introduction

The trade-off we're examining for Wish's mobile app is between optimizing for faster load times and performance versus adding more features and functionality to enhance the shopping experience. This scenario touches on the classic tension between speed and richness in mobile app development. I'll analyze this trade-off by considering user needs, business goals, and technical constraints to provide a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking Wish might be facing user retention issues. Could you share any recent trends in our user engagement metrics?

Why it matters: Helps prioritize between speed and features based on current user behavior. Expected answer: Declining engagement, especially in app session duration. Impact on approach: Would lean towards performance optimization if users are dropping off quickly.

• Business Context: Based on Wish's business model, I assume we operate on thin margins. How critical is our conversion rate to overall profitability?

Why it matters: Determines whether we should focus on speed for higher conversions or features for higher average order value. Expected answer: Conversion rate is crucial due to thin margins. Impact on approach: Would prioritize speed improvements to boost conversions.

• User Impact: I'm guessing our user base is price-sensitive. How does our target demographic typically access the app - via high-end devices or budget smartphones?

Why it matters: Influences whether performance or feature richness is more critical for our core users. Expected answer: Majority use budget smartphones with limited processing power. Impact on approach: Would emphasize performance optimization for better experience on lower-end devices.

• Technical: Considering our current app architecture, how challenging would it be to significantly improve load times without a major overhaul?

Why it matters: Determines the feasibility and resource requirements for performance improvements. Expected answer: Moderate difficulty, requiring optimization of existing code and assets. Impact on approach: Would explore quick wins in performance before considering new features.

• Resource: Given our current team structure, do we have more bandwidth in our performance engineering team or our feature development team?

Why it matters: Helps align our strategy with available resources and expertise. Expected answer: More bandwidth in feature development team. Impact on approach: Might consider a hybrid approach, focusing on high-impact features while gradually improving performance.