During my Application Design foundational course at HfG Schwäbisch Gmünd, we faced a challenge: redesigning the Moodle mobile app. We focused on improving Moodle’s usability, as the original app suffered from overly deep information structures that made simple tasks frustrating. Our goal was not only to simplify navigation but to rethink the app strategically. By applying a user-centered design approach within an academic setting, we aimed to create a more intuitive learning tool. The final concept was iteratively tested and validated with users to ensure a user-centered experience and functional improvement.
The redesigned Moodle concept centers on empowerment through clarity. A personalized dashboard surfaces what students actually need: upcoming deadlines, urgent messages, and tools for fast submission. Integrated voice chat fosters spontaneous collaboration, turning the app into a shared space—not just a task list. Developed in Figma, the prototype was tested and refined through multiple feedback loops. Each iteration simplified interactions, reduced decision fatigue, and focused on functional relevance. The result is a learning companion that doesn’t overwhelm but supports—from quick checks to deep dives.
To understand Moodle from a student’s perspective, we mapped daily usage patterns and dissected existing screen flows. Key insights emerged quickly: essential content was buried, notifications felt noisy, and the app lacked focus. Through interviews and usability tests, we observed how students worked around the app rather than with it. It wasn’t the features that failed—it was their framing. By combining structural analysis with real user stories, we uncovered a clear message: Moodle needed to become less about menus and more about moments that matter.
Real user voices reveal the real problems. Interface pain points often stem from structural blind spots. Testing early and iteratively allowed us to design with—not just for—students. Relevance trumps feature lists: users connect with tools that reflect their daily flow. And finally, design thinking isn't a checklist—it’s a mindset that only works when adapted to the problem at hand.
The system architecture was restructured for flow, not friction. At its core stands the dashboard, dynamically populated based on urgency and context. A notification hierarchy ensures critical updates rise to the surface without adding clutter. Course navigation was flattened into clearer pathways, avoiding deep nesting. The voice chat integrates file sharing, enabling real-time exchange without leaving the app. Every design decision—from color to content grouping—was tested against real student routines. The system adapts to learning rhythms, prioritizing visibility, speed, and relevance.
