----- Original Message ----- > Defining such an interface and managing the multiple client and server > versions is not awesome, but of course it can be done. And loading a > privileged page is equivalent: the interesting part is populating the > interface (or privileged page) from the Android Account object.
I still reserve judgement on the Android part. Using a GeckoView (doesn't exist yet) or a WebView (leery of support across various Android versions) has risks. There is also the "look and feel" issues. We'll need to talk to UX about how this would "feel" in the Android system. Remember, Android already has a native way of doing these things, desktop Firefox doesn't really need to worry about that. Also, making this look like the right "Android" UI could be challenging too. Obviously, getting something to work is first and foremost, but moaking it look and feel good is following closely. Let's not back ourselves into a corner. Lastly, I might be too noob to have caught the reasoning, but why are we intent on using web content? Does it make key generation easier since we are pushing that to the server? Is it a "we only need to make the UI once" thought? Cause that's not true: We'd need mobile and tablet(s) versions.
_______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
