For D2L's Brightspace mobile app, should development efforts focus on feature parity with the desktop version or on creating unique mobile-first experiences?

Introduction

For D2L's Brightspace mobile app, we're facing a critical decision: should we prioritize feature parity with the desktop version or focus on creating unique mobile-first experiences? This trade-off involves balancing user expectations, development resources, and the potential for innovation in the mobile learning space. I'll analyze this decision through the lens of product strategy, user experience, and technical feasibility.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming Brightspace is a learning management system (LMS) used by educational institutions. Could you confirm if this is correct and if there are any specific market segments (e.g., K-12, higher education) we're focusing on?

Why it matters: Different segments may have varying mobile usage patterns and needs. Expected answer: Primarily higher education, with some K-12 presence. Impact: Would influence feature prioritization and mobile-first design decisions.

• Business Context: Based on the ed-tech landscape, I'm thinking mobile usage might be growing rapidly. What percentage of our current user base accesses Brightspace via mobile devices?

Why it matters: Helps quantify the importance of mobile strategy. Expected answer: Around 30-40% of users, with steady growth. Impact: Higher percentages would justify more investment in mobile-first experiences.

• User Impact: Considering the diverse needs in education, I'm curious about our primary user personas. Who are the main user groups (e.g., students, instructors, administrators) and what are their key mobile use cases?

Why it matters: Ensures we're addressing the most critical mobile scenarios. Expected answer: Primarily students for content consumption and assignment submission; instructors for grading and announcements. Impact: Would guide feature prioritization and UX design for mobile.

• Technical: Given the complexity of LMS systems, I'm wondering about our current mobile app architecture. Is it native, hybrid, or web-based?

Why it matters: Affects the feasibility and effort required for feature parity or mobile-first development. Expected answer: Hybrid app using React Native. Impact: Would influence development strategy and timeline for either approach.

• Resource: Considering the scope of this decision, I'm thinking about our mobile development team capacity. How many dedicated mobile developers do we have, and what's their current workload?

Why it matters: Helps assess feasibility of different approaches within current constraints. Expected answer: Small team of 5-7 developers, currently at 80% capacity. Impact: Limited resources might favor a phased approach or narrower scope for mobile-first initiatives.