What exactly are you testing? If you're testing how well your users can use a mobile interface using either multitap or qwerty, then it would probably be easier to test the input methods separately from the application. For instance, what are the full range of characters a user can enter in your app? Letters (upper and lower), numbers, special characters (@*,/), etc. Get that list together, then create sample inputs in the form of sentences or whatever. Then test your input methods using those samples, noting input speed, error rate, satisfaction, etc. Once you have your test results, you can go back and apply them to your app and know which parts of your app will be more or less difficult for people using a given input method. You may want to note if some characters are particularly troublesome. I know the "@" can be difficult on some phones using multitap, in which case, you may want to alter your interface to account for that. For instance, instead of a "Email:______________" give them "Email:_______@____________". That eliminates the need to type the "@", which might be helpful for some users.
> Hi AllHope everybody is doing well.Recently I conducted a usability
> test a
> part of which involved testing a multitap vs a full QWERTY keypad on
> mobile phone.Major part was to test the QWERTY.After the test, I am
> if it is ok to compare these two ?Both of them have different
> interfaces and
> interactions; hence the type of errors users make will differ with both
> them.Is it ok to test QWERTY considering multitap as a benchmark if we
> looking at error rates ?Thoughts ?Ananya Vetaal
> (((Please leave all content below this line)))
> Welcome to the Interaction Design Association (IxDA) Discussion!
> Manage Account .......... http://www.ixda.org/user/29196/notifications
> Discussion Guidelines .......... http://www.ixda.org/help
> View original post: