OpenMU
one focused interface for the university tasks that otherwise live across separate services.livestudent utility · installable web app
Next.jsAstryxPWATypeScript
the problem
routine campus information is split across different surfaces. Students need to move between identity, class, timetable, transcript, event, alert, and service contexts for tasks that belong to the same day.the approach
- 01bring the recurring student workflows into one unofficial companion rather than reproduce the university around them
- 02package the experience as an installable PWA so the same interface works as a website and a home-screen app
- 03use a private sign-in boundary for personal campus information while keeping the product identity and limitations clear
key decisions
organize around student intentdigital ID, classes, timetable, transcript, events, alerts, and campus services are grouped as one daily workflow.
keep the interface consistentNext.js and Astryx provide a shared responsive component language across information-dense screens.
state the boundaryOpenMU is identified as an unofficial student-built companion, not an official university service.
the result
- a live, installable application with a single entry point for core campus workflows
- a responsive interface that can serve phone and desktop use without separate clients
- personal information remains behind the application login rather than appearing in the public portfolio