----- Original Message ----- > 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
