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