HK1221041B - Electronic touch communication - Google Patents

Description

Electronic touch communication

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent Application Serial No. 62/044,961, filed September 2, 2014; U.S. Provisional Patent Application Serial No. 62/129,955, filed March 8, 2015; and International Patent Application Serial No. PCT/US2015/034609, filed June 7, 2015; all of which are hereby incorporated by reference in their entireties.

This application is related to the following co-pending applications: International patent application serial number PCT/US2013/040061, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed on May 8, 2013; International patent application serial number PCT/US2013/069483, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed on November 11, 2013; U.S. provisional patent application serial number 62/026,532, entitled “Raise Gesture Detection in a Device,” filed on July 18, 2014; and U.S. provisional patent application entitled “REDUCED-SIZE INTERFACES FOR MANAING ALERTS,” filed on September 2, 2014, with Lawrence Yang et al. as inventors. The contents of these applications are incorporated herein by reference in their entirety.

Technical Field

The present invention relates generally to computer user interfaces and, more particularly, to user interfaces for communicating with other users.

Background Art

The use of electronic devices has increased significantly in recent years (e.g., to access music and send/receive messages). The devices receive input from the user, such as selecting a song for playback, selecting a message recipient from a phone book, entering text for a message body, and selecting a specific page of a document. As a result of increased device use, the frequency of user input into such devices has also increased significantly.

Summary of the Invention

In some embodiments, a method includes, at an electronic device having a touch-sensitive display and a rotatable input mechanism: displaying a user interface on the touch-sensitive display, the user interface including a plurality of objects and an affordance, each of the plurality of objects being associated with a contact from a plurality of contacts, the affordance having a visual appearance representing a first contact from the plurality of contacts; receiving a first input corresponding to a rotation of the rotatable input mechanism; and in response to receiving the input corresponding to the rotation of the rotatable input mechanism, updating the visual appearance of the affordance to represent a second contact from the plurality of contacts.

In some embodiments, a method includes, at an electronic device with a touch-sensitive display, at an electronic device with a touch-sensitive display and a rotatable input mechanism: displaying a user interface on the touch-sensitive display, the user interface including a plurality of objects and an affordance, each of the plurality of objects being associated with a contact from a plurality of contacts, the affordance having a visual appearance representing a first contact from the plurality of contacts; receiving a first input corresponding to a selection of an object from the plurality of objects that is associated with a second contact from the plurality of contacts; and in response to receiving the input corresponding to the contact on the object from the plurality of objects, updating the visual appearance of the affordance to represent the second contact from the plurality of contacts.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments, reference should be made to the following description of the embodiments in conjunction with the accompanying drawings, wherein like reference numerals designate corresponding parts throughout the drawings.

Figure 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for event processing according to some embodiments.

FIG2 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.

3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.

4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments.

FIG5A illustrates a personal electronic device in accordance with some embodiments.

5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.

6A-6E illustrate exemplary user interfaces for electronic touch communications.

7A-7E illustrate exemplary user interfaces for electronic touch communications.

FIG8 illustrates an exemplary user interface for electronic touch communications.

9A-9C illustrate exemplary user interfaces for electronic touch communications.

10A-10C depict a flow diagram illustrating a process for electronic touch communication.

11 is a flow chart illustrating a process for electronic touch communication.

12 is a flow chart illustrating a process for electronic touch communication.

13 is a functional block diagram of an electronic device in accordance with some embodiments.

FIG14 is a functional block diagram of an electronic device in accordance with some embodiments.

15 is a functional block diagram of an electronic device in accordance with some embodiments.

FIG16 is a functional block diagram of an electronic device in accordance with some embodiments.

FIG17 is a functional block diagram of an electronic device in accordance with some embodiments.

18A-18K illustrate exemplary user interfaces for electronic communications.

19A-19B illustrate exemplary user interfaces for electronic communications.

FIG20 illustrates an exemplary user interface for electronic communications.

FIG. 21 illustrates an exemplary user interface for electronic communications.

22 and 23 illustrate flow charts illustrating processes for electronic touch communication.

24 and 25 are functional block diagrams of electronic devices according to some embodiments.

DETAILED DESCRIPTION

The following description sets forth exemplary methods, parameters, etc. However, it should be appreciated that such description is not intended to limit the scope of the present disclosure, but is instead provided as a description of exemplary embodiments.

Below, Figures 1A-1B, 2, 3, 4A-4B, and 5A-5B provide descriptions of exemplary devices that can provide such user interfaces for electronic touch communication. Figures 6A-6E, 7A-7E, 8, 9A-9C, 18A-18K, 19A-19B, 20, and 21 illustrate exemplary user interfaces for electronic touch communication. The user interfaces in the figures are also used to illustrate the processes described below, including the processes in Figures 10A-10C, 11-13, 22, and 23.

Although the following description uses the terms "first," "second," etc. to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first touch can be referred to as a second touch, and similarly, a second touch can be referred to as a first touch without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.

The terms used in the description of the various described embodiments are used herein only to describe specific embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" used in the description of the various described embodiments and the appended claims are intended to also include plural forms. It should also be understood that the term "and/or" used herein refers to and covers any item in one or more items of the associated listed items and all possible combinations. It should further be understood that the terms "comprises", "having", "including" and/or "containing" when used in this specification specify the presence of features, wholes, steps, operations, elements and/or parts, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, parts and/or combinations thereof.

The term "if" may be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [stated condition or event] is detected" may be interpreted to mean "upon determination" or "in response to determining" or "upon detecting [stated condition or event]" or "in response to detecting [stated condition or event]," depending on the context.

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device (such as a mobile phone) that also includes other functionality, such as a PDA and/or music player functionality. Exemplary embodiments of portable multifunction devices include, but are not limited to, iPods and devices from Apple Inc. of Cupertino, California. Other portable electronic devices such as laptop computers or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads) may also be used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer with a touch-sensitive surface (e.g., touch screen displays and/or touch pads).

In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the computing device may include one or more other physical user interface devices, such as a physical keyboard, mouse, and/or joystick.

The device can support various applications, such as one or more of the following applications: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video recorder application, a web browsing application, a digital music player application, and/or a digital video player application.

Various applications executing on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and/or changed from one application to the next and/or within each application. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports various applications through a user interface that is intuitive and transparent to the user.

Attention is now directed to embodiments of portable devices with touch-sensitive displays. FIG1A is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes referred to as a “touch screen” and is sometimes considered or referred to as a touch-sensitive display system. Device 100 includes memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripherals interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input/output (I/O) subsystem 106, other input or control devices 116, and external ports 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of contacts on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 335 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

As used in the specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a numerical range that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). Optionally, various methods and various sensors or combinations of sensors are used to determine (or measure) the intensity of a contact. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of the contact. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of and/or changes to the contact area detected on the touch-sensitive surface, the capacitance of the touch-sensitive surface in proximity to the contact and/or changes thereto, or the resistance of the touch-sensitive surface in proximity to the contact and/or changes thereto are optionally used as a proxy for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the proxy measure for contact force or contact pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the proxy measure). In some implementations, the proxy measure for contact force or contact pressure is converted to an estimated force or estimated pressure, and the estimated force or estimated pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using intensity of contact as an attribute of user input allows user access to additional device functionality that would otherwise not be accessible to the user on a reduced size device (e.g., on a touch-sensitive display) having limited real estate for displaying affordances and/or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical/mechanical controls such as knobs or buttons).

As used in the specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of a device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of gravity of the device that is detected by a user using the user's sense of touch. For example, when a device or a component of the device is in contact with a touch-sensitive surface of a user (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a change in the physical properties of the device or component of the device that is felt. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) may be interpreted by the user as a "down click" or "up click" of a physical actuator button. In some cases, the user will feel a tactile sensation such as a "down click" or "up click" even when there is no movement of a physical actuator button associated with the touch-sensitive surface being physically pressed (e.g., displaced) by the user's movement. As another example, movement of the touch-sensitive surface may be interpreted or felt by the user as "roughness" of the touch-sensitive surface even when there is no change in the smoothness of the touch-sensitive surface. While this interpretation of touch by a user will be influenced by the user's individual sensory perceptions, there are many sensory perceptions of touch that are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "up click," "down click," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device or a component thereof for the described sensory perception for a typical (or average) user.

It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 may alternatively have more or fewer components than shown, may alternatively combine two or more components, or may alternatively have a different configuration or arrangement of components. The various components shown in FIG1A may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

Memory 102 may include one or more computer-readable storage media. Computer-readable storage media may be tangible and non-transitory. Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 may control access to memory 102 by other components of device 100.

Peripheral device interface 118 can be used to couple the input and output peripheral devices of the device to CPU 120 and memory 102. One or more processors 120 run or execute various software programs and/or instruction sets stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripheral device interface 118, CPU 120, and memory controller 122 can be implemented on a single chip (such as chip 104). In some other embodiments, they can be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuitry 108 converts electrical signals into/from electromagnetic signals and communicates with a communications network and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and the like. RF circuitry 108 optionally communicates wirelessly with, for example, the Internet, also known as the World Wide Web (WWW), intranets, and/or wireless networks such as cellular telephone networks, wireless local area networks (LANs), and/or metropolitan area networks (MANs), as well as other devices. RF circuitry 108 optionally includes known circuitry for detecting near-field communication (NFC) fields, such as via a short-range radio. Wireless communication may optionally use any of a variety of communication standards, protocols, and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolution Data Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11d), and/or IEEE 802.11e. 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet Message Access Protocol (IMAP) and/or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communications protocol, including communications protocols that have not been developed as of the filing date of this document.

The audio circuit device 110, the speaker 111, and the microphone 113 provide an audio interface between the user and the device 100. The audio circuit device 110 receives audio data from the peripheral device interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into sound waves audible to humans. The audio circuit device 110 also receives the electrical signal converted from the sound wave by the microphone 113. The audio circuit device 110 converts the electrical signal into audio data and transmits the audio data to the peripheral device interface 118 for processing. The audio data can be obtained from the memory 102 and/or the RF circuit device 108 and/or transmitted to the memory 102 and/or the RF circuit device 108 via the peripheral device interface 118. In some embodiments, the audio circuit device 110 also includes a headphone jack (e.g., 212 in FIG. 2). The headphone jack provides an interface between audio circuitry 110 and a removable audio input/output peripheral, such as output-only headphones or a headset capable of both output (eg, single or dual ear headphones) and input (eg, a microphone).

The I/O subsystem 106 couples the input/output peripherals on the device 100, such as the touch screen 112 and other input control devices 116, to a peripherals interface 118. The I/O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. Other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller(s) 160 are optionally coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. The one or more buttons (e.g., 208 in FIG2 ) optionally include up/down buttons for volume control of the speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in FIG2 ).

A quick press of the push button can unlock the touch screen 112 or begin the process of using gestures on the touch screen to unlock the device, as described in U.S. Patent Application No. 11/322,549, filed December 23, 2005, and U.S. Patent No. 7,657,849, "Unlocking a Device by Performing Gestures on an Unlock Image," which are incorporated herein by reference in their entirety. A longer press of the push button (e.g., 206) can power the device 100 on or off. The user can customize the function of one or more of the buttons. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and/or sends electrical signals to the touch screen 112. The touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, videos, and any combination of the above (collectively referred to as "graphics"). In some embodiments, some or all of the visual output may correspond to user interface objects.

The touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. The touch screen 112 and display controller 156 (together with any associated modules and/or instruction sets in memory 102) detect contact (and any movement or interruption of contact) on the touch screen 112 and convert the detected contact into interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch screen 112. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to the user's finger.

The touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. The touch screen 112 and display controller 156 may use any of a variety of touch sensing technologies now known or later developed to detect contact and any movement or interruption of contact, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or elements for determining one or more points of contact with the touch screen 112. In one exemplary embodiment, projected mutual capacitance sensing technology such as that found in Apple Inc. of Cupertino, California and iPod® is used.

In some embodiments of the touch screen 112, the touch-sensitive display may be similar to the multi-touch sensitive touchpads described in U.S. Patents 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is incorporated herein by reference in its entirety. However, the touch screen 112 displays visual output from the device 100, whereas a touch-sensitive trackpad does not provide visual output.

The touch-sensitive display in some embodiments of the touch screen 112 may be as described in the following applications: (1) U.S. patent application No. 11/381,313, filed on May 2, 2006, “Multipoint Touch Surface Controller”; (2) U.S. patent application No. 10/840,862, filed on May 6, 2004, “Multipoint Touchscreen”; (3) U.S. patent application No. 10/903,964, filed on July 30, 2004, “Gestures For Touch Sensitive Input Devices”; (4) U.S. patent application No. 11/048,264, filed on January 31, 2005, “Gestures For Touch Sensitive Input Devices”; (5) U.S. patent application No. 11/038,590, filed on January 18, 2005, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices”; (6) U.S. patent application No. 11/228,758, filed on September 16, 2005, “Virtual Input Device Placement On A Touch Screen User Interface”; (7) U.S. patent application No. 11/228,700, filed on September 16, 2005, “Operation Of A Computer With A Touch Screen Interface”; (8) U.S. patent application No. 11/228,737, filed on September 16, 2005, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard”; and (9) U.S. patent application No. 11/367,749, filed on March 3, 2006, “Multi-Functional Hand-Held Device”. All of these applications are incorporated herein by reference in their entirety.

The touch screen 112 can have a video resolution exceeding 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user can use any suitable object or appendage, such as a stylus, finger, etc., to make contact with the touch screen 112. In some embodiments, the user interface is designed to operate primarily through finger-based contacts and gestures, which are less precise than stylus-based input due to the larger contact area of a finger on the touch screen. In some embodiments, the device translates rough finger-based input into precise pointer/cursor positions or commands for performing the action desired by the user.

In some embodiments, in addition to the touch screen, device 100 may also include a touchpad (not shown) for activating or deactivating specific functions. In some embodiments, the touchpad is a touch-sensitive area of the device that does not display visual output, unlike the touch screen. The touchpad can be a touch-sensitive surface separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

The device 100 also includes a power system 162 for powering the various components. The power system 162 may include a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a charging system, power failure detection circuitry, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components related to the generation, management, and distribution of power in a portable device.

The device 100 may also include one or more optical sensors 164. FIG1A shows an optical sensor coupled to the optical sensor controller 158 in the I/O subsystem 106. The optical sensor 164 may include a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. The optical sensor 164 receives ambient light projected through one or more lenses and converts the light into data representing an image. In conjunction with the imaging module 143 (also referred to as a camera module), the optical sensor 164 can capture still images or video. In some embodiments, the optical sensor is located on the back of the device 100, opposite the touchscreen display 112 on the front of the device, so that the touchscreen display can be used as a viewfinder for still and/or video image acquisition. In some embodiments, the optical sensor is located on the front of the device, so that the user's image can be captured for video conferencing while viewing other video conference participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor in the device housing), so that a single optical sensor 164 can be used with the touchscreen display for both video conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact force sensors 165. Figure 1A shows contact force sensors coupled to force sensor controller 159 in I/O subsystem 106. Contact force sensors 165 optionally include one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of a contact on a touch-sensitive surface). Contact force sensors 165 receive contact force information (e.g., pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the back of device 100, opposite touch screen display 112 located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG1A shows a proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 may be coupled to input controller 160 in I/O subsystem 106. Proximity sensor 166 may be implemented as described in U.S. patent applications No. 11/241,839, “Proximity Detector In Handheld Device”; No. 11/240,788, “Proximity Detector In Handheld Device”; No. 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; No. 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and No. 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are incorporated herein by reference in their entireties. In some embodiments, when the multifunction device is near the user's ear (eg, when the user is on a phone call), the proximity sensor turns off and disables the touch screen 112.

