<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><div>On Nov 4, 2013, at 7:15 AM, Ryan Feeley <<a href="mailto:rfeeley@mozilla.com">rfeeley@mozilla.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Hi Lloyd,</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></blockquote><div><br></div><div>For an MVP, it's fine for <a href="http://accounts.firefox.com">accounts.firefox.com</a> to be a "one feature site". In fact, it shouldn't be a "site" at all, in the sense that I don't think <a href="http://accounts.firefox.com">accounts.firefox.com</a> should be destination, but instead just enables login/sign up to support Mozilla relying properties via ping-pong-y flows.</div><div><br></div><div>We can make it awesome later, but for now let's get the simplest thing that lets the users of consumer facing Mozilla relier properties log in with one account.</div><div><br></div><div>-chris</div><div><br></div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><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><a href="https://mail.mozilla.org/listinfo/sync-dev">https://mail.mozilla.org/listinfo/sync-dev</a><br></blockquote></div><br><div apple-content-edited="true">
<div style="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; "><br></div></div></div>_______________________________________________<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></body></html>