Labs/Jetpack/FlightDeck/1.0a2/UXChanges

From MozillaWiki
Jump to navigation Jump to search

Following are changes which should be done for the next iteration or before beta.

After FlightDeck UX review

FrontPage

  1. Add a place for tutorial
    • slideshow of the easiest path to create an addon as a placeholder
  2. Make it more descriptive

PackageBrowser

  1. Menu
    • Make [New Extension] / [New Library] more prominent
    • Myk: actually, it's only the [New Extension] link that should be more prominent, since our primary target audience is developers who want to build an addon, not those who want to build a library. See the mockup in bug 566252 for a visual explanation of the difference in prominence these links should have.
  2. Move See more to the bottom of the page
  3. Package Action bar
    1. Change [Edit] to [View Source] if user can't edit the code
    2. Add number of other plugins author has written
    3. Add author overall rating
    4. Remove versions
    5. Myk: also, remove "Try in browser" from this list of addons; users should view the source of an addon before deciding to try it out, since FlightDeck is a developer-focused site, where the purpose of giving developers access to other users' addons is to encourage developers to learn from each others' code

FlightDeck Plugin

  1. "Install Flightdeck" above Categories
  2. Myk: actually, we should remove Categories and the Install FlightDeck link entirely from the home page, since they don't provide any value (there are no categories, and it isn't necessary to install the addon to use the home page).
  3. Make a FlighDeck Plugin warning show when needed - not all the time
  4. Change the wording in confirmation after installed plugin
  5. Myk: I suggest we implement the following behavior:
    • when a user visits the home page, FlightDeck doesn't prompt her to install the Helper addon;
    • when the user presses the Build Add-on button to create a new addon or the Edit or View Source buttons for an existing addon, FlightDeck still doesn't prompt her to install the Helper addon;
    • when the user presses the Try in Browser button for an addon from the Edit or View Source pages, and she doesn't have the Helper addon installed, FlightDeck prompts her to install the Helper addon; once she installs it, the Helper addon notifies FlightDeck that it has been installed, and FlightDeck tells the Helper addon to install the addon being edited/viewed.

Editor

  1. Add [Duplicate & Edit] for Package
    • Myk: call this simply [Copy]
  2. Add ability to upload an icon
    • Myk: is this for display in FlightDeck itself or for including in the XPI bundle? If the former, this is not a priority, as the focus of the site is development, not distribution, so it is less important for addons to be able to advertise themselves better by using graphical aids like an icon. It will be valuable for libraries to advertise themselves via an icon, on the other hand, but library development is a lower priority in the initial phases of the application.

Test Now

  1. Change [Try in Browser] to [Test Now]
    • Myk: [Test] should be sufficient for this button, as "Now" is implicit and idiomatic.
  2. Make the button to show the status of testing - leave it pushed if the Addon is under testing
    • Myk: right! Also, if you press the button again, it should uninstall the addon being tested and then revert to its unpressed state.
  3. add another URL for create_xpi action - test_now - should do the same, but in # case it will do different action in the future - we're saved
    • Myk: it's not clear what this is trying to say; can you elaborate?

Login Page

  1. text: Log in to the Firefox Add-On Builder with your addons.mozilla.org account. Don't have an account? Get one.
  2. Remove Menu Bar

After build system changes

Editor

Jetpack-editor-wireframe.png
  • Manifest and other metadata are now edited inside a window. This window should be an "information window" if user has no editing rights (is not the author)
  • New Modules section - this is a list of Modules inside edited Package
  • Libraries section is to provide "Add Library" and "Library View/Remove" triggers.
  • View Library opens a new tab with the Editor
  • Sidebar contains Attachments Section
  • jetpack-core dependency is hidden and added in the back-end, however if someone would add a replacement to the FlightDeck it might be used and will not be overwritten by the SDK one

Other changes

Whole System (needs changes on the backend as well)

  1. Add rating
Retrieved from "https://wiki.mozilla.org/index.php?title=Labs/Jetpack/FlightDeck/1.0a2/UXChanges&oldid=225131"