Device 100 optionally also includes one or more tactile output generators 167. Figure 1A shows a tactile output generator coupled to a tactile feedback controller 161 in I/O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices (such as speakers or other audio components) and/or electromechanical devices that convert energy into linear motion (such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile outputs on the device)). Contact force sensor 165 receives tactile feedback generation instructions from tactile feedback module 133 and generates tactile output on device 100 that can be felt by a user of device 100. In some embodiments, at least one tactile output generator is collocated with or in proximity to a touch-sensitive surface (e.g., touch-sensitive display system 112), and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., in/out of the surface of device 100) or laterally (back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112 located on the front of device 100.

Device 100 may also include one or more accelerometers 168. FIG1A shows accelerometer 168 coupled to peripherals interface 118. Alternatively, accelerometer 168 may be coupled to input controller 160 in I/O subsystem 106. Accelerometer 168 may be implemented as disclosed in U.S. Patent Nos. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated herein by reference in their entireties. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on analysis of data received from one or more accelerometers. In addition to the accelerometer(s) 168 , the device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information regarding the position and orientation (e.g., portrait or landscape) of the device 100 .

In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact/motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a global positioning system (GPS) module (or instruction set) 135, and an application (or instruction set) 136. In addition, as shown in Figures 1A and 3, in some embodiments, memory 102 (Figure 1A) or memory 370 (Figure 3) stores a device/global internal state 157. The device/global internal state 157 includes one or more of the following: an active application state, indicating which applications (if any) are currently active; a display state, indicating what applications, views, and other information occupy various areas of the touch screen display 112; a sensor state, including information obtained from various sensors and input control devices 116 of the device; and position information related to the position and/or posture of the device.

The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

Communications module 128 facilitates communications with other devices over one or more external ports 124 and also includes various software components for processing data received through RF circuitry 108 and/or external ports 124. External ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are suitable for coupling directly to other devices or indirectly to other devices via a network (e.g., the Internet, a wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, similar to, and/or compatible with the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.

The contact/motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact/motion module 130 includes various software components for performing various operations related to the detection of contact, such as determining whether contact has occurred (e.g., detecting a finger-down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a proxy for force or pressure of the contact), determining whether there has been movement of the contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has ceased (e.g., detecting a finger-up event or contact break). The contact/motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact (represented by a sequence of contact data) optionally includes determining the rate (magnitude), velocity (magnitude and direction), and/or acceleration (change in magnitude and/or direction) of the contact. These operations optionally apply to a single contact (e.g., a one-finger contact) or multiple simultaneous contacts (e.g., "multi-touch"/multiple-finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.

In some embodiments, the contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator and are adjusted without changing the physical hardware of the device 100). For example, a mouse "click" threshold for a touchpad or touchscreen can be set to any of a wide range of predetermined thresholds without changing the touchpad or touchscreen display hardware. In addition, in some embodiments, a user of the device is provided with a software setting for adjusting one or more of the set of intensity thresholds (e.g., by utilizing a system-level click "intensity" parameter to adjust single and/or multiple intensity thresholds at once).

Contact/motion module 130 optionally detects gestures input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger down event followed by detecting a finger up (e.g., lift) event at the same location (or substantially the same location) as the finger down event (e.g., at an icon location). As another example, detecting a finger swipe gesture on the touch surface includes detecting a finger down event followed by detecting one or more finger drag events followed by detecting a finger up (lift) event.

The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including components for changing the visual effects (e.g., brightness, transparency, saturation, contrast, or other visual attributes) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including but not limited to: text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

In some embodiments, the graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes specifying the graphics to be displayed from an application or the like, along with coordinate data and other graphic attribute data, if necessary, and then generates screen image data for output to the display controller 156.

Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile output at one or more locations on the device in response to user interaction with device 100 .

Text input module 134 (which may be a component of graphics module 132) provides a soft keyboard for entering text into various applications (eg, contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).

The GPS module 135 determines the location of the device and provides this information for use by various applications (e.g., to the phone 138 for use in location-based dialing; to the camera 143 as picture/video metadata; and to applications that provide location-based services, such as weather widgets, local yellow pages widgets, and map/navigation widgets).

Application 136 may include the following modules (or instruction sets), or a subset or superset thereof:

Contacts module 137 (sometimes called an address book or contact list);

Telephone module 138;

Video conferencing module 139;

Email client module 140

Instant messaging (IM) module 141;

Exercise support module 142;

A camera module 143 for still and/or video images;

Image management module 144;

Video player module;

Music player module;

Browser module 147;

Calendar module 148;

Widget module 149, which may include one or more of the following: a weather widget 149-1, a stock widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, as well as a user-created widget 149-6; a widget creator module 150 for creating the user-created widget 149-6;

Search module 151;

Video and music player module 152, which combines the video player module and the music player module;

Memo module 153;

Map module 154; and/or

Online video module 155.

Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

In combination with the touch screen 112, display controller 156, touch/motion module 130, graphics module 132 and text input module 134, the contacts module 137 can be used to manage an address book or contact list (for example, stored in the application internal state 192 of the contacts module 137 in memory 102 or memory 370), including: adding (one or more) names to the address book; deleting (one or more) names from the address book; associating (one or more) phone numbers, (one or more) email addresses, (one or more) physical addresses or other information with a name; associating images with a name; categorizing and sorting names; providing phone numbers or email addresses to initiate and/or facilitate communications via telephone 138, video conferencing module 139, email 140 or IM 141, etc.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, phone module 138 can be used to enter a character sequence corresponding to a phone number, access one or more phone numbers in contact module 137, modify an already entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communication can use any of a variety of communication standards, protocols, and technologies.

In combination with the RF circuit device 108, the audio circuit device 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the controller of the optical sensor 158, the touch/motion module 130, the graphics module 132, the text input module 134, the contact module 137 and the telephone module 138, the video conferencing module 139 includes executable instructions for initiating, conducting and terminating a video conference between a user and one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch/motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with image management module 144, email client module 140 makes it easy to create and send emails with still or video images captured using camera module 143.

In conjunction with the RF circuitry 108, the touch screen 112, the display controller 156, the contact/motion module 130, the graphics module 132, and the text input module 134, the instant messaging module 141 includes executable instructions for entering a character sequence corresponding to an instant message, for modifying previously entered characters, for transmitting a corresponding instant message (e.g., using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for phone-based instant messaging, or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), for receiving instant messages, and for viewing received instant messages. In some embodiments, as supported by MMS and/or Enhanced Messaging Service (EMS), the transmitted and/or received instant messages may include graphics, photos, audio files, video files, and/or other attachments. As used herein, "instant messaging" refers to both phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages using XMPP, SIMPLE, or IMPS).

In combination with the RF circuit device 108, the touch screen 112, the display controller 156, the contact/motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154, and the music player module, the workout support module 142 includes executable instructions for creating workouts (e.g., with time, distance, and/or calorie burn goals); communicating with workout sensors (exercise equipment); receiving workout sensor data; calibrating sensors for monitoring a workout; selecting and playing music for a workout; and displaying, storing, and transmitting workout data.

In combination with the touch screen 112, the display controller 156, the optical sensor(s) 164, the optical sensor controller 158, the touch/motion module 130, the graphics module 132, and the image management module 144, the camera module 143 includes executable instructions for capturing still images or videos (including video streams) and storing them in the memory 102, modifying the characteristics of the still images or videos, or deleting the still images or videos from the memory 102.

In conjunction with touch screen 112, display controller 156, touch/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or manipulating, annotating, deleting, presenting (e.g., in a digital slide show or photo album), and storing still and/or video images.

In combination with the RF circuit device 108, the touch screen 112, the display controller 156, the touch/motion module 130, the graphics module 132 and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with user instructions (including searching, linking, receiving and displaying web pages or multiple parts of web pages and attachments and other files linked to the web pages).

In combination with the RF circuit device 108, the touch screen 112, the display controller 156, the touch/motion module 130, the graphics module 132, the text input module 134, the email client module 140 and the browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying and storing calendars and data associated with the calendar (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 is a small application that can be downloaded and used by a user (e.g., weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5), or a small application created by a user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., a Yahoo! widget).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch/motion module 130, graphics module 132, text input module 134, and browser module 147, widget creator module 150 may be used by a user to create widgets (e.g., convert a user-specified portion of a web page into a widget).

In combination with the touch screen 112, display controller 156, contact/motion module 130, graphics module 132 and text input module 134, the search module 151 includes executable instructions for searching the memory 102 for text, music, sound, images, video and/or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and play back recorded music and other sound files stored in one or more file formats (such as MP3 or AAC files), and includes executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch screen 112 or on a display connected externally via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player such as an iPod (trademark of Apple Inc.).

In conjunction with the touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the memo module 153 includes executable instructions for creating and managing memos, to-do lists, etc. according to user instructions.

In combination with the RF circuit device 108, the touch screen 112, the display controller 156, the touch/motion module 130, the graphics module 132, the text input module 134, the GPS module 135 and the browser module 147, the map module 154 can be used to receive, display, modify and store maps and data associated with the maps (e.g., driving directions; data about stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions that allow a user to access, browse, receive (e.g., by streaming and/or downloading), play back a particular online video (e.g., on the touch screen or on a display connected externally via external port 124), send an email with a link to a particular online video, and manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141, rather than email client module 140, is used to send a link to a particular online video. Additional descriptions of online video applications can be found in the following patent applications: U.S. Provisional Patent Application No. 60/936,562, filed on June 20, 2007, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," and U.S. Patent Application No. 11/968,067, filed on December 31, 2007, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," the contents of which are incorporated herein by reference in their entirety.

Each of the above modules and applications corresponds to an instruction set for performing one or more functions described above and the methods described in this application (e.g., computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) do not need to be implemented as separate software programs, processes, or modules, so various subsets of these modules can be combined or rearranged in various embodiments. For example, a video player module can be combined with a music player module into a single module (e.g., the video and music player module 152 of FIG. 1A ). In some embodiments, memory 102 can store a subset of the above modules and data structures. In addition, memory 102 can store other modules and data structures not described above.

In some embodiments, the device 100 is a device that is dedicated to performing operations of a predefined set of functions on the device through a touch screen and/or a touch pad. By using the touch screen and/or the touch pad as the primary input control device for operating the device 100, the number of physical input control devices (such as push buttons, dials, etc.) on the device 100 can be reduced.

The predefined set of functions performed exclusively via the touch screen and/or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 from any user interface displayed on the device 100 to a home screen, home screen, or root menu. In such embodiments, the "menu button" is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device rather than a touchpad.

FIG1B is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 (in FIG1A ) or memory 370 ( FIG3 ) includes an event classifier 170 (e.g., in operating system 126 ) and a corresponding application 136 - 1 (e.g., any of the aforementioned applications 137 - 151 , 155 , 380 - 390 ).

Event classifier 170 receives event information and determines application 136-1 and an application view 191 in application 136-1 to which the event information is delivered. Event classifier 170 includes an event monitor 171 and an event dispatcher module 174. In some embodiments, application 136-1 includes an application internal state 192 that indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global content state 157 is used by event classifier 170 to determine which applications are currently active, and application internal state 192 is used by event classifier 170 to determine the application view 191 to which the event information is delivered.

In some embodiments, the application internal state 192 includes additional information, such as one or more of the following: resume information to be used when the application 136-1 resumes execution, user interface state information indicating information that the application 136-1 is displaying or preparing to display, a state queue that enables the user to return to a previous state or view of the application 136-1, and a redo/undo queue of previous actions taken by the user.

Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or sensors such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). The information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 sends event information. In other embodiments, peripherals interface 118 sends event information only when a significant event occurs (e.g., receiving an input that exceeds a predetermined noise threshold and/or is longer than a predetermined duration).

In some embodiments, event classifier 170 also includes a hit view determination module 172 and/or an active event identifier determination module 173 .

Hit view determination module 172 provides software routines for determining where a sub-event has occurred in one or more views when touch-sensitive display 112 displays more than one view. A view consists of controls and other elements that a user can see on the display.

Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the respective application) in which a touch is detected can correspond to a programmatic level in the programmatic or view hierarchy of the application. For example, the lowest-level view in which a touch is detected can be referred to as a hit view, and the set of events recognized as correct input can be determined based at least in part on the hit view of the initial touch that initiated the touch-based gesture.

Hit view determination module 172 receives information about sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the lowest-level view in the hierarchy that should handle the sub-event as the hit view. In most cases, the hit view is the lowest-level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events that forms an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source that caused it to be identified as the hit view.

Active event recognizer determination module 173 determines which view or views in the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views, including the physical location of the sub-event, are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, views higher in the hierarchy will still remain as actively participating views.

Event dispatcher module 174 dispatches event information to an event recognizer (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores the event information in an event queue for retrieval by corresponding event receiver 182.

In some embodiments, operating system 126 includes event classifier 170. Alternatively, application 136-1 includes event classifier 170. In other embodiments, event classifier 170 is a separate module or part of another module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the user interface of the application. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more event recognizers 180 are part of a separate module (such as a user interface kit (not shown)), or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and/or event data 179 received from an event classifier 170. Event handler 190 can utilize or call data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more corresponding event handlers 190. Likewise, in some embodiments, one or more of the data updater 176 , the object updater 177 , and the GUI updater 178 are included in a corresponding application view 191 .

A corresponding event identifier 180 receives event information (e.g., event data 179) from event classifier 170 and identifies an event based on the event information. Event identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event identifier 180 also includes at least a subset of the following: metadata 183 and event delivery instructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event classifier 170. The event information includes information about a sub-event (e.g., a touch or touch movement). Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of a touch, the event information may also include the rate and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

Event comparator 184 compares event information with predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 include definitions of events (e.g., a predefined sequence of sub-events), such as event 1 (187-1), event 2 (187-2), and so on. In some embodiments, sub-events in event 187 include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, event 1 (187-1) is defined as a double tap on a displayed object. The double tap, for example, includes a first touch (touch start) of a predetermined phase on the displayed object, a first lift (touch end) of a predetermined phase on the displayed object, a second touch (touch start) of a predetermined phase on the displayed object, and a second lift (touch end) of a predetermined phase on the displayed object. In another example, event 2 (187-2) is defined as a drag on a displayed object. The drag, for example, includes a touch (or contact) of a predetermined phase on the displayed object, movement of the touch on the touch-sensitive display 112, and lift (touch end) of the touch. In some embodiments, the event also includes information for one or more associated event handlers 190 .

In some embodiments, event definition 187 includes definitions of events for corresponding user interface objects. In some embodiments, event comparator 184 performs a hit test to determine the user interface object associated with a sub-event. For example, in an application view in which three user interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects the event handler associated with the sub-event and object that triggered the hit test.

In some embodiments, the definition of the corresponding event (187) also includes a delay action that delays delivery of the event information until it has been determined whether the sequence of sub-events corresponds to the event type of the event identifier.

When a corresponding event recognizer 180 determines that a sub-event sequence does not match any event in event definition 186, the corresponding event recognizer 180 enters the event impossible, event failed, or event ended state, after which the corresponding event recognizer 180 ignores subsequent sub-events of the touch-based gesture. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

In some embodiments, corresponding event recognizers 180 include metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers may or can interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to different levels in the view or program hierarchy.

In some embodiments, a corresponding event recognizer 180 activates an event handler 190 associated with the event when one or more specific sub-events of the event are recognized. In some embodiments, a corresponding event recognizer 180 delivers event information associated with the event to event handler 190. Activating event handler 190 is distinct from sending (or delaying sending) the sub-events to the corresponding hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with a series of sub-events or an actively participating view. The event handler associated with the series of sub-events or the actively participating view receives the event information and executes a predetermined process.

In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates phone numbers used in contact module 137 or stores video files used in video player module 145. In some embodiments, object updater 177 creates and updates data used in application 136-1. For example, object updater 177 creates new user interface objects or updates the positions of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other embodiments, data updater 176, object updater 177, and GUI updater 178 are included in two or more software modules.

It should be understood that the foregoing discussion of event handling for user touches on a touch-sensitive display also applies to other forms of user input for operating a multifunction device 100 having an input device, where not all user input is initiated on the touch screen, for example, mouse movements and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holds; contact motions on a touchpad (such as taps, drags, scrolling, etc.); stylus input, movement of the device; voice commands; detected eye movements, biometric input; and/or any combination of the foregoing, optionally used as input corresponding to sub-events defining the event to be recognized.

FIG2 illustrates a portable multifunction device 100 with a touch screen 112 according to some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment, as well as other embodiments described below, a user can select one or more graphics by gesturing with the graphics (e.g., with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses (not drawn to scale in the figure)). In some embodiments, selection of the one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, from right to left, up and/or down), and/or rotation of a finger already in contact with the device 100 (from right to left, from left to right, up and/or down). In some implementations or circumstances, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture across an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

The device 100 may also include one or more physical buttons, such as a “home” or menu button 204. As previously described, the menu button 204 may be used to navigate to any application 136 in a collection of applications that may be executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch screen 112.

In some embodiments, device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on/off and locking the device, as well as volume adjustment buttons 208, a subscriber identity module (SIM) card slot 210, a headphone jack 212, and a docking/charging external port 124. Push button 206 is optionally used to turn the device on/off by pressing and holding the button for a predefined time interval; to lock the device by pressing and releasing the button before a predefined time interval has elapsed; and/or to unlock the device or initiate an unlocking process. In an alternative embodiment, device 100 also accepts voice input for activating or deactivating certain functions via microphone 113. Device 100 optionally also includes one or more contact force sensors 165 for detecting contact force on touch screen 112 and/or one or more tactile output generators 167 for generating tactile output for a user of device 100.

Fig. 3 is a block diagram of an exemplary multifunctional device with a display and a touch-sensitive surface according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system or a control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more networks or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. Communication bus 320 optionally includes a circuit device (sometimes referred to as a chipset) for interconnecting and controlling communication between system components. Device 300 includes an input/output (I/O) interface 330 containing a display 340 (which is typically a touch screen display). Input/output interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, a tactile output generator 357 for generating tactile output on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A ), and sensors 359 (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A ). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state storage devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 may optionally include one or more storage devices remote from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, those stored in memory 102 of portable multifunction device 100 ( FIG. 1 ). Furthermore, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, a word processing module 384, a website creation module 386, a disk authoring module 388, and/or a spreadsheet module 390, while memory 102 of portable multifunction device 100 ( FIG. 1A ) optionally does not store these modules.

Each element of the above-mentioned elements in Fig. 3 can be stored in one or more aforementioned memory devices.Each module in the above-mentioned modules corresponds to the instruction set for performing the functions described above.Above-mentioned modules or programs (e.g., instruction sets) do not need to be implemented as separate software programs, processes or modules, so the various subsets of these modules can be combined or otherwise rearranged in various embodiments.In certain embodiments, memory 370 can store a subset of the above-mentioned modules and data structures.In addition, memory 370 can store additional modules and data structures not described above.

Attention is now directed to embodiments of user interfaces that may be implemented on, for example, portable multifunction device 100 .

Figure 4A illustrates an exemplary user interface for an application menu on portable multifunction device 100 in accordance with some embodiments. A similar user interface may be implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

Signal strength indicators 402 for wireless communication(s), such as cellular and Wi-Fi signals;

Time 404;

Bluetooth indicator 405;

Battery status indicator 406;

Tray 408, with icons for frequently used applications such as:

o An icon 416 for the phone module 138, labeled "Phone," which optionally includes an indicator 414 of the number of missed calls or voicemail messages;

o An icon 418 for the email client module 140 , labeled “Mail,” which optionally includes an indicator 410 of the number of unread emails;

o Icon 420 for the browser module 147, labeled "Browser"; and

o Icon 422 for the video and music player module 152, also referred to as the iPod (trademark of Apple Inc.) module 152, labeled “iPod”; and

Icons for other applications, such as:

o Icon 424 for IM module 141, labeled "Messages";

o Icon 426 for calendar module 148, labeled "Calendar";

o Icon 42 for image management module 144, labeled "Photos";

o Icon 430 for camera module 143, labeled "Camera";

o Icon 432 for the online video module 155, labeled "Online Video";

o Icon 434 for the stock widget 149 - 2 , labeled “Stocks”;

o Icon 436 for the map module 154, labeled "Map";

o Icon 438 for the weather widget 149 - 1 , labeled “Weather”;

o Icon 440 for the alarm clock widget 149 - 4 , labeled “Clock”;

o Icon 442 for the exercise support module 142, labeled "Exercise Support";

o Icon 444 for the memo module 153, labeled "Memo";

o An icon 446 for a settings application or module, labeled “Settings,” which provides access to settings for the device 100 and its various applications 136 .

It should be understood that the icon labels illustrated in FIG4A are exemplary only. For example, icon 422 for video and music player module 152 may alternatively be labeled "Music" or "Music Player." Other labels may alternatively be used for individual application icons. In some embodiments, the label for a respective application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to the particular application icon.

4B illustrates an exemplary user interface on a device (e.g., device 300 of FIG. 3 ) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3 ) that is separate from a display 450 (e.g., touch screen display 112 ). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more sensors of sensors 357 ) for detecting intensity of contacts on touch-sensitive surface 451 and/or one or more tactile output generators 359 for generating tactile outputs to a user of device 300.

Although some of the following examples will be presented with respect to input on a touchscreen display 112 (where the touch-sensitive surface is combined with the display), in some embodiments, as shown in FIG4B , the device detects input on a touch-sensitive surface that is separate from the display. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG4B ) has a primary axis (e.g., 452 in FIG4B ) that corresponds to a primary axis (e.g., 453 in FIG4B ) on the display (e.g., 450). According to these embodiments, the device detects contacts (e.g., 460 and 462 in FIG4B ) with the touch-sensitive surface 451 at locations corresponding to corresponding locations on the display (e.g., 460 corresponds to 468 and 462 corresponds to 470 in FIG4B ). In this manner, when the touch-sensitive surface is separated from the display (e.g., 450 in FIG4B ) of the multifunction device, user input (e.g., contacts 460 and 462 and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG4B ) is used by the device to manipulate a user interface on the display of the multifunction device. It should be understood that similar methods may optionally be used for other user interfaces described herein.

In addition, although the following examples are primarily given with reference to finger input (e.g., finger contact, finger tap gesture, finger swipe gesture), it should be understood that in some embodiments, one or more finger inputs can be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of contact) followed by moving the cursor along the swipe path (e.g., instead of moving the contact). As another example, a tap gesture is optionally replaced by a mouse click when the cursor is at the location of the tap gesture (e.g., instead of detecting contact and then ceasing to detect the contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or that mice and finger contacts are optionally used simultaneously.

Figure 5A illustrates an exemplary personal electronic device 500. Device 500 includes a body 502. In some embodiments, device 500 may include some or all of the features described with respect to devices 100 and 300 (e.g., Figures 1A-4B). In some embodiments, device 500 has a touch-sensitive display screen 504, hereinafter referred to as a touch screen 504. Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) may have one or more intensity sensors for detecting the intensity of contact (e.g., touch) being applied. The one or more intensity sensors of the touch screen 504 (or touch-sensitive surface) may provide output data representing the intensity of the touch. The user interface of device 500 may respond to the touch based on the intensity of the touch, meaning that touches of different intensities may invoke different user interface operations on device 500.

For example, technology for detecting and processing touch intensity can be found in the following related applications: International Patent Application Serial No. PCT/US2013/040061, filed on May 8, 2013, entitled “Device, Method, and Graphical User Interface for Displaying UserInterface Objects Corresponding to an Application,” and International Patent Application Serial No. PCT/US2013/069483, filed on November 11, 2013, entitled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” each of which is incorporated herein by reference in its entirety.

In some embodiments, the device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508 (if included) can be physical. Examples of physical input mechanisms include push buttons and rotational mechanisms. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) can allow the device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, chains, pants, belts, shoes, handbags, backpacks, etc. These attachment mechanisms can allow the device 500 to be worn by the user.

FIG5B depicts an exemplary personal electronic device 500. In some embodiments, device 500 may include some or all of the components described with respect to FIG1A, FIG1B, and FIG3. Device 500 has a bus 512 that operatively couples an I/O portion 514 with one or more computer processors 516 and a memory 518. I/O portion 514 may be connected to a display 504, which may have a touch-sensitive component 522 and, optionally, touch intensity sensitivity 524. In addition, I/O portion 514 may be connected to a communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near-field communication (NFC), cellular, and/or other wireless communication technologies. Device 500 may include input mechanisms 506 and/or 508. For example, input mechanism 506 may be a rotatable input device or a depressible and rotatable input device. In some examples, input mechanism 508 may be a button.

In some examples, input mechanism 508 can be a microphone. Personal electronic device 500 can include various sensors, such as a GPS sensor 532, an accelerometer 534, an orientation sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and/or combinations thereof, all of which can be operatively connected to I/O portion 514.

The memory 518 of the personal electronic device 500 can be a non-transitory computer-readable storage medium for storing computer-executable instructions that, when executed by one or more computer processors 516, can, for example, cause the computer processor to perform the techniques described above, including processes 1000-1200 (Figures 10A-10C, Figures 11, and 12). Computer-executable instructions can also be stored and/or transmitted within any non-transitory computer-readable medium for use by or in conjunction with an instruction execution system, device, or apparatus, such as a computer-based system, a system containing a processor, or other system that can fetch instructions from and execute the instructions. For the purposes of this document, a "non-transitory computer-readable storage medium" can be any medium that can tangibly contain or store computer-executable instructions for use by or in conjunction with an instruction execution system, device, or apparatus. Non-transitory computer-readable storage media can include, but are not limited to, magnetic storage devices, optical storage devices, and/or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memory such as flash memory, solid-state drives, etc. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B , but may include other or additional components in a variety of configurations.

As used herein, the term "affordance" refers to a user-interactive graphical user interface object that can be displayed on a display screen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) can each constitute an affordance.

