947195 - [DSDS][Wap Push] Browser on the correct SIM

Status: RESOLVED WONTFIX

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

Description

[Wilfred Mathanaraj [:WDM]]

As a user if I click on a link in the wap push message I want to be able to browse to the link using the SIM the message was received on.

Acceptance Criteria:

AC1: I want to use the SIM the wap push message was received on to browse to the link
AC2: I want to be informed if the default data sim has to be changed to browse to that link
AC3: if I need to change the data SIM then I expect the change only to be valid for that specific session only.

Comment 1

[Enpei]

(In reply to Wilfred Mathanaraj [:WDM] from comment #0)
> As a user if I click on a link in the wap push message I want to be able to
> browse to the link using the SIM the message was received on.
> 
> Acceptance Criteria:
> 
> AC1: I want to use the SIM the wap push message was received on to browse to
> the link
> AC2: I want to be informed if the default data sim has to be changed to
> browse to that link
> AC3: if I need to change the data SIM then I expect the change only to be
> valid for that specific session only.

Hi Wilfred,

Is there any reason why user must open the link from the very same SIM which received the wap push message? I mean using default primary outgoing data SIM to open links from another wap push message should be fine, right?

Thanks.

Comment 2

[Wilfred Mathanaraj [:WDM]]

if an operator sends a WAP Push message with a link to the portal (needs authentication against MSISDN) and there is content to be bought (which is billed against MSISDN) then the user needs to make sure he uses the right SIM to get to this link so he can be identified and billed.

Its easier for us to implement a straight use the SIM where ever the WAP Push message came from.

Comment 3

[Enpei]

(In reply to Wilfred Mathanaraj [:WDM] from comment #2)
> if an operator sends a WAP Push message with a link to the portal (needs
> authentication against MSISDN) and there is content to be bought (which is
> billed against MSISDN) then the user needs to make sure he uses the right
> SIM to get to this link so he can be identified and billed.
> 
> Its easier for us to implement a straight use the SIM where ever the WAP
> Push message came from.

Thanks, Wilfred. It just I tried on Android reference phone and it will not request to change outgoing data(just SI message with URL link, not payment related). But still it depends on what's the best approach for FxOS.

Comment 4

[Neo Hsieh [:neo]]

Attachment: [DSDS] WAP_Push_140110.pdf

Please check uploaded UX spec document, Any questions please let me know. Thanks

Comment 5

[Neo Hsieh [:neo]]

Attachment: [DSDS] WAP_Push_140121.pdf

UX sepc updated

Comment 6

[Neo Hsieh [:neo]]

Attachment: [DSDS] WAP_Push_140121_fixed.pdf

Add one page for normal process flow

Comment 7

[Gabriele Svelto [:gsvelto]]

Moving to the new Gaia::Wappush component.

Comment 8

[Neo Hsieh [:neo]]

Attachment: [DSDS] WAP_Push_140128.pdf

Comment 9

[Gabriele Svelto [:gsvelto]]

I'm about to implement bug 947192 so this will be next and I've got an issue with the current UX spec. It seems that we're allowing the user to open the link only with the SIM it's been received on; besides being different than what Android does it might be detrimental for the user. Case in point: the user has a dataplan only on one SIM but receives a SI message with a link on the other one, with the current UX design he won't be able to open the link at all.

My suggestion is to either go with Android's behavior as per Enpei's description in comment 3 (open the link with whatever dataplan is currently selected) or in the SIM switch screen to provide an option to switch SIMs and another go ahead with the current one (as opposed to switching SIMs or canceling the operation).

Comment 10

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

ni Carrie for DSDS UX.

Comment 11

[Carrie Wang [New account: [e-mail]]]

Hi Gabriele,  

For the first suggestion, since we don't support auto-switch for users (automatically switch the primary data and then switch it back after finishing the task), we can't adopt it for now, but hopefully we can make it soon in the future.

About the second suggestion, we did consider it before. However, it will take a lot of steps to go SIM manager and then come back to complete the operation and probably go there again to switch the SIM back afterwards. Our solution shorten the process by tapping the confirm key for SIM switch. In addition, the design pattern has been applied in MMS retrieve and other cases as well. We hope users can learn it in different scenario and then get used to it. Thanks! :)

Comment 12

[Wilfred Mathanaraj [:WDM]]

feature does not block release

Comment 13

[BMO Automation]

Firefox OS is not being worked on