Closed Bug 1007941 Opened 12 years ago Closed 11 years ago

[User Story] As a user I would like to have fall back mechanisms to communicate via Loop with non-Loop users

Categories

(Firefox OS Graveyard :: Gaia::Loop, defect, P1)

Product:
Firefox OS Graveyard
Component:
Gaia::Loop
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: oteo, Unassigned)

References

Details

(Whiteboard: [ucid:WebRTC22,2.0, ft:webrtc])

User Story

When I have tried to contact a user, and it is not possible because it is not signed-up in Loop I have the option to share with him an URL that he can use to connect to a Loop session. I see a message asking me whether I am interested in doing so, if I confirm there are two possibilities:

  - The contact has multiple IDs (e-mails or MSISDNs) I need to select which one.
  - There is only one ID, that one is the selected one.

If the ID is an e-mail the e-mail composer will be open via the e-mail activity, and if the ID is an MSISDN the SMS composer will be open instead. The Destination (ID), Body (containing URL) and Subject (in e-mail only) fields are prepopulated.

Note: In case there are more applications that offer the "share" activity, the user will be prompted about what activity want to use to share the URL so SMS and E-mail applications respectively will be the default ones but there could be more options.

Important: QA should cover in the test plan the scenario when link clickers are on browsers not supporting H264, as Chrome or Opera, so VP8 is used instead.
No description provided.
Blocks: loop_start_call
User Story: (updated)
Depends on: 988394
No longer depends on: 988394
Depends on: 988396
User Story: (updated)
Depends on: 1009550
Summary: As a user I would like to have fall back mechanisms to communicate via Loop with non-Loop users → [User Story] As a user I would like to have fall back mechanisms to communicate via Loop with non-Loop users
Priority: -- → P1
Whiteboard: [ucid:WebRTC22,2.0, ft:webrtc]
No longer depends on: 1026066
Depends on: 1027027
Please note that this bug should include tests for VP8 support in scenarios where link clickers are on browsers not supporting H264.
(In reply to Romain Testard [:RT] from comment #1) > Please note that this bug should include tests for VP8 support in scenarios > where link clickers are on browsers not supporting H264. Sure, in the test plan that scenario is already covered but I will add a Note in the US too. Thanks!
User Story: (updated)
Depends on: 1034041
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.