As used herein, the term "focus selector" refers to an input element that indicates the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B ) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface is adjusted based on the detected input. In implementations that include a touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4A ) that implements direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a "focus selector" such that when input (e.g., a press input by a contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted based on the detected input. In some implementations, focus is moved from one area of a user interface to another area of a user interface without corresponding movement of a cursor or contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another); in some implementations, a focus selector moves in accordance with the movement of focus between different areas of the user interface. Regardless of the specific form taken by the focus selector, the focus selector is generally a user interface element controlled by a user (or a contact on a touch screen display) to communicate the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user intended to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intended to activate the corresponding button (rather than other user interface elements shown on the device's display).

As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more contact intensities. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after detecting the contact, before detecting the lift of the contact, before or after detecting the start of movement of the contact, and/or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of the contact is optionally based on one or more of the following: a maximum value of the intensity of the contact, an average value of the intensity of the contact, a mean value of the intensity of the contact, the top 10% value of the intensity of the contact, the half-height value of the intensity of the contact, the value at 90% of the maximum value of the intensity of the contact, etc. In some embodiments, the duration of the contact is used to determine the characteristic intensity (e.g., when the characteristic intensity is an average value of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by the user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first threshold and does not exceed the second threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, the comparison between the characteristic intensity and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or abandon the corresponding operation), and is not used to determine whether to perform the first operation or the second operation.

In some embodiments, a portion of a gesture is identified for the purpose of determining characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact that transitions from a start position to an end position, with the intensity of the contact increasing at the point at the end position. In this example, the characteristic intensity of the contact at the end position may be based on only a portion of the continuous swipe contact rather than the entire swipe contact (e.g., only the portion of the swipe contact at the end position). In some embodiments, a smoothing algorithm may be applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm may optionally include one or more of: an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes and dips in the intensity of the swipe contact for the purpose of determining characteristic intensity.

The intensity of a contact on a touch-sensitive surface can be characterized relative to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from that typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, when a contact is detected having a characteristic intensity that is below the light press intensity threshold (e.g., and above a normal contact detection intensity threshold, where the contact will no longer be detected below the normal contact detection intensity threshold), the device will move the focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. In general, unless otherwise stated, these intensity thresholds are consistent across different sets of user interface diagrams.

An increase in the characteristic intensity of a contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in the characteristic intensity of a contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in the characteristic intensity of a contact from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. A decrease in the characteristic intensity of a contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting lift of the contact from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a corresponding press input, or in response to detecting a corresponding press input performed with a corresponding contact (or contacts), wherein the corresponding press input is detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting an increase in intensity of the corresponding contact above the press input intensity threshold (e.g., a "downward stroke" of the corresponding press input). In some embodiments, the press input includes an increase in intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in intensity of the contact below the press input intensity threshold, and in response to detecting a subsequent decrease in intensity of the corresponding contact below the press input intensity threshold (e.g., an "upward stroke" of the corresponding press input), the corresponding operation is performed.

In some embodiments, the device employs intensity hysteresis to avoid unexpected inputs, sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold that has a predefined relationship to a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold, and in response to detecting the subsequent decrease in intensity of the corresponding contact below the hysteresis intensity threshold (e.g., an "upward stroke" of the corresponding press input), a corresponding operation is performed. Similarly, in some embodiments, a press input is detected only when the device detects an increase in intensity of the contact from at or below the hysteresis intensity threshold to at or above the press input intensity threshold, and optionally a subsequent decrease in intensity of the contact to at or below the hysteresis intensity, and in response to detecting the press input (e.g., an increase in intensity of the contact or a decrease in intensity of the contact, depending on the circumstances), a corresponding operation is performed. For ease of explanation, descriptions of operations performed in response to a press associated with a press input intensity threshold or in response to a gesture that includes a press input are optionally triggered in response to detecting any of: the intensity of the contact increasing above the press input intensity threshold, the intensity of the contact increasing from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, the intensity of the contact decreasing below the press input intensity threshold, and/or the intensity of the contact decreasing below a hysteresis intensity threshold that corresponds to the press input intensity threshold. Furthermore, in examples where operations are described as being performed in response to detecting the intensity of the contact decreasing below the press input intensity threshold, the operations are optionally performed in response to detecting the intensity of the contact decreasing below a hysteresis intensity threshold that corresponds to and is below the press input intensity threshold.

As used herein, an "installed application" refers to software that has been downloaded to an electronic device (e.g., device 100, 300, and/or 500) and is ready to be launched (e.g., become open) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installer that extracts program portions from a download package and integrates the extracted portions with the operating system of the computer system.

As used herein, the term "open application" or "executing application" refers to a software application that has retained state information (e.g., as part of device/global internal state 157/application internal state 192). An open or executing application can be any of the following types of applications:

Active applications, which are currently displayed on the display of the device on which the application is being used;

Background applications (or background processes), which are not currently displayed, but for which one or more processes are being processed by one or more processors; and

• A suspended or dormant application that is not running, but has state information stored in memory (volatile and non-volatile, respectively) that can be used to resume execution of the application.

As used herein, the term "closed application" refers to a software application that does not retain state information (e.g., the state information for a closed application is not stored in the device's memory). Thus, closing an application includes stopping and/or removing the application process for the application and removing the application's state information from the device's memory. Typically, opening a second application within a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application. As used herein, "launching" an application refers to opening a closed application so that it becomes an active, open application.

Attention now turns to a user interface ("UI") and associated processes that may be implemented on a multifunction device with a display and a touch-sensitive surface, such as devices 100, 300, and/or 500 (FIGS. 1, 3, and 5), to provide electronic touch communication functionality. One or more of the techniques described below may be referred to as "electronic touch" communication.

1. Exemplary Electronic Touch Communication

6A-6D depict exemplary electronic touch communications between users of computing devices 600 and 699. In some embodiments, each of devices 600 and 699 is device 100, 300, or 500 (FIGS. 1, 3, and 5). For clarity, the top portion of the illustrations in FIG6A-6C corresponds to a user interface displayed on device 600, and the bottom portion of the illustrations corresponds to a user interface displayed on device 699.

As shown, device 600 displays a user interface 602 having multiple icons for launching various modules on the device, including icon 604. Icon 604 can correspond to an alarm clock application, for example, which means that when the icon is selected (e.g., touched), device 600 launches the corresponding alarm clock application. Device 600 also has input mechanism 606. In some embodiments, input mechanism 606 is a push button.

When device 600 detects activation (e.g., pressing) of button 606, device 600 displays phonebook contacts user interface (UI) 610. For example, phonebook contacts UI 610 may have affordances representing the user's friends and family. The contacts represented in phonebook contacts UI 610 are obtained from application data accessible to device 600, such as data associated with a phone or calendar application. Such data may be stored locally on the device, remotely on a companion's cell phone, and/or remotely in the "cloud."

Phonebook contacts UI 610 can be scrolled and/or zoomed to reveal additional affordances representing phonebook contacts. For example, a swipe input can be used to scroll phonebook contacts UI 610, and a pinch/unpinch input can be used to zoom phonebook contacts UI 610. In some embodiments, device 600 has a rotatable input mechanism, and movement of the rotatable input mechanism causes phonebook contacts UI 610 to zoom (or scroll). In some embodiments, the contacts represented on phonebook contacts UI 610 are a subset of the full set of phonebook contacts accessible to device 600. The displayed subset can represent contacts that have been previously designated by the user, for example, as the user's "favorites," or a user- or system-defined "whitelist" or "greylist."

In response to selection of affordance 611, device 600 displays a contact information user interface 616 that provides additional information about the selected phonebook contact. In the illustrated example, the phonebook contact's name 617 and image 620 are displayed. In an alternative embodiment, when an image of the contact is not available, a system-generated monogram can be provided using the contact's name initials. In addition, contact information UI 616 has affordance 618 for initiating a call (audio and/or video) and affordance 619 for initiating a message to phonebook contact 617 (e.g., a short message via services such as SMS and MMS, a text message via services such as those provided by Apple Inc. of Cupertino, California).

In response to user input detected while displaying contact information UI 616, device 600 transitions to displaying drawing area 630 (also referred to as a canvas). Drawing area 630 provides an area for touch-based drawing. In some embodiments, the user input for invoking drawing area 630 is a touch on phonebook contact name 617 or contact image 620. In some embodiments, the user input required to invoke drawing area 630 is a touch on contact information UI 616 away from affordances 618 and 619.

6B , device 600 detects user input 632 in drawing area 630. User input 632 includes a swipe motion resembling a smiley face. Device 600 displays a visual representation 634 corresponding to user input 632. Visual representation 634 gradually fades after being displayed for a certain amount of time, as indicated by dashed line 636.

Device 600 sends data representing input 632 to device 699. In some embodiments, device 600 sends the data after a predetermined amount of time has elapsed since input 632. When input 632 includes multiple swipes, device 600 may wait until a predetermined amount of time has elapsed after the last swipe before sending the data. In some embodiments, the sending of the data is coordinated with the fading of visual representation 634. In this way, the fading of visual representation 634 also helps to notify the user that a touch communication has been sent to device 699.

At an external device 699 associated with the phonebook contact 617, incoming data is received and an output is provided to notify the user of the incoming communication. In some embodiments, the device 699 displays an alert 638 indicating the incoming communication. In some embodiments, the device 699 initially generates an audible and/or tactile output, and upon detecting movement of the device (e.g., such as the user lifting or picking up the device), the alert 638 becomes displayed. In some embodiments, the device 699 generates an audible and/or tactile output while displaying the alert 638. The use of tactile output is particularly effective in this context due to the close proximity between the wearable electronic device 699 and its user—it is likely that the user will feel the tactile vibration.

While viewing the reminder 638, the user can accept or decline to view the incoming communication. In some embodiments, a tap input on the reminder 638, or an input associated with the user looking at the reminder 638 for a duration exceeding a threshold duration (e.g., an accelerometer input or a camera input), indicates acceptance. Upon acceptance, the device 699 displays a visual representation of the received communication. In some embodiments, upon accepting to view the communication, the device 699 launches the corresponding electronic touch communication application and displays a drawing area for showing the incoming drawing. In some embodiments, upon accepting to view the communication, the device 699 displays the communication without additionally launching the electronic touch communication application. In some embodiments, a swipe (e.g., up or down) on the reminder 638 indicates to dismiss, and in response, the device 699 does not display the incoming communication.

Techniques for determining when a device, such as device 699, is raised or picked up to a viewing position are described in co-pending U.S. Provisional Patent Application Serial No. 62/026,532, entitled “Raise Gesture Detection in a Device,” filed on July 18, 2014. Techniques for determining whether a user has looked at an alert for a duration exceeding a threshold are described in co-pending U.S. Provisional Patent Application Serial No. 62/026,532, entitled “REDUCED-SIZE INTERFACES FOR MANAGING ALERTS,” filed on September 2, 2014, naming Lawrence Yang et al. as inventors. The contents of these applications are incorporated herein by reference in their entirety.

In the illustrated example, device 699 detects user acceptance to view the communication and, in response, launches the electronic touch communication application to display a drawing area 640. Drawing area 640 has a visual representation 642 of touch input 632. Turning to FIG6C , visual representation 642 fades away after being displayed for some threshold duration, as depicted by dashed line 644.

When displaying drawing area 640, device 699 can detect user input 650 with a swipe that resembles a smiley face. In response, device 699 displays a visual representation 654 of the detected input 650. Turning to Figure 6D, after a period of time, device 699 sends data to device 600 notifying device 600 of the detected input 650. Device 699 also fades out visual representation 654 (as indicated by dotted line 656). Since device 600 has already displayed drawing area 630, when data representing input 650 is received from device 699, device 650 displays a visual representation 660 (e.g., a smiley face) of input 650. In this way, users of devices 600 and 699 can communicate with each other using touch-based electronic communication.

In some embodiments, the displayed visual representation of the stroke is removed by an on-screen animation that fades out the displayed visual representation. In some embodiments, the fade occurs from one end of the visual representation to the other, which corresponds to the beginning and end of the represented stroke. For example, the visual representation 660 (similar to a smiley face) can fade from the left eye to the right eye and to the mouth, as drawn in that order.

In some embodiments, the dynamics of the swipe input are reflected in its visual representation. For example, if the initial swipe movement in input 650 is fast but the subsequent movement in swipe input 650 is slow, then as device 600 renders visual representation 660 (and as device 699 renders visual representation 654), the stroke is first displayed quickly and then slowly toward the end, consistent with the dynamics information indicating the manner in which the stroke was drawn. As another example, during the display of visual representations 654 and 660, jitter in the movement of swipe input 650 is also indicated. Dynamics information can also be included in the data sent between devices 600 and 699.

In some embodiments, as the visual representation of the swipe input is displayed on the screen, the pauses between portions of the swipe input are reflected. For example, if the eyes of the smiley face of swipe input 650 are drawn with intermediate pauses, the eyes are drawn with the same amount of intermediate pauses (or, proportional amounts of pauses) as they are displayed on devices 600 and 699.

In some embodiments, the drawing area includes a color selection mechanism for selecting a color to use in displaying the visual representation of the swipe input. FIG6E illustrates an exemplary color selection mechanism, referred to as a color picker. As shown, device 600 is displaying drawing area 670 with color picker affordance 672. Although not shown, color picker affordance 672 is displayed in the current color, meaning that strokes drawn by the user of device 600 are displayed in the color of affordance 672 in both device 600 and device 699.

A user can select color picker affordance 672 to display color selection user interface 680. Color selection UI 680 has affordances representing previously (e.g., most recently) used colors. The user can select one of the displayed affordances to select the represented color as the current drawing color. Color selection UI 680 can include affordance 682 for invoking a color palette. In response to the user selection of affordance 682, device 600 displays a color palette user interface 690 that provides a spectrum of colors for the user to select. The user can select a portion of color palette 692 to select the corresponding color as the current drawing color.

In some embodiments, the device 600 has more than one palette user interface. For example, palettes can be grouped for presentation via additional palette user interfaces. As shown in FIG6E , the palette user interface 690 can have a paging indicator 694 for indicating the number of pages of available colors and for indicating the order of the current page within the set of pages. In the illustrated example, when displaying UI 690, in response to a swipe input in a first direction or a second direction (e.g., a horizontal swipe), the device 600 displays an additional palette user interface 696.

The order of colors on the page can be based on the frequency of use of the colors, the recency of use of the colors, or a combination of the two. The user can select a portion of the color palette 698 to select the corresponding color as the current drawing color. When a color is selected from the color palette UI, the device 600 returns to the drawing area 670. The color picker affordance 672 is updated to reflect the currently selected color.

Returning temporarily to Figure 6B-6D, in some embodiments, color picker affordances provide additional user interface functionality. As depicted in Figure 6C, device 699 sometimes displays color picker affordances 646 in drawing area 640, but hides color picker affordances 646 at other times. For example, in some embodiments, when displaying incoming communication (e.g., visual representation 642), device 699 does not illustrate color picker affordances. On the contrary, after visual representation 642 has gradually disappeared (as illustrated via dotted line 644), color picker affordances 646 are illustrated. In these embodiments, the presentation of the color picker affordance in the drawing area signals the user who is receiving touch input. Once again, reiterate, in these embodiments, when displaying incoming communication (e.g., visual representation 642), device temporarily stops receiving drawing input so that incoming communication can be displayed uninterruptedly. At some point, the color picker affordance (e.g., 646) is hidden to indicate that drawing input is being ignored, at least for the displayed representation in the drawing area (e.g., 640).

As another example, in some embodiments, while a user is currently drawing, incoming communications are queued for display after the current drawing is sent. In these embodiments, after the drawing is sent and the queued drawing is displayed, the user cannot draw their own drawings during this time. At some times, the color picker affordance (e.g., 646) is hidden to indicate that drawing input is being ignored, at least for the displayed representation in the drawing area (e.g., 640).

2. Additional Exemplary Communication Technologies

7A-7E illustrate additional exemplary touch communication techniques between users of electronic devices 700 and 799. In some embodiments, devices 700 and 799 are devices 100, 300, and/or 500 (FIGS. 1, 3, and 5).

Attention now turns to how device 700 converts discrete taps on its touch screen into electronic touch communications. In FIG7A , devices 700 and 799 are engaged in a communication session. Device 700 receives user input 712 at position 714 in drawing area 710. Data representing user input 712 at position 714 is sent by device 700 to device 799. Upon receiving this data, device 799 displays a visual representation 722 of the input in drawing area 720. Device 799 draws the visual representation on the screen at a position corresponding to position 714. Following input 712, device 700 may receive additional user input 716 at a different position 718. Data representing user input 716 at position 718 is sent by device 700 to device 799. Upon receiving this data, device 799 displays a visual representation 724 of input 716. As before, the on-screen position of visual representation 724 corresponds to position 718 of touch input 716.

Detection and display of touch contacts such as touch contacts 712 and 716 (e.g., drawing strokes, single-finger taps, multi-finger taps) can be implemented by event classifier 170, event recognizer 180, and event handler 190 (Figure 1B). Event monitor 171 in event classifier 170 detects contacts on touch-sensitive surface display 112, and event dispatcher module 174 delivers event information to application 136-1. A corresponding event recognizer 180 of application 136-1 compares the event information with a corresponding event definition 186 and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as a single-finger contact, a multi-finger touch contact, or a swipe. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 can utilize or call data updater 176 or object updater 177 to update application internal state 192. In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application.

In some embodiments, visual representation 722 is displayed for the duration of touch input 714, meaning that visual representation 722 remains displayed until touch input 714 is released. In some embodiments, visual representation 722 is displayed for a duration, meaning that visual representation 722 is removed from display after visual representation 722 has been displayed for a duration, regardless of whether touch input 714 has been released. In some embodiments, visual representation 722 is removed from the display by fading out.

While visual representation 722 can be any on-screen graphical output, such as an image, an animated image, a line drawing, etc., it should be noted that visual representation 722 represents a touch input (that has been received on an external electronic device). In the context of visual representation 722, "representation" means that the visual information communicates at least some information about the touch input. Examples of information that can be communicated include the location of the touch, duration, intensity, contact size of the touch, and the number of touch objects (e.g., fingers) that make up the touch. Therefore, the following exemplary visual representations of touch are representative:

An image located at a position corresponding to the position of the detected touch;

An image displayed for a duration corresponding to the duration of the detected touch;

An image sized according to the size of the touch contact (e.g., an oval); or

A color scheme (e.g., a heat map) corresponding to the intensity of the detected touch;

However, in contrast to this, since some touch input is detected, it goes without saying that a simply displayed general image should not be considered representative even if its display is caused by the touch input.

In some embodiments, visual representation 722 is circular, elliptical, or oval. The size of visual representation 722 can indicate the size of the contact of touch input 714, such as the size of the user's finger. In some embodiments, visual representation 722 includes multiple circles, ellipses, or ovals. The shapes can be displayed concentrically. When visual representation 722 includes multiple geometric shapes, the number of shapes can provide a visual representation that suggests or corresponds to the intensity of the contact. Similarly, when visual representation 722 includes multiple shapes, as visual representation 722 exits the screen display, the shapes can gradually fade out, similar to ripples in water, which provides an indication of time.

In some embodiments, the touch input required to cause display of visual representations 722 and 724 on device 799 (e.g., 712 and 716) is a single-finger tap, meaning that a multi-finger touch on device 700 will not produce the same visual representation on device 799, and a single-finger swipe on device 700 will not produce the same visual representation. In some embodiments, the display of visual representations 722 and 724 is accompanied by audible and/or tactile output.

In certain embodiments, device 799 can display visual representation 722 and/or 724, regardless of whether it is currently displaying a drawing area. That is, even if device 799 does not actively run an electronic touch communication application, device 799 can still be able to display a visual representation. On the contrary, device 799 can simply start vibration and/or display visual representation 722 and/or 724 in response to the incoming data about single-finger tapping 712 and/or 716. In certain embodiments, the display of the visual representation is accompanied by tactile output. In certain embodiments, tactile output is first provided, and as determined by input (such as, accelerometer input or camera input associated with a user looking at the device), after the user has moved the device to the viewing position, the display of the visual representation occurs.

Attention now turns to how device 700 converts repeated, discontinuous taps into electronic touch communications. In FIG7B , device 700 is displaying phonebook contacts user interface 730, which in some embodiments is contacts user interface 610 ( FIG6A ). Phonebook contacts UI 730 has affordances 731-734 representing phonebook contacts. When device 700 receives user input 736 as a double tap touch input, device 700 sends data corresponding to the detected double tap to device 799. In response, device 799 transitions from an inactive state to a display of reminder 740, indicating that the user of device 700 has sent a communication. In some embodiments, reminder 740 is accompanied by an audible and/or tactile output. The audible and/or tactile output can correspond to the number of double taps detected by device 700. For example, device 799 can generate discontinuous (i.e., different) vibrations in response to each double tap detected at device 700.

Attention now turns to how device 700 converts sustained touch contact on its touch screen into electronic touch communication. In FIG7C , the device detects user input 752, which is a two-finger touch contact in drawing area 710. In response, device 700 sends data representing the multi-finger input to device 799. Upon receiving this data, device 799 displays image 754 on drawing area 740. In some embodiments, image 754 is a heart-shaped image. Device 799 continues to display image 754 until two-finger touch 752 is released from device 700.

Detection and display of touch contacts such as touch contact 752 (e.g., drawing a stroke, a single-finger tap, a multi-finger tap) can be implemented by event classifier 170, event recognizer 180, and event handler 190 (Figure 1B). Event monitor 171 in event classifier 170 detects contacts on touch-sensitive surface display 112, and event dispatcher module 174 delivers event information to application 136-1. A corresponding event recognizer 180 of application 136-1 compares the event information with a corresponding event definition 186 and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as a single-finger contact, a multi-finger touch contact, or a swipe. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 can utilize or call data updater 176 or object updater 177 to update application internal state 192. In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application.

In some embodiments, as shown in Figure 7C, image 754 pulsates so that its size changes over time. In some embodiments, the pulsation of image 754 is accompanied by tactile and/or audio from device 799. In some embodiments, device 700 has a galvanic skin response (GSR) sensor that senses the heart rate of its user and sends heart rate information to device 799 so that device 799 can pulsate image 754 in accordance with detected biometric information. The pulsation of image 754 can also be accompanied by audible and tactile output. For example, device 799 can vibrate in synchronization with each visual pulse.

In some embodiments, device 799 can display image 754 regardless of whether it is currently displaying a drawing area. That is, even if device 799 is not actively running an electronic touch communication application, device 799 can still be able to display image 754. Instead, device 799 can simply begin vibrating and/or displaying image 754 in response to incoming data about multi-finger taps 752. In some embodiments, the display of the image is accompanied by a tactile output. In some embodiments, the tactile output is first provided, and as determined by an input (such as an accelerometer input or a camera input associated with a user looking at the device), the image display appears after the user has moved the device to a viewing position.

Attention now turns to how device 700 accommodates verbal input during an electronic touch communication session. In FIG. 7D , device 700 is displaying drawing area 710 while device 799 is displaying drawing area 720. Drawing areas 710 and 720 have visual representations 762 and 764 of brush strokes representing earlier communications in the ongoing electronic touch communication session. While displaying drawing area 710, device 700 detects activation of input mechanism 772. In some embodiments, the input mechanism is a mechanical button. For the duration of activation, device 700 records input provided to the device. In other words, the user of device 700 can provide a verbal message that is subsequently recorded. Upon releasing input mechanism 772, device 700 sends an audio recording to device 799, where the recording is played back. As depicted in FIG. 7D , while device 700 is recording, device 799 continues to display drawing area 720 so that the user of device 799 can continue to participate in the communication session.

Attention now turns to alternative methods for how device 700 can allow for contact between participants in an electronic touch communication session. Figure 7E illustrates a contextual user interface 790, which, in some embodiments, can be invoked from drawing area 710. As shown, device 700 is displaying drawing area 710 and receiving touch input 792. Touch input 792 has a high characteristic contact intensity, meaning it is a deep contact. In some embodiments, a contact with a characteristic intensity above a threshold intensity is considered a high-intensity contact. In response to detecting a high-intensity touch 792 while displaying drawing area 710, device 700 displays contextual user interface 790 with an affordance for initiating other forms of communication with (one or more) participants in the electronic touch communication session (e.g., contact A in Figure 6A). It should be noted that, as discussed above with reference to Figures 7A-7C, touches below the threshold are interpreted as single-finger contacts (such as taps and swipes) and/or multi-finger touches.

For example, contextual user interface 790 has affordance 794 that, when selected, initiates a phone call (audio and/or video) with contact A. Contextual user interface 790 also has affordance 796 that, when selected, initiates a draft email to contact A. Contextual user interface 790 also has affordance 798 that, when selected, initiates a message (e.g., a short message via services such as SMS and MMS, a text message via services such as those provided by Apple Inc. of Cupertino, California) to contact A.

3. Alternative Communication Models

Attention now turns to other models of electronic touch communication between devices used in some embodiments with reference to Figures 8 and 9A-9B.

In some embodiments, electronic touch communication occurs after a conversation initiated by one participant and accepted by the receiving participant. This aspect is discussed with reference to FIG8 . In FIG8 , device 800 (in some embodiments, device 100 , 300 , or 500 ( FIG1 , FIG3 , and FIG5 )) is displaying phonebook contacts user interface 810 . In response to a user selecting one of the displayed affordances 811 - 814 , device 800 displays contact information user interface 820 , represented in this case by affordance 811 for contact “A”. The user continues to invite contact “A” to the communication session by touching user interface 820 . In response, device 800 sends a request to device 899 to invite contact “A” to the communication and displays user interface 830 with an indication 834 indicating that contact “A” is invited. Simultaneously, device 899 associated with contact “A” transitions from its inactive state to displaying an alert 840 , which shows that the user of device 800 (in this case, contact “Z”) is requesting electronic touch communication.

In some embodiments, the user of device 800 can cancel the invitation by navigating away from user interface 830 (such as, by activating another input mechanism on the device by swiping input or). In some embodiments, the user of device 899 can accept the pending invitation by touching reminder 840. The user can also reject the invitation by swiping away reminder 840 (for example, in an upward or downward direction). If the request is accepted, devices 800 and 899 continue to display drawing areas 850 and 860 respectively, and thereby establish a two-way communication session. Therefore, as used herein, after (i) one user sends an invitation for communication to another user and (ii) the received user accepts, a two-way communication "session" is established. If the invitation is rejected (not shown), device 800 returns to contact information user interface 820 and identification 899 returns to its previous (inactive) state.

Attention now turns to the embodiment with reference to Figures 9A-9B, in which electronic touch communication can collaboratively participate in a communication session. In Figure 9, device 900 (in some embodiments, device 100, 300, or 500 (Figures 1, 3, and 5)) is displaying a drawing area 910. Device 999 (in some embodiments, device 100, 300, or 500 (Figures 1, 3, and 5)) is displaying a drawing area 920. As shown, device 900 detects a swipe input 912, which represents a downward stroke 914 on drawing area 910. In response, device 900 displays a visual representation 916 of the detected stroke. Visual representation 916 can have the appearance of a brush stroke. Simultaneously, device 900 sends data representing stroke 914 (e.g., swipe input 912) to device 999. Upon receiving this information, device 999 displays a visual representation 922 of the stroke in its drawing area 920.

Two users can continue drawing. As shown, device 900 detects additional swipe input 926 representing strokes 928, while device 999 detects additional swipe input 930 representing strokes 932. Device 900 displays visual representation 936 of swipe input 926, and recognition 999 displays visual representation 940 of swipe input 930. Data representing both strokes 928 (swipe input 926) and strokes 932 (swipe input 930) are exchanged by the devices, which means that device 900 sends data representing strokes 928 (e.g., swipe input 926) to device 999, and device 999 sends data representing strokes 932 (e.g., swipe input 930) to device 900. After this exchange of information, the two devices display visual representations corresponding to the received information. In the case of device 900, in addition to visual representations 916 and 936, visual representation 946 is also displayed. In device 999, in addition to visual representations 922 and 940, visual representation 942 is also displayed. In some embodiments, the displayed visual representation has the appearance of brush strokes. As can be seen, in this way, users of devices 900 and 999 can mutually participate in a drawing session, particularly the drawing of a smiley face.

In order to make room for drawing areas 640 and 642 for additional drawings, in some embodiments, the displayed visual representations are removed after a given duration. The duration can be predetermined, for example, 1 second, 2 seconds, or 3 seconds. As shown in FIG. 9B , since visual representations 916 and 930 are caused by earlier user input, visual representations 916 and 930 are removed first. Subsequently, visual representations 936 and 946, as well as 942 and 940, are removed from the drawing area because they represent later user input.

It is very likely for a user to miss an incoming electronic touch communication (e.g., a power outage or no network connection). It is also possible for a user to ignore the tactile and/or visual output associated with the incoming communication. In some embodiments, device 900 displays an indicator of the missed communication that identifies the missed communication. This aspect is discussed in conjunction with Figure 9C. Figure 9C depicts phone book contacts user interface 990 (in some embodiments, phone book contacts user interface 610 (Figure 6A)). Phone book contacts UI 990 includes multiple affordances representing phone book contacts, including affordance 992 representing contact "D". Indicator 994 is displayed adjacent to affordance 992 (meaning that indicator 994 is closest to affordance 992 among all displayed affordances). Indicator 994 indicates to the user of device 900 that an incoming electronic touch communication from contact "D" has been missed. Optionally, the visual appearance of indicator 994 conveys additional information about the missed electronic touch communication. For example, indicator 994 can have a particular shape to indicate a missed reminder (reminder 638, Figure 6A), a missed request for a reminder (reminder 840, Figure 8), a missed single tap (Figure 7A), a missed double tap (Figure 7B), a missed multi-touch (Figure 7C), etc. As another example, the size of indicator 904 can reflect the number of missed communications. In some embodiments, multiple indicators can be displayed adjacent to a contact affordance to indicate that multiple types of communications have been missed.

In some embodiments, it is possible for phonebook contacts user interface 990 to display information about parties in electronic touch communications that are not currently registered as contacts with device 900. For example, phonebook contacts UI 990 may show phone numbers of people not previously known to device 990. In this example, phonebook contacts UI 990 may provide an add affordance for registering the previously unknown person as a contact.

In some embodiments, phonebook contacts user interface 990 is configured to display a subset of user-specified and/or system-defined contacts. In these embodiments, it is possible for phonebook contacts user interface 990 to display information about parties to an electronic touch communication that are not user-specified or system-defined contacts. For example, device 990 may have recently received an incoming communication from a user's frequent contact (not one of the user's favorite contacts). In this example, phonebook contacts UI 990 may provide an add affordance for designating the contact as a favorite contact. As another example, device 990 may have recently received an incoming communication from a person previously unknown to device 990. In this example, phonebook contacts UI 990 may provide an add affordance for registering the previously unknown person as a contact (and optionally designating the newly added contact as a user favorite).

4. Exemplary Electronic Touch Communication Process

Attention may now be implemented on devices 100, 300, and/or 500 (FIGS. 1, 3, 5) to perform the processes of the techniques described above with reference to FIGs. 6A-6E, 7A-7E, 8, and 9A-9C.

Figures 10A-10C depict a flowchart illustrating a process 1000 for electronic touch communication. In various embodiments, process 1000 can be performed by an electronic device, such as device 100, 300, and/or 500 (Figures 1, 3, and 5). At block 1002, multiple affordances representing contacts are displayed. The display can be triggered by user input. Optionally, the contacts represented can be a user-specified subset of available phone book contacts, such as the user's "favorites" contacts, or a system-defined "white list" or "grey list." An exemplary display of affordances representing contacts is the user interface 610 depicted in Figure 6A. At block 1004, the device detects a user selection of the displayed affordance and, in response, displays contact information identifying the selected contact. The information can include the contact's name, image, number, etc. Figure 6A provides an exemplary contact information user interface 616.

At block 1006, in response to user selection of the displayed affordance, a canvas such as drawing area 630 ( FIG. 6A ) is displayed. In some embodiments, an invitation is optionally sent to the selected contact or an electronic device associated with the selected contact, inviting the contact to electronic touch communication. In some embodiments, the device optionally waits for acceptance of the invitation before displaying the drawing area.

While the drawing area is displayed, at block 1008, a user input in the form of a swipe is detected. Upon detecting the user input, the process continues to decision block 1010, where a determination is made as to whether the input is a single-finger or multi-finger touch input. If the input is a multi-finger touch, the process continues to 1012, where the device transmits data representing the multi-finger touch to an external device. The transmitted data provides instructions to the external device for generating an image, such as image 754 in FIG. 7C . If the input is a single-finger touch, the process continues to decision block 1014, where a determination is made as to whether the single-finger input is a swipe or a tap. If the single-finger touch input is a tap, the process continues to block 1016, where data representing the single-finger tap is transmitted to the external device. The transmitted data causes a visual representation (such as visual representation 722 in FIG. 7A ) to be generated on the external device. The transmitted data can thus have the effect of triggering the display of individual visual representations on the external device.

If the single-finger input is a swipe, the process continues to block 1018, where the device displays a visual representation of the swipe input, such as one of the eyes in the smiling face represented by visual representation 634 in Figure 6B. At block 1020, a determination is made as to whether a threshold amount of time has passed since the last detected swipe. If the threshold amount of time has passed, the process continues to block 1022, where the device sends data indicating the received swipe input(s) to the external device. The transmitted data causes a visual representation, such as visual representation 642 (Figure 6B), to be generated on the external device. If the threshold amount of time has not passed, the process continues to block 1024, where additional swipes can be detected in the drawing area. After block 1024, the process returns to block 1018 to cause any additional received inputs to be displayed on the screen. The operations of blocks 1018, 1020, and 1024 may be repeated as needed until there is some end to the input, e.g., the user has finished drawing, as indicated by a cessation of drawing input exceeding a threshold duration. When this occurs, the process continues to block 1022, where the device transmits data indicating the received swipe input to the external device. The transmitted data may thus have the effect of triggering the display of various visual representations on the external device.

FIG11 depicts a flow diagram illustrating a process 1100 for electronic touch communication. In various embodiments, process 1100 can be performed by an electronic device, such as devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). At block 1102, data corresponding to an input detected by an external device is received at the electronic device performing process 1100. The received data can represent an incoming electronic touch communication. In response to receiving the data, the electronic device generates a tactile output. At block 1106, a determination is made as to whether a user input is received within a predetermined time threshold after the tactile output is emitted.

