Closed Bug 836393 Opened 11 years ago Closed 10 years ago

Need to check if Sync flow needs any improvement or redesign to feel more friendly and/or Metro

Categories

(Firefox for Metro Graveyard :: Sync, defect)

x86_64
Windows 8.1
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: MarcoM, Unassigned)

References

Details

Attachments

(3 files)

      No description provided.
Summary: Need to check if the flow needs any improvement or redesign to feel more friendly and/or Metro → Work - Need to check if the flow needs any improvement or redesign to feel more friendly and/or Metro
Summary: Work - Need to check if the flow needs any improvement or redesign to feel more friendly and/or Metro → Work - Need to check if Sync flow needs any improvement or redesign to feel more friendly and/or Metro
Update the Sync setup flow at this website:
https://projects.invisionapp.com/share/3QBUUTKA#/screens

Screens include:
1. Set up ("Pair this device")
2. Pair this device
3. Sync Now
4. Disconnect this device
5. Add another device ("Pair a device")
Based on the feedback from 02/04 mtg:
Updated flow for sync: http://invis.io/X2BV91JE  

Changed the term from "Pair this device" to "Set up sync";  
Using "Connect" instead of "Pair" for actions in Setup;
Added strings for new users who don't have sync account
Yuan could I get some new mockups for this?
Flags: needinfo?(ywang)
I don't mind taking this after my current iteration story (bug 831614), but I don't think this has to do with auto setup sync from desktop which it is linked to in bug 831614.  Can we move this to another story?

I would move it to bug 831615 but it is a p3.
Flags: needinfo?(asa)
I think you're right that this work item is blocking the wrong story. I've moved it to Bug 831615 - Story - Set up Sync from Metro Firefox
Blocks: 831615
No longer blocks: 831614
Flags: needinfo?(asa)
(In reply to Brian R. Bondy [:bbondy] from comment #3)
> Yuan could I get some new mockups for this?

Hi Brian, please go over the flow of Sync set up and pairing in this link: https://projects.invisionapp.com/share/X2BV91JE#/screens
 
Let me know if you have any question. Thanks!
Flags: needinfo?(ywang)
Awesome! Thanks!
Assignee: yuan → netzen
general->sync 10 bugs
Component: General → Sync
No longer blocks: 831615
What should happen to this bug now that is no longer blocking Bug 831615?
Flags: needinfo?(netzen)
Flags: needinfo?(asa)
I'll just throw it in v2 triage for now
Flags: needinfo?(netzen)
Flags: needinfo?(asa)
Attached image flyout - connected
(In reply to Richard Newman [:rnewman] from comment #13)
> Comment on attachment 744700 [details]
> [Mockup] Disconnect sync
> 
> Minor nit: "from", not "with".
> 
> The warning is good (and accurate), but it's almost reassuring a user into
> thinking that this is a reversible action, when it's absolutely not.
> 
> To continue your point about symmetry: a user expects that when they hit
> "disconnect", the button then turns into "connect". 
> 
> Disconnecting is something users do on a regular basis -- wifi networks,
> chat clients, Xbox Live, etc. It's perhaps even weaker than "sign out",
> because that has the implication of a cleared sign-in box for someone else
> to type into.
> 
> Removing your device from a Sync account is a potentially unrecoverable
> action, and there's no one-click "reconnect" concept (and shouldn't be; so
> much state must be discarded that it's not possible to resume where we left
> off).
> 
> The only way to recover is to set up Sync again, and go through the whole
> first sync rigamarole. Assuming you have access to another device...
> 
> A user who's traveling might want to temporarily disconnect because of
> bandwidth concerns, read this reassuring statement about how safe all their
> data will be in the mean time, and end up costing themselves a hundred bucks
> in roaming charges to set up Sync again.
> 
> (Quite apart from the concern that their Sync data will probably be gone by
> the time they come back...)
> 
> I understand that symmetry is important, but I argue that either it's worth
> breaking in this case (because the user actions aren't symmetric: connect
> once, disconnect never), or you should fix the setup flow to use other
> language like "Add this device to my Sync account", "Configure", "Start
> using", "Set up", with corresponding 'stop' language like "Stop using Sync
> on this device", "Unlink this device", "Permanently disconnect", etc.
> 
> 
> And our confirmation dialog should include language that clarifies what's
> going to happen: "Your browser data on this device will remain intact, but
> you will no longer be able to sync with this Sync account. You cannot undo
> this action."
See Also: → 867201
Assignee: netzen → nobody
Blocks: metrobacklog
No longer blocks: metrov2planning
Summary: Work - Need to check if Sync flow needs any improvement or redesign to feel more friendly and/or Metro → Need to check if Sync flow needs any improvement or redesign to feel more friendly and/or Metro
Whiteboard: feature=work → [feature] p=0
No longer blocks: metrobacklog
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Whiteboard: [feature] p=0
OS: Windows 8 Metro → Windows 8.1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: