Closed Bug 761821 Opened 13 years ago Closed 12 years ago

Dashboard leaves behind apps synced to BID account #1 when logged in as BID account #2

Categories

(Web Apps Graveyard :: AppsInTheCloud, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: jsmith, Unassigned)

References

Details

(Whiteboard: [blocking-aitc-])

Prerequsite: AITC is enabled and about:config enables myapps dashboard Steps: 1. Go to myapps and login with BID account #1 2. Go to apps.mozillalabs.com/appdir and install an app 3. Close Firefox 4. Restart Firefox 5. Go to myapps and login with BID account #2 Expected: No apps should be shown on the dashboard - BID account #2 has no apps installed in it. Actual: The app installed for BID account #1 continues to be shown.
Depends on: 746204
Whiteboard: [qa+]
Nominating for k9o per the same rationale as bug 746204.
blocking-kilimanjaro: --- → ?
Whiteboard: [qa+] → [qa+], [blocking-aitc-]
If you have multiple BID accounts, the dashboard should show you the apps for all of those accounts. So, the current behavior is actually expected behavior, especially in a world where there is "no sign into the browser" feature. Thunder, Ben - does this match your expectation as well?
Yup, works for me.
(In reply to Ragavan S [:rags] from comment #2) > If you have multiple BID accounts, the dashboard should show you the apps > for all of those accounts. So, the current behavior is actually expected > behavior, especially in a world where there is "no sign into the browser" > feature. Couldn't that cause problems with persona.org down the line (https://persona-dev.mozillalabs.com)? Or is that a separate problem on the web implementation side? The issue I'm referring to is a user flow of: 1. I login with account #1 2. I select my apps Result - How do I understand what apps are tied to my persona vs. what's overall installed on my machine? The user flow seems confusing here IMO, as you would not be able to figure out which apps are part of your persona vs. what's installed overall on my machine (i.e. what I'm trying to get at is back to the overarching problem is understanding the different states of app metadata and what they reference and how a user understands that). Note that the problem here is probably solved by the "need a AITC dashboard" k9o bug, but we should provide some way to at least to distinguish where the data derives from to the user in a visual form. I do agree that showing different data sources together is fine, but let's make sure the user understands where it's coming from and how and when they are modifying it.
Comment 4 note is referring to the long-term implications of this (i.e. UX), not the 1st release of AITC. I might move these ideas to the associated bug on that though...
I believe the apps dashboard will display everything in the AITC service, no matter who you were signed into the marketplace as when you installed the apps.
(In reply to Dan Mills [:thunder] from comment #6) > I believe the apps dashboard will display everything in the AITC service, no > matter who you were signed into the marketplace as when you installed the > apps. Let's take this discussion to bug 748977 (that's actually the bug on that). For now, I'll close this as not valid, given that I am in agreement with aggregated data source argument presented on the dashboard. The visualization of it is a UX issue, so I'll bring that up on the associated bug for that.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Whiteboard: [qa+], [blocking-aitc-] → [blocking-aitc-]
blocking-kilimanjaro: ? → ---
(In reply to Jason Smith [:jsmith] from comment #7) > (In reply to Dan Mills [:thunder] from comment #6) > > I believe the apps dashboard will display everything in the AITC service, no > > matter who you were signed into the marketplace as when you installed the > > apps. > > Let's take this discussion to bug 748977 (that's actually the bug on that). > For now, I'll close this as not valid, given that I am in agreement with > aggregated data source argument presented on the dashboard. The > visualization of it is a UX issue, so I'll bring that up on the associated > bug for that. Although after checking how Google Play handles this, now I'm rethinking this, given that AITC deals with acquired apps, not installed apps. Reopening.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
blocking-kilimanjaro: --- → ?
And now I'm confused, as the current implementation of AITC on nightly now is doing the behavior I originally expected in this bug (per persona account management), although I know there was debate above in the comments to go in another direction. Did somebody break something? There's some weird stuff going on with the dashboard right now...
blocking-kilimanjaro: ? → ---
(In reply to Jason Smith [:jsmith] from comment #8) > (In reply to Jason Smith [:jsmith] from comment #7) > > (In reply to Dan Mills [:thunder] from comment #6) > > > I believe the apps dashboard will display everything in the AITC service, no > > > matter who you were signed into the marketplace as when you installed the > > > apps. > > > > Let's take this discussion to bug 748977 (that's actually the bug on that). > > For now, I'll close this as not valid, given that I am in agreement with > > aggregated data source argument presented on the dashboard. The > > visualization of it is a UX issue, so I'll bring that up on the associated > > bug for that. > > Although after checking how Google Play handles this, now I'm rethinking > this, given that AITC deals with acquired apps, not installed apps. > Reopening. Actually I'll back off on this. I'll follow the policy followed on the web runtime - if we don't have a use case for this now in the short-term, then close it as such and reopen if it's become a clear need. When the UX gets defined for the AITC dashboard for k9o, we'll know what is and isn't acceptable. But what exists now is acceptable.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → INVALID
Product: Web Apps → Web Apps Graveyard
You need to log in before you can comment on or make changes to this bug.