If the user provides input within the time threshold, the process continues to block 1108 where a notification regarding the incoming data is displayed (e.g., reminder 638 in FIG. 6A , reminder 840 in FIG. 8 ). At block 1100 , user input is received on the displayed reminder, and in response, the electronic device launches an appropriate application for electronic touch communication and displays a visual representation of the incoming data.

In an alternative embodiment (not shown in FIG. 11 ), at block 1110 , in response to user input while displaying the reminder, the electronic device displays a visual representation of the incoming data without opening an additional application. In this alternative embodiment, the user will need to take additional steps to initiate the appropriate electronic touch communication before displaying the drawing canvas for the electronic touch communication with the sender. However, by bypassing the opening of the application, the electronic device may be able to present the received information more quickly, which may be useful in situations where the recipient is only able to glance at the incoming communication briefly.

If the user does not provide input within the time threshold, the process continues to block 1112, where the electronic device returns to its previous process (or inactive state). At block 1114, at a later time, the electronic device displays an indication of the missed incoming communication. The indication can be the indicator 994 depicted in Figure 9C.

Figure 12 depicts a flowchart illustrating a process 1200 for electronic touch communication. In various embodiments, process 1200 can be performed by an electronic device, such as device 100, 300, and/or 500 (Figures 1, 3, and 5). At block 1202, data corresponding to an input detected by an external device is received at the electronic device performing process 1200. The received data can represent an incoming electronic touch communication. At block 1204, in response to receiving the data, the electronic device determines whether it is actively running an open application suitable for processing electronic touch communication. If a suitable application is open, the process continues to block 1206, where a visual representation of the incoming data is displayed. For example, Figure 6D illustrates processing incoming data in this manner (particularly with respect to the display of visual representation 600) when both devices 600 and 699 are displaying a drawing area. If the appropriate application is not open, the process continues to block 1208 where a notification regarding the incoming data is displayed (e.g., alert 638 in FIG. 6B , alert 840 in FIG. 8 ). At block 1210 , user input is received on the displayed alert, and in response, the electronic device launches the appropriate application for electronic touch communication and displays a visual representation of the incoming data (e.g., display of visual representation 642 in drawing area 640 in FIG. 6B ).

FIG13 illustrates exemplary functional blocks of an electronic device 1300 that performs the functions described above in some embodiments. As shown in FIG13 , electronic device 1300 may include a display unit 1302 configured to display graphical objects; a human input interface unit 1304 configured to receive user input; one or more RF units 1306 configured to detect and communicate with external electronic devices; one or more feedback units configured to provide tactile, audio, and/or visual feedback to the user; and a processing unit 1310 coupled to display unit 1302, human input interface unit 1304, RF unit(s) 1306, and feedback unit 1308. In some embodiments, processing unit 1312 is configured to support electronic touch communication processing unit 1312 and display enabling unit 1314.

In some embodiments, the display enabling unit 1314 is configured to cause display of a user interface (or a portion of a user interface) in conjunction with the display unit 1302. For example, the display enabling unit 1314 can be used to display one or more of the user interfaces described with reference to Figures 6A-6E, 7A-7E, 8, and 9A-9C.

In some embodiments, the electronic touch communication processing unit 1312 is configured to process touch communications according to the examples discussed above with reference to Figures 6A-6E, 7A-7E, 8, and 9A-9C. As discussed with reference to Figures 10A-10C, 11, and 12, the electronic touch communication processing unit 1312 can determine when to send outgoing data representing electronic touch communications (e.g., whether a necessary time threshold has passed since receiving the input) and when to remove the visual representation on the screen (e.g., whether a necessary display time threshold has passed).

The units of Figure 13 can be used to implement the various techniques and methods described above with reference to Figures 6-12. The units of Figure 13 are optionally implemented by hardware, software, or a combination of hardware and software to perform the principles of the embodiments described herein. It will be understood by those skilled in the art that the functional blocks described in Figure 13 are optionally combined or separated into sub-blocks to implement the principles of the examples described herein. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

According to some embodiments, Figure 14 shows a functional block diagram of an electronic device 1400 configured according to the principles of the various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of hardware and software to perform the principles of the various described embodiments. It will be appreciated by those skilled in the art that the functional blocks described in Figure 14 are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

14 , electronic device 1400 includes a display unit 1402 configured to display a graphical user interface, a touch-sensitive surface unit 1404 configured to receive contacts, and a processing unit 1406 coupled to display unit 1402 and touch-sensitive surface unit 1404. In some embodiments, processing unit 1406 includes a detecting unit 1408, a display enabling unit 1410, a replacing unit 1412, a sending unit 1414, a determining unit 1416, a fading enabling unit 1418, a receiving unit 1420, an updating enabling unit 1422, a scaling enabling unit 1424, a recording unit 1426, and a stopping unit 1428.

Processing unit 1406 is configured to detect user input (e.g., using detection unit 1408) and, in response to detecting the user input, enable display of a plurality of affordances representing contacts (e.g., using display enabling unit 1410). Processing unit 1406 is configured to detect user selection of a displayed affordance representing contacts (e.g., using detection unit 1408); in response to detecting the user selection of the displayed affordance, replace the plurality of affordances (e.g., using replacing unit 1412) with display of contact information identifying the selected contact, the selected contact being represented by the selected affordance; while displaying the contact information, detect a touch on the touch-sensitive display (e.g., using detection unit 1408); and, in response to detecting the touch: enable display of a drawing area (e.g., using display enabling unit 1410), wherein the drawing area is responsive to the touch input. Processing unit 1406 is further configured to detect a first touch input representing a first stroke in the drawing area (e.g., using detection unit 1408); enable display of a visual representation of the first stroke in the drawing area (e.g., using display enabling unit 1410); and send data representing the first stroke to an external device associated with the selected contact (e.g., using sending unit 1414).

In some embodiments, processing unit 1406 is further configured to determine (e.g., using determination unit 1416) whether a first predetermined duration has passed after the first touch input, wherein sending data representing the first stroke includes: sending data in response to determining that the first predetermined duration has passed.

In some embodiments, processing unit 1406 is further configured to: detect (e.g., using detection unit 1408) a second touch input representing a second stroke in the drawing area on the screen before the first predetermined duration has elapsed, wherein the first stroke and the second stroke are separated by an intermediate time amount; and send (e.g., using sending unit 1414) data to an external device associated with the second stroke and the intermediate time amount.

In some embodiments, the first stroke has characteristic dynamics, and sending data representing the first stroke includes sending data indicative of the characteristic dynamics to an external device.

In some embodiments, the processing unit 1406 is further configured to enable fading of the displayed visual representation of the first stroke (eg, using the fade enabling unit 1418 ) after the first stroke has been received for a second predetermined duration.

In some embodiments, sending the data triggers the external device to: display an indication that the data was received, and display an affordance, wherein the affordance, when selected, causes the external device to display a visual representation of the first stroke.

In some embodiments, sending the data triggers the external device to display a visual representation of the first stroke.

In some embodiments, sending data triggers the external device to display a visual representation of a first stroke, followed by a pause of an intervening amount of time, and then display a visual representation of a second stroke.

In some embodiments, sending the data triggers the external device to display a visual representation of the first stroke having the characteristic dynamics.

In some embodiments, the processing unit 1406 is further configured to enable fading of the visual representation of the stroke (eg, using the fade enabling unit 1418 ) after determining that the visual representation has been displayed for the third predetermined duration.

In some embodiments, the processing unit 1406 is further configured to: receive data from an external device (e.g., using the receiving unit 1402), the data representing a third touch input detected by the external device, the third touch output representing a third stroke; and enable display of a visual representation of the third stroke in a drawing area of the electronic device (e.g., using the display enabling unit 1410).

In some embodiments, the processing unit 1406 is further configured to enable fading of the visual representation of the third stroke (using the fade enabling unit 1418 ) after a fourth predetermined duration.

In some embodiments, the second predetermined duration, the third predetermined duration, and the fourth predetermined duration are the same duration.

In some embodiments, the stroke has a beginning and an end, and fading out the visual representation of the stroke comprises fading out the corresponding beginning of the visual representation before fading out the corresponding end of the visual representation.

In some embodiments, processing unit 1406 is further configured to: enable display of a color picker affordance in the drawing area (e.g., using display enabling unit 1410), wherein the color picker affordance has a color indicative of a currently selected color, wherein displaying the affordance for the first stroke comprises: displaying a visual representation in the currently selected color; and in response to detecting selection of the color picker affordance, enable display of multiple color affordances representing colors (e.g., using display enabling unit 1410).

In some embodiments, the plurality of color affordances includes a plurality of color affordances representing previously selected colors.

