Closed
Bug 1085388
Opened 11 years ago
Closed 9 years ago
[UX] Notifying a user that someone joined his room even if Firefox is closed
Categories
(Hello (Loop) :: Client, defect, P3)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
| backlog | backlog+ |
People
(Reporter: RT, Unassigned)
References
Details
(Whiteboard: [investigation])
User Story
As a registered or account-less user on a computer where Firefox is installed but closed, I want to be notified when some relevant event happens in a room I have joined before, so that I can be aware of what is happening in the room (someone joined the room, someone added a URL to the room, someone added a comment to the room, ...). Acceptance criteria: * Notifications delivered on OSX, Windows, Linux even when Firefox is closed * Notifications can be turned on or off Users are used to closing a communication client whilst still being able to receive notifications when someone tries to talk to them: * On desktop: Skype, Viber, OCS, Vidyo * On mobile: Skype, Viber, Whatsapp, Hangouts, Tango, Kik, WeChat, ... Reachability is key for a communication solution and it seems Firefox is often used as a secondary browser (i.e installed but not often used). This means that a scenario whereby a user closes Firefox and expects it to send a notification when someone joins a room is likely. UX work is needed to understand the following: * How can we notify a user on the main supported platforms * Should we let a user take an action directly from the notification (join a room from a notification) * How can notifications be managed (turn-off notifications when Firefox is closed)
No description provided.
Comment 1•11 years ago
|
||
do you have a target for this type of functionality? even if fx40.
backlog: --- → backlog
Flags: needinfo?(dhenein)
Comment 2•11 years ago
|
||
My hope for this was as soon as possible. I have it shown in my original rooms design document, using native system notifications to alert a user that someone has joined their room (and they could click it to open that room in Firefox).
Flags: needinfo?(dhenein)
Comment 3•11 years ago
|
||
I've set this to Fx37? and we can evaluate the priority of this relative to other Fx37 work in our triage.
backlog: backlog → Fx37?
Updated•11 years ago
|
backlog: Fx37? → Fx38?
Comment 4•11 years ago
|
||
investigation bug only at first, on what it would take to plug into native system notifications.
backlog: Fx38? → Fx38+
Priority: -- → P3
Whiteboard: [UX] → [UX][investigation]
Updated•11 years ago
|
backlog: Fx38+ → backlog+
Rank: 35
Flags: firefox-backlog+
| Reporter | ||
Updated•10 years ago
|
User Story: (updated)
Updated•10 years ago
|
Whiteboard: [UX][investigation] → [investigation]
Comment 5•9 years ago
|
||
Support for Hello/Loop has been discontinued.
https://support.mozilla.org/kb/hello-status
Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•