ux evaluation report_clevertexting

1 © 2009 Digia Plc

User Experience

Digia Plc

In partnership with Forum Nokia

User Experience Evaluation for

Clever Texting

2 © 2009 Digia Plc

Evaluated Application

022.001Firmware version:

1.00(0)Application version:

22.12.2009Evaluation date:

Digia PlcEvaluator:

6730cPhone used:

DeviceEvaluation tool:

Clever Texting by Luna Ergonomics Pvt LtdApplication name:

3 © 2009 Digia Plc3 © 2009 Digia Plc

About this document

• The purpose of this evaluation is to discover any possible problems the end users may have with the submitted application.

• The evaluation results are listed by view or functionality and then by criteria in question.

• The evaluation was done using mobile usability heuristics1:• Visibility of system status and losability/findability of the mobile device

• Match between system and the real world

• Consistency and mapping

• Good ergonomics and minimalist design

• Ease of input, screen legibility and glanceability

• Flexibility, efficiency of use, and personalization

• Aesthetic, privacy, and social conventions

• Realistic error management

1) Joanna Lumsden: Handbook of Research on User Interface Design and Evaluation for Mobile Technology. Edited by: Joanna Lumsden, National Research, Council of Canada, Canada , Released Feb2008. ISBN: 978-1-59904-871-0.

4 © 2009 Digia Plc4 © 2009 Digia Plc

About this document

• Another reference we used in the report is the User Experience Evaluation Model (referred to as FNUX).

• Since the application is targeted for Nokia S60 devices we also checked that your application is consistent with the Nokia S60 UI style.

• For general information regarding User Experience Design for Nokia devices, please refer to forum.nokia.com/designcenter.

• For more information on design patterns and their usage, please refer to the Forum Nokia wiki.

• Please refer to the Forum Nokia Developer Libraries for more technical details.

5 © 2009 Digia Plc

Summary: What was good usability

• In general there are no critical usability problems, service is easy

and intuitive to use.

• Overall look and feel of the service is clear, there are no

unnecessary elements.

• Usability and ergonomics were taken into account in CleverTexting

keypad. Fingerprint showed what button was pressed last and this

helped to perceive which button to press next. The keypad had also

several typing modes to support different kind of users and typing

habits.

6 © 2009 Digia Plc

Summary: What needs improvement

• The headers of the views or selection list items did not always correspond

to the purpose or the action.

• To begin to compose messages the user needed to go relatively deep in the

application structure. Application structure could be revised.

• Functions of the views should be thought carefully and organize the

features according to the view purpose.

• Some labels could be named to correspond to familiar terms.

• In some views the navigation caused problems because of the lack of titles.

• There are few layout problems that affect to the usability. It is

recommended to rethink location and functionalities of some buttons.

RESULTS

8 © 2009 Digia Plc

Application structure and terms

• Criteria:

• Ease of input, screen readability, and glaceability: Screen content

should be easy to read.

• FNUX-2.6.20: The same terms are used for the same things

throughout the application and the terms must correspond with the

functionality.

• Issue:

• The labels do not correspond the functions related to them.

• The functions should appear in right context.

• It is recommended that deep application structures are avoided.

� Improvement ideas:

• Rename terms ‘Send Message’ to ‘Create message’ and ‘Write

Message’ to ‘Compose Message’ to correspond the familiar terms

and right meaning.

• Combine views to avoid deep application structure. The contents of

the list views are related to each other.

9 © 2009 Digia Plc

Compose message view

• Criteria:

• Visibility of system status: Through the mobile device, the system

should always keep users informed about what is going on.



• Issue:

• The header does not correspond to the purpose of the view.

• Readability of the soft keys and the character map is not good.


• Change the header to e.g. ‘New message’.

• Enlarge the virtual keypad and character map.

10 © 2009 Digia Plc

Options menu

• Criteria:

• FNUX-2.12.53: Two commands with different titles must not execute

the same action.

• Issue:

• ‘View text’ and ‘Send’ executes the same action (moves to the ‘View

or Edit text’ view).


• Options menu would be simpler if ‘View text’ and ‘Send’ items were

combined. Another option is to send the message from the ‘Send’

(according to the header of the view).


Send message view

• Criteria:

• Consistency and mapping: the user’s conceptual model of the

possible function/interaction with the mobile device or system should

be consistent with the context.

• Issue:

• After sending the message the application does not return to the

main view as it could be assumed.


• Show Main view after sending.


Sent items view

• Criteria:



• Issue:• Sent messages are shown with one-row list of phone numbers.


• Show ‘Sent Messages’ as a two-row list to show also the beginning of

the message. This would make it easier to distinguish the messages

from each others.



• Criteria:




• Issue:

• The character counter differs from the normal indication of how

many characters there are left.

• Deleting characters happen in an unconventional way.

� Improvement ideas:• Basic functionalities should be the same as in traditional editor.

• Remove the background of the character counter and move it to the

status pane area of the screen.

In normal editor the right button closes

the application, in CleverTexting this

button is used for deleting text.



• Criteria:

• Good ergonomics and minimalist design: Screen content should be

easy to read and navigate through.

• Issue:

• It is not possible to move the cursor in an editor. This causes that the

user cannot add/remove characters that are in the middle of the

sentence.


• The user should be able to move in the middle of the sentence freely.

Navi key could be used so that the user can navigate between

characters in the editor.

The user can not navigate in the text



• Criteria:

• Match between system and the real world: the system should have

the capability to sense its environment and adapt the presentation of

information accordingly.

• Issue:

• The application does not suggest upper-case letters after writing

symbols that normally require an upper-case letter. Instead the same

character list is still shown.


• The application should suggest the right case automatically. E.g. after

an upper-case letter it should suggest lower-case letters and after

special characters upper-case letters.

The application suggests symbol after typing a symbol

and after choosing Next List it suggests a lower case letters.



• Criteria:




• Issue:

• The system does not have all the symbols that the user needs and is

used to having when using a normal text editor.


• Add the missing symbols.

Symbols in normal

texting

Symbols in CleverTexting


Help view

• Criteria:



• Issue:

• The text does not fit to the screen.

• The layout of the text is not ideal. It seems that the text is not aligned

in any way.


• Use alignment.

• Make sure that all the text fits to the screen regardless of the phone

model. The text should automatically adapt to the screen size.


Help and mode view

• Criteria:• Flexibility, efficiency of use, and personalization: Allow mobile users

to tailor / personalize frequent user actions.

• Issue:

• In the Mode view there are many mode options and the user can

select which one to use. It is hard to know what the different modes

are and how they differ from each other.


• Add information about the different modes in the help. Also there

could be tooltips or some other short info text about the modes in

the Mode view.


Help view

• Criteria:

• Visibility of system status: .Through the mobile device, the system

should always keep users informed about what is going on.

• Issue:

• Breadcrumbs is an excellent way to indicate where user is in the

system. Unfortunately this is not shown when scrolled down in long

views.


• Keep the breadcrumbs visible all the time.

• Each view should have a title.

Thank You!

Digia also provides services for:

• Facelift for application to create WOW effect

• UI concept design and UI Specification

• Usability testing with real users

• Expert evaluations with prioritized listings and concrete

improvement suggestions

• For more information, visit: www.digia.com

ux evaluation report_clevertexting

Documents