In some embodiments, processing unit 1406 is further configured to: in response to detecting selection of a color affordance of the displayed plurality of color affordances, enable display of the color palette (eg, using a display enabling unit).

In some embodiments, the color palette includes multiple portions having different colors, and processing unit 1406 is further configured to: in response to detecting selection of a portion of the color palette corresponding to a selected color: enable display of the drawing area (e.g., using display enable unit 1410); and enable updating of a color picker affordance displayed in the drawing area (e.g., using update enable unit 1422) so that the color picker affordance is updated with the selected color.

In some embodiments, sending data representing the first stroke to the external device includes sending data representing a selected color.

In some embodiments, the electronic device includes a rotatable input mechanism, and the processing unit 1406 is further configured to: when enabling display of multiple affordances representing contacts, detect (e.g., using the detection unit 1408) user input representing movement of the rotatable input mechanism; and in response to the detected user input: enable scaling of the display of multiple user-specified contacts (e.g., using the scaling enabling unit 1424), wherein the scaling display includes changing the size of the contacts being displayed.

In some embodiments, enabling scaling of the display includes enabling a change in the number of contacts being displayed.

In some embodiments, the touch-sensitive display includes one or more sensors for detecting the intensity of a touch on the touch-sensitive display, and the processing unit 1406 is further configured to: when enabling display of the drawing area, detect a touch on the touch-sensitive display (e.g., using the detection unit 1408), wherein the touch has a characteristic intensity; determine (e.g., using the determination unit 1416) whether the characteristic intensity exceeds a predetermined threshold intensity; in response to determining that the characteristic intensity exceeds the predetermined threshold intensity: enable display of a call offering (e.g., using the display enabling unit 1410), wherein when the call offering is selected, cause the processing unit to initiate a call to an external device associated with the contact; and in response to determining that the characteristic intensity does not exceed the predetermined threshold intensity, send data representing the touch to the external device (e.g., using the sending unit 1414).

In some embodiments, the touch-sensitive display includes one or more sensors for detecting the intensity of a touch on the touch-sensitive display, and the processing unit 1406 is further configured to: when enabling display of the drawing area, detect a touch on the touch-sensitive display (e.g., using the detection unit 1408), wherein the touch has a characteristic intensity; determine (e.g., using the determination unit 1416) whether the characteristic intensity exceeds a predetermined threshold intensity; in response to determining that the characteristic intensity exceeds the predetermined threshold intensity: enable display of a text affordance (e.g., using the display enabling unit 1410), wherein when the text affordance is selected, cause the processing unit to initiate a message to an external device associated with the contact; and in response to determining that the characteristic intensity does not exceed the predetermined threshold intensity, send data representing the touch to the external device (e.g., using the sending unit 1414).

In some embodiments, processing unit 1406 is further configured to: when display of contact information identifying a selected contact is enabled, enable display of a call affordance (e.g., using display enabling unit 1410), wherein when the call affordance is selected, cause processing unit 1406 to initiate a call to an external device associated with the selected contact.

In some embodiments, processing unit 1406 is further configured to: when display of contact information identifying a selected contact is enabled, enable display of a text affordance (e.g., using display enabling unit 1410), wherein when the text affordance is selected, cause processing unit 1406 to initiate a message to an external device associated with the selected contact.

In some embodiments, enabling display of a plurality of affordances representing contacts includes enabling display of a plurality of affordances representing user-specified contacts, the user-specified contacts being a subset of contacts accessible to the electronic device.

In some embodiments, the electronic device includes a depressible input mechanism separate from the touch-sensitive display, and detecting the user input includes detecting activation of the depressible input mechanism.

In some embodiments, the electronic device includes a pressable input mechanism and a microphone, and the processing unit is further configured to: when display of the drawing area is enabled, detect the activated display of the pressable input mechanism (for example, using detection unit 1408); in response to detecting the activation: while the pressable input mechanism remains pressed, record an audio message based on the input received from the microphone (for example, using recording unit 1426); detect the release of the pressable input mechanism (for example, using detection unit 1408); and in response to detecting the release: stop recording the audio message (for example, using stop unit 1428) and send the recorded audio message to an external device associated with the selected contact.

The operations described above with reference to Figures 10A-10C may optionally be implemented by the components depicted in Figures 1A-1B or Figure 14. For example, display operations 1002 and 1018, detection operations 1004, 1006, and 1008, determination operations 1010, 1014, and 1020, sending operations 1012, 1016, and 1022, and optional receiving operation 1024 may optionally be implemented by event classifier 170, event recognizer 180, and event handler 190. Event monitor 171 in event classifier 170 detects contacts on touch-sensitive surface display 112, and event dispatcher module 174 delivers event information to application 136-1. The corresponding event recognizer 180 of application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first contact at the first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as selection of an object on a user interface or rotation of a device from one direction to another. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses a corresponding GUI updater 178 to update the content displayed by the application. Similarly, it will be clear to those skilled in the art how to implement other processes based on the components depicted in Figures 1A-1B.

According to some embodiments, Figure 15 shows a functional block diagram of an electronic device 1500 configured according to the principles of the various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of hardware and software to perform the principles of the various described embodiments. Those skilled in the art will appreciate that the functional blocks described in Figure 15 are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

15 , electronic device 1500 includes a display unit 1502 configured to display a graphical user interface, a touch-sensitive surface unit 1504 configured to receive contacts, and a processing unit 1506 coupled to display unit 1502 and touch-sensitive surface unit 1504. In some embodiments, processing unit 1506 includes a receiving unit 1508, a detecting unit 1510, a determining unit 1512, and a sending unit 1514. The electronic device is optionally configured to communicate with an external device associated with the contact.

Processing unit 1506 is configured to: receive a user selection of a displayed affordance representing a contact (e.g., using receiving unit 1508); after receiving the selection, detect user input on the touch-sensitive display (e.g., using detecting unit 1510); determine (e.g., using determining unit 1512) whether the touch input is a single-finger touch input or a multi-finger touch input; and based on the determination that the touch is a single-finger touch input, send data to an external device (e.g., using sending unit 1514), the data representing the single-finger touch input.

In some embodiments, sending data triggers the external device to provide output corresponding to the single-finger touch input.

In some embodiments, sending the data triggers the external device to display a notification that the data was received and, when the affordance is selected, causes the external device to display a visual representation of the single-finger touch input.

In some embodiments, detecting user input on a touch-sensitive display of an electronic device includes detecting a single-finger touch input at a location on the touch-sensitive display, and when displaying a visual representation of the single-finger touch input, displaying a visual representation of the single-finger touch input at a location on a display screen of an external device corresponding to the location where the single-finger touch input was detected.

In some embodiments, the visual indication comprises one or more circles, ellipses, and/or ovals.

In some embodiments, the visual indication comprises two or more concentric circles, ellipses, and/or ovals.

In some embodiments, after displaying the visual indication for a predetermined amount of time, the visual indication on the external device fades out.

In some embodiments, the single-finger touch is a single-finger tap.

In some embodiments, processing unit 1506 is further configured to: based on the determination that the detected user input represents a multi-touch input, send data to an external device (for example, using sending unit 1514), wherein sending the data triggers the external device to continuously display a visual indication of the multi-touch input.

In some embodiments, the output includes a notification that the data was received and, when the affordance is selected, causes the processing unit to enable persistent display of a visual indicator of the multi-touch input.

In some embodiments, the visual indicator is an image.

In some embodiments, the visual indicator is an animated image.

In some embodiments, the visual indicator is an animated image of a beating heartbeat.

In some embodiments, the electronic device further comprises a biosensor configured to detect a rate of a heartbeat, wherein the rate of the beats of the pulsating heartbeat is based on the detected rate of the heartbeat.

In some embodiments, the electronic device further includes a biosensor configured to detect a rate of heartbeat, wherein sending the data triggers the external device to provide a tactile output corresponding to the detected rate of heartbeat.

In some embodiments, sending data triggers an external device to provide tactile output.

In some embodiments, the electronic device includes a rotatable input mechanism, wherein receiving a user selection of a contact includes: enabling display of multiple affordances representing contacts; detecting user input representing movement of the rotatable input mechanism; and in response to detecting the user input: enabling display of multiple user-specified contacts, wherein scaling the display includes changing the size of the contacts being displayed.

In some embodiments, enabling scaling of the display includes enabling a change in the number of contacts being displayed.

In some embodiments, processing unit 1506 is further configured to: when display of multiple affordances representing contacts is enabled, detect user input on the displayed affordances (e.g., using detection unit 1510); and in response to detecting touch input, send data to an external device associated with the contact (e.g., using sending unit 1514), wherein sending the data triggers the external device to provide tactile output.

In some embodiments, detecting touch input on the displayed affordance includes detecting a first touch and releasing the displayed affordance within a predetermined duration, and then detecting a second touch and releasing the displayed affordance within a predetermined duration.

The operations described above with reference to Figures 10A-10C may optionally be implemented by the components depicted in Figures 1A-1B or Figure 15. For example, display operations 1002 and 1018, detection operations 1004, 1006, and 1008, determination operations 1010, 1014, and 1020, sending operations 1012, 1016, and 1022, and optional receiving operation 1024 may optionally be implemented by event classifier 170, event recognizer 180, and event handler 190. Event monitor 171 in event classifier 170 detects contact on touch-sensitive surface display 112, and event dispatcher module 174 delivers event information to application 136-1. The corresponding event recognizer 180 of application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first contact at the first location on the touch-sensitive surface (or whether the device is rotated) corresponds to a predefined event or sub-event, such as selection of an object on the user interface or rotation of the device from one direction to another. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses a corresponding GUI updater 178 to update the content displayed by the application. Similarly, it will be clear to those skilled in the art how to implement other processes based on the components depicted in Figures 1A-1B.

According to some embodiments, Figure 16 shows a functional block diagram of an electronic device 1600 configured according to the principles of the various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of hardware and software to perform the principles of the various described embodiments. Those skilled in the art will appreciate that the functional blocks described in Figure 16 are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

16 , electronic device 1600 includes a display unit 1602 configured to display a graphical user interface, a touch-sensitive surface unit 1604 configured to receive contacts, and a processing unit 1606 coupled to display unit 1602 and touch-sensitive surface unit 1604. In some embodiments, processing unit 1606 includes a receiving unit 1608, an issuing unit 1610, a detecting unit 1612, a determining unit 1614, a display enabling unit 1616, a replacing unit 1618, a playing unit 1620, and an identifying unit 1622. The electronic device may optionally be configured to communicate with an external device.

Processing unit 1606 is configured to: receive data corresponding to input detected by an external device (e.g., using receiving unit 1608); in response to receiving the data, emit a tactile output (e.g., using emitting unit 1610); after issuing the tactile output, detect user input (e.g., using detecting unit 1612); determine (e.g., using determining unit 1614) whether user input is detected within a predetermined time interval after the tactile output; and based on a determination that user input is detected within the predetermined time interval, enable display of a notification on the display (e.g., using display enabling unit 1616), wherein the notification indicates the availability of information for playback.

In some embodiments, processing unit 1606 is further configured to: when enabling the stopped display, detect a second user input (e.g., using detection unit 1612); determine (e.g., using determination unit 1614) whether the received data includes visual information; and based on the determination that the received data includes visual information: replace the displayed notification with the visual information (e.g., using replacement unit 1618).

In some embodiments, the processing unit 1606 is further configured to: determine (e.g., using the determination unit 1614) whether the received data includes audio information; and based on the determination that the received data includes audio information: play the audio information through a speaker operatively connected to the electronic device (e.g., using the playback unit 1620).

In some embodiments, the processing unit 1606 is further configured to: identify a user associated with the external device (e.g., using the identification unit 1622); and based on a determination that user input is detected after a predetermined time interval: enable display of multiple affordances representing user-specified contacts (e.g., using the display enabling unit 1616), and the affordances represent the user associated with the external device; and enable display of an indicator corresponding to the affordance representing the user associated with the external device (e.g., using the display enabling unit 1616), the indicator indicating the availability of information received from the user associated with the external device for playback.

In some embodiments, the processing unit 1606 is further configured to: (e.g., using the identification unit 1622) identify multiple contacts accessible to the electronic device; (e.g., using the determination unit 1614) determine whether the external device is associated with a contact among the multiple contacts accessible to the electronic device; based on the determination that the external device is not associated with a contact among the multiple contacts accessible to the electronic device: (e.g., using the display enabling unit 1616) enable display of an add contact affordance, wherein when the add contact affordance is selected, the processing unit enables display of a user interface screen for registering contacts and associating the device with the contacts.

In some embodiments, the processing unit 1606 is further configured to: (e.g., using the identification unit 1622) identify a subset of multiple contacts accessible to the electronic device as multiple user-specified contacts; (e.g., using the determination unit 1614) determine whether the external device is associated with a user-specified contact among the multiple user-specified contacts; and based on the determination that the external device is associated with a contact among the multiple contacts accessible to the electronic device but is not associated with a user-specified contact among the multiple user-specified contacts: (e.g., using the display enabling unit 1616) enable display of a designated affordance, wherein when the designated affordance is selected, the processing unit enables display of a user interface screen for designating a contact associated with the external device as a user-specified contact.

In some embodiments, processing unit 1606 is further configured to: identify a contact name associated with the external device (eg, using identification unit 1622 ), wherein enabling display of the notification on the display includes enabling display of the identification of the contact name.

In some embodiments, processing unit 1606 is further configured to: identify (eg, using identification unit 1622) an image associated with the contact name, wherein enabling display of the notification on the display includes enabling display of the image.

In some embodiments, detecting user input includes detecting movement of the electronic device.

In some embodiments, detecting user input includes detecting lifting of the electronic device.

The operations described above with reference to FIG11 may optionally be implemented by the components depicted in FIG1A-1B or FIG16. For example, receiving operations 1101 and 1110, detecting operation 1104, determining operation 1006, displaying operations 1008 and 1114, and returning operation 1112 may optionally be implemented by event classifier 170, event recognizer 180, and event handler 190. Event monitor 171 in event classifier 170 detects contact on touch-sensitive surface display 112, and event dispatcher module 174 delivers event information to application 136-1. The corresponding event recognizer 180 of application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first contact at the first location on the touch-sensitive surface (or whether the device is rotated) corresponds to a predefined event or sub-event, such as selection of an object on the user interface or rotation of the device from one orientation to another. Upon detecting the corresponding predefined event or sub-event, event recognizer 180 activates the event handler 190 associated with the detection of the event or sub-event. Event handler 190 can utilize or call data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses corresponding GUI updater 178 to update the content displayed by the application. Similarly, it will be clear to those skilled in the art how to implement other processes based on the components depicted in Figures 1A-1B.

According to some embodiments, Figure 17 shows a functional block diagram of an electronic device 1700 configured according to the principles of the various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of hardware and software to perform the principles of the various described embodiments. Those skilled in the art will appreciate that the functional blocks described in Figure 17 are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

17 , electronic device 1700 includes a display unit 1702 configured to display a graphical user interface, a touch-sensitive surface unit 1704 configured to receive touches, and a processing unit 1706 coupled to display unit 1702 and touch-sensitive surface unit 1704. In some embodiments, processing unit 1706 includes a receiving unit 1708, a determining unit 1710, a playback unit 1712, a display enabling unit 1714, a providing unit 1716, and a fade enabling unit 1718. The electronic device may optionally be configured to communicate with an external device.

Processing unit 1706 is configured to receive (e.g., with receiving unit 1708) data from an external device representing user input received at the external device; determine (e.g., with determining unit 1710) whether the electronic device is actively executing a playback application; based on determining that the electronic device is actively executing the playback application, play back (e.g., with playback unit 1712) the received data; and based on determining that the electronic device is not actively executing the playback application: enable display (e.g., with display enabling unit 1714) an indication that data is received; and enable display (e.g., with display enabling unit 1714) an affordance, wherein the affordance, when selected, initiates the playback application and causes the electronic device to play back the received data.

In some embodiments, the processing unit is further configured to provide (eg, with providing unit 1716 ) a tactile output in response to receiving the data based on determining that the electronic device is not actively executing the playback application.

In some embodiments, playing back the received data also includes, based on determining that the user input is a single-finger touch input on the external device, enabling display of a visual representation of the single-finger touch input on the screen of the electronic device corresponding to a location on the external device where the single-finger touch input is detected.

In some embodiments, the visual indication comprises one or more circles, ellipses, and/or ovals.

In some embodiments, the visual indication comprises two or more concentric circles, ellipses, and/or ovals.

In some embodiments, the processing unit 1706 is further configured to enable fading out (eg, with the fade-out enabling unit 1718) of the visual indication after a predetermined amount of time.

In some embodiments, playing back the received data further comprises: enabling display of a persistent visual indicator for the multi-touch input based on determining that the user input is a multi-touch input on the external device.

In some embodiments, the visual indicator is an image.

In some embodiments, the visual indicator is an animated image.

In some embodiments, the visual indicator is an animated image of a beating heart.

In some embodiments, processing unit 1706 is further configured to provide (eg, with providing unit 1716 ) a tactile output while enabling display of the visual indicator.

In some embodiments, playing back the received data further comprises: based on determining that the user input is a double tap on the external device, enabling display of an identification of a user associated with the external device and providing a tactile output while displaying the identification.

In some embodiments, playing back the received data further comprises: playing the audio recording based on determining that the user input is an audio recording recorded using a microphone of the external device.

In some embodiments, playing back the received data further comprises: upon determining that the user input is a swipe contact on the external device representing a stroke, enabling display of a visual representation of the stroke.

In some embodiments, the processing unit 1706 is further configured to enable fading out of the stroke after a predetermined duration.

The operations described above with respect to FIG. 12 may optionally be implemented by the components depicted in FIG. 1A-1B and FIG. 17 . For example, receiving operations 1202 and 1210 , determining operation 1204 , and displaying operations 1206 and 1208 may optionally be implemented by event classifier 170 , event recognizer 180 , and event handler 190 . An event monitor 171 in event classifier 170 detects a contact on touch-sensitive display 112 , and event dispatcher module 174 delivers the event information to application 136 - 1 . The corresponding event recognizer 180 of application 136 - 1 compares the event information with a corresponding event definition 186 and determines that a first contact at a first location on the touch-sensitive surface (or rotation of the device) corresponds to a predefined event or sub-event, such as selecting an object on a user interface or rotating the device from one orientation to another. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates the event handler 190 associated with the event or sub-event detection. Event handler 190 optionally uses or calls data updater 176 or object updater 177 to update application external state 192. In some embodiments, event handler 190 accesses the corresponding GUI updater 178 to update what is displayed by the application. Similarly, it should be clear to one of ordinary skill in the art how other processes can be implemented based on the components depicted in Figures 1A-1B.

Figures 18A-18B illustrate an example embodiment of a touch-sensitive display including a user interface 1802 at an electronic device 1800. The user interface 1802 and the methods described below allow a user to communicate with one or more contacts whose information is stored on the electronic device 1800. In some embodiments, the user may have stored a large number of contacts on the electronic device 1800 and therefore require an efficient method for identifying and communicating with a particular contact. Moreover, in some cases, the user may frequently only access a subset of the stored contacts. In this way, it would be inconvenient to scroll through the contact list each time the user desires to communicate with a particular contact. Therefore, in order to enhance the user experience and improve efficient communication, it may be desirable for the electronic device 1800 to display a user interface that includes a limited number of one or more contacts selected by the user.

Electronic device 1800 can be the same as or similar to portable multifunction device 100 and/or device 500. Furthermore, electronic device 1800 can include a rotatable input mechanism 1820, which can be the same as or similar to rotatable input mechanism 506. Electronic device 1800 can include a touch-sensitive display, which can include a user interface 1802 and can be the same as or similar to touch-sensitive display system 112 and/or display 504.

As shown in Figure 18A, electronic device 1800 can be configured to display multiple objects (e.g., first object 1808, second object 1810, third object 1812, and objects 1840a-1840i) arranged or otherwise positioned around affordance 1804 on a touch-sensitive display including user interface 1802. In some embodiments, one or more of the multiple objects can be associated with one of the multiple contacts. For example, first object 1808 can be associated with contact Steve Jones. Accordingly, first object 1808 can include a set of initials (e.g., SJ), which can be displayed within first object 1808. In some embodiments, the geometry of the initials can be a monogram, such as, but not limited to, stylized, interwoven, or overlapping initials. Similarly, second object 1810 can include the initials "AS," and third object 1812 can include the initials "IS." In some embodiments, the user interface can include 12 objects, each arranged in a position corresponding to the hours on a standard clock or dial (e.g., an object at the first hour, the second hour, the third hour, etc.). In other embodiments, there may be 6 objects arranged at positions corresponding to every two hours on a standard clock, or 24 objects at positions corresponding to every 30 minutes.

User interface 1802 may also include affordance 1804, which may display a visual appearance based on the position of visual indicator 1806 relative to an object in the plurality of objects. For example, the visual appearance of the affordance may be a collection of initials of contacts representing a plurality of contacts, or a collection of images of contacts representing a plurality of contacts. As shown in FIG18A , the visual appearance of affordance 1804 may be an image of a contact associated with first object 1808.

