On 13-08-12 8:51 AM, Gavin Sharp wrote:
On Mon, Aug 12, 2013 at 8:42 AM, Nick Alexander <[email protected]> wrote:
I'm concerned that as we push the Firefox Account + Sync setup flow into the
first run experience, there is going to be an awkward jump from web content
to native (and even worse, possibly back for password reset).
I'm not sure I understand. That seems to assume that the server won't
know about your devices and can't show that page itself, and I'm not
sure why that has to be the case.
That is a good point, and one that I hadn't considered. This does make
testing a hassle, since now you're not serving static content (in the
fashion of FHR).
Even granting that, I see several
potential solutions that are relatively straightforward:
- postMessage required data to the page so that it can show status
- have the "auth sucess" method trigger loading of a privileged page
which can show the status
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 agree that these are straightforward solutions, but they are all but
guaranteed to grow: as we add services to your account; service
discovery of new partners; updates and outage messages; ...
But actually, doing this is *better* with web content, so let me think
further.
Thanks!
Nick
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
