Usability/Developers Survey Report
Z Kadu
Results of a Developers Survey for the Kadu Usability Project
July 2008
--Akai 02:25, 2 sie 2008 (CEST)
The Kadu Usability Project aims to make current Kadu functions more user-friendly and easily accessible for users representing different levels of expertise as well as provide the developers team with help with the introduction of new features (especially multiple communication protocols) in the best way possible as far as usability goes.
The first step in gathering information about Kadu's existing and intended userbase was conducting an informal survey with the current developers of the project. The data I've acquired both helped me design a user survey that's currently being deployed and determine the goals and the vision shared by the developers.
The developer survey was conducted via an e-mail exchange in June 2008. The exchange was coordinated by Piotr Pełzowski (patpi), the public relations manager of the Kadu project.
As the developers have indicated themselves, the data presented below isn't hard facts acquired in any kind of research but rather beliefs and observations of the Kadu developer team.
1. For whom Kadu is intended?
It's intended for everybody. As is typical for Open Source projects, the users that speak up in the forums, report bugs and/or commit their own efforts into making Kadu better are more easily noticeable for the developer team. Because they communicate their needs directly there is a risk of putting them forth, but the developers try to remember about the rest of the users who can't or aren't willing to speak up for themselves as well.
The needs of the users who are willing to communicate them are the most important though as this part of the userbase is considered the most valuable by the developers. In the second place, the developers aim to fulfill their own needs and finally they are trying to consider the other users as well.
2. For whom the authors of external modules write them?
The authors of external modules extending the functionality of Kadu tend to write them to fulfill their own needs in the first place. They may be willing to consider the other users as well though, especially if they participate in the development of the module in some way.
3. What level of technical knowledge do you expect from Kadu users?
The least acceptable level is the ability to use typical applications geared towards Internet usage such as Web browsers or basic Internet Messaging software without any third party's constant help.
Kadu developers presume that most of their users use Linux on a daily basis and have installed and configured their systems themselves. Their level of technical knowledge is high compared to the general population. They are able to use different applications intuitively without putting much effort into learning to use them. The goal isn't to create an application that would only be useful for advanced computer users though. By default no advanced options are enabled and the interface is kept simple.
It's supposed to be possible to start using Kadu with minimal effort put into its configuration - right after supplying username and password for the Gadu-Gadu server in the extremely simple initial configuration wizard. On the other hand Kadu supplies very advanced configuration options as possibilities for advanced users.
4. Why do you think Kadu users have need for a Gadu-Gadu-only Internet Messenger for Linux?
People use Gadu-Gadu because it's the most popular protocol in Poland and their affiliates are most likely to use it. Many people in Poland don't have need for any other protocols in their everyday life.
Searching for a Gadu-Gadu client for Linux or Mac OS X they are likely to stumble across Kadu, as it is touted the replacement for the official Windows client for Linux and Mac, differentiated from the numerous multiple protocol IMs that include Gadu-Gadu by its Polish roots and Gadu-Gadu-only Internet Messenger characteristic.
Therefore some Kadu users are likely people who don't care about other protocols and don't wish for these other protocols to hinder their way.
5. In what ways do you think the users of Gadu-Gadu and Jabber protocols are different?
Jabber isn't as popular in Poland and it is mostly chosen by its users consciously because of its favorable characteristics. It is also standard among the dedicated Linux users because of its open character. One of the goals of Kadu developers is introducing Jabber in Kadu in a such way that will make it possible for its current users, the less advanced as well, to start using Jabber without changing their habits, often originating from their earlier experiences from Windows. Jabber is supposed to be exceptionally easy to use in Kadu compared to the Jabber-dedicated clients.
Kadu won't be showcasing the differences between Jabber and more traditional protocols. The e-mail metaphor may be favorable for Jabber as well. The list of recommended servers will be supplied to the user and it won't be required of him to be knowledgeable with the Jabber-specific infrastructure.
6. How important is accessibility for the Kadu project?
No questions or complaints regarding the accessibility of Kadu were ever recorded. It seems there is no significant amount of people with disabilities among the current users. So far is hasn't been a concern and for as long as more pressing issues aren't addressed by the developers first accessibility won't be taken into account at all.
7. Are you taking into account the needs of corporate users?
Kadu is intended solely for home users.
8. Do you intend to attract users from outside Poland?
The developers have high hopes concerning attracting users and possibly more developers from outside Poland after introducing more protocols that will make Kadu a viable Internet Messenger for more people. The English version of the interface is considered especially important.
9. For whom and for what Kadu isn't intended for sure?
There are no users that should be excluded completely, though Kadu is lacking the manpower to cater to the very rare and specific needs that aren't actually communicated by the user community. As far as features go Kadu is an Internet Messenger and it won't incorporate features that aren't involved in Internet messaging. On the other hand external modules may do whatever and cater to the most specific of needs.
10. What do you expect from the computer Kadu is supposed to be running on?
Kadu can work on any system that's able to run other fairly modern graphic applications. It can be used comfortably on a fairly old hardware as it is a small program that isn't consuming much resources, but it isn't intended to run specifically on obsolete hardware.
11. How important is it for Kadu to work comfortably on specific hardware such as netbooks, UMPCs, MID, PDA and smartphones?
It's not particularly important. The fact that Kadu is able to run on some of this hardware is acknowledged but not enough users seem to be interested in using Kadu on it and having significant problems on the way. These issues will be addressed if and when users will show signs of having widely adapted such hardware.
12. What operating system is Kadu intended for in the first place? How do you think this will be changing in the future?
So far it's intended for Linux and other Unix systems it can be compiled on. As far as Mac OS X goes the current rough port should become mature shortly.
It will be possible to port Kadu to Windows as well, but it's not overly important. Doing much development of the Windows version isn't possible with the current number of developers.
13. What desktop environment / window manager is Kadu intended for in the first place?
It shouldn't matter. The developers are working on using the Qt 4 potential to achieve consistent look with the GTK applications. Kadu doesn't use KDE libraries either. The goal is to make Kadu look and work good in all desktop environments.
The same goes for Mac OS X and Windows. For instance, additional icon themes may be developed to assure visual integration with these systems as well.
14. What Internet Messengers are Kadu's primary rivals?
- Psi - Jabber-only Internet Messenger based on the Qt library; Kadu developers believe that Psi users may exchange it for Kadu once it incorporates Jabber and the motivation behind their move may be the appreciation for Kadu's better usability
- Kopete and Pidgin - classic Linux multiple protocol Internet Messengers
Once the Windows port will be functional all the Internet Messengers typical for the Polish market.
15. What are the final goals for the Kadu project?
- replicate all features of the official Gadu-Gadu client for Windows
- add multiple protocol support
- clean up both the code and the interface