In some embodiments, electronic device 1800 may be configured to receive a first input corresponding to a rotation of rotatable input mechanism 1820. Furthermore, as shown in FIG18B , electronic device 1800 may be configured to update the visual appearance of affordance 1804 to represent a second contact (e.g., “IS”) in the plurality of contacts in response to receiving the input corresponding to the rotation of rotatable input mechanism 1820. Furthermore, user interface 1802 may include a visual indicator 1806 associated with a first object 1808 of the plurality of objects, the first object associated with the first contact (e.g., “Steve”) in the plurality of contacts.

As an example, electronic device 1800 may be configured to receive input from a user indicating a desire to communicate or otherwise consider another contact of the plurality of contacts. Based on the rotation of rotatable input mechanism 1820, the visual appearance of affordance 1804 may change from first object 1808 to third object 1812, as shown in FIG18B . Additionally, the position and movement of visual indicator 1806 may correspond to the rotation of rotatable input mechanism 1820. Thus, as rotatable input mechanism is rotated, visual indicator 1806 may move from one object to another in a circular manner around affordance 1804.

In particular, for example, in response to receiving a first input corresponding to a rotation of the rotatable input mechanism 1820, the electronic device 1800 can be configured to stop associating the visual indicator 1806 with a first object 1808 of a plurality of objects, and instead associate the visual indicator 1806 with an object in the plurality of objects that is associated with a second contact of the plurality of contacts (e.g., a contact associated with the second object 1810).

In some embodiments, electronic device 1800 can be configured to display visual indicator 1806 as part of user interface 1802 based on a position value. For example, the value can be within a range of position values, where each of the plurality of objects can be associated with a position within the range of position values. Furthermore, electronic device 1800 can be configured to determine whether the first input is a request to update the position value of visual indicator 1806 to a second position value that is not associated with an object of the plurality of objects.

Thus, the electronic device 1800 can be configured to snap the visual indicator to the nearest or closest object among the multiple objects. Specifically, the electronic device is configured to update the position value of the visual indicator 1806 to a third position value and update the display of the visual indicator according to the third position value, the third position value corresponding to the position value of the object closest to the second position value within the position value range among the multiple objects. For example, the aforementioned display update can be performed based on determining that the first input is a request to update the position value of the visual indicator 1806 to the second position value, which second position value is not associated with an object among the multiple objects.

The electronic device 1800 may also be fast-moved to or otherwise moved to the nearest or another object based on the received input to enhance the user experience. For example, to ensure that the visual indicator 1806 is close to or otherwise associated with the object, the electronic device 1800 may be configured to initially determine that the rotation of the rotatable input mechanism does not cause the visual indicator 1806 to be associated with a second contact of the plurality of contacts (e.g., a second object 1810). Moreover, the electronic device may be configured to determine whether the position of the visual indicator 1806 is within the object transition area based on determining that the rotation of the rotatable input mechanism does not cause the visual indicator to be associated with the second contact of the plurality of contacts. In some embodiments, the object transition area may be an area behind the first object 1808 and an area before the second object 1810 associated with the second contact.

Additionally, the electronic device 1800 may be configured to associate the visual indicator 1806 with a second contact of the plurality of contacts based on determining that the position of the visual indicator 1806 is within the object transition region. Furthermore, the electronic device 1800 may be configured to maintain the association of the visual indicator 1806 with the first object 1806 of the plurality of contacts based on determining that the position of the visual indicator 1806 is not within the object transition region.

In some embodiments, as illustrated in Figure 18C, electronic device 1800 may be configured to receive a first input corresponding to a contact at a contact of an object (e.g., third object 1812) on a touch-sensitive display that includes user interface 1802. For example, the input may represent a touch/contact via finger 1830 on the touch-sensitive display that includes user interface 1802. Furthermore, electronic device 1800 may be configured to update the visual appearance of affordance 1804 to represent a second contact (e.g., "IS") from the plurality of contacts in response to receiving the input corresponding to a contact at the location of an object (e.g., third object 1812) on the touch-sensitive display that includes user interface 1802.

In some embodiments, each of the plurality of objects may not be associated with a contact. For example, objects 1840a-1840i, each of which may not be associated with a corresponding contact, may be displayed differently from objects associated with a contact (e.g., first object 1808, second object 1810, and third object 1812). Thus, different sizes, shapes, and/or patterns may indicate available or empty object locations.

Furthermore, in some embodiments, each of the multiple objects can be associated with and/or include a unique color scheme. For example, first object 1808 can be a first color, second object 1810 can be a second color, third object 1812 can be a third color, and each of objects 1840a-1840i can be another color. In such embodiments, the color of each object can be different from another color. Thus, in a non-limiting example, Figure 18A can include 12 different colors, each color associated with a single object.

In some embodiments, visual indicator 1806 can be a discrete area where the displayed color of one or more of affordances 1804 is changed. For example, electronic device 1800 can be configured to change the color of the visual indicator from a first color based on the color of first object 1808 in the plurality of objects to a second color based on the color of second object 1810 in the plurality of objects. Additionally, electronic device 1800 can be configured to change the color of visual indicator 1806 from a first color associated with first object 1808 in the plurality of objects to a second color associated with a second contact (e.g., and second object 1810) in the plurality of contacts. In particular, electronic device 1800 can be configured to blend the first color and the second color as visual indicator 1806 moves from a first position associated with first object 1808 to a second position that is prior to the position of second object 1810 associated with a contact.

In a further embodiment, when the visual indicator 1806 is in a first position that overlaps at least a portion of the first object 1808 and one or more displayed colors of the first object 1808 are changed, the visual indicator 1806 may be associated with the first object 1808 of the plurality of objects. The electronic device 1800 may be configured to display the movement of the visual indicator 1806. In particular, the electronic device 1800 may be configured to move the visual indicator 1806 from the first position to a second position that overlaps at least a portion of the second object 1810 and one or more displayed colors of the second object 1810 are changed.

In some embodiments, electronic device 1800 may be configured to update the visual appearance of affordance 1804. Additionally, after updating the visual appearance of the affordance, electronic device 1800 may be configured to receive a second input corresponding to selecting a third object 1812 from the plurality of objects, where the third object is different from first object 1808 and second object 1810. Accordingly, electronic device 1800 may be configured to update the visual appearance of affordance 1806 to represent the third contact from the plurality of contacts.

In another embodiment shown in FIG18F , electronic device 1800 can be configured to display user interface screen 1802-1 for interacting with a selected contact (e.g., Steve, shown in FIG18F ) represented by and associated with affordance 1804. In some embodiments, device 1800, upon receiving appropriate input or satisfying a condition, displays contact screen 1802-1 while displaying one of the multiple interfaces described with respect to FIG18A-18D . For example, electronic device 1800 can enter contact-specific screen 1802-1 when a predetermined amount of time has elapsed without further rotation of mechanism 1820. In particular, electronic device 1800 can be configured to determine, after updating the visual appearance of affordance 1804, that no input has been received for a time period. In some embodiments, electronic device 1800 can cease displaying the plurality of objects in response to determining that no input has been received for the time period. The electronic device can also display one or more second affordances (e.g., affordance 1834) in response to determining that no input has been received for the time period.

In another embodiment, the electronic device may enter a contact-specific screen based on detecting a third input for selection of an affordance after updating the visual appearance of affordance 1806. Accordingly, electronic device 1800 may forgo displaying the plurality of objects in response to detecting the third input. Electronic device 1800 may display the second affordance in response to detecting the third input.

In some embodiments, a second affordance within a contact-specific screen (e.g., FIG. 18F may include one or more affordances, such as, but not limited to, a call affordance 1814, a message affordance 1816, a coaching affordance 1832, an affordance that restores a user interface including multiple objects including affordance 1834, and a drawing affordance 1818, each described in detail below) is displayed. In some embodiments, affordance 1834 functions as a “back” button to restore a previous screen or a pre-selected screen (e.g., the user interfaces of FIG. 18A through 18D ). For example, the electronic device may detect selection of coaching affordance 1832. In particular, the electronic device may detect a fourth input corresponding to selection of coaching affordance 1832. In response to the fourth input, electronic device 1800 may display a user interface including one or more instructions for operating the electronic device (e.g., instructions for how to draw an image or send a touch). In some aspects, coaching affordance 1832 may disappear after it has been accessed a set number of times. User interface screen 1802 - 1 provides the user with one or more affordances for connecting with the contact represented by affordance 1804 (ie, the represented contact), while simultaneously reducing cognitive dissonance by omitting or ceasing to display display objects not associated with the currently selected contact.

Additionally, in some embodiments, as shown in Figure 18A, each object in the plurality of objects can be associated with and/or positioned according to the hour markings of a clock. In some embodiments, the plurality of objects can include 12 circular objects positioned around affordance 1804. However, it should be understood that more or fewer than 12 objects can be positioned on user interface 1802.

User interface 1802 may also include a call/phone affordance 1814. For example, upon receiving input representing a contact or selection of call/phone affordance 1814, electronic device 1800 may enable a call to a contact in the plurality of contacts (e.g., the selected contact displayed at center affordance 1804). User interface 1802 may also include a message affordance 1816. For example, upon receiving input representing a contact or selection of message affordance 1816, electronic device 1800 may enable a call to a contact in the plurality of contacts (e.g., the selected contact displayed at center affordance 1804).

User interface 1802 indicator 1824 (Figure 18A) provides an indication of one or more unread messages from a contact associated with an object adjacent to the indicator (object 1812). In some embodiments, indicator 1824 may include a number or some other visual indication of the number of unread messages. Accordingly, electronic device 1800 may be configured to determine whether one or more messages received from a contact in a plurality of contacts have not been read, and based on determining that a message received from a contact in a plurality of contacts has not been read, display indicator 1824 adjacent to an object in a plurality of objects associated with the one or more messages (e.g., third object 1824 in Figure 18A).

Figure 18E illustrates an example user interface for adding or otherwise associating a contact to an object. In some embodiments, a visual indicator can be positioned near empty object 1840a. Empty object 1840a can be an empty circle location that is converted to include a plus icon. Furthermore, affordance 1804 can also include a plus icon indicating the progress of adding a contact. Additionally, selecting affordance 1804 in Figure 18E can initiate or otherwise trigger the contact selection process.

For example, electronic device 1800 may receive an input representing a second rotation of rotatable input mechanism 1820 and, in response, may determine whether visual indicator 1804 is proximate to an object that is not associated with any contact (e.g., object 1804a). Furthermore, electronic device 1800 may update the display of affordance 1804 to an add contact affordance based on determining that visual indicator 1806 is proximate to an object that is not associated with any contact. Electronic device 1800 may receive another input corresponding to a selection to add a contact and, in response to receiving a fourteenth input, display a user interface for adding a contact.

Figures 18G-18I illustrate additional example embodiments of a touch-sensitive display, including user interface 1802 at electronic device 1800 and having a visual indicator 1850 associated with first object 1808. As shown in Figure 18G, first object 1808 is associated with the currently selected contact represented by central affordance 1804. In such an embodiment, visual indicator 1850 can provide the user with an indication that the contact associated with object 1808 is currently selected. In Figure 18G, visual indicator 1850 is depicted as a circle that is slightly larger than 1808; however, in other embodiments, visual indicator 1850 can be presented differently and still convey to the user the currently selected object.

In some embodiments, visual indicator 1850 can be presented as an object having the same scale and dimensions as the currently selected object (e.g., object 1808). In some embodiments, the visual indicator is an object presented in the foreground of the user interface so that it blocks the elements of the user interface below the visual indicator. In other embodiments, the visual indicator is a translucent or transparent foreground object so that the following elements of the user interface are visible below the visual indicator. In such embodiments, the visual indicator can operate as a filter to change the visual appearance of the user interface elements below the visual indicator.

In other embodiments, the visual indicator can be displayed separately; even visual indicator 1850 can be a predefined area where the appearance (e.g., a change in color, brightness, contrast) of the elements below the interface is changed. In some such embodiments, the visual indicator can present a "spotlight" effect, whereby objects that are partially or completely below within the current predefined area occupied by visual indicator 1850 have an altered appearance so that their appearance (or at least the portion within the visual indicator area) is emphasized or changed (e.g., a change in color, brightness, contrast). Note that such an effect can be visually very similar to a visual indicator that operates to filter overlap, as described above, although those skilled in the art will appreciate that similar visual effects are implemented differently. In some embodiments, the spotlight-like visual indicator can only change the appearance of the objects arrayed in a circle around affordance 1804 (e.g., 1808, 1810, 1812), without changing the appearance of any portion of the background of user interface 1802 that may be within the area of the visual indicator.

In some embodiments, the appearance of visual indicator 1850 can be a blended color composed of the color of one object and the color of another object as visual indicator 1850 moves between objects. Specifically, the appearance of visual indicator 1850 can be a blended color based on the percentage of overlap. For example, blue can be associated with first object 1850, while red can be associated with second object 1810. Accordingly, the color of visual indicator 1850 can be a first percentage of the first color and a second percentage of the second color, depending on the X and Y overlap. In this way, as visual indicator 1850 moves between objects, its color can be dynamically updated based on the inverse proportional relationship between the color of the preceding object (e.g., first object 1808) and the color of the adjacent object (e.g., second object 1810). In other words, as visual indicator 1850 moves toward the second object, the color of the second object will be more heavily weighted in the color of visual indicator 1850 than the color of the first object. In other words, as visual indicator 1850 moves from a first object to a second object, the percentage of the first object's color that forms the color of visual indicator 1850 will decrease as visual indicator 1850 moves toward or closer to second object 1810, and as such, the percentage of the second object's color will increase.

In FIG18H , in response to an input corresponding to a rotation of mechanism 1820, visual indicator 1850 has moved to a second position between object 1808 and object 1810. Visual indicator 1808 now partially overlaps each of object 1808 and object 1810. FIG18I shows the visual indicator in a third position, now associated with object 1810 and no longer overlapping, or associated with, object 1808. Although not depicted, continued rotational input on mechanism 1820 may cause the visual indicator to move further along the circle, to object 1812, and so on, so that the visual indicator may move from object to object along the loop formed around affordance 1804. To enable the user to control the movement of visual indicator 1850 along the loop (e.g., from objects 1808, 1810, 1812, and so on), a "magnetic" relationship is associated between each selectable object and visual indicator 1850. Each element (e.g., 1808, 1810, 1812) is associated with a simulated magnetic value. In this example, the magnetic values of elements 1808, 1810, 1812 are equal. In other examples, the magnetic values can be different so that visual indicator 1850 can have more magnetic affinity for one object relative to another object.

Using a magnetic relationship between an object and a visual indicator 1850, physics-based modeling can be used to simulate the magnetic attraction between the object and the visual indicator. As a result, when the user input is not obtained while the visual indicator 1850 is not aligned with any object (e.g., the second position depicted in Figure 18H), the visual indicator 1850 eventually reaches a stable state where it is aligned with one of the objects (e.g., 1808, 1810, 1812, etc.). When the visual indicator is not converted or moved due to the rotation mechanism 1820, the visual indicator 1850 is considered to be in a stable state. This physics-based magnetic modeling causes the user interface to display a virtual brake, which assists the user in selecting an object using the visual indicator 1850 without the need for precise positioning or repositioning of the visual indicator. Moreover, this behavior limits instances in which two objects are simultaneously indicated by the visual indicator 1850 (e.g., Figure 18H), which reduces cognitive dissonance.

In this example, physics-based magnetic modeling is implemented, for example, by modeling each object (e.g., 1808, 1810, 1812, etc.) as an object made of a magnetized material that creates its own persistent magnetic field, and modeling the visual indicator 1850 as a material that is attracted to magnets, such as ferromagnetic materials including iron, cobalt, and nickel. In another example, physics-based modeling can be implemented by modeling each object as an object made of a material that is attracted to magnets, and modeling the visual indicator 1850 as a material that creates its own persistent magnetic field. In another example, physics-based modeling can be implemented by modeling each object as an object that creates its own persistent magnetic field, and modeling the visual indicator 1850 as a material that also creates its own persistent magnetic field, such as two magnets that attract. Each of these physics-based models can be adapted to include a magnetic field that changes rather than remains persistent, based on certain factors, such as the distance between a given object and the visual indicator 1850, the speed of the visual indicator 1850, the acceleration of the visual indicator 1850, or a combination of two or more factors. For example, a varying magnetic field can be simulated using an electromagnet that can be turned on or off and can have varying strengths. In some embodiments, the magnetic modeling is the model described in U.S. Non-Provisional Patent Application No. 14/476,657, filed on September 3, 2014, entitled "USER INTERFACE FOR MANIPULATING USER INTERFACE OBJECTS WITH MAGNETIC PROPERTIES," or PCT Patent Application Serial No. PCT/US2014/053961, filed on September 3, 2014, entitled "USER INTERFACE FOR MANIPULATING USER INTERFACE OBJECTS WITH MAGNETIC PROPERTIES," both of which are incorporated herein by reference for their disclosure of at least their magnetic models of motion.

18H and 18I , in some embodiments, if the rotation of mechanism 1820 causes visual indicator 1850 to transition to a position such as shown in FIG18H , device 1800 may snap visual indicator 1850 to the nearest object (in this case, object 1810). As shown in FIG18I , visual indicator 1850 is not allowed to maintain a stable state between objects 1808 and 1810. Device 1800 determines that the object has the most magnetic influence on visual indicator 1850 (e.g., the closest object in the case where objects 1808 and 1810 have the same magnetic value) and “snap” the visual indicator to that object. As shown in FIG18I , this determination results in snapping the visual indicator to object 1810.

In some embodiments, the movement of the visual indicator of the loop formed around the affordance 1804 from object to object is modeled as a range of potential positions or potential positions that the visual indicator can occupy. Objects (e.g., 1808, 1810, 1812, etc.) can be associated with specific positions along a range of potential positions or potential position ranges. In response to the rotation of mechanism 1820, device 1800 can determine whether the input will cause the visual indicator to transition to a position within a series or range that is not associated with any object (e.g., the position of visual indicator 1850 in Figure 18H). If so, device 1800 can update the position of the visual indicator to the most recent position associated with the object (object 1810 in Figure 18H) and then display the visual indicator at the updated position. In some embodiments, modeling motion of a visual indicator based on a model based on a series of positions or a range of positions is implemented according to the model described in U.S. non-provisional patent application 14/476,657, filed on September 3, 2014, entitled “USER INTERFACE FOR MANIPULATING USER INTERFACE OBJECTS WITH MAGNETIC PROPERTIES,” or PCT patent application serial number PCT/US2014/053961, filed on September 3, 2014, entitled “USER INTERFACE FOR MANIPULATING USER INTERFACE OBJECTS WITH MAGNETIC PROPERTIES,” both of which are incorporated herein by reference for at least their disclosures of modeling based on a range of positions or a series of positions (e.g., as depicted and described with respect to Figures 6A through 9B of each application).

18G-18I , the visual indicator is displayed in a first position associated with a first object in the plurality of objects (object 1808). In response to receiving a first input corresponding to a rotation of the rotatable input mechanism, device 1800 stops associating the visual indicator with the first object in the plurality of objects and associates the visual indicator with an object in the plurality of objects that is associated with a second contact in the plurality of contacts (object 1810).

In some embodiments, such as the embodiments of Figures 18G-18I , as part of a user interface, device 1800 displays a visual indicator (visual indicator 1850) based on a position value within a range of position values, each object in a plurality of objects (e.g., 1808, 1810, 1812, etc.) being associated with a position within the range of position values. Further in response to the first input (rotation of mechanism 1820), device 1800 determines whether the first input is a request to update the position value of the visual indicator to a second position value that is not associated with an object in the plurality of objects, or is not associated with a single object in the plurality of objects. Based on determining that the first input is a request to update the position value of the visual indicator to the second position value that is not associated with an object in the plurality of objects, or is not associated with a single object in the plurality of objects, device 1800 updates the position value of the visual indicator to a third position value that corresponds to the position value of the object in the plurality of objects that is closest to the second position value within the range of position values, and further updates the display of the visual indicator based on the third position value.

In some embodiments, such as the embodiments of Figures 18G-18I , a visual indicator is displayed in a first position associated with a first object (object 1808) in the plurality of objects. In response to receiving a first input corresponding to a rotation of a rotatable input mechanism, device 1800 ceases associating the visual indicator with the first object in the plurality of objects and associates the visual indicator with a second contact in the plurality of contacts by determining that the rotation of the rotatable input mechanism did not result in the visual indicator being associated with the second contact in the plurality of contacts. Based on determining that the rotation of the rotatable input mechanism did not result in the visual indicator being associated with the second contact in the plurality of contacts, device 1800 determines whether the position of the visual indicator is within an object transition region, where the object transition region is a region located behind the first object and before a second object associated with the second contact. Based on determining that the position of the visual indicator is within the object transition region, device 1800 associates the object transition region with the second contact in the plurality of contacts; and based on determining that the position of the visual indicator is not within the object transition region, device 1800 maintains the association of the visual indicator with the first object in the plurality of objects.

18J-18K illustrate an embodiment of a touch-sensitive display including a user interface 1802 on an electronic device 1800 and having a page indicator 1860. In particular, based on a determination by the electronic device 1800 that the number of objects meets or exceeds an object display limit/threshold, the electronic device 1800 is configured to display one or more additional pages and/or user interfaces of one or more objects (e.g., contacts) on the user interface 1802. That is, in some embodiments, the electronic device 1800 enables a user to select and cause any number of objects (e.g., contacts) to be displayed on additional (e.g., two or more) pages or user interfaces in a manner similar to that described herein with respect to FIGURES 18A-18I.

