m (→UX Workflow in a Nutshell) |
|||
| Line 1: | Line 1: | ||
| - | = MeeGo QA | + | = MeeGo QA tools user experience = |
This is the main page for user experience (UX) work done for MeeGo QA tools. The purpose of the UX activities is to improve the QA-tools so that they are easier, more efficient and more pleasant to use. For this, end-users and their input are crucial. By understanding the users and their needs, it is possible to develop something that really benefits the users. | This is the main page for user experience (UX) work done for MeeGo QA tools. The purpose of the UX activities is to improve the QA-tools so that they are easier, more efficient and more pleasant to use. For this, end-users and their input are crucial. By understanding the users and their needs, it is possible to develop something that really benefits the users. | ||
| - | This page is meant for giving an overview of UX activities regarding QA tools | + | This page is meant for giving an overview of UX activities regarding QA tools. Even if some traditional user-centered design methods (user studies, usability tests etc.) require offline working, the results of those should be published here or be directly filed as enhancements/bugs to Bugzilla. |
== UX Workflow in a Nutshell== | == UX Workflow in a Nutshell== | ||
| Line 19: | Line 19: | ||
Meeting users face-to-face is preferred but online methods can also be used. E.g. the input can be gathered via mailing lists or IRC, and design drafts can be published to wiki or Bugzilla. | Meeting users face-to-face is preferred but online methods can also be used. E.g. the input can be gathered via mailing lists or IRC, and design drafts can be published to wiki or Bugzilla. | ||
| - | == | + | == Ongoing Work== |
| - | === Testrunner | + | === Testrunner and Testplanner === |
| - | * | + | * Improve the visual look |
| - | + | * Design UI improvements based on user feedback | |
| - | + | * Report the improvement proposals to Bugzilla | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
== Proposal for Future Work == | == Proposal for Future Work == | ||
| Line 46: | Line 33: | ||
** Evaluate the ease of the installation and the first time use | ** Evaluate the ease of the installation and the first time use | ||
** Improve visual look of the GUI tools, e.g. improve icons and other graphical elements | ** Improve visual look of the GUI tools, e.g. improve icons and other graphical elements | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
== How to Participate == | == How to Participate == | ||
| Line 63: | Line 38: | ||
The UX work is no different from the other development work of QA-tools. You can, for instance, work on the tasks presented on this page or just propose new tasks. In general, the best channels for participating are: | The UX work is no different from the other development work of QA-tools. You can, for instance, work on the tasks presented on this page or just propose new tasks. In general, the best channels for participating are: | ||
* [http://webchat.freenode.net/?channels=meego-qa-tools #meego-qa-tools IRC channel on irc.freenode.net] for discussing about the tools | * [http://webchat.freenode.net/?channels=meego-qa-tools #meego-qa-tools IRC channel on irc.freenode.net] for discussing about the tools | ||
| - | * [http://bugs.meego.com/enter_bug.cgi?product= | + | * [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20Quality%20Assurance] for reporting enhancement ideas or usability problems |
Contents |
This is the main page for user experience (UX) work done for MeeGo QA tools. The purpose of the UX activities is to improve the QA-tools so that they are easier, more efficient and more pleasant to use. For this, end-users and their input are crucial. By understanding the users and their needs, it is possible to develop something that really benefits the users.
This page is meant for giving an overview of UX activities regarding QA tools. Even if some traditional user-centered design methods (user studies, usability tests etc.) require offline working, the results of those should be published here or be directly filed as enhancements/bugs to Bugzilla.
User experience is not something that could just be added to a product as the last thing of the implementation process. On the contrary, user experience work focuses on taking the users into account in every phase of the development process. The following gives just one example on how you can do user-centered design in practice:
Meeting users face-to-face is preferred but online methods can also be used. E.g. the input can be gathered via mailing lists or IRC, and design drafts can be published to wiki or Bugzilla.
The UX work is no different from the other development work of QA-tools. You can, for instance, work on the tasks presented on this page or just propose new tasks. In general, the best channels for participating are: