I have some questions about the details of linking out to Monitor and Send, particularly in the case where the button says "Continue as ...". I'm assuming that these buttons will open monitor.firefox.com or send.firefox.com in a new tab, but the mocks don't specify what should happen in that new tab. We need to consider a little state matrix where the browser is either signed in or not, and the website is either not signed in, signed in as the same user, or signed in as a different user. What is the desired experience in each of these cases? My guess at the optimal desired experience is: | | **Browser not signed in** | **Browser signed in as UserA** | | --- | --- | --- | | **Website not signed in** | Opens FxA signin page for the website | Opens website with UserA automagically signed in and ready to go | | **Website signed in as UserA** | Opens website in existing state, signed in as UserA | Opens website in existing state, signed in as UserA | | **Website signed in as UserB** | Opens website in existing state, signed in as UserA | Opens website with UserB automagically signed out, UserA automagically signed in and ready to go | It's not trivial to build that experience based on what we have available today, but if that's where we want to be then we can figure out how to work towards it. It will probably reqiure us to spin off a couple of dependant bugs for making changes in Monitor and Send. A slightly jankier experience, but which could be a lot quicker to ship, would be the following: | | **Browser not signed in** | **Browser signed in as UserA** | | --- | --- | --- | | **Website not signed in** | Opens FxA signin page for the website | Opens FxA signin page for the website, prefilled for one-click signin as UserA | | **Website signed in as UserA** | Opens website in existing state, signed in as UserA | Opens website in existing state, signed in as UserA | | **Website signed in as UserB** | Opens website in existing state, signed in as UserA | Opens FxA signin page for the website, prefilled for one-click signin as UserA | Ryan, thoughts? Would you be happy for us to do the second first as an MVP, then the first "automagical" version as a followup?
Bug 1562006 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I have some questions about the details of linking out to Monitor and Send, particularly in the case where the button says "Continue as ...". I'm assuming that these buttons will open monitor.firefox.com or send.firefox.com in a new tab, but the mocks don't specify what should happen in that new tab. We need to consider a little state matrix where the browser is either signed in or not, and the website is either not signed in, signed in as the same user, or signed in as a different user. What is the desired experience in each of these cases? My guess at the optimal desired experience is: | | **Browser not signed in** | **Browser signed in as UserA** | | --- | --- | --- | | **Website not signed in** | Opens FxA signin page for the website | Opens website with UserA automagically signed in and ready to go | | **Website signed in as UserA** | Opens website in existing state, signed in as UserA | Opens website in existing state, signed in as UserA | | **Website signed in as UserB** | Opens website in existing state, signed in as UserA | Opens website with UserB automagically signed out, UserA automagically signed in and ready to go | It's not trivial to build that experience based on what we have available today, but if that's where we want to be then we can figure out how to work towards it. It will probably require us to spin off a couple of dependent bugs for making changes in Monitor and Send. A slightly jankier experience, but which could be a lot quicker to ship, would be the following: | | **Browser not signed in** | **Browser signed in as UserA** | | --- | --- | --- | | **Website not signed in** | Opens FxA signin page for the website | Opens FxA signin page for the website, prefilled for one-click signin as UserA | | **Website signed in as UserA** | Opens website in existing state, signed in as UserA | Opens website in existing state, signed in as UserA | | **Website signed in as UserB** | Opens website in existing state, signed in as UserA | Opens FxA signin page for the website, prefilled for one-click signin as UserA | Ryan, thoughts? Would you be happy for us to do the second first as an MVP, then the first "automagical" version as a followup?