1138908 - [UX] Design Spike: Create concept for an in-product communication channel

Status: RESOLVED FIXED

(Firefox :: General, defect)

Description

[(Currently slow to respond) Philipp Sackl [:phlsa] (Firefox UX) please use needinfo]

It is currently very hard for us communicate with users when we don't have the time to e.g. let a notification bar ride the trains. The only channel we have right now is the snippet, which is only seen by a portion of our user base.

Objectives of this bug:
- Design an unintrusive messaging mechanism
- Define constraints for messages (e.g. only text, images and links may be used)
- Messages should be seen by a majority of users
- Users should probably be able to opt out of these messages

Notes for implementation:
- It should be possible to A/B test different kinds of messaging
- Should be possible to only send messages to certain locales

Comment 1

[Winston Bowden]

measurement:
- ensure we can measure impressions
- measure CTR

Comment 2

[Marco Mucci [:MarcoM]]

Hi Michael, can you provide a point value.

Comment 3

[Verdi [:verdi] Best to slack me]

(In reply to Marco Mucci [:MarcoM] from comment #2)
> Hi Michael, can you provide a point value.

8 points

Comment 4

[(Currently slow to respond) Philipp Sackl [:phlsa] (Firefox UX) please use needinfo]

As a note: it makes sense that we already have a bunch of messaging interactions with the user:
- Notification bars
- System alerts
- Page-specific doorhangers (e.g. permissions)
- Feature tours

Many of those mechanisms have problems. Missed permissions doorhangers are mostly lost, feature tours can be too in-your-face etc. It would be great if we could use this opportunity to fix at least some of that situation.