Closed andymckay-limited-access closed 9 years ago
Starter feature list:
UI mockups and flow (the flow doesn’t describe how the system will work in great detail, but gives you an idea of the style that Firefox Accounts Settings is going to follow).
Updated UI mockups and flow to address use case of removing payment account and how it impacts existing subscription.
And, as promised, below is a user flow diagram that details how each functionality within this page will work.
Deleting an account is a good idea we hadn't considered. There's also only so much we can delete, we need to keep data around. I'm thinking we should do something like AMO does and after removing any subscriptions, blank out any personal information like email address, name etc. and anything that tied the user to the account, whilst keeping the actual transactions around for reporting and auditing.
Receipts and Subscriptions looks like it could become a big page. And presumably we'll need to be able to paginate the receipts list?
This is cool, Bram. What if instead of replacing the card in each orphaned subscription one by one they could do something like "replace all subscriptions that used this card with X" ? I suppose they may still want to review/replace one by one but if that list is long then they'd be tempted to click "Later" and that could result in money lost.
Sorry if its not ready for commenting yet, but was excited to see this. Weeee!
FYI, I think implementing changing email address is here: https://github.com/mozilla/fxa-content-server/issues/2335
implementing changing email address is here
FYI we haven't scheduled this form implementation yet, if you need it lined up with a particular schedule on your end please comment in that bug.
Prepare a first pass of the UX flow for the management screens. This is where users will add payment methods, manage their subscriptions and other tasks.
Doing a first pass at this early so we can be sure we are on the right page.