We encourage you to give us feedback about development topics and other matters related to this web site.
Submit feedbackCalling All Innovators - Nokia's annual app development contest
Nokia releases new Qt developer offerings
$1M Growth Economy Venture Challenge - deadline for submissions: April 18
Capturing and uploading image, video or audio files to server with Flash Lite and APIBridge
Mr. Axel Jäger
Read more about Axel on the Champions website.
International CTIA WIRELESS 2010
March 23, 2010
Las Vegas
O’Reilly Where 2.0 Conference
March 30, 2010
San Jose, California
Building N900 Apps Using Qt Creator and Qt 4.6
April 14, 2010
2 p.m. London, 4 p.m. Helsinki
Building N900 Apps Using Qt Creator and Qt 4.6
April 14, 2010
11 a.m. San Francisco, 2 p.m. New York
Building N900 Apps Using Qt Creator and Qt 4.6 (In Chinese)
April 15, 2010
11 a.m. Beijing
Version 1.0 / 26 July 2004
When porting applications to different platforms, some features may need to be added or dropped. An application that is optimal for one particular device may be too complex or too simple for another platform. Thus, it might not be a good idea to simply implement all the features in all the platforms. When ported downwards to simpler devices, an application often needs to be more focused on its core features in order to be usable. When ported upwards to more complex devices, device capabilities should be fully used by implementing additional features.
This requires flexibility from both the application engine and the developer. Be clear about the primary and secondary features of the application when making decisions about which features to support in certain platforms. For example, consider the typical owner of a Series 40 mobile phone and the owner of a Series 80 communicator. Each is likely to have different expectations as well as different needs for a particular application. If the same application is ported to both platforms, it may be too complex for a Series 40 user and too simple for a Series 80 user.
You'll have a better idea of what we mean when we examine how certain standard applications have been implemented in existing handsets. Let’s take a closer look at the implementation of the calendar functionality in different devices

The calendar application in a Series 40 mobile device is minimalist, but supports the main features: viewing and editing of calendar entries, and reminders. The only views are a monthly view and a daily view. In some models it is also possible to synchronize the calendar with a desktop PC.

In this calendar implementation, the additional screen size is used to enhance the application. Users can conveniently view future reminders, notes, and meetings at one glance. They can also choose a monthly, weekly, or daily view. All Series 60 devices can synchronize the calendar with a desktop computer. Additionally, some devices are capable of General Packet Radio Service (GPRS) synchronizing. Users can choose their own alarm tone, as well as if they prefer a daily, monthly, or weekly view by default. Additionally, there are different types of calendar events. Repeated calendar events are supported.

In a Series 80 device, the additional screen size is used to its fullest potential. Details of a calendar event are displayed beside the monthly view. There are also additional views, including a yearly view, and users can select different colors for different calendar events. Synchronization supports more features, there are more possible calendar event types, and it is possible to print the calendar via infrared. A QWERTY keyboard enables the use of longer and more complex calendar events.
User groups for different devices may vary in their needs as well as their level of expertise in using technology. When porting application to new platforms, some features may need to be dropped, added, or redesigned to suit user needs. Developers should be able to identify a reasonable number of functionalities and features for each platform. This decision-making process can be supported by user studies. After all, who would know better how much functionality users expect than users themselves?
References:
Usability Guidelines at Forum Nokia Usability Web site: www.forum.nokia.com/usability
You can provide feedback about content on this page here