Update:Remora Feedback: Difference between revisions
Jump to navigation
Jump to search
(made "fixed alpha feedback" page for reference) |
(moved lots of stuff to "fixed" page) |
||
| Line 3: | Line 3: | ||
See also the [http://blog.mozilla.com/webdev/2007/01/02/amo-3.0-alpha-public-preview/ announcement] on the Mozilla webdev blog. | See also the [http://blog.mozilla.com/webdev/2007/01/02/amo-3.0-alpha-public-preview/ announcement] on the Mozilla webdev blog. | ||
The feedback (bugs, suggestions) that we fixed/dealt with were moved to a [[Update:Remora Feedback/Alpha Feedback Fixed|reference page]]. | |||
== fligtar's comments == | == fligtar's comments == | ||
| Line 18: | Line 20: | ||
** maybe these category links should not even be displayed if they don't carry any add-ons. --[[User:Wenzel|wenzel]] 20:59, 2 January 2007 (PST) | ** maybe these category links should not even be displayed if they don't carry any add-ons. --[[User:Wenzel|wenzel]] 20:59, 2 January 2007 (PST) | ||
* Pages should validate | * Pages should validate | ||
* on the /addons/display page, the "bad trip" link does nothing | * on the /addons/display page, the "bad trip" link does nothing | ||
* Discussions can be started that aren't related to an addon (just click "discussions" in the header, then start a new topic) | * Discussions can be started that aren't related to an addon (just click "discussions" in the header, then start a new topic) | ||
* When a user creates an account, they only see a "created successfully" flash. When they try to login, it says they have to confirm their account first, but it never says how. -- will fix. [[User:Wenzel|wenzel]] | * When a user creates an account, they only see a "created successfully" flash. When they try to login, it says they have to confirm their account first, but it never says how. -- will fix. [[User:Wenzel|wenzel]] | ||
| Line 31: | Line 30: | ||
* 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 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. | * 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. | * Search algorithm is improvable: The binary matching creates many hits with the same score in spite of their obviously different relevance. | ||
* Developer usernames link to different places atm (URLs or nonexistent pages); we need a user info page and have them link there. | * Developer usernames link to different places atm (URLs or nonexistent pages); we need a user info page and have them link there. | ||
* "find similar add-ons" sometimes shows different categories with the same name? ([http://preview.addons.mozilla.org/en-US/addons/display/398 example]) | * "find similar add-ons" sometimes shows different categories with the same name? ([http://preview.addons.mozilla.org/en-US/addons/display/398 example]) | ||
| Line 44: | Line 40: | ||
* 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? | * 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? | ||
* I don't see any developer link or page where I can upload/manage my extensions/themes (not yet implemented?) | * I don't see any developer link or page where I can upload/manage my extensions/themes (not yet implemented?) | ||
== dria's comments == | == dria's comments == | ||
* Seems to be a bug at [http://preview.addons.mozilla.org/en-US/discussions/post.php?AddOnID=398] when not logged in. At very least there should be a significantly friendlier message suggesting the user log in :) | * Seems to be a bug at [http://preview.addons.mozilla.org/en-US/discussions/post.php?AddOnID=398] when not logged in. At very least there should be a significantly friendlier message suggesting the user log in :) | ||
== dolske's comments (from blog) == | == 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. | * 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) == | == jMax's comments (from blog) == | ||
| Line 73: | Line 54: | ||
* 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. | * 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. | * The "New and Updated" list on the "Extensions" page is missing the corner background. | ||
== Dao's comments == | == Dao's comments == | ||
| Line 82: | Line 61: | ||
== DonGato'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. | * 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. | * '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. | ||
| Line 89: | Line 66: | ||
== trev's comments == | == trev's comments == | ||
* Default Locale field on /developers/add seems to encode entities twice, e.g. I see Français there | * 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. | * 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. | ||
| Line 95: | Line 71: | ||
* Isn't it possible to detect add-on type automatically? The file will need to be unpacked and analyzed anyway. | * 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. | * When I fill out all fields correctly I get the error "Could not move file". Stuck at step 1. | ||
Revision as of 23:45, 12 January 2007
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:
- Having the search box at the bottom is too annoying. I don't want to have to scroll down to search. I also think there should be a search box somewhere on every page, as before the reskinning. AMO search doesn't suck now (hopefully) so we should make sure it's used instead Google on site:addons.mozilla.org which is how I currently find things. (bug 365918)
- Home is listed on both the top menu and the side menu. It seems a little strange and would be more appropriate to only be on the top menu.
- The sidebar still doesn't show the active page with a gray background (li class="selected")
- The discussion header/footer is noticeably different.
- This may be a vanilla bug, not sure: "Comment by made 1 day ago days ago"
- Discussions show a CakePHP favicon for me
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
- on the /addons/display page, the "bad trip" link does nothing
- Discussions can be started that aren't related to an addon (just click "discussions" in the header, then start a new topic)
- When a user creates an account, they only see a "created successfully" flash. When they try to login, it says they have to confirm their account first, but it never says how. -- will fix. wenzel
- 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 Add-ons page is kind of unfriendly and doesn't quite say what it is/does.
- 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.
- Developer usernames link to different places atm (URLs or nonexistent pages); we need a user info page and have them link there.
- "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?
- I don't see any developer link or page where I can upload/manage my extensions/themes (not yet implemented?)
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
- I don't see how the user is expected to find, say, Thunderbird extensions. AMO2 was too Firefox-centric, AMO3 seems even worse. http://www.erweiterungen.de/ does this better.
- Old URLs don't work, e.g. http://preview.addons.mozilla.org/firefox/398/ vs. http://preview.addons.mozilla.org/addons/display/398. I don't see the purpose of /addons (it's already in the subdomain) and /display.
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.