For example, in Figure 18J, electronic device 1800 can display a first set of one or more objects 1862. Additionally, electronic device 1800 displays a page indicator 1860 on touch-sensitive display 1802, which indicates the page or user interface at which the object is located. As shown in Figure 18J, page indicator 1860 can be a first position indicating a first page. For example, as shown in Figure 18J, the first user interface includes a first set of one or more objects. While displaying the first user interface (e.g., the first page), electronic device 1800 can be configured to receive an input corresponding to a request to display a second page. The input can be a swipe gesture detected by a user's finger 1830 and detected by touch-sensitive display 1802.

The electronic device 1800 can be configured to replace the display of the first user interface with a second user interface (e.g., a second page) in response to receiving input, as shown in Figure 18J. The electronic device 1800 can display a page indicator 1860 at a second position different from the first position on the second user interface. In some embodiments, the second page can be different from the first page so that the second page includes a second set of one or more objects (e.g., contacts), each associated with a contact of a plurality of contacts. In some embodiments, the objects (e.g., contacts) in the set of one or more objects can each be associated with a group. In some embodiments, the groups are different, such as between pages. For example, the first page can have each contact identified as a family member of the user (e.g., by the user or based on data associated with the contact); the second page can have each contact identified as a colleague of the user of the electronic device 1800 (e.g., by the user or based on data associated with the contact).

In some embodiments, providing a user with multiple pages and/or groups of one or more objects (e.g., contacts) can provide quick access to communications with the user's contacts, thereby reducing the cognitive burden on the user and producing a more efficient human-computer interface by reducing the amount of unnecessary, extraneous, repetitive, and/or redundant input, and can create a faster and more efficient user input arrangement that can reduce the amount of input required, reduce processing power, and reduce the amount of time for which the user interface needs to be displayed in order for a desired function to be accessed and executed.

Figures 19A-19B illustrate example user interfaces for displaying lifelike representations of contacts. For example, an electronic device may include a touch-sensitive display 1900 including a user interface 1910. Additionally, the electronic device may display a lifelike representation of a contact 1920 on the touch-sensitive display 1910. The user interface 1910 may also display a status 1930 of the contact 1920, which may include a current status and location. In one embodiment, the contact 1920 may be available and located in London. In another embodiment and at another point in time, the status 1930 of the contact 1920 may be updated to reflect a location in Manchester and a current status of sleeping.

In some embodiments, when the affordance represents a first contact, the visual appearance of the affordance (e.g., affordance 1804) can be an animated representation of the first contact. In some embodiments, updating the visual appearance of the affordance (e.g., affordance 1804) to represent a second contact in the plurality of contacts can include updating the visual appearance of the affordance to an animated representation of the second contact, as shown in Figures 19A-19B. Furthermore, the animated representation of the first contact can be dynamic and based on one or more of the second contact's time zone information, the second contact's location information, and information about a status specified by the second contact (e.g., do not disturb).

FIG20 illustrates an example user interface 2000 for enabling drawing within a drawing area. In some embodiments, electronic device 1800 ( FIG18A ) may receive an input corresponding to selecting drawing affordance 1818. In particular, electronic device 1800 ( FIG18A ) may detect a fifth input corresponding to selecting drawing affordance 1818 and may display drawing area 2010. The drawing area corresponds to a touch input. In another embodiment, electronic device 1800 may detect a sixth input corresponding to a first stroke in drawing area 2010 and, accordingly, display a visual representation of the first stroke in the drawing area. In some embodiments, user interface 2000 is or operates in a manner similar to drawing area 630 or drawing area 710.

In some embodiments, the electronic device 1800 ( FIG. 18A ) can display an animated dissipation of the residue 2130 along the stroke. In some embodiments, the animated dissipation of the residue is a comet-like effect that is displayed at the tail end of the location on the display representing the user contact 2020. Thus, as the user contacts the touch-sensitive display and moves the finger while maintaining contact, a comet-like effect will form and be displayed at the most recent contact location. Additionally, the electronic device 1800 ( FIG. 18A ) can display a fade-out in a smoke shape 21401 of the visual representation of the stroke from the drawing area. In some embodiments, fading out the visual representation includes an animation that displays the gradual dissipation of the stroke (e.g., a smoke-like effect of a disappearing drawing stroke).

FIG21 illustrates an example user interface 2100 having a clock affordance 2120 transition to a send affordance 2120 based on a user's desire to transmit a drawing to an external device. Specifically, a drawing area 2110 may include a drawing clock affordance 2120 that allows drawing only within the drawing area 2110. Furthermore, an input corresponding to selecting the drawing clock affordance may be received that disables the transmission of data representing any strokes in the drawing area 2110. Additionally, the drawing clock affordance 2120 may be replaced with a send affordance 2120 that allows the drawing to be transmitted to an external device.

In some embodiments, the user can also shake the electronic device 1800 to remove the most recent stroke in the drawing area. For example, the electronic device 1800 can receive input corresponding to a stroke in the drawing area. Furthermore, the electronic device 1800 can display a visual representation of the stroke in the drawing area in response to receiving the input. The electronic device 1800 can then detect a motion indicative of shaking or vibration and, in response, determine whether the motion of the electronic device meets a motion threshold. Thus, the electronic device 1800 can stop displaying the visual representation of the stroke in response to detecting the input indicative of a shaking motion and based on determining that the motion meets or exceeds the motion threshold.

In some embodiments, electronic device 1800 can be configured to detect or otherwise determine whether another device with which the user desires to communicate is capable of seizing the drawing process. Thus, if the contact does not have a device capable of processing and displaying data representing the strokes in the drawing, drawing affordance 181 will not be provided.

In an additional embodiment, electronic device 1800 can be configured to record and send a short audio message based on a long press on the touch-sensitive display, for example, while in a contact-specific screen. In particular, electronic device 1800 can be configured to detect another input representing a contact on the touch-sensitive display. Electronic device 1800 can be configured to determine whether the duration of the 12 inputs meets or exceeds a contact duration threshold. Accordingly, electronic device 1800 records the audio message based on determining whether the duration of the 12 inputs meets or exceeds the contact duration threshold. Additionally, electronic device 1800 sends the audio message to the electronic device associated with the second contact.

Figure 22 is a flow diagram illustrating a method 2200 for updating the visual appearance of an affordance, according to some embodiments. Method 2200 can be performed on a device having a touch-sensitive display and a rotatable input mechanism (e.g., 100, 300, 500, 550, and 1800). Some operations in method 2200 can be combined, the order of some operations can be changed, and some operations can be omitted.

In some embodiments, a rotatable input mechanism (e.g., rotatable input mechanism 506) can be configured to receive user input. In some embodiments, method 2200 can be performed at an electronic device having a touch-sensitive surface/display (e.g., 112, 355, and 504). Example devices that can perform method 2200 include devices 100, 300, 500, 550, and 1800 (Figures 1A, 3, 5A, and 18A-18I).

As shown below, method 2200 provides an intuitive way to interact with an electronic device by updating the visual appearance of an affordance. The method reduces the physical and/or cognitive burden on a user who may engage a rotatable input mechanism in various activities, thereby creating a more efficient human-machine interface.

At block 2202, method 2200 may display, on a touch-sensitive display, a user interface comprising a plurality of objects, each object associated with a contact in a plurality of contacts and an affordance having a visual appearance representing a first contact in the plurality of contacts. At block 2204, method 2200 may receive a first input corresponding to a rotation of a rotatable input mechanism. At block 2206, method 2200 may, in response to receiving the input corresponding to the rotation of the rotatable input mechanism, update the visual appearance of the affordance to represent a second contact in the plurality of contacts.

According to some embodiments, the user interface further comprises a visual indicator associated with a first object in the plurality of objects, the first object being associated with a first contact in the plurality of contacts.

According to some embodiments, further in response to receiving a first input corresponding to a rotation of the rotatable input mechanism: ceasing to associate the visual indicator with a first object in the plurality of objects; and associating the visual indicator with an object in the plurality of objects associated with a second contact in the plurality of contacts.

In accordance with some embodiments, as part of a user interface, a visual indicator is displayed based on a position value, which is within a range of position values, each object in a plurality of objects being associated with a position within the range of position values; and in response to a first input, a determination is made as to whether the first input is a request to update the position value of the visual indicator to a second position value that is not associated with an object in the plurality of objects; and based on determining that the first input is a request to update the position value of the visual indicator to a second position value that is not associated with an object in the plurality of objects: updating the position value of the visual indicator to a third position and updating the display of the visual indicator based on the third position value, the third position being responsive to a position value that is closest to the second position in the range of position values among the plurality of objects.

According to some embodiments, stopping associating the visual indicator with a first object among multiple objects and associating the visual indicator with a second contact among multiple contacts includes: determining that rotation of the rotatable input mechanism does not result in association of the visual indicator with the second contact among multiple contacts; based on determining that rotation of the rotatable input mechanism does not result in association of the visual indicator with the second contact among multiple contacts, determining whether the position of the visual indicator is in an object conversion area, wherein the object conversion area is an area located after the first object and before a second object associated with the second contact; based on determining that the position of the visual indicator is in the object conversion area, associating the visual indicator with the second contact among multiple contacts; based on determining that the position of the visual indicator is in the object conversion area, maintaining the association of the visual indicator with the first contact among multiple contacts.

In accordance with some embodiments, the visual indicator is a discrete area where one or more displayed colors of the available items are changed, and the method further includes: in response to receiving a first input corresponding to a rotation of a rotatable input mechanism: changing the color of the visual indicator from a first color based on a color of a first object in a plurality of objects to a second color based on a color of a second object in a plurality of objects.

According to some embodiments, changing the color of the visual indicator from a first color based on the color of a first object among a plurality of objects to a second color based on the color of a second object among a plurality of objects includes blending the first color and the second color as the visual indicator moves from a first position associated with the first object to a second position in front of the position of the second object associated with the contact.

According to some embodiments, the visual indicator is associated with a first object of the plurality of objects when the visual indicator is at a first location that overlaps at least a portion of the first object and a color of one or more displays of the first object is changed.

According to some embodiments, ceasing to associate the visual indicator with a first object among a plurality of objects and associating the visual indicator with a second contact among a plurality of contacts includes transitioning the visual indicator from a first position to a second position that overlaps at least a portion of the second object when one or more displayed colors of the second object are changed.

In accordance with some embodiments, when the affordance represents a first contact, the visual appearance of the affordance is an animated representation of the first contact, and wherein updating the visual appearance of the affordance to represent a second contact in the plurality of contacts includes updating the visual appearance of the affordance to the animated representation of the second contact.

According to some embodiments, the animated representation of the first contact is dynamically based on selecting information from the group consisting of: time zone information for the second contact, location information for the second contact, information regarding a status specified by the second contact, and combinations thereof.

In accordance with some embodiments, the method further includes, after updating the visual appearance of the affordance, receiving a second input corresponding to a rotation of a third object of the plurality of objects, the third object being different from the first object and the second object, and in response to receiving the second input, updating the visual appearance of the affordance to represent the third contact of the plurality of contacts.

According to some embodiments, after updating the visual appearance of the affordance, determining that no input has been received for a time period; and in response to determining that no input has been received for the time period, relinquishing display of the plurality of objects.

In accordance with some embodiments, after updating the visual appearance of the affordance, determining a third input corresponding to selection of the affordance; and in response to detecting the third input, relinquishing display of the plurality of objects.

According to some embodiments, the second affordance is displayed further in response to determining that no input has been received for the time period.

According to some embodiments, further in response to detecting the third input, the second affordance is displayed.

In accordance with some embodiments, the second affordance includes one or more affordances selected from the group consisting of: a call affordance, a message affordance, a coaching affordance, an affordance that restores a user interface including multiple objects (e.g., affordance 1834 of Figure 18F), and a drawing affordance.

According to some embodiments, the second affordance is a coaching affordance, the method further comprising: detecting a fourth input corresponding to selection of the coaching affordance; and in response to detecting the fourth input, displaying a user interface comprising one or more instructions for operating the electronic device.

According to some embodiments, the second affordance includes a drawing affordance, the method further comprising detecting a fifth input corresponding to selecting the drawing affordance; and in response to detecting the fifth input, displaying includes a drawing area, wherein the drawing area is responsive to the touch input.

According to some embodiments, a sixth input corresponding to the first stroke in the drawing area is detected; and in response to detecting the sixth input, a visual representation of the first stroke is displayed in the drawing area.

According to some embodiments, in response to detecting a sixth input, determining whether a first predetermined duration has passed after the sixth input; and based on determining that the first predetermined duration has passed after the sixth input, sending data representing the first stroke to an external device associated with the second contact.

According to some embodiments, the sixth input corresponds to two or more strokes comprising a first stroke forming a drawing, and the method further includes: also in response to detecting the sixth input, determining whether a first predetermined duration has passed after the sixth input; and based on determining that the first predetermined duration has passed after the sixth input, sending data representing the drawing to an external device associated with the second contact.

According to some embodiments, the drawing area includes a draw lock affordance that enables drawing only in the drawing area, the method further comprising detecting a seventh input corresponding to selecting the draw lock affordance; in response to detecting the seventh input, disabling sending data representing any strokes in the drawing area; and replacing the draw lock affordance with a send affordance that enables transmission of the drawing to the external device.

According to some embodiments, an eighth input corresponding to selecting the send affordance is detected; and in response to detecting the eighth input, data representing any stroke in the drawing area is enabled to be sent.

According to some embodiments, the electronic device includes one or more motion sensors, and the method further includes: receiving a ninth input corresponding to a stroke in the drawing area; in response to receiving the ninth input, displaying a visual representation of the stroke in the drawing area; detecting a ninth input corresponding to movement of the electronic device; in response to detecting the ninth input, determining whether the movement of the electronic device satisfies a motion threshold, and stopping displaying the visual representation of the stroke in response to detecting the ninth input and based on determining that the movement satisfies or exceeds the motion threshold.

According to some embodiments, ceasing to display the visual representation of the strokes comprises fading out the visual representation of the first stroke after a predetermined duration.

According to some embodiments, an eleventh input is received representing a stroke in the drawing area; while receiving the eleventh input, a residual animation is displayed along the stroke that dissipates; a visual representation of the stroke is displayed in the drawing area; and the visual representation of the stroke is faded out from the drawing area, wherein fading out the visual representation includes displaying a gradually dissipating animation of the stroke.

According to some embodiments, further in response to determining that no input has been received for the time period, determining whether the contact currently represented by the affordance is associated with a device capable of processing and displaying data representing strokes in a drawing; displaying the drawing affordance based on determining that the contact currently represented by the affordance is associated with a device capable of processing and displaying data representing strokes in a drawing; and forgoing displaying the drawing affordance based on determining that the contact currently represented by the affordance is not associated with a device capable of processing and displaying data representing strokes in a drawing.

According to some embodiments, also in response to a third input, it is determined whether the contact currently represented by the affordance is associated with a device capable of processing and displaying data representing strokes in a painting; based on determining that the contact currently represented by the affordance is associated with a device capable of processing and displaying data representing strokes in a painting, the drawing affordance is displayed; and based on determining that the contact currently represented by the affordance is not associated with a device capable of processing and displaying data representing strokes in a painting, displaying the drawing affordance is abandoned.

In accordance with some embodiments, a twelfth input representing contact on the touch-sensitive display is detected; a determination is made that a duration of the twelfth input meets or exceeds a contact duration threshold; an audio message is recorded based on the determination that a duration of the twelfth input meets or exceeds the contact duration threshold; and the audio message is sent to an electronic device associated with a second contact.

According to some embodiments, a thirteenth input is received representing a second rotation of the rotatable input mechanism; in response to receiving the thirteenth input, a determination is made as to whether the visual indicator is proximate to an object not associated with any contact; and based on determining whether the visual indicator is proximate to an object not associated with any contact, the display of the affordance is updated to an add contact affordance.

According to some embodiments, a fourteenth input corresponding to a selection to add a contact is received; and in response to receiving the fourteenth input, a user interface for adding a contact is displayed.

According to some embodiments, the visual appearance of the affordance is a collection of initials of contacts representing the plurality of contacts or an image of a contact representing the plurality of contacts.

According to some embodiments, the set of initials is a monogram.

According to some embodiments, the plurality of objects includes 12 circular objects positioned around the affordance.

According to some embodiments, it is determined that one or more messages received from a contact in a plurality of contacts are not read; and based on determining that the one or more messages received from the one contact in the plurality of contacts are not read, an indicator is displayed near an object in a plurality of objects associated with the one or more messages.

According to some embodiments, the indicator comprises an indication of a number of one or more unread messages.

According to some embodiments, each object in the plurality of objects includes a unique color scheme.

According to some embodiments, the visual indicator comprises a triangle that is movable with respect to the affordance.

According to some embodiments, each object in the plurality of objects includes a set of initials associated with a contact associated with the object.

According to some embodiments, the set of initials is a monogram.

According to some embodiments, each object of the plurality of objects is associated with an hour marking of a clock.

Figure 23 is a flow diagram illustrating a method 2300 for updating the visual appearance of an affordance, according to some embodiments. Method 2300 can be performed on a device with a touch-sensitive display and a rotatable input mechanism (e.g., 100, 300, 500, and 1800). Some operations in method 2300 can be combined, the order of some operations can be changed, and some operations can be omitted.

In some embodiments, a rotatable input mechanism (e.g., rotatable input mechanism 506) can be configured to receive user input. In some embodiments, method 2300 can be performed on an electronic device having a touch-sensitive surface/display (e.g., 112, 355, and 504). Example devices that can perform method 2300 include devices 100, 300, 500, and 1800 (Figures 1A, 2, 5A, and 18A-18I).

As described below, method 2300 provides an intuitive way to interact with an electronic device by updating the visual appearance of an affordance. The method reduces the physical and/or cognitive burden on the user, who can engage the rotatable input mechanism during various activities, thereby creating a more efficient human-machine interface.

At block 2302, method 2300 may display, on a touch-sensitive display, a user interface comprising a plurality of objects, each object associated with a contact in a plurality of contacts and an affordance having a visual appearance representing a first contact in the plurality of contacts. At block 2304, method 2300 may receive a first input corresponding to selecting an object in the plurality of objects associated with a second contact in the plurality of contacts. At block 2306, method 2300, in response to receiving the input corresponding to the contact on the object in the plurality of objects, updates the visual appearance of the affordance to represent the second contact in the plurality of contacts.

According to some embodiments, Figure 24 shows an example functional block diagram of an electronic device 2400, and the electronic device 2400 is configured according to the principle of various described embodiments. According to some embodiments, the functional block diagram of the electronic device 2400 is configured to perform the technology described above. The functional block diagram of the electronic device 2400 is optionally implemented by hardware, software, or a combination of hardware and software to realize the principle of various described examples. It will be understood by those skilled in the art that the functional blocks described in Figure 24 are optionally combined or separated into subframes to realize the principle of various described examples. Therefore, the description herein optionally supports any possible combination or separation or further qualification of the functional blocks described herein.

24 , electronic device 2400 includes a touch-sensitive display unit 2402, a rotatable input mechanism 2404, and a processing unit 2406 coupled to touch-sensitive display unit 2402 and rotatable input mechanism 2404. In some embodiments, processing unit 2406 includes a receiving unit 2408, an updating unit 2410, an associating unit 2412, a determining unit 2414, a detecting unit 2416, a replacing unit 2418, a recording unit 2420, a display enabling unit 2422, a changing unit 2424, a blending unit 2426, a transforming unit 2428, a sending unit 2430, and a fading unit 2432.

Processing unit 2406 is configured to: display (e.g., using display enabling unit 2422) on touch-sensitive display unit 2402 a user interface comprising a plurality of objects, each object being associated with a contact from a plurality of contacts and an affordance having a visual appearance representing a first contact from the plurality of contacts; receive (e.g., using receiving unit 2408) a first input corresponding to a rotation of a rotatable input mechanism; and in response to receiving the first input corresponding to a rotation of the rotatable input mechanism, update (e.g., using updating unit 2410) the visual appearance of the affordance to represent a second contact from the plurality of contacts.

According to some embodiments, the user interface further comprises a visual indicator associated with a first object in the plurality of objects, the first object being associated with a first contact in the plurality of contacts.

In accordance with some embodiments, the processing unit 2406 is further configured to, in further response to receiving a first input corresponding to a rotation of the rotatable input mechanism: stop associating the visual indicator with a first object among a plurality of objects; and associate the visual indicator with an object among the plurality of objects that is associated with a second contact among a plurality of contacts (e.g., using the associating unit 2412).

In accordance with some embodiments, the processing unit 2406 is further configured to, as part of a user interface, display (e.g., using the display enabling unit 2422) a visual indicator based on a position value that is within a range of position values, each of the multiple objects being associated with a position within the range of position values; and in response to a first input, determine (e.g., using the determining unit 2414) whether the first input is a request to update the position value of the position indicator to a second position value that is not associated with the object in the multiple objects; based on determining that the first input is a request to update the position value of the position indicator to a second position value that is not associated with the object in the multiple objects: update the position value of the time indicator to a third position value that corresponds to the position value of the object in the multiple objects that is closest to the second position value in the range of position values; and update the display of the visual indicator based on the third position value.

