about:weave mobile screens
Dan Mills
I added some notes from our about:weave discussion today here:
https://wiki.mozilla.org/Labs/Weave/About:Weave
I put some high-level goals under Mobile > design goals, we can
iterate on those too. We talked around them in the meeting somewhat,
but didn't explicitly (and it would be good to do that).
Dan
Madhava Enros
Took a first pass through it. The rough wireframes are attached.
I've split out the things that a user _has_ to do (keeping those on
the in-content setup page) and the things that they might want to
change but could successfully use weave without ever touching (putting
those in the options section of the add-on). Let me know what you
think!
Madhava Enros
to come through when you look at it embedded in the email.
Madhava
On Sep 18, 2009, at 5:59 PM, Madhava Enros wrote:
> <fennec_weave_workflow_2009-09-18.pdf>
--
Madhava Enros
User Experience Designer, Mozilla Corporation
Dan Mills
These are great, thanks!
I wonder if we can start by keeping the engine on/off prefs inside
about:weave where we have them now, though? I doubt users will need
quick access to them, and it will allow us to reuse some code.
Instead, I think the addons manager could have a button to open
about:weave, and maybe a global disable toggle, for those who want
quick access to enable/disable the whole thing.
What do you think?
Dan
Mike Connor
the most-used prefs directly in the extension manager, rather than
requiring users to open a separate panel/window/dialog (especially
given how slow that can be on mobile devices). Choosing which data to
sync/not sync seems like a much more common action than configuring
user/server data, so I think it makes a lot of sense to expose them
from the addon manager.
Code reuse is great, but I don't think that should come at the expense
of adding unnecessary steps for the user. IIRC, there will be an easy
way to register prefs+strings in the Fennec addon manager, so I don't
think it's that much extra code in any case...
-- Mike
Dan Mills
manager. And I don't think enabling/disabling engines is a common
action at all.
I think that unless we have data telling us users want to configure
these (or any other) settings often, the addons manager should have a
button to open up the Weave settings, and--maybe--a toggle to
enable/disable sync as a whole.
Dan
Mike Connor
On 21-Sep-09, at 2:07 AM, Dan Mills wrote:
>
> I am not suggesting we put any user/server data settings in the addons
> manager. And I don't think enabling/disabling engines is a common
> action at all.
manager...
> I think that unless we have data telling us users want to configure
> these (or any other) settings often, the addons manager should have a
> button to open up the Weave settings, and--maybe--a toggle to
> enable/disable sync as a whole.
why prefs aren't exposed by default), but far more common than user/
server settings. Since it's a small handful of prefs, I'm not sure
why we would force all users into about:weave instead of having them
right there. It's an extra click + pageload to tweak the most common
prefs... why is that your preferred interaction?
I don't think we need data to justify removing steps for users...
Dan Mills
> As for enabling/disabling, it's likely not all that common (which is
> why prefs aren't exposed by default), but far more common than user/
> server settings. Since it's a small handful of prefs, I'm not sure
> why we would force all users into about:weave instead of having them
> right there. It's an extra click + pageload to tweak the most common
> prefs... why is that your preferred interaction?
Establishing the relative importance of user/server/engine enabled
settings doesn't automatically promote some set to the addons manager.
I don't think the settings in question are commonly needed, so I am
suggesting we keep them where they are in the desktop UI. If I'm
wrong, fine, we move them up, but I would like some evidence of that
being the case.
Dan
Madhava Enros
I definitely appreciate the appeal of making changes incrementally, so
if that's what it comes down to I'm sure we can figure it out.
I started by thinking about how to fit the options in the about:weave
page, but as I thought about where to put the launch-point (it would
have to move, given the smaller presence of the device graphic) and
how to place and fit the panel that would contain all the options (it
will have to be much bigger to become finger-friendly, and basically
replace the main login prefs area when it's on screen), I realized
that in fact we now have a place in Fennec that presents options in
the way we'd want and that does that layout automatically given a list
of prefs. Here's the reference for that: https://wiki.mozilla.org/Mobile/Fennec/Extensions/Options
On top of that, there exist the points about which prefs people will
need to return to over the lifecycle of their weave use vs. which ones
they need pretty much only on first-run, but I came to this first as
just a pragmatic way to fit everything in a finger-friendly way. It
was my hope that, using the add-on options scheme, it would be
relatively little work for you guys to move those prefs vs. the design
problem of fitting all of those additional prefs somewhere in the page.
Let me know what you think!
Madhava Enros
disable the add-on, as there is for any add-on. Is that sufficient?
Madhava