Closed Bug 1030253 Opened 7 years ago Closed 7 years ago

[UX] Refined UX: Desktop client needs "incoming call" visual and audio (ringing) notification (alerting)

Categories

(Hello (Loop) :: Client, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: abr, Assigned: dhenein)

References

Details

(Whiteboard: [ux] p=3 s=33.3 [qa-])

User Story

As a FF browser user (signed-in or not), I get informed through audio and visual notifications of an incoming call, so that I can decide to answer it or not.
+++ This bug was initially created as a clone of Bug #1011472 +++

This is being opened for any (additional) UX work associated with called user alerting.
Adding needinfo from https://bugzilla.mozilla.org/show_bug.cgi?id=1011472#c26
No longer depends on: 1011472
Flags: needinfo?(mmucci)
Summary: [UX] Desktop client needs "incoming call" visual and audio (ringing) notification (alerting) → [UX] Refined UX: Desktop client needs "incoming call" visual and audio (ringing) notification (alerting)
Added to Iteration 33.2
Status: NEW → ASSIGNED
Flags: needinfo?(mmucci)
No longer blocks: 1027053
The following data should be part of the incoming call visual notification:
Incoming call visual notification when not signed in (link call-back only):
* URL name (custom or randomly generated name)
* Information whether the caller's media selection is audio only or audio+video
* Link creation date

Incoming call visual notification when signed in and receiving a link call-back:
* URL name (custom or randomly generated)
* Information whether the caller's media selection is audio only or audio+video
* Link creation date

Incoming call visual notification when signed in and receiving a direct call:
* Caller's friendly name (or ID if no friendly name)
* Caller's avatar (or default avatar if not applicable)
* Information whether the caller's media selection is audio only or audio+video
(In reply to Romain Testard [:RT] from comment #3)
> The following data should be part of the incoming call visual notification:
> Incoming call visual notification when not signed in (link call-back only):
> * URL name (custom or randomly generated name)
> * Link creation date

Both are bug 1020449

> * Information whether the caller's media selection is audio only or
> audio+video

This needs a new bug (note: I can't see a bug for the standalone client to select audio+video or audio only. I may have missed it, but it'd probably be worth a separate bug to displaying the selection).
Depends on: 1020449
Whiteboard: [ux] p=3 s=33.2 [qa-] → [ux] p=3 s=33.3 [qa-]
> 
> > * Information whether the caller's media selection is audio only or
> > audio+video
> 
> This needs a new bug (note: I can't see a bug for the standalone client to
> select audio+video or audio only. I may have missed it, but it'd probably be
> worth a separate bug to displaying the selection).

This is the bug https://bugzilla.mozilla.org/show_bug.cgi?id=1000127 where the user story says:
As a WebRTC browser but not on Firefox URL clicker, my browser opens the URL on a new Tab and I can decide to call-back the URL generator with audio only or video, so that I can define if the callee will see me or not.      

The choice of the link clicker will define the calling mode which will appear on the callee side.
client has this - will open bug to update audio files when they arrive
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.