Closed Bug 1138908 Opened 9 years ago Closed 1 year ago

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

Categories

(Firefox :: General, defect)

x86_64
All
defect
Points:
8

Tracking

()

RESOLVED FIXED
Iteration:
41.1 - May 25

People

(Reporter: phlsa, Assigned: verdi)

Details

(Whiteboard: [ux])

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
Flags: firefox-backlog+
measurement:
- ensure we can measure impressions
- measure CTR
Flags: qe-verify-
Hi Michael, can you provide a point value.
Assignee: nobody → mverdi
Status: NEW → ASSIGNED
Iteration: --- → 40.1 - 13 Apr
Flags: needinfo?(mverdi)
(In reply to Marco Mucci [:MarcoM] from comment #2)
> Hi Michael, can you provide a point value.

8 points
Points: --- → 8
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.
Flags: needinfo?(mverdi)
Iteration: 40.1 - 13 Apr → 40.2 - 27 Apr
Iteration: 40.2 - 27 Apr → 40.3 - 11 May
Iteration: 40.3 - 11 May → 41.1 - May 25
Severity: normal → S3
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.