On Tue, Aug 13, 2013 at 8:14 AM, Deb Richardson <[email protected]> wrote:
> So, towards closing the loop here ... > > Crystal: are you ok with the two proposed stories as written? > > --- > * As a user, I want optionally to specify which types of data will be > synced before I have to create a Firefox Account and log in to my browser. > During this process, I want to be able to get more information about what > each type of data is and what it means for me in terms of browser > functionality, potential bandwidth usage, and what happens to that data > after I have logged out of my browser. > > * As a user, I want to be able to modify my Sync data settings in my > browser at any time after I have set up Sync and am logged into my Firefox > Account. This seems like it needs more detail. Suppose that I am syncing my passwords and I decide to stop. What do you expect happens? > --- > > If so, I'll add them to the MVP list unless there is strenuous objection > otherwise. > A bunch of the properties in the first story seem pretty unnecessary for MVP. For instance, does Chrome sync even indicate potential bandwidth usage? -Ekr > ~ deb > > > > ----- Original Message ----- > > On Thu, Aug 8, 2013 at 1:22 PM, Justin Dolske < [email protected] > > wrote: > > > > > > > > > > I guess I'd want to know more about the user research that led to this. > > > > Does this mean user expectations/use-cases are so different that there > is no > > combination of default settings that will be acceptable to most users? > And > > that it _must_ be in the signup flow (and to what degree must it be > > exposed)? > > > > There is no combination of defaults that satisfies users. Each user in > our > > test identified a different combination of data types that reflected > their > > usage. Our users like little snowflakes. :D > > > > > > > > Also, this seems to say the choices have to be selectable "before" > creating > > an account. That seems surprising, perhaps this just means being able to > > learn about the various info listed before signup, and not actually > making > > choices? Seems weird to have UI exposed that's actually non-functional > until > > you signup. > > > > I get your point here. It does seem weird. The story should be > sufficiently > > flexible such that the UX can do whatever it needs to to craft the most > > usable interface we can. I think having a story that says we want users > to > > be able to control their data types is enough specificity. > > > > > > > > Should this actually be 2 stories -- one for "I want to understand what > sync > > will do" and the other about when/how the user can start controlling > that? > > > > I wouldn't have a separate story for "users should understand what > they're > > doing." That's a designer's job for each and every story. > > -- > > > > Crystal Beasley > > Product Designer for Identity > > Mozilla Corporation > > 503/360-5448 > > > > > > > > _______________________________________________ > > Sync-dev mailing list > > [email protected] > > https://mail.mozilla.org/listinfo/sync-dev > > > _______________________________________________ > Sync-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/sync-dev >
_______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