According to some embodiments, the processing unit 2406 is further configured to wherein stopping associating the visual indicator with the first object among multiple objects and associating the visual indicator with the second contact among multiple contacts includes: determining that rotation of the rotatable input mechanism does not cause the visual indicator to be associated with the second contact among multiple contacts; based on determining that rotation of the rotatable input mechanism does not cause the visual indicator to be associated with the second contact among multiple contacts, determining whether the position of the visual indicator is in an object conversion area, wherein the object conversion area is an area located after the first object and before the second object associated with the second contact; based on determining that the position of the visual indicator is in the object conversion area, associating the visual indicator with the second contact among multiple contacts; based on determining that the position of the visual indicator is in the object conversion area, maintaining the visual indicator in association with the first contact among multiple contacts.

In accordance with some embodiments, processing unit 2406 is further configured such that the visual indicator is a discrete area where one or more display colors of the available component are changed, and the method further includes: further in response to receiving a first input corresponding to a rotation of the rotatable input mechanism: changing (e.g., using changing unit 2424) the color of the visual indicator from a first color based on a color of a first object in a plurality of objects to a second color based on a color of a second object in a plurality of objects.

In accordance with some embodiments, processing unit 2406 is further configured to change (e.g., using changing unit 2424) a color of a visual indicator from a first color associated with a first object among a plurality of objects to a second color associated with a second contact among a plurality of contacts, including blending (e.g., using blending unit 2426) the first color and the second color as the visual indicator moves from a first position associated with the first object to a second position in front of a position of the second object associated with the contact.

According to some embodiments, the visual indicator is associated with a first object of the plurality of objects when the time indicator is in a first position overlapping at least a portion of the first object and one or more display colors of the first object are changed.

According to some embodiments, the processing unit 2406 is further configured to cease associating the visual indicator with a first object among a plurality of objects and to associate the visual indicator with a second contact among a plurality of contacts, including transitioning the visual indicator from a first position (e.g., using the transition unit 2428) to a second position that at least partially overlaps with the second object and one or more displayed colors of the second object are changed.

According to some embodiments, processing unit 2406 is further configured to: when the affordance represents a first contact, the visual appearance of the affordance is an animated representation of the first contact, and wherein updating the visual appearance of the affordance to represent a second contact among the plurality of contacts includes updating the visual appearance of the affordance to an animated representation of the second contact.

According to some embodiments, the processing unit 2406 is further configured to: the animated representation of the first contact is dynamically based on selecting information from the following group, including: time zone information of the second contact, location information of the second contact, information about the status specified by the second contact, and combinations thereof.

According to some embodiments, the processing unit 2406 is further configured to: after updating the visual appearance of the available component, receive a second input corresponding to a rotation of a third object of the multiple objects, where the third object is different from the first object and the second object, and in response to receiving the second input, update the visual appearance of the available component to represent the third contact among the multiple contacts.

According to some embodiments, processing unit 2406 is further configured to: after updating the visual appearance of the affordance, determine that no input has been received for the time period; and in response to determining that no input has been received for the time period, forgo displaying the plurality of objects.

According to some embodiments, processing unit 2406 is further configured to: after updating the visual appearance of the affordance, detect (e.g., with detection unit 2416) a third input corresponding to selection of the affordance; and in response to detecting the third input, relinquish display of the plurality of objects.

According to some embodiments, processing unit 2406 is further configured to: further in response to determining that no input has been received for the time period, display (eg, with display enabling unit 2422 ) a second affordance.

According to some embodiments, processing unit 2406 is further configured to: further in response to detecting the third input, display a second affordance.

According to some embodiments, the second affordance includes one or more affordances selected from the group consisting of: a call affordance, a message affordance, a coaching affordance, an affordance that restores a user interface including a plurality of objects, and a drawing affordance.

According to some embodiments, the second offer is a coaching offer, and the method further includes: detecting (e.g., using detection unit 2416) a fourth input corresponding to selecting the coaching offer; and in response to detecting the fourth input, displaying a user interface including one or more instructions for operating the electronic device.

According to some embodiments, the second affordance includes a drawing affordance, and processing unit 2406 is further configured to: detect a fifth input corresponding to selecting the drawing affordance; and in response to detecting the fifth input, display including a drawing area, wherein the drawing area is responsive to the touch input.

According to some embodiments, the processing unit 2406 is further configured to: detect a sixth input corresponding to the first stroke in the drawing area; and in response to detecting the sixth input, display a visual representation of the first stroke in the drawing area.

According to some embodiments, the processing unit 2406 is further configured to: also in response to detecting a sixth input, determine whether a first predetermined duration has passed after the sixth input; and based on determining that the first predetermined duration has passed after the sixth input, send data representing the first stroke (e.g., using the sending unit 2430) to an external device associated with the second contact.

According to some embodiments, the processing unit 2406 is further configured to: the sixth input corresponds to two or more strokes including the first stroke forming a painting, and the method further includes: also in response to detecting the sixth input, determining whether a first predetermined duration has passed after the sixth input; and based on determining that the first predetermined duration has passed after the sixth input, sending data representing the painting to an external device associated with the second contact.

According to some embodiments, processing unit 2406 is further configured to: the drawing area includes a drawing lock affordance that enables drawing only in the drawing area, the method further comprising detecting a seventh input corresponding to selecting the drawing lock affordance; in response to detecting the seventh input, disabling sending data representing any strokes in the drawing area; and replacing (e.g., with replacement unit 2418) the drawing lock affordance with a sending affordance that enables transmission of the drawing to an external device.

According to some embodiments, processing unit 2406 is further configured to: detect an eighth input corresponding to selecting the send affordance; and in response to detecting the eighth input, enable sending of data representing any stroke in the drawing area.

According to some embodiments, the electronic device includes one or more motion sensors, and the processing unit 2406 is further configured to: receive a ninth input corresponding to a stroke in the drawing area; in response to receiving the ninth input, display a visual representation of the stroke in the drawing area; detect a ninth input corresponding to movement of the electronic device; in response to detecting the ninth input, determine whether the movement of the electronic device satisfies a motion threshold, and stop displaying the visual representation of the stroke in response to detecting the ninth input and based on determining that the movement satisfies or exceeds the motion threshold.

According to some embodiments, the processing unit 2406 is further configured to: stop displaying the visual representation of the stroke comprises fading out (eg, using a fading unit 2432) the visual representation of the first stroke after a predetermined duration.

According to some embodiments, the processing unit 2406 is further configured to: receive an eleventh input representing a stroke in the drawing area; while receiving the eleventh input, display a residual animation dissipating along the stroke; display a visual representation of the stroke in the drawing area; and fade out the visual representation of the stroke from the drawing area, wherein fading out the visual representation includes displaying an animation of the stroke gradually dissipating.

According to some embodiments, processing unit 2406 is further configured to: further in response to determining that no input has been received for the time period, determine whether the contact currently represented by the affordance is associated with a device capable of processing and displaying data representing strokes in a drawing; display the drawing affordance based on determining that the contact currently represented by the affordance is associated with a device capable of processing and displaying data representing strokes in a drawing; and forgo displaying the drawing affordance based on determining that the contact currently represented by the affordance is not associated with a device capable of processing and displaying data representing strokes in a drawing.

According to some embodiments, the processing unit 2406 is further configured to: also in response to a third input, determine whether the contact currently represented by the affordance is associated with a device that can process and display data representing strokes in a painting; based on determining that the contact currently represented by the affordance is associated with a device that can process and display data representing strokes in a painting, display the drawing affordance; and based on determining that the contact currently represented by the affordance is not associated with a device that can process and display data representing strokes in a painting, abandon displaying the drawing affordance.

In accordance with some embodiments, the processing unit 2406 is further configured to: detect a twelfth input representing contact on the touch-sensitive display; determine that the continuation of the twelfth input meets or exceeds a contact duration threshold; record an audio message based on determining that the continuation of the twelfth input meets or exceeds the contact duration threshold; and send the audio message to an electronic device associated with a second contact.

According to some embodiments, the processing unit 2406 is further configured to: receive a thirteenth input representing a second rotation of the rotatable input mechanism; in response to receiving the thirteenth input, determine whether the visual indicator is close to an object that is not associated with any contact; and based on determining whether the visual indicator is close to an object that is not associated with any contact, update the display of the affordance to an add contact affordance.

According to some embodiments, the processing unit 2406 is further configured to: receive a fourteenth input corresponding to a selection to add a contact; and in response to receiving the fourteenth input, display a user interface for adding a contact.

According to some embodiments, the visual appearance of the affordance is a collection of initials of contacts representing the plurality of contacts or an image of a contact representing the plurality of contacts.

According to some embodiments, the set of initials is a monogram.

According to some embodiments, the plurality of objects includes 12 circular objects positioned around the affordance.

According to some embodiments, the processing unit 2406 is further configured to: determine that one or more messages received from one of the multiple contacts have not been read; and based on determining that one or more messages received from one of the multiple contacts have not been read, display an indicator of an object among the multiple objects associated with the one or more messages.

According to some embodiments, the indicator comprises an indication of a number of one or more unread messages.

According to some embodiments, each object in the plurality of objects includes a unique color scheme.

According to some embodiments, the visual indicator comprises a triangle that is movable with respect to the affordance.

According to some embodiments, each object in the plurality of objects includes a set of initials associated with a contact associated with the object.

According to some embodiments, the set of initials is a monogram.

According to some embodiments, each object of the plurality of objects is associated with an hour marking of a clock.

According to some embodiments, in order to display a user interface including multiple objects, the processing unit 2406 is also configured to display a user interface including page number indicators associated with a first page and a second page of the user interface, and the processing unit is further configured to: receive (for example, using the receiving unit 2408) an input corresponding to a request to display the second page; in response to receiving the input corresponding to the request to display the second page, replace the display of the first page with the second page (for example, using the replacing unit 2418), wherein the second page is different from the first page.

According to some embodiments, the second page includes a second object of the plurality of objects, each object being associated with a contact of the plurality of contacts.

According to some embodiments, a user interface is associated with the first page and a second user interface is associated with the second user interface, and wherein replacing display of the first page with the second page includes replacing the user interface with the second user interface.

According to some embodiments, the input is a swipe gesture on the touch-sensitive display.

According to some embodiments, Figure 25 shows an example functional block diagram of an electronic device 2500 configured according to the principles of various description embodiments. According to some embodiments, the functional block diagram of the electronic device 2500 is configured to perform the technology described above. The functional block diagram of the device 2500 is optionally implemented by hardware, software, or a combination of hardware and software to perform the principles of the various description examples. Those skilled in the art will appreciate that the functional block diagram described in Figure 25 is optionally combined or separated into sub-frames to implement the principles of the various description examples. Therefore, this document describes and optionally supports any possible combination or separation or further limitation of the functional blocks described above.

25 , electronic device 2500 includes a touch-sensitive display unit 2502, a rotatable input mechanism 2504, and a processing unit 2506 coupled to the touch-sensitive display unit 2502 and the rotatable input mechanism 2504. In some embodiments, processing unit 2506 includes a receiving unit 2508, an updating unit 2510, and a display enabling unit.

The processing unit 2406 is also configured to: display (e.g., using a display enabling unit) on the touch-sensitive display unit 2502 a user interface comprising a plurality of objects, each object being associated with a contact in a plurality of contacts and an affordance having a visual appearance representing a first contact in the plurality of contacts; receive (e.g., using a receiving unit 2508) a first input corresponding to selecting an object in the plurality of objects that is associated with a second contact in the plurality of contacts; and in response to receiving the input corresponding to a contact on an object in the plurality of objects, update (e.g., using an updating unit 2510) the visual appearance of the affordance to represent the second contact in the plurality of contacts.

For purposes of explanation, the foregoing description has been described with reference to specific embodiments. However, the discussion below the foregoing description is not intended to be exhaustive or to limit the invention to the precise form disclosed. Numerous modifications and variations are possible in light of the above teachings. The embodiments have been chosen and described to best illustrate the principles of these techniques and their practical applications. Others skilled in the art will thus be able to best utilize these techniques and various embodiments with various modifications as suited to the particular application contemplated.

Although the present disclosure and examples have been fully described with reference to the accompanying drawings, it should be noted that various changes and modifications will be apparent to those skilled in the art. Such changes and modifications should be understood to be included within the scope of the present disclosure and examples defined by the appended claims.

Claims (42)

1. An electronic device configured to communicate with an external device, the external device being associated with a contact, the electronic device comprising: a display unit configured to display a graphical user interface; a touch-sensitive surface unit configured to receive contact; and a processing unit coupled to the display unit and the touch-sensitive surface unit, the processing unit being configured to: receiving a user selection of a displayed affordance representing the contact; upon receiving the selection, detecting a touch input on the touch-sensitive display; Determine whether the touch input is a single-finger touch input or a multi-finger touch input; sending data to the external device based on determining that the touch input is a single-finger touch input, the data representing the single-finger touch input; and Based on determining that the touch input is a multi-touch input, sending data to the external device, wherein the data, when received by the external device, triggers the external device to display a visual indicator corresponding to the multi-touch input, further wherein: the data representing the single-finger touch input, when received by the external device, triggering the external device to display a visual representation different from the visual indicator without displaying the visual indicator; and The data representing the multi-touch input, when received by the external device, triggers the external device to display the visual indicator without displaying the visual representation. 2 . The electronic device of claim 1 , wherein the transmitted data, when received by the external device, triggers the external device to provide an output corresponding to the single-finger touch input. 3. The electronic device of claim 1 , wherein the transmitted data, when received by the external device, triggers the external device to display: receiving notification of said data; and An affordance that, when selected, causes the external device to display a visual representation of the single-finger touch input. 4. The electronic device according to claim 1, wherein in order to detect a touch input on the touch-sensitive display of the electronic device, the processing unit is further configured to detect the single-finger touch input at a position on the touch-sensitive display, and The visual representation of the single-finger touch input, when displayed, is displayed on the screen of the external device at a location corresponding to the position where the single-finger touch input is detected. 5 . The electronic device of claim 1 , wherein the visual representation comprises one or more circles, ellipses, and/or ovals. 6 . The electronic device of claim 1 , wherein the visual representation comprises two or more concentric circles, ellipses, and/or ovals. 7 . The electronic device of claim 1 , wherein the visual representation on the external device fades out after being displayed for a predetermined amount of time. The electronic device of claim 1 , wherein the single-finger touch input is a single-finger tap. 9. The electronic device according to claim 1, wherein the processing unit is further configured to: Based on a determination that the detected touch input represents a multi-touch input, data is sent to the external device, wherein the sent data, when received by the external device, triggers the external device to display the visual indicator for continuation of the multi-touch input. 10. The electronic device of claim 1 , wherein the transmitted data, when received by the external device, triggers the external device to provide an output corresponding to the multi-touch input, and wherein the output corresponding to the multi-touch input comprises: notification of receipt of said data; and An affordance that, when selected, causes the processing unit to enable display of the visual indicator for continuation of the multi-touch input. The electronic device of claim 9 , wherein the visual indicator is an image. 12. The electronic device of claim 9, wherein the visual indicator is an animated image. 13. The electronic device of claim 9, wherein the visual indicator is an animated image of a beating heart. 14 . The electronic device of claim 13 , wherein the electronic device further comprises a biosensor configured to detect a heartbeat rate, wherein the rate of the beating of the beating heart is based on the detected heartbeat rate. 15. An electronic device according to claim 13, wherein the electronic device further comprises a biosensor configured to detect a heartbeat rate, wherein the transmitted data, when received by the external device, triggers the external device to provide a tactile output corresponding to the detected heartbeat rate. 16. The electronic device of claim 1, wherein the transmitted data, when received by the external device, triggers the external device to provide a tactile output. 17. The electronic device of claim 1 , wherein the electronic device comprises a rotatable input mechanism, wherein to receive a user selection of the contact, the processing unit is further configured to: enabling display of multiple affordances representing contacts; detecting user input representing movement of the rotatable input mechanism; and In response to detecting the user input: enabling scaling of the display of a plurality of user-specified contacts, wherein scaling the display includes changing a size of the contacts being displayed. 18 . The electronic device of claim 17 , wherein to enable scaling of the display, the processing unit is further configured to enable a change in the number of contacts being displayed. 19. The electronic device according to claim 17, wherein the processing unit is further configured to: While enabling display of the plurality of affordances representing contacts, detecting touch input on the displayed affordances; and In response to detecting the touch input, data is sent to the external device associated with the contact, wherein the sent data, when received by the external device, triggers the external device to provide a tactile output. 20. An electronic device according to claim 19, wherein to detect the touch input on the displayed affordance, the processing unit is further configured to detect a first touch and release on the displayed affordance followed by a second touch and release on the displayed affordance within a predetermined duration. 21. A communication method, comprising: The following steps are performed at an electronic device having a touch-sensitive display, the electronic device being configured to communicate with an external device, the external device being associated with a contact: receiving a user selection of a displayed affordance representing the contact; upon receiving the selection, detecting a touch input on the touch-sensitive display; Determine whether the touch input is a single-finger touch input or a multi-finger touch input; Based on a determination that the touch input is a single-finger touch input, sending data to the external device, the data representing the single-finger touch input; and Based on a determination that the touch input is a multi-touch input, sending data to the external device, wherein the data, when received by the external device, triggers the external device to display a visual indicator corresponding to the multi-touch input, further wherein: the data representing the single-finger touch input, when received by the external device, triggering the external device to display a visual representation different from the visual indicator without displaying the visual indicator; and The data representing the multi-touch input, when received by the external device, triggers the external device to display the visual indicator without displaying the visual representation. 22. The communication method of claim 21, wherein the transmitted data, when received by the external device, triggers the external device to provide an output corresponding to the single-finger touch input. 23. The communication method of claim 21 , wherein the transmitted data, when received by the external device, triggers the external device to display: receiving notification of said data; and An affordance that, when selected, causes the external device to display a visual representation of the single-finger touch input. 24. The communication method according to claim 21, Wherein detecting a touch input on the touch-sensitive display of the electronic device comprises: detecting the single-finger touch input at a position on the touch-sensitive display, and The visual representation of the single-finger touch input, when displayed, is displayed on the screen of the external device at a location corresponding to the position where the single-finger touch input is detected. 25. The communication method of claim 21, wherein the visual representation comprises one or more circles, ellipses and/or ovals. 26. The communication method of claim 21, wherein the visual representation comprises two or more concentric circles, ellipses and/or ovals. 27. The communication method of claim 21, wherein the visual representation on the external device fades out after being displayed for a predetermined amount of time. 28. The communication method of claim 21, wherein the single-finger touch input is a single-finger tap. 29. The communication method according to claim 21, further comprising: Based on a determination that the detected touch input represents a multi-touch input, data is sent to the external device, wherein the sent data, when received by the external device, triggers the external device to display the visual indicator for continuation of the multi-touch input. 30. The communication method of claim 21 , wherein the transmitted data, when received by the external device, triggers the external device to provide an output corresponding to the multi-touch input, and wherein the output corresponding to the multi-touch input comprises: notification of receipt of said data; and An affordance that, when selected, causes the external device to enable display of the visual indicator for continuation of the multi-touch input. 31. The communication method of claim 29, wherein the visual indicator is an image. 32. The communication method of claim 29, wherein the visual indicator is an animated image. 33. The communication method of claim 29, wherein the visual indicator is an animated image of a beating heart. 34. The communication method of claim 33, wherein the electronic device further comprises a biosensor configured to detect a heartbeat rate, wherein the rate of the beating of the beating heart is based on the detected heartbeat rate. 35. A communication method according to claim 33, wherein the electronic device further includes a biosensor configured to detect a heartbeat rate, wherein the transmitted data, when received by the external device, triggers the external device to provide a tactile output corresponding to the detected heartbeat rate. 36. The communication method of claim 21, wherein the transmitted data, when received by the external device, triggers the external device to provide a tactile output. 37. The communication method of claim 21 , wherein the electronic device includes a rotatable input mechanism, wherein receiving a user selection of the contact comprises: At the electronic device: displaying multiple affordances representing contacts; detecting user input representing movement of the rotatable input mechanism; and In response to detecting the user input: scaling the display of a plurality of user-specified contacts, wherein scaling the display includes changing a size of the contacts being displayed. 38. The communication method of claim 37, wherein scaling the display comprises changing the number of contacts being displayed. 39. The communication method according to claim 37, further comprising: While displaying the plurality of affordances representing contacts, detecting touch input on the displayed affordances; and In response to detecting the touch input, data is sent to the external device associated with the contact, wherein the sent data, when received by the external device, triggers the external device to provide a tactile output. 40. The communication method of claim 39, wherein detecting the touch input on the displayed affordance comprises detecting a first touch and release on the displayed affordance followed by a second touch and release on the displayed affordance within a predetermined duration. 41. An electronic device comprising means for executing the communication method according to any one of claims 21 to 40. 42. A computer readable medium having stored thereon computer readable instructions which, when executed, cause a device to perform the communication method according to any one of claims 21 to 40.