Notes from engineering sync:

We'd like to sync and land on phases of development. This is a big screen so it would be nice to build this incrementally, with more clear lines on what is "releasable". These are possible increments I can think of:

1. Build one big list that displays all projects and notifications, no tabs, no filters, no search. Edit button and selecting to mark as read and unread still works. Swipe actions are maybe only mark as read and go to primary url? This also includes badges.
2. Add tabs
3. Add additional quick actions & deep links.
4. Add Search
5. Add local filter button, screen and functionality (read, unread, all)
6. Add local project filter button, screen and functionality

@cmadeo @JMinor This is something we'd like to discuss in sync on Thursday. Can y'all sort a priority list of UI functionality on this screen so we can be sure we're building the most important stuff first? The list above are just ideas around ways to break it down. Tagging @Dmantena in case he has any other thoughts.

Yep totally understandable. From my perspective 1 and 3 are the most important, in that order. I think a version with only 1 would be "shippable" but 3 seems pretty vital to make the workflows tractable at all.

Here's my ordering for the others:

• Add local filter button, screen and functionality (read, unread, all)
• Add local project filter button, screen and functionality
• Add Search
• Add tabs

We've already cut type filter from the scope, but I do think showing all read/unread as step towards filtering is useful. Also I think search is a no go unless we can get the API update (otherwise its misleading bc you're not able to search all your notifications just the local ones, so the platform might make that decision for us.

+1 to @JMinor's prioritization!