|
1 <?xml version="1.0" encoding="utf-8"?> |
|
2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. --> |
|
3 <!-- This component and the accompanying materials are made available under the terms of the License |
|
4 "Eclipse Public License v1.0" which accompanies this distribution, |
|
5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". --> |
|
6 <!-- Initial Contributors: |
|
7 Nokia Corporation - initial contribution. |
|
8 Contributors: |
|
9 --> |
|
10 <!DOCTYPE concept |
|
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
|
12 <concept id="GUID-1FCD0312-7B28-47F9-BE54-822B74A8934C" xml:lang="en"><title>Designing |
|
13 applications for touch UI</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
14 <p>Both touch screens and hybrid devices are supported by Symbian platform. |
|
15 Touch screen enables direct manipulation of content and objects, allowing |
|
16 for far more natural interaction with the device. This means a completely |
|
17 different user experience and interaction style compared to using a hardware |
|
18 keypad.</p> |
|
19 <fig id="GUID-0895B1BD-27D2-4824-A02C-F89137A16E53"> |
|
20 <image href="GUID-59F26729-3FFB-48AE-91FB-4B9AC2955A06_d0e74654_href.png" scale="60" placement="inline"/> |
|
21 </fig> |
|
22 <p>All applications must be touch-enabled, which means that they can be used |
|
23 with the touch screen alone, regardless of the presence of a keypad. There |
|
24 are only three mandatory hardware keys in touch devices based |
|
25 on the Symbian platform - Send, End, and Multi-tasking key.</p> |
|
26 <p>The application features must follow the platform support for different |
|
27 hardware. When designing a touch-enabled Symbian application, the UI must |
|
28 be designed so that everything can be accomplished by using the touch screen |
|
29 interface, as the potential target devices may or may not have a hardware |
|
30 keyboard. </p> |
|
31 <p>The touch UI in the Symbian platform is based on the use of resistive and |
|
32 capacitive touch screens. In <b>resistive touch screen</b> technology, two |
|
33 conductive and resistive layers are separated by a thin space. When an object |
|
34 touches this kind of touch panel, the layers are connected at a certain point, |
|
35 and a touch event is registered. This allows efficient stylus control, in |
|
36 addition to finger touch - unlike capacitive panels, which usually register |
|
37 only finger touch. Additionally, resistive touch screen offers a higher resolution |
|
38 and more durability. In <b>capacitive touch screen</b> technology, the panel |
|
39 consists of an insulator such as glass, coated with a transparent conductor |
|
40 (such as indium tin oxide (ITO)). When an object touches the surface of the |
|
41 screen, it results in a distortion of the local electrostatic field, measurable |
|
42 as a change in capacitance. Then a touch controller measures the frequency |
|
43 variations to ascertain the co-ordinates of the object's touch. Capacitive |
|
44 touch screen supports <xref href="GUID-17C64C2F-9426-4B41-9F0A-23060289D644.dita">multi-touch</xref>.</p> |
|
45 <p>The hardware is supported by various:</p> |
|
46 <ul> |
|
47 <li><p>touch-specific components (see <xref href="GUID-BB8B3A11-0BBC-4759-A7F4-A28C9E70573F.dita">Touch |
|
48 support for common UI components</xref>)</p></li> |
|
49 <li><p>component and UI behavior changes</p></li> |
|
50 <li><p>layout changes, and</p></li> |
|
51 <li><p>additions to the interaction style.</p></li> |
|
52 </ul> |
|
53 <p>The touch UI is designed to enable full task flow with touch, with minimal |
|
54 need to switch to hardware keys. Thus, the design ensures that users can complete |
|
55 a task with the chosen interaction method from start to finish. </p> |
|
56 <p>While designing and implementing applications for touch screen devices |
|
57 based on the Symbian platform, consider interactions that benefit the most |
|
58 from the touch UI. </p> |
|
59 <p>If you can apply direct manipulation of the UI, for example when moving |
|
60 items from one place to another, or scrolling a page, do not confine the user |
|
61 with unnecessary scrollbars or have the user resort to options list commands.</p> |
|
62 <p>Instead, enable the user to view pages larger than a screen by panning |
|
63 them directly, and dragging and dropping items rather than marking them and |
|
64 using menu options. </p> |
|
65 <ul> |
|
66 <li><p>Remember that the most intuitive touch screen interactions that can |
|
67 be performed using a finger are tapping, stroking up/down/left/right, and |
|
68 the long tap. </p></li> |
|
69 <li><p>Utilize strokes that are easily discovered to the users in the given |
|
70 context. It should be explicit to the user where strokes can be performed. </p></li> |
|
71 <li><p>Design to ensure that users can complete a task with the same interaction |
|
72 method from start to finish - touch or hardware keys, stylus, or finger, and |
|
73 using one hand or both hands. </p></li> |
|
74 <li><p>Aim to optimize system performance and battery consumption to provide |
|
75 a fluid and reliable touch user experience. </p></li> |
|
76 </ul> |
|
77 <p><b>See Also</b>:</p> |
|
78 </conbody></concept> |