Page MenuHomePhabricator

As someone with notifications turned on, I want notifications to lead me to somewhere that is actionable / appropriate
Closed, ResolvedPublic

Description

Why are we doing this?

We will be supporting all Echo notifications / alerts in the iOS app, so we would like to know where these alerts should direct people / link out to. We would also like to use this as a way to plan for the future (eg. are there MVP versions of web features that we want to prioritize in service of a better notification experience?)

Audience story

As someone with notifications turned on, I want notifications to lead me to somewhere that is actionable and appropriate, with as few redirects to web as possible.

Relevant documents

Proposed mapping

Google Spreadsheet with notification definitions and mappings (currently duplicated from RHo's slide deck)

Proposed general notification flow

View flow on Miro

iOS Notifications Flows - Copy of General notifications flow.jpg (3×12 px, 890 KB)

Related

https://phabricator.wikimedia.org/T288687
https://phabricator.wikimedia.org/T288670

Event Timeline

@cmadeo one question with the flow chart - it says when the user goes into app notification center and "user dismisses notification" > "notification is dismissed in the app center and on the web", what does it mean to dismiss a notification in the app center? Is this similar to Android's archive feature?

I think the spreadsheet deep links make sense. We're shooting for version 1, correct? We may reach out as we dig into deep link locations if we have more questions.

@Tsevener sorry this was before we defined terminology, please read 'dismissed' as either tapping on or 'marking as read'

And yes, we're shooting for no. 1

I'm going to move this into Blocked and Waiting for now. I feel like it's covered in other tasks (T288687, T288670), so maybe it can be a QA-only task to be looked at once that routing is done.

I believe this work is done and testable. Note we are not doing long pressing on the system notification because we decided to cut rich notification support for now. I think the only bubble in this flow that could also be inaccurate is "Recipient taps on a secondary link (to be designed) or long presses/swipes. We aren't supporting long pressing a cell, and so far secondary links only show up after tapping "More" from the swipe menu.

Moving this into Needs Design Review since it's a little fuzzy.

@Tsevener, thanks for these notes, I've updated the flow and will move over to QA now.

JMinor claimed this task.