org.symbian.tools.wrttools.doc.WebDeveloper/html/GUID-B2976236-0DC6-4CBB-B2FA-B1A6E6639A1D.html
Bug 2892 - Import wgz file from Import menu should have same functionality as File New Project Create from wgz
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/><meta name="copyright" content="(C) Copyright 2009"/><meta name="DC.rights.owner" content="(C) Copyright 2009"/><meta name="DC.Type" content="concept"/><meta name="DC.Title" content="Designing for a specific audience"/><meta name="abstract" content="Every application you design should have a specific purpose. Find out who will use the application, what they will use it for, and which mobile devices they have. Then design the application to fit a specific context of use."/><meta name="description" content="Every application you design should have a specific purpose. Find out who will use the application, what they will use it for, and which mobile devices they have. Then design the application to fit a specific context of use."/><meta name="DC.Relation" scheme="URI" content="GUID-7962116F-3FDB-4960-B1C9-6367451554FD"/><meta name="DC.Relation" scheme="URI" content="GUID-D54DEFE7-E878-4530-B707-A5388DFE1D9D"/><meta name="DC.Relation" scheme="URI" content="GUID-5949FE0C-207D-4B15-8C03-96AE48986973"/><meta name="DC.Format" content="XHTML"/><meta name="DC.Identifier" content="GUID-B2976236-0DC6-4CBB-B2FA-B1A6E6639A1D"/><meta name="DC.Language" content="en"/><title>Designing for a specific audience </title><script type="text/javascript">
function initPage() {}
</script><link href="../PRODUCT_PLUGIN/book.css" rel="stylesheet" type="text/css"/><link href="css/s60/style.css" rel="stylesheet" type="text/css" media="all"/></head><body onload="initPage();"><div class="body"><div class="contentLeft prTxt"><h1 class="pageHeading" id="GUID-B2976236-0DC6-4CBB-B2FA-B1A6E6639A1D">Designing for a specific audience</h1><div><p>Every application you design should have a specific purpose. Find out who will use the application, what they will use it for, and which mobile devices they have. Then design the application to fit a specific context of use.</p>
<div><h3>Analyzing users and their tasks</h3><p>Gather information about the user group to learn about the context the people live in, their current tasks, their problems with current solutions, their needs for new products or services, and underlying motivations that would get them to adopt and use them. Possible methods for gathering the information include interviewing users, observing them at their current tasks, asking them to document their daily activities, and creating questionnaires. For example, gather information about the use of a Web site to determine which content or service is accessed most frequently and would thus make a useful widget.</p><p>You can combine content from Web sites with a local context to deliver personalized services that are relevant to your users. For example, a weather widget can use the global positioning system (GPS) in mobile devices to access the user's location and deliver information about the local weather.</p><p>For more information on user experience techniques, see <a href="http://library.forum.nokia.com/topic/Design_and_User_Experience_Library/GUID-D4AFE068-97E8-487A-A79B-CE1422127623.html" target="_blank">Usability in a mobile application development project</a>.</p></div>
<div><h3>Selecting supported devices</h3><p>You can install and run widgets on <a href="GUID-1A3ECAC1-3F09-4602-A1CD-82164040A664.html#GUID-1A3ECAC1-3F09-4602-A1CD-82164040A664">devices that support Web Runtime (WRT)</a>. Each unique device targets a different market niche, a combination of form, functionality, and price, which expands the total addressable market for mobile applications. The characteristics of your target devices, such as screen size and orientation, touch support, and the availability of a keyboard or home screen, affect widget design.</p><p>For more information on the target devices, see <a href="http://www.forum.nokia.com/devices" target="_blank">Device Specifications</a>.</p></div>
<div><h3>Designing for a specific context of use</h3><p>When designing for mobile devices, keep in mind the context in which users use their mobile devices:</p><ul>
<li><p>Location—Where and how do users use the widget? Are they standing up or sitting down? Do they have one hand free?</p><p>Design widgets that users can use with one hand, while walking. For more information, see <a href="GUID-6DD2B3D2-BA3B-4936-BBC9-F61B6757B6F8.html#GUID-6DD2B3D2-BA3B-4936-BBC9-F61B6757B6F8">Managing user interaction</a></p></li>
<li><p>Time—How much time can users afford to spend on the widget? How much attention can they give to it?</p><p>Design widgets that fit into the natural flow of users and do not take them out of it. For more information, see <a href="GUID-C359CC7E-B8BA-491B-A0C4-0FF1D3C4110C.html#GUID-C359CC7E-B8BA-491B-A0C4-0FF1D3C4110C">Moving within widgets</a>.</p></li>
<li><p>Light—Are the users inside or outside? What are the weather conditions?</p><p>Design widgets that users can see even in direct sunlight. For more information, see <a href="GUID-B74565A3-C981-4377-99F0-FAD87B9E516D.html#GUID-B74565A3-C981-4377-99F0-FAD87B9E516D">Designing for small screens</a>.</p></li>
<li><p>Situation—Can users or those around them be disturbed by the mobile device?</p><p>Because users take their devices with them everywhere, design widgets that remain silent when devices are set to silent.</p></li>
<li><p>Ease of use—How experienced are users in using mobile devices?</p><p>Design widgets that even inexperienced users can use. For more information, see <a href="GUID-7962116F-3FDB-4960-B1C9-6367451554FD.html#GUID-7962116F-3FDB-4960-B1C9-6367451554FD">Designing simple pages</a>.</p></li>
</ul></div>
</div></div></div><div class="footer"><hr/><div class="copy">© Nokia 2009.</div></div></body></html>