Beelinguapp provides stories in target languages translated into users' home languages, tagged by difficulty levels, but has significant shortcomings in personalization and cultural depth. Users, particularly English learners (EL students), faced challenges with:
These limitations contributed to disengagement and stereotype threat, negatively affecting language acquisition and student motivation.
We reviewed leading language-learning apps (Duolingo, Memrise, LingQ) and found none offer true community-driven storytelling or deep cultural context. This gap directly informed our feature set and prioritization.
Implement research-backed ed-tech to address language inequalities in his ESOL classroom.
Students falling behind due to inconsistent ESOL programs and lack of faculty training on new tools.
My initial sketch focused on the core “Community Stories” flow, with:
This low-fi version helped validate the information hierarchy before moving into mid-fi mockups.
As UX lead for Community Stories, my responsibilities included:
Primary methods of data collection:
Analysis methods included:
To ground our design in real user needs, I led an affinity‐diagramming workshop to synthesize qualitative insights from our contextual inquiries and think‐aloud sessions. This helped us:
The resulting affinity map became our north star—driving feature prioritization and informing the initial prototype.
User feedback indicated a positive reception of the dedicated community page and search functionality but pointed to issues with insufficient filtering and unclear story contexts.
Enhancements:
Feedback identified a need for additional filtering, clearer story contexts, and better UI presentation for the preview component.
Final iteration included:
Community-driven storytelling aligns with key educational principles:
This design reflects the Recognition Over Recall and Consistency & Standards UI principles, providing an intuitive, inclusive, and engaging experience for diverse language learners.
We ran five discrete usability sessions with both team members and external bilingual users:
Iterative testing was indispensable—each cycle revealed both usability wins and new pain points. In particular, our filtering feature received strong praise, and standardizing the Figma frames greatly improved layout consistency. Going forward, I plan to:
If I could tweak the assignment, I’d front-load the Figma workshops and extend the user-testing window to better accommodate busy schedules.