Update:Remora Feedback

From MozillaWiki
Revision as of 02:48, 17 January 2007 by Wenzel (talk | contribs) (→‎xeen's comments: developer pages ex)
Jump to navigation Jump to search

Alpha Feedback - http://preview.addons.mozilla.org

This page is for consolidation of the feedback on the new AMO Alpha. If you're more comfortable filing bugs, you're welcome to do that instead.

See also the announcement on the Mozilla webdev blog.

The feedback (bugs, suggestions) that we fixed/dealt with were moved to a reference page.

fligtar's comments

I like the overall look, but I have a few comments about certain aspects:

  • The sidebar still doesn't show the active page with a gray background (li class="selected")
  • The discussion header/footer is noticeably different.
  • Discussions show a CakePHP favicon for me
  • This may be a vanilla bug, not sure: "Comment by made 1 day ago days ago"
    • That was a l10n bug and is likely to be still present in different languages due to a l10n tag inconsistency in the vanilla code. I fixed it in English and German, though. --wenzel 18:44, 16 January 2007 (PST)

clouserw's comments

  • Old URLs should redirect into the new format so we don't get 404s (bug 362526)
  • If there are no addons in a category, an unfriendly/unstyled message is flashed, and the user is redirected to the front page. (bug 365853)
    • maybe these category links should not even be displayed if they don't carry any add-ons. --wenzel 20:59, 2 January 2007 (PST)
  • Pages should validate
  • Discussions can be started that aren't related to an addon (just click "discussions" in the header, then start a new topic)
  • The "More..." link under "Popular Extensions" on the browse page goes nowhere.
  • Since search engines are addons now, if you type a search engine id into the URL, you get a really ugly display page

wenzel's comments

  • Browse Category page has a "more" link for new and updated add-ons which leads to the new add-ons RSS feed (atm it's even a 404); it should maybe lead to a new page showing the new add-ons for this category only.
  • Browse Add-ons page could use category specific RSS feeds.
  • Search algorithm is improvable: The binary matching creates many hits with the same score in spite of their obviously different relevance.
  • "find similar add-ons" sometimes shows different categories with the same name? (example)

xeen's comments

  • When browsing by category I don't know which category I am in ("Subscribe to this Category" isn't useful either. What about 'Subscribe to "XYZ"'?) (sancus)
  • Categories with only 1 extension/theme directly link to the theme, which is confusing (sancus)
  • "Other Add-ons" only lists extension names but doesn't offer a link to "traditional" browsing with summaries.
  • Extension summaries should be limited to a certain length so that we don't have 2 pages description when browsing extensions. I kind-of see this when looking at the extension's page where the same description appears twice. Is this supposed to be "long" and "short" description?

dria's comments

  • Seems to be a bug at [1] when not logged in. At very least there should be a significantly friendlier message suggesting the user log in :)

dolske's comments (from blog)

  • How is browsing an extension category going to work? There seems to only be a limited subset of extensions on the preview site, so it’s hard to tell. It looks like a category page has 1 major featured extension, 2 minor featured extensions, and then just a list of other extension titles. It’s a bit hard to browse the current AMO, but a big block of title links seems too condensed.

jMax's comments (from blog)

  • The add-on licenses should be exposed, so the user knows what he's about to install.

Gijs' (Hannibal's) comments

  • There are small 'medals' next to extensions on the category pages. However, they don't have tooltips, are not links, and don't resurface on the actual addon page. What do they mean (and can we make that more clear in the actual addons UI)?
  • Could we sort categories, so it becomes easier to find something specific? Right now there's just unsorted lists of about 12-15 items, which is not very easy to use.
  • The "New and Updated" list on the "Extensions" page is missing the corner background.

Dao's comments

DonGato's comments

  • There is no information about the last update of an extension (at least in the home page and most probably in the newest page as with current AMO, but I can't say as this page is not available in the preview). This is an important information while browsing extensions.
  • 'Welcome to Mozilla add-ons' should stand up more in design but not space. Currently is taking a lot of space and not being necessarily clear.
  • Doesn't discussion header looks bad? I think a right and left border is needed.

trev's comments

  • Default Locale field on /developers/add seems to encode entities twice, e.g. I see Français there
  • If you don't select the addon type, you will get a second message: "That file extension (.xpi) is not allowed for the selected add-on type." That pretty pointless.
  • Having to re-upload files on errors is not nice at all. Files should be kept and the input field should be replaced by the file name to indicate that they are already there.
  • Isn't it possible to detect add-on type automatically? The file will need to be unpacked and analyzed anyway.
  • When I fill out all fields correctly I get the error "Could not move file". Stuck at step 1.

pascalc's comments

  • on the right sidebar menu, the "Build your own" link should point to the localized version of the documentation (http://developer.mozilla.org/{locale}/docs/Extensions) if it exists
    • I agree. But I wonder how we can find out if it exists, before making the link. --wenzel 10:24, 16 January 2007 (PST)
  • Website ignores Thunderbird, the front page should at least say "Add-ons extend Firefox and Thunderbird..." and not only Firefox

LCaution's comments (from blog)

  • I’d like to have an option to display items with a one-line description. Display a simple, hyperlinked list, in alphabetical order, with the name of the extension/theme/whatever and a one-sentence description of what it does. Click on the one-liner and a new tab opens to a page with a full description, comments, download, etc.

Omnisilver's comments (from blog)

  • Create a page with microformats (or use microformats in the app, at least)