Closed Bug 1006540 Opened 10 years ago Closed 10 years ago

[User Story] As a FxOS user who launches the Loop application, if Loop is not in logged-in status, I want to be prompted to log-in into Loop

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:WebRTC17,2.0, ft:webrtc])

User Story

As a FxOS user who launches the Loop application for the first time, I want to be prompted to log-in into Loop.

This situation can occur when Loop is launched either manually by clicking on Loop icon or by using an activity. This screen might be seen in 3 different possible conditions:
- User has never used Loop and hence it is the first time it’s launched.
- User has launched Loop before but he never entered successfully log-in details.
- User has launched Loop and logged-in before but he has successfully performed a log-out afterwards.

The following options would be offered to the user:
     1) Sign-in via MSISDN. (Need to detail based on MSISDN data flow. Need to take into account that entered MSISDN might correspond to device SIM or not)
     2)FxAccount: In this case, two situations may occur:
         2.1) If the user is signed in the device with Firefox Accounts (via FTU or via Settings), the registered email will be used as ID.
         2.2) If the user is not signed in the device with Firefox Accounts, the application will start the FxAccounts creation flow. During the creation process, user needs to verify the e-mail address before FxAccounts can be used. This needs to be done before continuing, so Loop will show an intermediate screen while listening for the event on verified (bug 1008901) to check this and continue.

- If user signs-out from FxAccounts later on (via the device settings menu), he will be also automatically logged-out from Loop.

- Before the user has successfully logged-in in Loop, if this is the first time he has done so he will be guided through a wizard-process to let him know about loop. During this process a first "loop call" will be made with the target of requesting the user the GUM permissions so they can be remembered and never asked back again. 

- After successful login in Loop the user will be directected to main loop page (Call History).

- The user does not have the option to skip the sign-in dialog or the wizard in case of first login(e.g. he cannot access Loop Call Log or any other Loop screen). If the user has not completed all the login / wizard steps he will be asked to do so before doing any further action... If the user closes and opens the application back he will be returned to the place he was before leaving the app so that he cannot skip this process.

NOTE: The exact flow, error cases, what happens after logging-in and so must be detailed in Loop Wireframes. UX Decision.
As a FxOS user who launches the Loop application for the first time, I want to be prompted to log-in into Loop.

This situation can occur when Loop is launched either manually by clicking on Loop icon or by using an activity. This screen might be seen in 3 different possible conditions:
- User has never used Loop and hence it is the first time it’s launched.
- User has launched Loop before but he never entered successfully log-in details.
- User has launched Loop and logged-in before but he has successfully performed a log-out afterwards.

The following options would be offered to the user:
     1) Sign-in via MSISDN. (Need to detail based on MSISDN data flow. Need to take into account that entered MSISDN might correspond to device SIM or not)
     2)FxAccount: In this case, two situations may occur:
         2.1) If the user is signed in the device with Firefox Accounts (via FTU or via Settings), the registered email will be used as ID.
         2.2) If the user is not signed in the device with Firefox Accounts, he will be redirected to the device settings application to sign-up into Firefox Accounts via that app.

- If user signs-out from FxAccounts later on (via the device settings menu), he will be also automatically logged-out from Loop.

- Once the user has successfully logged-in in Loop, the user ID will be reached at the Loop application in the device. 

- The user does not have the option to skip the sign-in dialog (e.g. he cannot access Loop Call Log or any other Loop screen). In that case the only way user could have to launch loop app is by clicking on a Loop session URL, which will start Loop Application in anonymous way.

NOTE: The exact flow, error cases, what happens after logging-in and so must be detailed in Loop Wireframes. UX Decision.
Blocks: loop_mobile_ID
User Story: (updated)
Depends on: 988394
Depends on: 1008901
User Story: (updated)
User Story: (updated)
Summary: As a FxOS user who launches the Loop application, if Loop is not in logged-in status, I want to be prompted to log-in into Loop → [User Story] As a FxOS user who launches the Loop application, if Loop is not in logged-in status, I want to be prompted to log-in into Loop
Priority: -- → P1
Whiteboard: [ucid:WebRTC17,2.0, ft:webrtc]
Depends on: loop_msisdn_verific, mobileid
Depends on: 1046170
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.