2024-09-19 - UX/UI Working Group Meeting
Date
Sep 19, 2024
Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
10 mins | Quick updates on current projects |
| |
30 mins | Discussion on notifications and grouping | @Sam Daitzman |
Meeting notes
1. Overdue Assignment Notifications:
Current Implementation:
On Web, multiple overdue assignment notifications show separately, even if they belong to the same course (Level 1).Proposed Grouping Levels:
Level 2: Group notifications by course. Users receive one notification per course, regardless of how many assignments are overdue.
Level 3: One notification for all overdue assignments across courses. Tapping the notification leads to a view showing all overdue assignments.
Mobile vs. Web:
On mobile, users can view all overdue assignments at Level 3, while on Web, routing still needs to be refined. Tapping on Level 2 should lead users to a course's Dates tab for clarity.
2. Migration to Confluence:
The existing notification tables and documentation in Notion and Figma will be migrated to Confluence for better visibility and input.
The Confluence database will help catalog metadata for all types of notifications, ensuring alignment and feedback collection.
3. Forum Notifications:
Forum notifications were the first implementation of the Web notification framework under a separate project. These notifications are categorized as "discussion" in the broader notification system.
Other notification categories include course dates and grading.
A second forum-related project is improving course updates, which will require product and UX exploration