Account Dashboards

[vmunix]

3 stories (an epic!?) just to capture these. Breakout/fix as needed.

1. As a signed in user, I want be able view a dashboard page that shows me what services are attached to my Firefox Account so that I can quickly understand how my account is being used. Ex: https://www.google.com/settings/dashboard

2. As a signed in user, I want to download my data in published formats for services that are attached to my Firefox Account. Ex: https://www.google.com/settings/takeout

3. As a signed in user, I want to see a report of my Account Activity so that I can understand how/when attached services are being used. Ex: https://www.google.com/settings/activity

[ckarlof]

Google's dashboards are pretty slick. It's probably not a near term feature for us, but I could see us adding it in the next 12-18 months.

[jbonacci]

💯 to this.
Yea, this time next year.... :-)

[ryanfeeley]

John and I had schemed up something to this effect. The primary view would list devices and services connected using FxA (a subset of add-ons and app marketplace), and for each service would be a detail view containing a description and URL (likely to the marketing page for the service, as not all services would be a available from all browsers). A service could provide us this information with each request to FxA, or their initial request.

[johngruen]

WRT FFOS, I propose the following:

Story 1: Targeted for 1.4...I already have art for this in current flows:

Story 2: This doesn't make sense for 1.4 as we are supporting only WMF and Marketplace. This feature will become critical as FxA expands into properties like Sync etc, but I'm not sure it fits clearly right now.

Story 3: Target for 1.5. It would be fantastic to provide this capability on the phone. If we wanted a simple way to educate users (and target 1.4), we could add a brief explanation of how/why each service uses the account. Maybe something like this:

[vmunix]

IMO doing the majority of this on a web view (i.e. not chrome) would be completely acceptable. I do like the FFOS screens that explicitly highlight the apps on device that are "registered". Cool stuff, John.

I'd also suggest that while it would certainly be a lot of work to do this completely/generically, we know what the first service is (Sync) and we could possibly come out the gate signalling to end users that this is the pattern we intend to follow by building the story 1 feature just for the initial service more or less statically. I'd like to scope that work, at least, before scheduling it in a backlog.

[shane-tomlinson]

Assigning to @rfk to add to roadmap and close when appropriate.

[rfk]

We have this on our roadmap under "future goals" but it's not scheduled for implementation. I think this bug is old enough that we can leave it closed it out and revisit with fresh eyes when we get around to implementing this.