<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Hi Lloyd,</div><div><br></div><div>Chris, John and I have been working on some designs for a website that sits at (proposed) <a href="http://accounts.firefox.com">accounts.firefox.com</a>.</div><div><br></div><div>User flow and low-fidelity wireframes PDF: <a href="https://www.lucidchart.com/publicSegments/view/5277b812-0330-4f29-8075-04e70a005059">https://www.lucidchart.com/publicSegments/view/5277b812-0330-4f29-8075-04e70a005059</a></div><div><br></div><div>We need to make sure there is parity with the mobile flow (PDF): <a href="https://www.lucidchart.com/publicSegments/view/5277b847-0db0-4cb0-afcb-38d30a005c69">https://www.lucidchart.com/publicSegments/view/5277b847-0db0-4cb0-afcb-38d30a005c69</a></div><div><br></div><div>John even took it a step further on Friday with an high-fidelity animation.</div><div><br></div><div><a href="https://www.dropbox.com/sh/479jwcduu005416/gqjcFKG2bl/site video.m4v">https://www.dropbox.com/sh/479jwcduu005416/gqjcFKG2bl/site%20video.m4v</a></div><div><br></div><div>What happens in the final frames is very important. We aim to indicate what services the user has authenticated with their Firefox Account. Each service will get its own page with a description, and a URL.</div><div><br></div><div>Very early, but thoughts? I will be meeting with Chris today to develop further. Hopefully <a href="http://accounts.firefox.com">accounts.firefox.com</a> can be more than a one-feature site to change the account password (which can also be done with a reset view).</div><div><br></div><div><div apple-content-edited="true"><div style="orphans: 2; text-align: -webkit-auto; widows: 2; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Ryan Feeley</div><div>Product Designer, Identity</div><div>Mozilla UX</div><div>IRC: rfeeley</div><div><br></div></div></div></div><br><div><div>On Nov 4, 2013, at 10:04 AM, Lloyd Hilaiel <<a href="mailto:lhilaiel@mozilla.com">lhilaiel@mozilla.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">In discussions in madrid and over the past couple weeks, it’s becoming increasingly clear that we will have to host web based resources for various parts of the sign-up flows we’re implementing.<br><br>This is some squishy work that will cut across multiple efforts. I’m curious if anyone has started trying to aggregate all of the different screens that will need to be web hosted across sync and fxa on fxos to figure out the best way to host all this jelly. From software layout to url strategy…<br><br>lloyd<br>_______________________________________________<br>Sync-dev mailing list<br><a href="mailto:Sync-dev@mozilla.org">Sync-dev@mozilla.org</a><br>https://mail.mozilla.org/listinfo/sync-dev<br></blockquote></div><br><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br></div></div></div></body></html>