Submitting patches that alter the user interface of Firefox doesn't need to be a scary or long process. This document outlines tips to getting a speedy and helpful response from the Firefox UX team.
Asking for general direction?
There are times where you may not know which direction to go in. There is nothing wrong with implementing what you think will provide the best user experience, or implementing multiple variations of your idea. Sometimes the experience of implementing another idea may show some pluses and minuses in the design and help with your decision making.
If you still have some general questions about design, *please* don't hesitate to join the #ux channel on IRC. If somebody doesn't answer your questions, just ask again in a few hours (people may be sleeping due to timezone differences).
Looking for feedback or ui-review on your patch?
If you're about to upload a patch and request feedback or ui-review, please link to either a screenshot, screencast/video, and/or try-server builds that contain the patch.
Here are some good links to software that can be used to create screenshots and screencasts:
- TechSmith Jing (free and paid version makes PNG screenshots, free version makes SWF videos, paid version makes MP4 videos)
- TechSmith Camtasia Studio/Camtasia:Mac (useful for detailed/longer screencasts)
Please attach your screenshots/screencasts to the bug, since the lifetime of Bugzilla will probably outlive the lifetime of some external image hosting website.
After attaching your media, please flag the special UX email address (to be determined by bug 717745) for feedback or ui-review.
Expectations of the UX team
The UX team has a goal of responding to a request within 48 hours.