Closed Bug 523503 Opened 13 years ago Closed 13 years ago

Append the word "Persona" to Persona designs in the Add-Ons manager

Categories

(Websites Graveyard :: getpersonas.com, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: sgupta, Assigned: osunick)

Details

Need to figure out details here, but creating the bug to track.
Assignee: nobody → rdoherty
OS: Mac OS X → All
Hardware: x86 → All
Really? I think this is a pretty bad idea, for a couple of reasons.

First and foremost, it doesn't seem necessary. Why do we think users care if their theme is a lightweight persona or not? I'm not sure what the differentiation adds in terms of user value, other than additional text (which may often wrap or flow out of view, leaving ellipses.

Second, the entire goal of integrating Personas into Firefox was to integrate Personas into Firefox. Calling them out as something new or different means providing a new "object" that users need to learn and reason about, and to my mind, does not feel like integration as much as bundling.

Third, while I understand that there is to be continued exploration through the Personas Add-on, I don't think that this provides a strong signal to users that if they want to extend their Personas experience they should investigate that Add-on. To me this seems intended to be a branding exercise, but that doesn't have a lot of place in the UI used to select the active persona or theme. Further, I would note that this branding and addition of the word "Persona" will *not* appear in the Personas Add-on itself, which may lead to confusion when someone migrates from the built-in experience to that of the Add-on.

Finally, the eventual direction is for Personas (as I understand it) is to replace the current theme infrastructure, adding additional power to provide graphics for buttons, textures, backgrounds, etc. What we know of as "themes" today would then migrate to add-ons, better reflecting the fact that they can change the default UI in shape as well as skin. In that future, everything in the list would be "Personas", meaning at some point we'd have to go remove that word from the items, potentially causing further confusion.
(In reply to comment #1)
> First and foremost, it doesn't seem necessary. Why do we think users care if
> their theme is a lightweight persona or not?

I think it's pretty confusing that some themes can be switched to immediately and others require a browser restart, and there's no way to tell what's going to happen when you click Use Theme -- it might switch or it might ask you to restart.

And some themes disappear when you add more than a certain number but other themes always stick around.

I don't think adding Persona after is the best solution to that problem, but it's a start.

But I don't have strong feelings about this either way.
(In reply to comment #2)
> I think it's pretty confusing that some themes can be switched to immediately
> and others require a browser restart, and there's no way to tell what's going
> to happen when you click Use Theme -- it might switch or it might ask you to
> restart.

So? Some themes require a restart, others won't. Users will be happy with the ones that don't, and disappointed with the ones that do. I think we're going out of our way here to support a legacy system (themes) which we fully intend to eventually deprecate. Don't really see a need to do that in ways that compromise the new hotness.

> And some themes disappear when you add more than a certain number but other
> themes always stick around.

That's a slightly more confusing aspect to this, sure, but I don't know why "Personas" will make that any better. I think that's just part of the entire system's user experience that needs to be rethought for 3.7.

Recommend this be WONTFIX.
No activity for a while, marking as wontfix.
Will be raising this issue in the Personas Uplift meeting this Wednesday at 2:30pm, PST to determine whether this should be a wontfix. Also including Nick so that he can familiarize himself with the issue and weigh in.
NO strong opinion here.  At the end of the day most users probably won't have a mental distinction between the two.
Event though there is no strong opinion from AMO, I'm assigning to Nick so that he can monitor the status quo in the 3.6 beta and make a call as to whether this is a priority or a won't fix.
Assignee: rdoherty → nnguyen
Target Milestone: 2.0 → 2.1
(In reply to comment #6)
> NO strong opinion here.  At the end of the day most users probably won't have a
> mental distinction between the two.

I vote no on this also. Can we wontfix?
Target Milestone: 2.1 → 2.2
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Product: Websites → Websites Graveyard
You need to log in before you can comment on or make changes to this bug.