How AMO could improve the user experience for the Themes section:
1. Revise the Categories.
What the heck do Miscellaneous or OS Integration or Modern even mean?
- Why are these three most popular Categories completely vague? I know some of them have "historical" significance, but it's time to move on. Modern and Misc don't mean anything and if OS Integration does mean something, apparently none of the people putting their themes in that category knows what it means, and I can't hope that users would either.
Why Large and not Assessibility?
- While Large is a vague term that could mean anything, Assessibility users have really specific needs. These needs are NOT filled by Mozilla and Firefox is getting worse and worse about providing a browser that vision-impared users can interact worth. There are many themes in the Large section which are ridiculously hard to look at even for people with perfect vision.
Some proposals for new additional Categories:
- Assessibility
- Dark
- White
- Bright Colors
- Holiday/Seasonal
- Cartoony
- Software Simulations (other browsers or software)
- OSX Look (seems to be very popular on other platforms than OSX)
- Uncategorized (more on that below)
2. Police the Categories.
At some point there needs to be a serious look at how themes are categorized. There are MANY that don't fit into their categories, especially in Large and Compact, which are specifically the two Categories for people who NEED accurate results: Assessibility users and netbook users. If your theme is no smaller than the default then it's not Compact, and if it's not any larger than the default then it's not Large, and it's certainly not for Accessibility users. The randomness of the results of the Categories (as well as the absolute vagueness of the three most popular) makes them useless. Having accuracy in the Categories would be an important part of my final point.
3. Browse instead of Search.
When you are looking for an extension, it makes sense to look up keywords based on what you want to accomplish. This makes absolutely no sense when searching for a theme. Instead, themes should be filtered, similar to how apartment or classifieds listings work on websites. So instead of the starting point being a search box... the starting point is your OS/Firefox version:
Firefox 10
OSX
From there you should ONLY be shown themes compatible with Firefox 10 and OSX. You shouldn't be shown incompatible themes right in the top results like you do now. Incompatible themes are very very unlikely to actually work and only testers should see them. Currently there is absolutely no way for an OSX user to just browse through the available themes for OSX. In the apartment analogy, this would be your price and neighborhood. These are the non-negotiables and should be automatically detected (but with the option of changing). Visually this part would look basically the same as what AMO already does. Filters in the sidebar to the left, sorters at the top.
The next step is to offer the Categories as filters. This should work as a series of checkboxes, with all of them checked by default. At the bottom of that list could be two buttons: Select All, Unselect All. The concept here is filtering by exclusion. So starting with All checked, if I was to uncheck Dark, my results would show all themes that are not Dark. If you look at the top results for Themes right now you will see how popular Dark themes are, and how important it is to be able to filter them out. On the other hand, if you want to only see OSX-like themes you could Unselect All and then check Mac-Look, thereby filtering out everything else:
Firefox 10
OSX
Mac-Look
Which would only show themes that match the Mac look and are compatible with OSX and Firefox 10 in *two clicks*. This is currently impossible to do at all, let alone quickly and easily. Going back to the apartments listing analog, this is like the optionals: pets allowed, smoking, nearby schools, number of bedrooms, etc. Being more picky gives you limited listings, being less picky gives you a wider variety to choose from. Accuracy of the results would depend very heavily on the first two points being accomplished well.
This was the first reply to my email. It is from Andrew who is an AMO Editor:
1. - sounds good. The complicated part will be working out what should happen to themes under the existing categories though (do you clear them and just give them Uncategorized? If so we would have to devise a strategy for contacting all theme developers asking them to reclassify)
2. - not sure about this one. I'd prefer to keep it developer led (and who exactly is going to do the policing?). Maybe we could just add better guidance for developers on what categories to choose.
3. - at its simplest it comes down to having the search filters on browse pages though I suspect it may need a large change in how search/browse is implemented in the back end. Having filters as multiple selections rather than a single selection would also be a significant change. They're worthy improvements definitely but non-trivial so would take a while to implement I'd guess.
Andrew Williamson
AMO Editor
The following reply is from Jorge Villalobos who is the Add-on Developer Relations Lead (aka in charge of all AMO editors):
1. I agree with recategorizing themes. It'd be good to have a discussion with theme developers to refine the category list and provide a final proposal with the most important categories at the top (since we might not accept all of them).
2. You can use Abuse reports for that. It might be abusing the feature (zing!), but people already use it for that.
3. I thought AMO already pre-filtered add-ons by app version (not sure about platform). Does he have the Add-on Compatibility Reporter installed? Like Andrew said, this is the least likely to happen. Search is a tricky thing to get right, and you need to balance usefulness with simplicity.
- Jorge
The following reply was from Axel who is an AMO editor in regards to Patrick's suggestion #1:
To an extent I would also like to have the same discussion on Thunderbird Extensions Categories. I think it is a little bit under categorized, at this stage.
There should be some more Tb specific Categories such as:
Tags
Filtering
Productivity / Message Administration
Calendar
Connectivity / Import / Export
Message Composition
------
Browser Addons - should contain all addons that have Firefox as the main target audience (say having 10times more Fx users than Tb) and that aren't really specific to Tb, such as Adblock Plus or NoScript. IMHO these just muddy the waters as they really focus on the browsing aspect of Gecko/Thunderbird.
I think that would be a good start.
Also, statistics should stop counting Fx downloads/users of multi-app extensions on the Tb AMO pages (I believe this bug was filed already; I believe the update ping has a userAgent, so this is a reasonable request)
So the big question is, if there are going to be new categories for themes, what should they be and how should they be defined so that theme developers can properly choose the categories their themes belong in? Theme developer feedback is clearly wanted and if a clear and logical proposal is brought forth for theme categories it could probably be implemented fairly easily.