Closed
Bug 1300222
Opened 8 years ago
Closed 8 years ago
Send Tab notification should be a Heads-Up notification if possible
Categories
(Firefox for Android Graveyard :: General, defect, P1)
Firefox for Android Graveyard
General
Tracking
(firefox51 fixed)
RESOLVED
FIXED
Firefox 51
Tracking | Status | |
---|---|---|
firefox51 | --- | fixed |
People
(Reporter: Grisha, Assigned: Grisha)
References
Details
(Whiteboard: [MobileAS][send-tab])
Attachments
(2 files)
According to Android's notification docs, for a notification to be shows as a "heads up", it should have a high priority and use either one of ringtone or vibrate a device.
See https://developer.android.com/guide/topics/ui/notifiers/notifications.html#Heads-up
Assignee | ||
Updated•8 years ago
|
Whiteboard: [MobileAS] → [MobileAS][send-tab]
Comment 1•8 years ago
|
||
Given that this is probably the most invasive UX, I think we should tread carefully here. Can I see a build of this to test?
Phone is asleep > User receives tab > Heads up notification > phone vibrates > Action in notification to "Open now".
Note: this UX should replace the current notifications UX if we choose to go down this path, rather than supplement it. I'm mostly worried about notification fatigue here since it's easy to "block all" but extremely difficult to recover from.
Comment 2•8 years ago
|
||
^ In case I was unclear, bug 1300225 (in addition to our current notifications) would be the V1 UX we can go with in the mean time.
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → gkruglov
Priority: P3 → P2
Updated•8 years ago
|
Priority: P2 → P1
Updated•8 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•8 years ago
|
||
Attached is the Heads-up build. In this case, I'm using a default notification sound and a high importance flag to trigger "heads up" mode.
In practice, this feels quite natural - tab comes in, heads-up notification is displayed for a couple of seconds and then goes away.
- If phone is in regular mode (sound enabled), notification sound is played.
- If phone is in vibrate mode, quick vibration happens.
- If phone is in silent mode, there's no vibration or sound, but notification is still displayed in the heads up mode.
You might have to manually trigger a sync to see the notifications due to Bug 1300230 - ymmv.
Attachment #8788693 -
Flags: feedback?(alam)
Comment 4•8 years ago
|
||
Comment on attachment 8788693 [details]
Heads-up build URL
tried this IRL, in practice, it feels a lot better than a snackbar actually. I think we should go with this UX. For versions of Android that won't get the heads up, they will still get the current notification UX so it degrades nicely too.
Sebastian, do you foresee any compat issues that I might not be thinknig about?
Flags: needinfo?(s.kaspari)
Attachment #8788693 -
Flags: feedback?(alam) → feedback+
Comment 5•8 years ago
|
||
To be clear, we should not be doing bug 1300225 if we're doing this one.
Comment hidden (mozreview-request) |
Comment 7•8 years ago
|
||
mozreview-review |
Comment on attachment 8789951 [details]
Bug 1300222 - Trigger heads-up notification mode for incoming tabs
https://reviewboard.mozilla.org/r/77976/#review76960
Attachment #8789951 -
Flags: review?(ahunt) → review+
Pushed by gkruglov@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bce489c0ccba
Trigger heads-up notification mode for incoming tabs r=ahunt
Comment 9•8 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-firefox51:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 51
Comment 10•8 years ago
|
||
(In reply to Anthony Lam (:antlam) from comment #4)
> Sebastian, do you foresee any compat issues that I might not be thinknig
> about?
Not really. Just note that Android does not guarantee to show a notification as a heads-up notification and that the behavior triggering a heads-up notification can change in future versions.
Flags: needinfo?(s.kaspari)
Updated•8 years ago
|
Iteration: --- → 1.4
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•