Hi All, Ian here from Fennec UX To give some context on the Android designs, the initial designs here http://cl.ly/image/0v3h0Z2o2K0f were a carry-over from trying to maintain consistency with how desktop was handling the UI in content. But upon thinking about it some more, for the sake of a more consistent and focused flow it probably makes more sense to do the whole sign-in flow in a Settings style UI instead of in-content as my initial mockups showed.
It gives us more flexibility with the design across different versions of Android that use different visual styles, and more importantly it helps users stay more focused on the task of signing in / signing up by leaving them fewer options to wander off and get lost (ie navigating back and forward, going off to another tab or a different website, stopping their task halfway through etc). I can iterate on the design with Nick in bug 899217, but for the purposes of this discussion the basic design should look something like this http://cl.ly/image/0v3h0Z2o2K0f but with a Settings header instead of a URL bar on top. Ian On 2013-08-14, at 1:04 AM, Mark Finkle <[email protected]> wrote: > > > I'd like to understand more about your concern about the Android native > way. I see three situations where Firefox Accounts will interact with > the user: > > 1. Creating an account; > 2. Updating an account's password; > 3. Viewing/changing account settings [1]. > > In no case do I intend to use GeckoView or a Web View. I intend to open > Fennec itself. > That's good, but presents it's own challenges. You have done a nice job > listing the various scenarios and technically, I don't see any reason why we > couldn't use the "in content" approach. There are some fine points we'll need > to consider: > * We can't try to make the UI presented in the content look like Android in > any way. It will fail on some subset of devices and look out of place. We'd > need to take a "webby" approach. > * We could make about:accounts work like about:home -> implemented using Java > and native widgets, If we feel the need to go this route, why bother using > Fennec? > * Using about:accounts means the UI is in the back/forward session history of > the tab and might get saved with session restore and any other "loaded in a > tab" kind of behavior. This might be good or bad. We'll need UX to help > clarify. > > In fact, we'll need UX to help with all of these issues. My point is, > choosing to use in-content UI has repercussions. We just need to understand > them and be OK with them. Using the native account approach is kinda a solved > thing, since we already do it. With the exception of the tweaking Sync > settings in-product instead of opening the account system. > > _______________________________________________ > 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
