StudyBuddy

Organizing the Product Around the Course Hub: The course was chosen as the primary unit of product organization instead of treating every feature as an isolated destination. The relational model connects each course to enrollments, notes, resources, discussions, meetings, events, progress, and AI conversations, while the interface exposes these systems through a unified course hub. This reduces context switching, gives every action a clear academic context, and allows the dashboard to aggregate activity without losing its connection to the original course.

Building a Complete Account Lifecycle Instead of a Cosmetic Login: Registration and account activation were separated so a newly created email account does not receive an authenticated token before verification. Passwords are hashed with bcrypt, email codes are HMAC-hashed rather than stored in plain text, and each code has an expiry, consumed state, and attempt limit. The system also links Google identities to existing users, returns a generic forgot-password response to reduce account disclosure, and protects frontend and API routes independently. This created a complete account lifecycle rather than a local sign-in mock.

Treating Responsiveness, Localization, and Display Access as Interface Architecture: Mobile behavior, Arabic support, and display preferences were treated as system-level concerns rather than late visual patches. Central breakpoints control navigation, spacing, cards, dialogs, and typography across device classes, switching between full and compact sidebars and a mobile drawer with bottom navigation. Locale, direction, theme, contrast, text size, and number style are also managed centrally, alongside reusable loading, empty, and error states. This keeps the experience consistent without solving each screen independently.