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