----- Original Message ----- > Chris Karlof and I were talking yesterday, and I was noting how awesome the > implementation approach of Persona on FirefoxOS has been. The, the relevant > code that ships with the device is limited to a container capable of running > web content, and some setup code which invokes a function within the context > of that web content when necessary. Further, the navigator.id. apis are > intercepted by firefoxos, and cause raising of the "trusted" content window > and relaying parameters into it.
> All of the code inside the persona dialog is still loaded live from our > servers. > This approach has saved us a number of times, and is the thing that allows us > to fix issues related to persona or roll out changes that land on all > firefoxos devices instantly. The other nice thing that this does is provide > a tiny contract between the firefoxos codebase and persona (both of which > are still very dynamic at the moment). > So as I look at the UX mocks that we need to implement, I wonder why we > wouldn't use the same approach here? Namely, the "setting up sync" window > could be entirely implemented in HTML, and the only desktop client work > would be to raise a container. You asked the desktop team, but I assume we'd use this for Android too. I am a little concerned about the flow since Android actually has a "Sync & Accounts" area in the OS Settings. The creation and login would likely happen without any involvement with Firefox. I think we need to investigate what it would take to get Firefox involved in the flow, if possible. If it's tricky, we'd need to fallback to use a native UI, like we do now.
_______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
