HK1220525B - Reduced-size interfaces for managing alerts - Google Patents

Description

Reduced size interface for managing alerts

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent Application No. 62/044,894, filed on September 2, 2014, entitled “Reduced-Size Interfaces For Managing Alerts,” and to U.S. Provisional Patent Application No. 62/129,818, filed on March 7, 2015, entitled “Reduced-Size Interfaces For Managing Alerts.” The contents of these applications are incorporated herein by reference for all purposes.

This application is related to co-pending U.S. Provisional Patent Application No. 62/129,924, filed on March 8, 2015, entitled “Reduced-Size Notification Interface,” U.S. Provisional Patent Application No. 62/044,953, filed on September 2, 2014, entitled “Reduced-Size Notification Interface,” U.S. Provisional Patent Application No. 62/129,903, filed on March 8, 2015, entitled “User Interface For Receiving User Input,” U.S. Provisional Patent Application No. 62/127,800, filed on March 3, 2015, entitled “User Interface For Receiving User Input,” U.S. Provisional Patent Application No. 62/044,923, filed on September 2, 2014, entitled “User Interface For Receiving User Input,” and U.S. Provisional Patent Application No. 62/129,903, filed on March 8, 2015, entitled “User Interface For Receiving User Input.” and U.S. Provisional Patent Application No. 62/026,532, filed on May 8, 2013, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” International Patent Application No. PCT/US2013/040061, filed on May 8, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” and U.S. Provisional Patent Application No. 62/044,894, filed on September 2, 2014. The contents of these applications are incorporated herein by reference in their entirety.

Technical Field

The disclosed examples generally relate to user interfaces for electronic devices.

Background Art

A reduced-size electronic device configured to be worn by a user (e.g., a device smaller than a typical cellular telephone) can allow the user to view and respond to various types of alerts, such as text messages, emails, voicemails, and calendar alerts. A user interface that enables the reduced-size electronic device to be efficiently used to view and respond to alerts is desirable.

Summary of the Invention

According to some embodiments, a method is performed at an electronic device having a display. The method includes receiving an alert including information and, in response to receiving the alert, issuing a sensory output. The method includes detecting a user input and determining whether the user input is detected within a predetermined time interval after the sensory output. The method includes, based on determining that the user input is detected within the predetermined time interval, displaying a notification on the display, wherein the notification includes a first portion of the information.

According to some embodiments, a method is performed at an electronic device having a display. The method includes receiving a first alert and a second alert. The method includes, in response to receiving the first alert and the second alert, determining whether the first alert and the second alert meet a grouping criterion. The method includes, in response to determining that the first alert and the second alert meet the grouping criterion, displaying a notification indicating a grouping of the first alert and the second alert. The method includes, in response to determining that the first alert and the second alert do not meet the grouping criterion, displaying a first notification indicating the first alert and replacing the display of the first notification with the display of the second notification indicating the second alert.

In accordance with some embodiments, a method is performed at an electronic device that is actively displaying content. The method includes receiving an alert that includes information. The method includes, in response to receiving the alert, displaying a notification banner across a portion of a display, wherein the notification banner includes a first portion of the information and wherein at least a portion of the content continues to be displayed. The method includes detecting a contact at a location on the display corresponding to the notification banner, and in response to detecting the contact, displaying a second portion of the information, wherein the second portion is different from the first portion.

According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs including instructions is disclosed. The instructions, when executed by one or more processors of an electronic device having a display, cause the electronic device to: receive an alert including information; in response to receiving the alert, issue a sensory output; detect user input; determine whether the user input is detected within a predetermined time interval after the sensory output; and, based on determining that the user input is detected within the predetermined time interval, display a notification on the display, wherein the notification includes a first portion of the information.

According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs including instructions is disclosed. The instructions, when executed by one or more processors of an electronic device having a display, cause the electronic device to: receive a plurality of alerts; in response to receiving the plurality of alerts, determine whether the plurality of alerts meet a grouping criterion; in response to determining that the plurality of alerts meet the grouping criterion, display a notification representing a grouping of the plurality of alerts; and in response to determining that the plurality of alerts do not meet the grouping criterion, display a plurality of notifications representing the plurality of alerts.

In accordance with some embodiments, a non-transitory computer-readable storage medium storing one or more programs including instructions is disclosed. The instructions, when executed by one or more processors of an electronic device with a touch-sensitive display, cause the electronic device to: while actively displaying content, receive an alert including information; in response to receiving the alert, display a notification banner across a portion of the display, wherein the notification banner includes a first portion of the information and wherein at least a portion of the content continues to be displayed; detect a contact on the touch-sensitive display at a location corresponding to the notification banner; and in response to detecting the contact, display a second portion of the information, wherein the second portion is different from the first portion.

According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs including instructions is disclosed. The instructions, when executed by one or more processors of an electronic device having a display, cause the electronic device to: receive an alert including information; in response to receiving the alert, issue a sensory output; detect user input; determine whether the user input is detected within a predetermined time interval after the sensory output; and, based on determining that the user input is detected within the predetermined time interval, display a notification on the display, wherein the notification includes a first portion of the information.

According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs including instructions is disclosed. The instructions, when executed by one or more processors of an electronic device having a display, cause the electronic device to: receive a plurality of alerts; in response to receiving the plurality of alerts, determine whether the plurality of alerts meet a grouping criterion; in response to determining that the plurality of alerts meet the grouping criterion, display a notification representing a grouping of the plurality of alerts; and in response to determining that the plurality of alerts do not meet the grouping criterion, display a plurality of notifications representing the plurality of alerts.

In accordance with some embodiments, a non-transitory computer-readable storage medium storing one or more programs including instructions is disclosed. The instructions, when executed by one or more processors of an electronic device with a touch-sensitive display, cause the electronic device to: while actively displaying content, receive an alert including information; in response to receiving the alert, display a notification banner across a portion of the display, wherein the notification banner includes a first portion of the information and wherein at least a portion of the content continues to be displayed; detect a contact on the touch-sensitive display at a location corresponding to the notification banner; and in response to detecting the contact, display a second portion of the information, wherein the second portion is different from the first portion.

An electronic device comprises: a display; one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, the one or more programs comprising instructions for: receiving an alert comprising information, and in response to receiving the alert, issuing a sensory output; detecting user input and determining whether the user input is detected within a predetermined time interval after the sensory output; and displaying a notification on the display based on determining that the user input is detected within the predetermined time interval, wherein the notification comprises a first portion of the information.

An electronic device comprises: a display; one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include instructions for: receiving a first alarm and a second alarm, and in response to receiving the first alarm and the second alarm, determining whether the first alarm and the second alarm meet a grouping criterion; in response to determining that the first alarm and the second alarm meet the grouping criterion, displaying a notification representing the grouping of the first alarm and the second alarm; in response to determining that the first alarm and the second alarm do not meet the grouping criterion, displaying a first notification representing the first alarm, and replacing the display of the first notification with the display of the second notification representing the second alarm.

An electronic device comprising: a touch-sensitive display; one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, the one or more programs comprising instructions for: receiving an alert comprising information and, in response to receiving the alert, displaying a notification banner across a portion of the display, wherein the notification banner comprises a first portion of the information and wherein at least a portion of the content continues to be displayed; detecting contact at a location on the display corresponding to the notification banner; and, in response to detecting the contact, displaying a second portion of the information, wherein the second portion is different from the first portion.

Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program products configured for execution by one or more processors. Executable instructions for performing these functions are optionally included in a transient computer-readable storage medium or other computer program products configured for execution by one or more processors.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various embodiments described, reference should be made to the following description of the embodiments in conjunction with the following drawings, in which like reference numerals refer to 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.

FIG5C illustrates contact detection using an intensity sensor.

FIG5D illustrates the assignment of polymerization strengths to contacts.

5E-5H illustrate detection of gestures with contact intensity.

6A-6C illustrate exemplary user interfaces.

FIG7 illustrates an exemplary user interface.

FIG8 illustrates an exemplary user interface.

FIG9 illustrates an exemplary user interface.

FIG10 illustrates an exemplary user interface.

FIG11 illustrates an exemplary user interface.

12A-C illustrate exemplary user interfaces.

13A-B illustrate exemplary user interfaces.

FIG14 illustrates an exemplary user interface.

FIG15 illustrates an exemplary user interface.

FIG16 illustrates an exemplary user interface.

FIG17 illustrates an exemplary user interface.

FIG18 illustrates an exemplary user interface.

FIG19 illustrates an exemplary user interface.

FIG20 illustrates an exemplary user interface.

FIG21 illustrates an exemplary user interface.

FIG22 illustrates an exemplary user interface.

23A-23C illustrate exemplary user interfaces.

FIG24 illustrates an exemplary user interface.

FIG. 25 illustrates an exemplary process for managing alerts.

FIG. 26 illustrates an exemplary process for managing alerts.

FIG. 27 illustrates an exemplary process for managing alerts.

28-31 illustrate exemplary functional block diagrams of electronic devices in accordance with some embodiments.

DETAILED DESCRIPTION

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

As discussed above, a reduced-size personal electronic device configured to be worn by a user can enable the user to view and respond to various alerts, such as text messages, emails, voicemails, audio messages, stock alerts, alarms, calendar alerts, fitness alerts, store coupons, or loyalty program alerts, for example, via a user interface. However, there are several challenges associated with viewing and responding to alerts on a reduced-size device. For example, user interface approaches designed for larger screens may not function properly on an electronic device with a reduced-size screen. For example, a smaller screen size may make it challenging to read text associated with an alert or provide accurate input to a touch screen. There may not be enough screen space to display detailed device usage instructions, so it is important to make the user interface intuitive to learn and use. Limited screen size may make it impractical to display multiple tiled screens; therefore, replacing one screen with another and limiting the amount of information displayed on a single screen may be a more effective user interface strategy.

In addition to the above usability concerns, there may be privacy concerns if the reduced-size electronic device is worn externally by the user (e.g., by attaching it to a shirt, belt, bracelet, or necklace) rather than being carried in a pocket, suitcase, or purse as is common with larger electronic devices such as cell phones or laptop computers. The user may be concerned that others nearby will be able to view the alert, so it may be desirable that such a user interface allows the user to control when the alert content is displayed and how much alert content is displayed. In addition, if the device is worn by the user and is therefore in closer contact with the user than, for example, a cell phone, it may be desirable that such a user interface does not interfere with the user through frequent interruptions. Ideally, the user interface should make it quick, easy, and intuitive for the user to view and respond to alerts on the reduced-size personal electronic device. Such technology can reduce the cognitive load on the user using the alert, thereby improving productivity. Further, such technology can reduce processor and battery power that would otherwise be wasted on redundant user input.

Below, Figures 1A-1B, 2, 3, 4A-4B, and 5A-5B provide descriptions of exemplary devices for performing techniques for managing alert notifications. Figures 6A-24 illustrate exemplary user interfaces for managing alert notifications. The user interfaces in the figures are also used to illustrate the processes described below, including the processes in Figures 25-27.

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 may be referred to as a second touch, and similarly, a second touch may be referred to as a first touch, without departing from the scope of the various embodiments described. Both the first touch and the second touch are touches, but they are not the same touch.

The technical terms used in the description of the various embodiments described herein are only for the purpose of describing specific embodiments and are not intended to be limiting. As used in the description of the various embodiments described and in the appended claims, the singular forms "a" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the terms "and/or" used herein refer to and include any and all possible combinations of one or more items in the associated listed items. It will be further understood that the terms "comprises," "comprising," and/or "containing" when used in this specification specify the presence of stated features, integers, steps, operations, elements, and/or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts, and/or groups thereof.

The term "if" may be understood 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 understood to mean "upon determining" 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.

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, which 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, the iPod from Apple Inc. of Cupertino, California, and optionally other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads). 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 electronic device can optionally include one or more 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: a drawing application, a presentation application, a word processing application, a website creation application, a disk creation 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 camcorder 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 a corresponding application. In this way, the common physical architecture of the device (such as a touch-sensitive surface) optionally supports a variety of applications with user interfaces that are intuitive and transparent to the user.

Attention is now directed to embodiments of portable devices with touch-sensitive displays. Figure 1A 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" for convenience, and is sometimes referred to as or referred to as a "touch-sensitive display system." Device 100 has memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input/output (I/O) subsystem 106, other input 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 intensity of contact on device 100 (e.g., a touch-sensitive surface such as the 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 355 of device 300). These components optionally communicate via 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 a surrogate (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). Various approaches and various sensors or combinations of sensors are optionally used to determine (measure) the intensity of a contact. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure the force at various points on the touch-sensitive surface. In some embodiments, the force measurements from multiple force sensors are combined (e.g., weighted averaged) 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 the contact area detected on the touch-sensitive surface and/or its change, the capacitance of the touch-sensitive surface in proximity to the contact and/or its change, and/or the resistance of the touch-sensitive surface in proximity to the contact and/or its change are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the surrogate measurement for contact force or pressure is used directly to determine whether a lightness threshold has been exceeded (e.g., an intensity threshold described in units corresponding to the surrogate measurement). In some embodiments, the surrogate measurement for contact force or pressure is converted to an estimated force or pressure, and the estimated force or 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 the intensity of the contact as an attribute of the user input allows for user access to additional device functionality that might otherwise not be accessible to the user on a reduced size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) 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 will be 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 perceived change in a physical property of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally 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 that is physically pressed (e.g., displaced) by the user's movement. As another example, movement of the touch-sensitive surface may, optionally, be interpreted or sensed by the user as "roughness" of the touch-sensitive surface even in the absence of a change in the smoothness of the touch-sensitive surface. While such interpretation of touch by a user will be subject to the user's individualized sensory perception, 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 that would generate 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 incorporate two or more components, or may alternatively have a different configuration or arrangement of components. The various components shown in FIG1A are implemented in hardware, including one or more signal processing and/or application specific integrated circuits, software, or a combination of both hardware and software.

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.

Peripherals interface 118 may be used to couple the device's input and output peripherals 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 process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 may be implemented on a single chip, such as chip 104. In some other embodiments, they may 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 communication network and other communication devices via the electromagnetic signals. RF circuitry 108 optionally includes well-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 with networks such as the Internet, also known as the World Wide Web (WWW), wireless networks such as cellular telephone networks, wireless local area networks (LANs), and/or metropolitan area networks, as well as with other devices via wireless communications. RF circuitry 108 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via short-range communication radios. The wireless communication may optionally use any of a number of communication standards, protocols and techniques, 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). 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 with Extensions for Instant Messaging and Presence (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 yet been developed as of the filing date of this document.

The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between the user and the device 100. The audio circuit 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 that can be heard by the human ear. The audio circuit 110 also receives an electrical signal converted from the sound wave by the microphone 113. The audio circuit 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 retrieved from the memory 102 and/or the RF circuit 108 by the peripheral device interface 118 and/or transmitted to the memory 102 and/or the RF circuit 108. In some embodiments, the audio circuit 110 also includes a headphone jack (e.g., 212 in FIG. 2). The headphone jack provides an interface between the audio circuit 110 and a detachable audio input/output peripheral (such as a headset with only output or a headset with output (e.g., headset for one or both ears) and input (e.g., microphone)).

The I/O subsystem 106 couples input/output peripherals on the device 100, such as the touch screen 112 and other input control devices 116, to the 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 electrical signals from or send electrical signals to the other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, wave buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, the input controllers 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 FIG. 2 ) 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 (eg, 206 of FIG. 2 ).

As described in U.S. Patent Application No. 11/322,549, filed December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," and U.S. Patent No. 7,657,849, which are incorporated herein by reference in their entirety, 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. A longer press of the push button (e.g., 206) can turn 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 buttons.

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 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, video, and any combination thereof (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 collection of sensors that accepts input from a user based on tactile and/or haptic 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 the display controller 156 may use any of a number of touch sensing technologies now known or developed in the future, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 112, to detect contact and any movement or interruption thereof. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that used in the iPhone and iPod Touch from Apple Inc. of Cupertino, California.

In some embodiments of 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, touch screen 112 displays visual output from device 100, whereas a touch-sensitive touchpad does not provide visual output.

In some embodiments of the touch screen 112, the touch-sensitive display may be as described in the following U.S. applications: (1) U.S. patent application Ser. No. 11/381,313, filed May 2, 2006, entitled “Multipoint Touch Surface Controller”; (2) U.S. patent application Ser. No. 10/840,862, filed May 6, 2004, entitled “Multipoint Touchscreen”; (3) U.S. patent application Ser. No. 10/903,964, filed July 30, 2004, entitled “Gestures For Touch Sensitive Input Devices”; (4) U.S. patent application Ser. No. 11/048,264, filed January 31, 2005, entitled “Gestures For Touch Sensitive Input Devices”; (5) U.S. patent application Ser. No. 11/086,694, filed January 18, 2005, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive Input No. 11/038,590, entitled “Virtual Input Device Placement On A Touch Screen User Interface,” filed on September 16, 2005; (6) U.S. patent application No. 11/228,758, entitled “Virtual Input Device Placement On A Touch Screen User Interface,” filed on September 16, 2005; (7) U.S. patent application No. 11/228,700, entitled “Operation Of A Computer With A Touch Screen Interface,” filed on September 16, 2005; (8) U.S. patent application No. 11/228,737, entitled “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed on September 16, 2005; and (9) U.S. patent application No. 11/367,749, entitled “Multi-Functional Hand-Held Device,” filed on March 3, 2006. 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 contact the touch screen 112. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device converts the rough finger-based input into a precise pointer/cursor position or command for performing the action desired by the user.

In some embodiments, in addition to the touch screen, device 100 may 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, unlike a touch screen, does not display visual output. 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.

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

Device 100 may also include one or more optical sensors 164. Figure 1A shows an optical sensor coupled to optical sensor controller 158 in I/O subsystem 106. Optical sensor 164 may include a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Optical sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. In conjunction with imaging module 143 (also known as a camera module), optical sensor 164 can capture still images or video. In some embodiments, the optical sensor is located on the back of device 100, opposite 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 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 for both video conferencing and still and/or video image acquisition, along with the touchscreen display.

Device 100 optionally also includes one or more contact force sensors 165. Figure 1A shows a contact force sensor coupled to force sensor controller 159 of I/O subsystem 106. Contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical 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 sensor 165 receives contact force information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact force sensor is co-located with or adjacent 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 controller 160 in I/O subsystem 106. Proximity sensor 166 may be implemented as described in U.S. patent application Ser. Nos. 11/241,839, “Proximity Detector In Handheld Device,” 11/240,788, “Proximity Detector In Handheld Device,” 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output,” 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices,” and 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 placed 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. FIG1A shows a tactile output generator coupled to 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 outputs on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is co-located with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112) and optionally generates tactile outputs by moving the touch-sensitive surface vertically (e.g., inward/outward of the surface of device 100) or laterally (e.g., 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 .

The device 100 may also include one or more accelerometers 168. FIG1A shows an accelerometer 168 coupled to the peripherals interface 118. Alternatively, the accelerometer 168 may be coupled to the input controller 160 in the I/O subsystem 106. The accelerometer 168 may implement as described in U.S. Patent Publication No. 2005/0190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 2006/0017692, “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 the one or more accelerometers. In addition to accelerometer 168 , device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information about the position and orientation (e.g., portrait or landscape) of 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 applications (or instruction sets) 136. In addition, in some embodiments, as shown in Figures 1A and 3, memory 102 (Figure 1A) or 370 (Figure 3) stores device/global internal state 157. The device/global internal state 157 includes one or more of the following: active application state, indicating which applications, if any, are currently active; display state, indicating which applications, views, or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and location information regarding the device's position and/or posture.

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 common system tasks (e.g., memory management, storage device control, power management, etc.) and facilitating communication between various hardware and software components.

The communication module 128 facilitates communication with other devices through one or more external ports 124 and also includes various software components for processing data received by the RF circuitry 108 and/or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling to other devices directly or indirectly through 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 Apple (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 touch detection, 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 surrogate for the 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 a break in the contact). The contact/motion module 130 receives contact data from the touch-sensitive surface. The movement of the contact point, represented by a series of contact data, is determined, optionally including determining the velocity (magnitude), rate (magnitude and direction), and/or acceleration (change in magnitude and/or direction) of the contact point. These operations optionally apply to a single point of contact (e.g., a single finger contact) or multiple simultaneous points of contact (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" on an icon). In some embodiments, a subset of the intensity thresholds is determined based on at least a software parameter (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator and can be adjusted without changing the physical hardware device 100). For example, a mouse "click" threshold for a touchpad or touchscreen display can be set to any predetermined threshold in a wide range of predetermined thresholds without changing the touchpad or touchscreen display hardware. In addition, in some embodiments, a software setting is provided to a user of the device for adjusting one or more intensity thresholds in the set of intensity thresholds (e.g., by adjusting a single intensity threshold and/or by adjusting multiple intensity thresholds at once using a system-level click "intensity" parameter).

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 motion, timing, and/or intensity of the detected contact). 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 (liftoff) event at the same location (or substantially the same location) as the finger down event (e.g., at the location of an icon). As another example, detecting a finger sweep gesture on the touch-sensitive surface includes detecting a finger down event followed by detecting one or more finger drag events, and then followed by detecting a finger up (liftoff) 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 impact (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 as 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 167 to produce tactile output at one or more locations in response to user interaction with device 100 .

The text input module 134, which may be a component of the graphics module 132, provides a soft keyboard for entering text in 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 in various applications (e.g., to the phone 138 for 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: weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5 and other widgets acquired by the user, and user-created widget 149-6;

A widget creator module 150 for making user-created widgets 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 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the optical sensor controller 158, the touch/motion module 130, the graphics module 132, the text input module 134, the contacts 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, contact/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 the corresponding instant message (e.g., using the 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 phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In combination with the RF circuitry 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, marking, 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 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 circuitry 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 calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.

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

In combination with the RF circuitry 108, touch screen 112, display controller 156, touch/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 can 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, videos 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, the display controller 156, the contact/motion module 130, the graphics module 132, and the 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 circuitry 108, touch screen 112, display controller 156, touch/motion module 130, graphics module 132, text input module 134, GPS module 135, and 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 U.S. provisional 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 executable 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, and therefore 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 that are specifically performed via the touch screen and/or touchpad optionally includes navigation between user interfaces. In some embodiments, when touched by the user, the touchpad 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.

Figure 1B is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 (Figure 1A) or memory 370 (Figure 3) 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 event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes 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 the currently active application(s), 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 ready 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 performed 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 circuit 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 occurs 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 the view or views in the view hierarchy that 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 the particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that comprise the physical location of the sub-event are actively involved views, and therefore determines that all actively involved views should receive the 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 involved 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 application's user interface. 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, each 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's internal state 192. Alternatively, one or more of 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 speed 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 the event information with predefined event or sub-event definitions and, based on the comparison, determines the event or sub-event, or determines or updates the state of the 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 user interface object (if any) 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 the event handler 190 that 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 each 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 each event recognizer 180 determines that the 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, each event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to the effectively involved 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, each event recognizer 180 activates an event handler 190 associated with the event when one or more sub-events of the event are recognized. In some embodiments, each 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 a valid view. The event handler associated with the series of sub-events or the valid 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 combined 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; verbal commands; detected eye movements, biometric input; and/or any combination of the foregoing, are optionally used as input corresponding to defining a sub-event to be recognized.

FIG2 illustrates a portable multifunction device 100 with a touch screen 112 in accordance with 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 203 (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, right to left, upward, and/or downward), and/or rolling of a finger that is already in contact with the device 100 (from right to left, left to right, upward, and/or downward). In some implementations or circumstances, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps across an application icon may 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 one embodiment, 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 verbal 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 does not need to 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 gaming device or a control device (for example, 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 (sometimes referred to as a chipset) for interconnecting and controlling communication between system components. Device 300 includes an input/output interface 330 containing a display 340 (which is typically a touch screen display). I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and a 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 optionally includes 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. 1A ). In addition, 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 creation 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 rearranged in various embodiments.In certain embodiments, memory 370 can store a subset of 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 indicator(s) 402 for wireless communication(s), such as cellular signals and Wi-Fi signals;

Time 404;

Bluetooth indicator 405;

Battery status indicator 406;

A 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 of the email client module 140, labeled "Mail," which optionally includes an indicator 410 of the number of unread emails;

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

o Icon 422 of 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 apps, such as:

o Icon 424 of the IM module 141, labeled "Messages";

o an icon 426 of the calendar module 148, labeled "Calendar";

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

o Icon 430 of camera module 143, labeled “Camera”;

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

o Icon 434 of the stock widget 149-2, labeled "Stocks";

o an icon 436 of the map module 154, labeled "Map";

o an icon 438 for the weather widget 149-1, labeled "Weather";

o an icon 440 for the alarm clock widget 149-4, labeled "Clock";

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

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

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

It should be understood that the icon labels shown in FIG4A are exemplary only. For example, the icon 422 of the 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 of a respective application icon includes the application name corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the application name 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, 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 (e.g., 450 in FIG4B ) 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 respect to finger inputs (e.g., finger contacts, finger tap gestures, finger sweep gestures), 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 sweep gesture is optionally replaced by a mouse click (e.g., instead of contact) followed by moving the cursor along the sweep 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 a mouse 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 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 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 a touch based on its intensity, 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 related applications: International Patent Application 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 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, 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, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can allow 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 device 500 to be worn by a 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, 1B, and 3. 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, an intensity sensor 524 (e.g., a contact intensity sensor). 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. Personal electronic device 500 can also include a haptic mechanism 542. Haptic mechanism 542 can emit a vibration or other tactile output that can be perceived by the user. In some embodiments, haptic mechanism 542 can emit tactile output in a manner similar to that described for tactile output generator 167 of device 100.

The memory 518 of the personal electronic device 500 can be a non-transient 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 2500-2700 (Figures 25-27). Computer-executable instructions can also be stored and/or transmitted in any non-transient computer-readable storage 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-transient 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-transient computer-readable storage media can include, but are not limited to, magnetic storage, optical storage, and/or semiconductor storage. Examples of such storage 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 can 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 device 100, device 300, and/or device 500 (Figures 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 and other positioning markers, 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 element is adjusted based on the detected input. In some implementations that include a touch screen display that enables direct interaction with user interface elements on the touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4A ), a contact detected 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 the user interface without corresponding movement of a cursor or contact on the touchscreen display (e.g., by using the tab key or arrow keys to move focus from one button to another); in these implementations, a focus selector moves in accordance with the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, a focus selector is generally a user interface element (or contact on the touchscreen display) that is controlled by a user 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 is intending to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of a focus selector (e.g., a cursor, contact, or selection box) on a corresponding button will indicate that the user is intending to activate the corresponding button (as opposed to 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 the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) in association with a predetermined event (e.g., after the contact is detected, before the lift-off of the contact is detected, before or after the start of the movement of the contact is detected, before the end of the contact is detected, before or after an increase in the intensity of the contact is detected, and/or before or after a decrease in the intensity of the contact is detected). 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, a median value of the intensity of the contact, an average value of the intensity of the contact, a value in the top 10% of the intensity of the contact, a value at half the maximum of the intensity of the contact, a value at 90% the maximum 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 of the intensity of the contact over time). In some embodiments, the feature intensity is compared to one or more intensity thresholds to determine whether the user has performed an operation. 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 feature intensity that does not exceed the first threshold results in a first operation, a contact with a feature intensity that exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second operation, and a contact with a feature intensity that exceeds the second threshold results in a third operation. In some embodiments, the comparison between the feature 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), rather than being used to determine whether to perform the first operation or the second operation.

Figure 5C illustrates detecting multiple contacts 552A-552E on touch-sensitive display screen 504 using multiple intensity sensors 524A-524D. Figure 5C additionally includes an intensity graph showing the current intensity measurements of intensity sensors 524A-524D relative to intensity units. In this example, the intensity measurements of intensity sensors 524A and 524D are each 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are each 7 intensity units. In some implementations, the aggregate intensity is the sum of the intensity measurements of multiple intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a corresponding intensity as part of the aggregate intensity. Figure 5D illustrates assigning aggregate intensity to contacts 552A-552E based on their distance from force center 554. In this example, each of contacts 552A, 552B, and 552E is assigned a contact strength of 8 strength units of the aggregate strength, and each of contacts 552C and 552D is assigned a contact strength of 4 strength units of the aggregate strength. More generally, in some implementations, each contact j is assigned a corresponding strength Ij as a portion of the aggregate strength A according to a predetermined mathematical equation Ij=A·(Dj/ΣDi), where Dj is the distance of the corresponding contact j to the force center, and ΣDi is the sum of the distances of all corresponding contacts (e.g., i=1 to the last) to the force center. The operations described with respect to Figures 5C-5D can be performed using an electronic device similar to or the same as device 100, 300, or 500. In some embodiments, the characteristic strength of a contact is based on one or more contact strengths. In some embodiments, a strength sensor is used to determine a single characteristic strength (e.g., a single characteristic strength of a single contact). It should be noted that the strength graph is not part of the displayed user interface, but is included in Figures 5C-5D to assist the reader.

In some embodiments, portions of a gesture are identified for the purpose of determining characteristic strength. For example, a touch-sensitive surface may receive a continuous sweeping contact that transitions from a starting position and reaches an ending position, at which point the contact strength increases. In this example, the characteristic strength of the contact at the ending position may be based only on a portion of the continuous sweeping contact rather than the entire sweeping contact (e.g., only the portion of the sweeping contact at the ending position). In some embodiments, before determining the characteristic strength of the contact, a smoothing algorithm may be applied to the intensity of the sweeping contact. For example, the smoothing algorithm may optionally include one or more of the following: 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 peaks or dips in the intensity of the sweeping contact for the purpose of determining characteristic strength.

The intensity of a touch 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 touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from the operation typically associated with clicking a button of a physical mouse or touchpad. In some embodiments, when a contact is detected with a characteristic intensity that is below the light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, below which the contact is no longer detected), the device will move the focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing the operation associated with the light press intensity threshold or the deep press intensity threshold. In general, unless otherwise specified, these intensity thresholds are consistent across different sets of user interface graphics.

An increase in the characteristic intensity of a contact from an intensity below a 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 a 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 a 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 a contact lifted 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 by 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 "downstroke" 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 the corresponding operation is performed in response to detecting a subsequent decrease in intensity of the corresponding contact below the press input threshold (e.g., an "upstroke" of the corresponding press input).

Figures 5E-5H illustrate detection of a gesture including a press input corresponding to an increase in the intensity of contact 562 from an intensity below a light press intensity threshold (e.g., "IT _L ") in Figure 5E to an intensity above a deep press intensity threshold (e.g., "IT _D ") in Figure 5H . While cursor 576 is displayed over application icon 572B corresponding to App2, a gesture performed in conjunction with contact 562 is detected on touch-sensitive surface 560, on displayed user interface 570 including application icons 572A-572D displayed in predetermined area 574. In some embodiments, the gesture is detected on touch-sensitive display 504. An intensity sensor detects the intensity of the contact on touch-sensitive surface 560. The device determines that the intensity of contact 562 reaches above a deep press intensity threshold (e.g., "IT _D "). Contact 562 is maintained on touch-sensitive surface 560. As shown in Figures 5F-5H, in response to detection of the gesture, and based on contact 562 having an intensity that exceeds a deep press intensity threshold (e.g., "IT _D ") during the gesture, scaled-down representations 578A-578C (e.g., thumbnails) of recently opened documents for App2 are displayed. In some embodiments, the intensity compared to the one or more intensity thresholds is a characteristic intensity of the contact. It should be noted that the intensity map for contact 562 is not part of the displayed user interface, but is included in Figures 5E-5H to assist the reader.

In some embodiments, the display of representations 578A-578C includes animation. For example, as shown in Figure 5F, representation 578A is initially displayed near application icon 572B. As shown in Figure 5G, as the animation proceeds, representation 578A moves upward and representation 578B is displayed near application icon 572B. Representation 578A then moves upward, 578B moves upward toward representation 578A, and as shown in Figure 5H, representation 578C is displayed near application icon 572B. Representations 578A-578C form an array above icon 572B. In some embodiments, the animation proceeds according to the intensity of contact 562, as shown in Figures 5F-5G, wherein representations 578A-578C appear and move upward as the intensity of contact 562 increases toward a deep press intensity threshold (e.g., "IT _D "). In some embodiments, the intensity on which the animation proceeds is the characteristic intensity of the contact. The operations described with respect to Figures 5E-5H can be performed using an electronic device similar or identical to device 100, 300, or 500.

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 predetermined relationship to a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than 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 a corresponding contact above the press input intensity threshold and a subsequent decrease in intensity of the contact below a hysteresis intensity threshold that corresponds 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 "upstroke" 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 the intensity of the contact from an intensity equal to or less than a hysteresis intensity threshold to an intensity equal to or greater than a press input intensity threshold, and, optionally, a subsequent decrease in the intensity of the contact to an intensity equal to or less than the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, as the case may be).

For ease of explanation, descriptions of operations performed in response to a press input associated with a press input intensity threshold, or in response to a gesture including the press input, are optionally triggered in response to detecting any of: an increase in the intensity of a contact above the press input intensity threshold, an increase in the intensity of a contact from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, a decrease in the intensity of a contact below the press input intensity threshold, and/or a decrease in the intensity of a contact below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in the intensity of a contact below the press input intensity threshold, the operation is optionally performed in response to detecting a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold. Attention is now directed to embodiments of a user interface and associated processes that can be implemented on a multifunction device with a display and a touch-sensitive surface (such as device 100, 300, and/or 500) to improve the user experience in managing alerts.

1. User interface for managing alerts

The user interface for managing alarms described below is illustrated by exemplary sequences of screens that device 500 can display in response to receiving an alarm and detecting various user inputs. In these sequences, arrows indicate the order in which the screens may be displayed.

a. Display notification

6A-6B depict exemplary screens 604, 612 that device 500 can display after receiving an alarm. Initially, touch screen 504 can be turned off or inactive. In response to receiving an alarm, device 500 can issue a sensory output 602, such as a tactile output that is audible, visible, or can be perceived by the user. In some embodiments, device 500 can issue a sensory output by causing the tactile mechanism on device 500 to issue a tactile output. In some embodiments, device 500 can issue a sensory output by playing a sound or tone that is audible to the user. In some embodiments, device 500 can issue a sensory output by displaying a visible output, such as an indicator on a flash or touch screen 504.

In some embodiments, emitting a tactile output includes emitting a first tactile output, and emitting a second tactile output after emitting the first tactile output, wherein the first tactile output is different from the second tactile output. In order to improve the significance of the user's perception of the tactile output, the user may wish to receive a "pre-alarm" tactile output. As described below, the first tactile output can prime the user to receive the second tactile output, which in some embodiments can indicate specific information (e.g., the source of the alarm) or be associated with a second perceptual output (e.g., audible or visible output). For example, it may be difficult for the user to perceive the tactile output when moving or paying attention to something else. Therefore, it may be advantageous to prepare the user for the first tactile output to perceive the second tactile output (and optionally, the associated second perceptual output).

The user may wish to receive a tactile output based on the source of the alarm. For example, the user may wish to receive a different tactile output for an email alarm than for a voicemail alarm. In order to provide different tactile outputs, the device can emit tactile outputs with different audible or visible outputs, or the device can emit tactile outputs with different qualities (e.g., different intensities, durations, and/or patterns). Allowing the user to receive different tactile outputs that distinguish the source of the alarm enables the user to perceive the type of alarm without having to look at the display, thereby saving battery life. In some embodiments, the second tactile output is based on the source of the alarm. In some embodiments, the second tactile output is emitted together with the audible or visible output.

In some embodiments, the first tactile output has greater intensity and/or duration than the second tactile output. This can be advantageous, for example, by providing a stronger tactile signal to the user, drawing their attention to the device 500 preparing for the second tactile signal (e.g., a second tactile signal with a unique aspect based on the source of the alarm, or a second tactile signal associated with an audible or visible output). In some embodiments, the device 500 may include a user interface (not shown) for configuring whether issuing a tactile output includes issuing a first, “prepare” tactile output. In such an embodiment, if the device 500 is configured not to issue a “prepare” tactile output, issuing a tactile output may include issuing only one tactile output.

As depicted in FIG6A , in response to detecting subsequent user input within a predetermined time interval after sensory output 602, device 500 may display display 604 with a notification 606 indicating a received alert. In some embodiments, user input may be a contact on touchscreen 504, such as a swipe or tap. In some embodiments, if device 500 is worn on a user's wrist, user input may be a signal instructing the user to move device 500 to a viewing position by raising or rotating their wrist. As used herein, a viewing position is a position of device 500 at which the user can view touchscreen 504. In some embodiments, device 500 may detect a signal instructing the user to raise or lower their wrist, as described in U.S. Provisional Patent Application No. 62/026,532, “Raise Gesture Detection in a Device,” which is incorporated herein by reference in its entirety.

The received alert includes information. Such information may include the source of the alert, the application associated with the alert, and/or the time and/or date associated with the alert, for example, along with text, image, or audio content. In some embodiments, the notification representing the received alert includes a portion of the alert information. For example, as depicted in FIG6A , notification 606 includes the source 610 (Jason Jones) of the alert and an application affordance 608 indicating the application associated with the alert—in this example, a text messaging application. (The dotted rectangle depicted on screen 604 indicates the content of the notification, but the dotted rectangle may not be displayed.) In some embodiments, in response to detecting selection of application affordance 608, device 500 may launch the application associated with the alert. In some embodiments, launching the application includes displaying the application on touch screen 504 and opening the alert within the application for viewing, editing, or responding.

As discussed above, device 500 can display screen 604 in response to detecting a user input within a predetermined time interval following the tactile output. In some embodiments, the predetermined time interval can range from 0 seconds to 3 minutes. In other embodiments, the predetermined time interval can range from 0 seconds to 1 minute. In other embodiments, the predetermined time interval can be set by the user, or can be determined by device 500 based on previous user behavior (such as, an average of previously elapsed time) before the user provides input.

The scenario depicted in FIG6A may correspond to a situation when a user, having perceived a sensory output emitted by device 500 in response to receiving an alert, wishes to immediately view a notification representing the received alert and therefore moves device 500 to a position suitable for viewing touch screen 504 (e.g., by raising their wrist) within a predetermined time interval.

As depicted in Figure 6B, if device 500 detects user input after a predetermined time interval, device 500 can respond by displaying clock face 612 instead. This scenario can correspond to a situation when the user does not want to view the notification immediately and raises his wrist to view touch screen 504 at some point after perceiving output 602. In some embodiments, clock face 612 may include a user interface object 616 indicating the current time. In some embodiments, clock face 612 may include an indication of unread alerts 614 corresponding to received alerts because the alert content has not yet been displayed. As shown in Figure 6B, indication 614 may be a dot. Figure 6C describes another embodiment in which indication 614 is a chevron. In some embodiments, instead of a chevron, device 500 displays an arrow, a triangle, or other graphic objects that provide a directional indication. The following describes the indication of unread alerts in more detail.

In some embodiments, device 500 may display a home screen instead of clock face 612. An exemplary home screen 706 is depicted in Figure 7. The home screen may include multiple affordances representing multiple applications and may include an indication of unread alerts corresponding to received alerts.

If device 500 does not detect user input within a predetermined time interval after the sensory output, device 500 may remain in its initial dark or inactive state without displaying screen 604. This scenario may correspond to a situation when the user does not wish to view the notification immediately or wishes to avoid allowing others nearby to view the notification, and therefore does not move device 500 to a position for viewing touch screen 504 after perceiving the sensory output.

When notification 606 is displayed, if device 500 detects a second user input within a second predetermined time interval after displaying the notification, device 500 may return touch screen 504 to its initial dark or inactive state. For example, the second user input may be a signal instructing the user to move device 500 out of the viewing position by lowering and/or rotating their wrist. In response to detecting the second user input within the second predetermined time interval, device 500 may return the display to its initial dark or inactive state. This scenario may correspond to a situation in which a user who has viewed a notification no longer wishes to view or interact with device 500 and therefore lowers their wrist.

In some embodiments, displaying notification 606 involves displaying an animation that slides notification 606 in a vertical direction onto touchscreen 504. For example, device 500 may display an animation that slides notification 606 upward onto touchscreen 504 from the bottom of touchscreen 504. Such an animation can provide a visual cue to the user, because the notification rises from (for example) the bottom of the screen, that dismissing the alert can be performed by making contact with touchscreen 504 in the opposite direction of the animation (such as swiping downward) to "push down" the notification. The user can also infer from the animation that contact with touchscreen 504 in the same direction as the animation can "pull up" (for example, to display) additional alert information, such as the body of a text message or additional text associated with a calendar alert. Thus, the animation displayed by device 500 can provide a visual cue to the user regarding potential input the user can provide to device 500. Those skilled in the art will recognize that the animation direction for a notification need not be in an upward direction; for example, a notification can slide downward onto the touchscreen from the top of the screen, in which case the user may infer that dismissing the notification may require swiping upward. Such visual cues can improve the human-computer interface by guiding the user to apply appropriate inputs without requiring detailed instructions to be displayed on a reduced-size screen.

As described above, in some embodiments, device 500 can emit a sensory output, such as by causing a haptic mechanism to emit a tactile output in response to receiving an alert, thereby notifying the user that the alert has been received. However, in some embodiments, device 500 can delay the issuance of a sensory output in response to receiving an alert so that the sensory output is delivered at a time that is more convenient for the user. For example, device 500 can delay the sensory output until the user is relatively inactive and therefore more likely to perceive the sensory output, or delay the sensory output when the user is actively engaged in an activity or is sleeping to avoid disturbing the user. In some embodiments, in response to receiving an alert, device 500 can obtain data from one or more motion sensors, accelerometers, heart rate monitors, and/or other types of sensors to determine the current user activity level—such as whether the user is exercising, typing, or sleeping. Device 500 can delay the sensory output until the determined user activity level meets activity criteria. In some embodiments, for example, the activity criteria can include the user being relatively still (as determined by output from sensors on device 500), having paused from typing on a physical keyboard, having paused speaking, or not sleeping. In this way, device 500 can emit a sensory output to notify the user that a new alert has been received at a time that is likely to be less intrusive to the user, while being more likely to be perceived by the user.

After device 500 has displayed a notification, the user may choose to dismiss the notification, display the alert content (eg, the body of a text message or text associated with a calendar alert), etc.

b. Cancellation notification

FIG7 illustrates another exemplary sequence of screens that device 500 can display on touch screen 504 after receiving an alert. As discussed with respect to FIG6A , touch screen 504 may initially be black or inactive. In response to receiving the alert, device 500 may issue a sensory output. As depicted in FIG6A , in response to receiving user input within a first predetermined time interval following the sensory output, device 500 displays screen 604 including notification 606 indicating the received alert. In this exemplary sequence, displaying notification 606 on screen 604 involves displaying an animation of notification 606 sliding upward from the bottom of touch screen 504.

If device 500 detects a contact on touch screen 504 that satisfies dismissal criteria while notification 606 is displayed, device 500 can dismiss notification 606. In some embodiments, dismissing notification 606 involves removing notification 606 from the display and/or replacing the display of the notification with a clock face (such as clock face 612 in FIG. 6B ) or display of home screen 706.

In some embodiments, a contact satisfies the dismissal criteria if it is a sweep or swipe across touch screen 504. In some embodiments, a contact satisfies the dismissal criteria if it is a sweep or swipe across touch screen 504 in a particular direction, such as a sweep or swipe in the opposite direction to the direction in which the animation slid the notification onto touch screen 504. For example, if the animation slides the notification onto touch screen 504 from the bottom up, the contact may satisfy the dismissal criteria if it is a sweep in a downward direction across touch screen 504. In some embodiments, the contact may satisfy the dismissal criteria if the distance of the sweep or swipe across the touch screen exceeds a threshold distance. In some embodiments, the threshold distance may be 1/4, half, or 3/4 of the length of touch screen 504.

Returning to FIG. 7 , in some embodiments, in response to detecting movement of a contact (such as a swipe) on the touch screen 504 while displaying notification 606, the device 500 may slide notification 606 on the touch screen in the direction of the contact's movement and display a dismiss indicator 714 adjacent to the notification. As shown in FIG. 7 , in some embodiments, if the direction of the contact's movement is downward, the dismiss indicator may be displayed above the notification. The dismiss indicator 714 may provide a visual cue to the user that the notification will be dismissed if the movement of the contact continues in the same direction. After displaying the dismiss indicator, in some embodiments, if the contact meets threshold criteria, then in response to receiving a release of the contact, the device 500 may dismiss the notification 606 and remove the dismiss indicator 714 from the touch screen 504. If the contact does not meet the threshold criteria (e.g., if the movement of the contact does not exceed a threshold distance), the device 500 may display an animation that slides the notification 606 back to its initial position on the display and removes the dismiss indicator 714 from the display. Thus, in this example, the user must "push down" the notification far enough to exceed the threshold distance in order to dismiss the notification; otherwise, the notification bounces back to its original position. In some embodiments, as depicted in FIG7 , dismissing notification 606 involves displaying an animation that slides notification 606 off touch screen 504. In some embodiments, the animation slides notification 606 off touch screen 504 in the direction of the sweep or swipe.

As previously discussed, a user can also dismiss a notification by lowering their wrist (as detected by device 500) while the notification is displayed. In some embodiments, device 500 can respond differently when dismissing a notification in response to detecting a contact that meets the dismissal criteria (as discussed with respect to FIG. 7 ) than when dismissing a notification in response to detecting a signal indicating lowering the user's wrist, as described earlier. For example, if device 500 is worn on a user's wrist and device 500 detects a signal indicating that the user has lowered their wrist, device 500 can assume that the user is no longer viewing touchscreen 504 and, therefore, can turn off or deactivate touchscreen 504 after dismissing the notification. Conversely, if device 500 is displaying a notification and detects a contact on touchscreen 504 that meets the dismissal criteria (such as a downward swipe), device 500 can assume that the user is still actively viewing touchscreen 504 and can respond to the contact by dismissing the notification and then displaying a clock face, a home screen, or some other screen (such as the screen that was being displayed before the alert was received).

c. Display the alarm content

As previously discussed, a received alert includes information that may include the source of the alert, the application associated with the alert, and the time of the alert, along with (possibly) alert content, such as the body of a text message or email, a voicemail message, details about a calendar reminder, or other types of content. A notification representing a received alert may include a first portion of the alert information, such as the source of the alert, the associated application, and the time of receipt.

6A, 6B, and 7, upon receiving an alert, device 500 may emit a sensory output and then, in response to detecting a user input within a first time interval following the sensory output, display notification 606. After raising their wrist to view the notification, the user may then wish to view the associated alert content.

In some embodiments, if the device 500 determines that the user continues to maintain the device 500 in the viewing position for a predetermined time interval after displaying the notification, the device 500 may display some or all of the alert content, which may be referred to as the second portion of the information. That is, in some embodiments, if the user maintains the device 500 in the viewing position and waits, the device 500 may automatically transition from displaying the notification to displaying the alert content.

FIG8 depicts an exemplary sequence of screens that device 500 can display in response to receiving an alert. Initially, touch screen 504 may be black or inactive. In response to receiving the alert, device 500 may issue a sensory output. In response to receiving user input (as described with respect to FIG6A ) within a predetermined time period after the sensory output, device 500 may display notification 606. In response to determining that user input continues to be received after a second predetermined time period after displaying notification 606 (thereby indicating that device 500 remains in the viewing position), device 500 may display screen 802, which includes notification 606 and alert content 804. In some embodiments, device 500 may display screen 802 in response to detecting a lack of second user input within the second predetermined time period after displaying notification 606. For example, the second user input may be a signal instructing the user to lower their wrist, and the lack of such input indicates that device 500 remains in the viewing position.

In this example, alert content 804 is the body of the text message represented by notification 606. In other examples, the alert content may include the subject line and some or all of the body of a received email alert, or may be some or all of the text content associated with a calendar alert or, for example, a multimedia message.

8 , in some embodiments, displaying alert content 804 involves displaying an animation that slides notification 606 upward on touchscreen 504 while alert content 804 slides upward from the bottom of touchscreen 504 for display, such that the notification and alert content are displayed on the same screen. In some embodiments, device 500 may slide notification 606 to an upper corner of touchscreen 504 to provide space for displaying the alert content. In some embodiments, device 500 may shrink the display size of notification 606 to provide space for displaying the alert content.

In some embodiments, if the alert content is too long to be fully displayed on the touch screen 504, the alert content can be scrolled. In response to detecting user input, the device 500 can scroll the alert content to allow the user to view additional alert content on the touch screen 504. For example, such scrolling input can include contact on the touch screen 504 (such as an upward or downward swipe or flick), or, if present, can include rotation of a rotatable input mechanism. In some embodiments, the device 500 can scroll the alert content based on user input; for example, in response to an upward swipe on the touch screen 504, the device 500 can move the alert content upward on the touch screen 504.

As depicted in FIG8 , in some embodiments, as previously described with respect to FIG7 , the device 500 can dismiss the notification and alert content in response to detecting a contact that meets the dismissal criteria. In some embodiments, dismissing the notification 606 and alert content 804 involves sliding the notification 606 and alert content 804 off the touch screen 504. In some embodiments, the device 500 can display a dismiss indicator and, as previously described, “bounce” the notification and alert content when the movement of the contact does not exceed a threshold distance. In some embodiments, the device 500 can display a clock face 612 after dismissing the notification and alert content. In some embodiments, because the alert content is already displayed, if the clock face 612 is displayed after dismissing the alert content, the clock face can be displayed without an indication of unread alerts.

As previously discussed, device 500 can display alert content in response to detecting that the device has been maintained in a viewing position after displaying the notification. However, in some cases, the user may not want to wait to view the alert content by maintaining device 500 in a viewing position for a predetermined time interval. Therefore, in some embodiments, device 500 can also display screen 802 in response to detecting contact with touch screen 504 when notification 606 is displayed. In some embodiments, the contact for calling the display of alert content 804 can include movement of the contact on touch screen 504, such as a sweep or swipe. In some embodiments, the sweep or swipe must be in the same direction as the animation of sliding notification 606 onto touch screen 504, such as an upward swipe on touch screen 504, thereby conceptually "pulling up" more alert information after the notification. In some embodiments, the contact can be a touch (e.g., a finger tap) on or near notification 606.

As depicted in FIG24 , in some embodiments, in response to receiving an alert while touchscreen 504 is actively displaying content, device 500 can display notification banner 2402 across the top of touchscreen 504 while still displaying at least a portion of the screen content. In some embodiments, in response to receiving an alert while touchscreen 504 is actively displaying content, device 500 can also emit sensory output 702. In the example shown in FIG24 , the displayed content is home screen 706. In response to detecting contact, such as a swipe or tap, on notification banner 2402, device 500 can display screen 802 with alert content 804.

Some alarms may not have any alarm content. For example, an alarm clock, a low battery alarm, or a fitness alarm may not have any alarm content. Therefore, in some embodiments, the device 500 may continue to display the notification without transitioning to displaying the alarm content.

d. Prohibit automatic display of alarm content

In some cases, due to privacy concerns or for other reasons, the user may not want the device 500 to automatically display the alert content as described with respect to FIG. 8 . Therefore, in some embodiments, the device 500 can provide the user with an option to disable the automatic display of such alert content by changing the configuration data stored on the device 500. In some embodiments, before transitioning to the display of the alert content, the device 500 can obtain the configuration data to determine whether the alert content should be displayed. If the configuration data indicates that the alert content should be displayed, the device 500 can display the alert content as previously described with respect to FIG. 8 . If the configuration data indicates that the alert content should not be displayed, the device 500 can continue to display the notification without transitioning to the alert content.

In some embodiments, if device 500 is configured (via configuration data) to disable automatic display of alert content, device 100 may still display the alert content in response to detecting a contact (such as a tap or swipe) on a displayed notification.

e. Alerts that include audio content

In some embodiments, the alarm contents of display can comprise audio content.Some alarms received can comprise audio content.Such alarm can comprise voice mail, audio frequency or " push to speak (push to talk) " message.In certain embodiments, as described in Figure 9, the alarm contents shown can comprise playback affordance 902 for playback audio content.In response to detecting the selection of playback affordance 902, device 500 can play audio content.In certain embodiments, if audio content is received as a part for live audio conversation (such as, if the device is operated in " push to speak " pattern) and user selects playback affordance, then device 500 can play initial audio message in response to the selection of affordance, and device 500 can play subsequent audio message (as they are received) in live broadcast, and does not require the selection of subsequent affordance.

f. Text message alerts

In some embodiments, if the alert is a text message, the user may wish to view the text message conversation associated with the alert. Figure 10 depicts a sequence of screens that device 500 can display after receiving a text message alert. The sequence is similar to the sequence shown in Figure 8 and depicts notification 606 and alert content 804 corresponding to a text message received from sender Jason Jones. However, in this example, while displaying screen 802, device 500 detects contact on touch screen 504. For example, the contact can be a touch or tap on touch screen 504 at the location corresponding to application affordance 608, or a horizontal swipe across touch screen 504. In response to detecting contact with touch screen 504, device 500 can display screen 1002.

Screen 1002 includes some or all of a text message conversation between a user and the source of a text message alert. In this example, the text message conversation includes text messages sent to and received from Jason Jones. In some embodiments, the text messages in the text message conversation are arranged in chronological order based on the order in which they were received or sent.

g. Response Options

In some cases, while viewing the content of a notification or alert, a user may wish to respond to the alert. Because device 500 is a reduced-size device with a relatively small touch screen, a user interface that may be used to respond to alerts on a larger device (such as a cell phone) may be ineffective and/or awkward on touch screen 504. A user may wish to be able to respond to an alert without having to provide a sequence of relatively precise touch screen inputs, which may be difficult or frustrating on a reduced-size device. Therefore, in some embodiments, device 500 can provide a user interface that enables a user to respond to alerts more quickly and easily on a reduced-size device.

As previously described, device 500 can scroll the alert content in response to detecting a contact on touch screen 504 or, in some embodiments, in response to rotation of a rotatable input mechanism. In some embodiments, if the user attempts to scroll beyond the bottom of the alert content (the end of the content), device 500 can respond by displaying a user interface object associated with an action that can be performed by an application associated with the alert.

For example, Figure 11 describes the screen sequence that device 500 can display in response to receiving an alarm. These screens are similar to those described with respect to Figure 4. When the bottom of the alarm content 804 is displayed (in this case, the alarm content is a text message), device 500 detects a user input requesting to scroll beyond the bottom of the alarm content; that is, a user input requesting to move the alarm content upwards to display more alarm content. For example, the user input can be an upward swipe on the touch screen 504, or a rotation of a rotatable input mechanism. In response to detecting the user input, device 500 can scroll notification 606 and alarm content 804 upwards and scroll user interface objects 1112, 1114 below the alarm content on the touch screen 504. In this example, notification 606 is scrolled out of the top of the touch screen 504 and is no longer displayed.

In the example of FIG11 , the alert is a text message. Thus, in this embodiment, user interface objects 1112, 1114 that scroll onto touch screen 504 are associated with actions corresponding to the text messaging application. Specifically, user interface object 1112 is associated with a reply action, and user interface object 1114 is associated with a dismiss action. For other types of alerts, the user interface objects that scroll onto touch screen 504 may be different. For example, for a calendar invitation, the actions may include accepting or declining. For a voicemail alert, the actions may include calling back or sending a message. In some embodiments, there may be more than two displayed user interface objects.

In some embodiments, in response to detecting selection of user interface object 1114 , which is associated with a dismissal action, device 500 may dismiss the alarm as previously described with respect to FIG. 8 .

In some embodiments, in response to detecting selection of user interface object 1112, which is associated with a reply action, device 500 can display screen 1120. Screen 1120 includes several user interface objects 1122, 1124, 1126, 1128, which correspond to options for replying to a text message. In this example, the reply options include "Smart Reply," "Emoji," "Dictation," and "KB" (keyboard). Such response options may include functionality described in the following U.S. Provisional Patent Applications: U.S. Provisional Patent Application No. 62/044,923, “Historical Buttons for Input Mehtods,” filed on September 2, 2014, and naming Nicholas Zambetti as inventor; U.S. Provisional Patent Application No. 62/127,800, “Historical Buttons for Input Mehtods,” filed on March 3, 2015, and naming Nicholas Zambetti as inventor; and U.S. Provisional Patent Application No. 62/129,903, “Historical Buttons for Input Mehtods,” filed on March 8, 2015, and naming Nicholas Zambetti as inventor. These applications are incorporated by reference in their entirety.

In response to detecting selection of user interface object 1122 corresponding to "Smart Reply," device 500 may display smart reply screen 1130. Smart reply screen 1130 includes a user interface for selecting predetermined response messages 1132, 1134, 1136. In some embodiments, the content of the predetermined response message may be provided by device 500 as a default value or may be customized by the user. In some embodiments, the content of the predetermined response message may be received by device 500 from an external device.

In response to detecting the selection of the predetermined response message 1132, 1134, 1136, the device 500 may send the predetermined response message to the alarm source and display a message sent confirmation screen 1140. After displaying the message sent confirmation screen 1140 for a predetermined time interval, the device 500 may display the clock face 212 or the home screen. In this example, because the alarm content has already been displayed, the clock face 212 does not include an indication of unread alarms corresponding to the received alarm.

Returning to screen 1120, if device 500 detects selection of user interface object 1124 instead of user interface object 1122, device 500 may display a user interface for selecting an emoticon (e.g., an ideogram, clip art, or animation) to send as a reply to the alert source. In response to detecting selection of an emoticon, device 500 may send the selected emoticon to the alert source and display a message sent confirmation screen 1140.

In some embodiments, instead of sending a predetermined response or emoticon immediately upon selection, device 500 can display a confirmation affordance. In response to detecting selection of the confirmation affordance, device 500 can send a predetermined response or emoticon as described above.

In some embodiments, in response to detecting selection of user interface object 1126, device 500 can record audio input from a microphone on device 500 and send data corresponding to the recorded audio to the source as a reply. In some embodiments, the recorded audio can be sent as audio message data. In other embodiments, the recorded audio can be transcribed by device 500 and sent as transcription data. In some embodiments, instead of immediately sending data representing the audio recording to the source, device 500 can display an indication of the recorded audio on touch screen 504 along with a send affordance that, when selected, causes device 500 to send data corresponding to the audio to the source.

In some embodiments, in response to detecting selection of user interface object 1128 , device 500 may display a virtual keyboard to enable the user to type a response to the alert.

As depicted in FIG12A , in some embodiments, after scrolling user interface objects 1112, 1114 upward onto touch screen 504, in response to detecting user input requesting scroll past the bottom of user interface object 1114, device 500 can scroll user interface objects 1202, 1204, 1206, and 1208 representing reply options onto touch screen 504 below user interface objects 1112, 1114. These reply options include the two predetermined response messages 1202, 1204, as well as the dictation 1208 and emoticon 1206 options previously described with respect to FIG11 . In response to detecting selection of one of reply options 1202, 1204, 1206, 1208, device 500 can respond as described with respect to FIG11 .

12B , in some embodiments, instead of scrolling user interface objects 1112, 1114 upward below the bottom of the alert content, device 500 can scroll user interface objects 1202, 1204, 1206, and 1208 below the bottom of the alert content on the screen. In this example, in response to detecting user input (such as an upward swipe) requesting to scroll past the bottom of alert content 804, device 500 scrolls the reply options below the bottom of the alert content on touch screen 504.

Figure 12C illustrates an exemplary animation that can be displayed by device 500 as part of an interface for using "smart reply" as described above with reference to Figures 11-12B. On screen 1210, device 500 displays an alert (e.g., text message 1212) and a user interface object 1214 associated with a reply action. In response to receiving user input associated with a reply action (e.g., a touch on touch screen 504 at the location of user interface object 1214), device 500 can display an animated presentation of multiple predetermined response messages. For example, as shown in Figure 12C, screen 1220 initially displays user interface objects 1222 and 1224 corresponding to predetermined response messages. User interface objects 1222 and 1224 are animated to appear at the bottom of screen 1220 and translate across the screen in an upward direction as indicated by arrow 1226. During the animation, as user interface objects 1228, 1230, and 1232 appear below screen 1220, user interface objects 1222 and 1224 translate to the top of screen 504. User interface object 1228 indicates a third predetermined response message, while user interface object 1230 indicates an emoticon response, and user interface object 1232 indicates a spoken response.

The user may provide user input indicating the selection of a predetermined response message or other response options (e.g., an emoticon or spoken text). For example, the user may provide a touch on touch screen 504 at the location of user interface object 1228. In response to detecting user input indicating the selection of a predetermined response message or other response options, device 500 may remove the display of other predetermined response messages and response options (e.g., those not selected by the user). As shown in FIG12C , in response to receiving user input indicating the selection of a predetermined response message (e.g., user interface object 1228) indicating "uncertain," device 500 removes the display of user objects 1222, 1224, 1230, and 1232. Next, device 500 may animate the selected predetermined response message to briefly pause, then, as indicated by arrow 1234, translate out of screen 1220 and disappear. After pausing, translating, and removing the displayed predetermined response message/other response options, device 500 may display a second user interface screen (e.g., screen 1240), such as clock face 212 or a home screen. For example, after user interface object 1224 translates off screen 1220, device 500 may present screen 1240 by fading in, transitioning from blurred to sharp, etc. Device 500 may also send a selected predetermined response message to the alert source.

Device 500 can display other response options to enable the user to respond to other types of alarms. For example, Figures 13A-B show an exemplary screen sequence that device 500 can display on touch screen 504 to enable the user to respond to an alarm alarm or a social media "friend request" alarm. In the example shown in Figure 13A, device 500 receives an alarm alarm and issues a sensory output. In response to detecting user input within a predetermined time interval after the sensory output, device 500 displays screen 1302 including notification 1304 corresponding to the alarm alarm. In response to detecting contact on notification 1304, device 500 displays response screen 1330. Contact can be an upward swipe on touch screen 504 when notification 1304 is displayed. In response to this contact, device 500 displays screen 1330. In this case, the response options include "snooze" 1306 and "dismiss" 1308.

In the example shown in FIG13B , device 500 receives a “friend request” alert from a social media application and issues a sensory output. In response to detecting user input within a predetermined time interval after the sensory output, device 500 displays screen 1310 including notification 1312 corresponding to the friend request alert. In response to detecting contact with touch screen 504 while displaying screen 1310, device 500 displays response screen 1340. For example, the contact may be an upward swipe on touch screen 504. In response to detecting the contact, device 500 displays screen 1340. In this case, the alert response options include “Accept” 1314 and “Reject” 1316, allowing the user to accept or reject the friend request.

Those skilled in the art will recognize that many other response options are possible for other types of alerts.

It should be noted that in the previous examples shown in Figures 8-11, in response to an upward swipe on the touch screen 504 while displaying a notification, the device 500 displays the alert content associated with the received alert. However, in the examples shown in Figures 13A-B, the received alert does not have associated alert content. In some embodiments, if the received alert does not have alert content, the device 500 can respond to a contact (such as an upward swipe or tap) on the touch screen 504 by displaying response options while displaying the notification rather than by displaying the alert content.

As discussed earlier, in some embodiments, device 500 can detect the intensity of a contact on touch screen 504 (e.g., using intensity sensor 524). Device 500 can then respond to the contact on touch screen 504 based on the intensity of the contact. Returning briefly to FIG 11 , in some embodiments, while displaying alert content 804, in response to detecting a contact with touch screen 504 having a characteristic intensity above a threshold intensity, device 500 can display some or all of user interface objects 1122, 1124, 1126, and 1128.

In some embodiments, the user can access user interface objects 1122, 1124, 1126 and/or 1128 by scrolling beyond the bottom of the alert content as described earlier or by touching the touch screen 504 with a characteristic intensity above a threshold intensity (e.g., a strong press on the touch screen 504 as detected by the intensity sensor 524).

14 depicts another sequence of screens that can be displayed by device 500 to enable a user to respond to a received alert. In this example, while alert content 804 is displayed, device 500 detects a contact with touch screen 504 having a characteristic intensity above a threshold intensity. In response to detecting the contact having a characteristic intensity above the threshold, device 500 can display response screen 1402.

Response screen 1402 includes four user interface objects 1404, 1406, 1408, 1414 corresponding to four response options. In response to detecting input indicating selection of user interface object 1404, device 500 may display screen 1120 as shown and described with respect to FIG.

In response to detecting selection of user interface object 1406 , device 500 may dismiss the alarm and display a clock face or home screen.

In response to detecting selection of user interface object 1408, device 500 may suppress subsequent alerts indefinitely or for a predetermined period of time (e.g., by not causing a sensory output in response to receiving the alert, and/or by not displaying any new notifications).

In some embodiments, in response to detecting the selection of user interface object 1410, device 500 can launch the application associated with the received alert and view the alert in the application. Launching the application can correspond to executing the application in the foreground of device 500 and/or displaying the application on touch screen 504. In this example, because the alert is a text message, device 500 may launch a text messaging application. In other examples, based on the received alert, the application launched can be an email application, a calendar application, a weather application, a social networking application, or some other type of application. After launching the application, in response to detecting the pressing of a hardware button or the pressing of a rotatable, depressible mechanism (as described in Figure 5A, if either or both are present on device 500), the device can exit the application and display the home screen.

In the example shown in Figure 14, response screen 1402 includes user interface objects 1404, 1406, 1408, 1410 that are suitable for responding to text messages or email alerts. However, as previously discussed with respect to Figure 12A-B, the response screen can have different user interface objects that are suitable for responding to different types of alerts. For example, if the alert is an alarm clock, then instead of the "reply" option 1404, the response screen can provide a "snooze" option. As another example, if the alert is an audio message, the response screen can provide a "play" option to allow the user to play the audio message. In some embodiments, the response screen can provide an "open in phone" option. In response to detecting the selection of the "open in phone" option, device 500 can send data to an external electronic device (such as a cellular phone) in communication with device 500 so that the external electronic device starts an application associated with the alert.

It should be noted that the response interface described with respect to Figures 13A-B and 14 is not part of the associated application, which may or may not be executed on device 500; instead, the response interface is part of the alert user interface. In some embodiments, a third party can provide response options for an application executed on an external electronic device in communication with device 500.

2. Manage multiple alerts

In some embodiments, device 500 may receive multiple alerts and display multiple consecutive notifications.

FIG15 depicts a sequence of screens that may be displayed by device 500 in response to receiving multiple alerts. As in the previous example, initially, touch screen 504 may be black or inactive. In response to receiving the first alert, device 500 issues first sensory output 602. As previously shown and described with respect to FIG6A , in response to receiving user input within a first time interval following first sensory output 602, device 500 displays first notification 606.

While displaying the first notification, device 500 receives a second alert. In response to receiving the second alert, device 500 replaces screen 604 with screen 1502. In some embodiments, in response to receiving the second alert, device 500 may also emit a second sensory output 1506. Screen 1502 includes a second notification 1504 representing the second received alert. In this example, the second received alert is an email from sender Julia Smith. The second notification can be animated on the screen in a manner similar to that described earlier with respect to FIG. 8.

As previously discussed with respect to FIG8 , in response to detecting that the user input satisfies the dismissal criteria, the device 500 can dismiss the second notification 1504. After dismissing the second notification, the device 500 can display the home screen 706 or the clock face 612. As depicted in FIG15 , the home screen or clock face can include an indication of two unread alarms, corresponding to the first alarm and the second alarm. Note that the indicator 614 for the unread alarms depicted on the clock face 612 in FIG15 is larger than the indicator for the unread alarms depicted on the clock face 612 in FIG6B . As will be discussed in more detail below, in some embodiments, the size of the indicator can provide an indication of the number of unread alarms.

FIG16 depicts another exemplary sequence of screens that may be displayed by device 500 in response to receiving multiple alerts. In this example, device 500 receives a first alert, emits a first sensory output 602, and, as previously described with respect to FIG8 , displays a first notification 606 and first alert content 804 in response to various user inputs.

While displaying first alert content 804, device 500 then receives a second alert including information. As described with respect to FIG. 15 , in response to receiving the second alert, device 500 may display screen 1502 with second notification 1504. In some embodiments, in response to receiving the second alert, device 500 may emit second sensory output 1506. As previously described with respect to FIG. 8 , device 500 may dismiss second notification 1504 in response to user input that meets dismissal criteria. As previously described with respect to FIG. 15 , after dismissing second notification 1504, device 500 may display clock face 612 or home screen 706. In some embodiments, instead of displaying clock face 612 or home screen 706, after dismissing second notification 1504, device 500 may redisplay first alert content 804.

FIG17 depicts another screen sequence that device 500 can display. This sequence is similar to the sequence depicted in FIG16 , but instead of dismissing second notification 1504, the user wishes to view second alert content. As previously described with respect to FIG8 , while displaying second notification 1504, device 500 can display second alert content 1712 in response to detecting user input. In this example, second alert content 1712 includes subject line 1710 for an email alert. For example, the user input can be an upward swipe or tap on the second notification.

17 , after viewing second alert content 1712, the user wishes to invoke an application associated with the second alert. In some embodiments, in response to detecting a contact on touch screen 504 at a location corresponding to the second alert content or the second alert notification, device 500 may launch the application associated with the second alert and display screen 1714. In some embodiments, in response to detecting selection of application affordance 1708, device 500 may launch the application associated with the second alert and display screen 1714.

In this example, the application associated with the second alert is an email application. Thus, in response to detecting selection of application affordance 1708, device 500 can launch the email application. In some embodiments, when device 500 launches the application associated with the alert in this manner, the alert is opened within the application, as depicted in screen 1714.

After launching and viewing an application, the user may wish to return to the home screen. In response to detecting a press of input button 506, which may be a depressible hardware button or a depressible, rotatable input mechanism, device 500 may display home screen 706. In this example, because both first alert content 804 and second alert content 1712 are already displayed, home screen 706 is displayed without an indication of unread alerts corresponding to the first alert and the second alert.

18-20 depict additional sequences of screens that the device 500 can display in response to receiving multiple alerts and detecting input as previously described.

In the sequence depicted in FIG18 , as shown and described with respect to FIG17 , device 500 receives a first alert and displays a first notification. While displaying the first notification, device 500 receives a second alert. In response to receiving the second alert, device 500 displays the second notification. In this example, as previously described with respect to FIG16 , the user dismisses the second notification. After dismissing the second notification, device 500 redisplays the first notification. The user then dismisses the first notification, and device 500 displays the home screen. In this example, the home screen is displayed with indications of two unread alerts, corresponding to the first alert and the second alert.

FIG19 is similar to FIG18 . However, in this example, as previously described with respect to FIG18 , after device 500 displays the first notification, the user holds device 500 in a viewing position, and device 500 responds by displaying the first alert content. While displaying the first alert content, device 500 receives a second alert and displays the second notification. The user dismisses the second notification, and device 500 then redisplays the first alert content. The user dismisses the first alert content, and device 500 displays home screen 706 . In this example, the home screen is displayed with an indication of unread alerts corresponding to the second alert.

FIG20 is similar to FIG15 . Then, instead of dismissing the second notification, the user taps application affordance 2002 to launch the application associated with the second alert. In response to detecting selection of application affordance 2002, device 500 launches the application and displays the second alert content within the application. The user then exits the application and returns to home screen 706 by pressing a hardware button or depressible/rotatable input mechanism 506.

Device 500 can display other user interfaces for viewing multiple notifications or alerts. As depicted in Figure 21, in some embodiments, in response to detecting contact on a notification 606 representing a first alert, device 500 can display a screen 2102 comprising a portion of a first pane 2104 having alert content 2106 associated with notification 606, and one or more additional panes 2108 indicating other alert content for other received alerts. In some embodiments, screen 2102 can include paging points 2110 that provide the user with an indication of the number of other panes that can be displayed and the position of the currently displayed pane. In response to detecting a swipe or sweep on touch screen 504, device 500 can scroll the panes to display alert content for other received alerts.

In some embodiments, in response to detecting a contact on pane 2104, device 500 may display screen 2114 including the complete alert content 2120 associated with notification 606. In some embodiments, screen 2114 further includes paging dots 2118 that may provide the user with an indication of other messages that may be displayed, such as other messages in a text message conversation. In some embodiments, the color of paging dots 2118 on screen 2114 may indicate the type of message. For example, the paging dots associated with pane 2116 containing the current alert content 2120 may be one color, while other messages, such as reply messages, may be indicated by paging dots having different colors.

3. Mute notifications

In some cases, after receiving an alert from a source, a user may wish to disable subsequent sensory output for alerts from the same source and/or disable the display of notifications representing alerts from the same source. That is, if subsequent alerts are received from the same source, the user may not wish to have the notification sensory output and/or may not wish to have the associated notification displayed on touchscreen 504. As depicted in FIG22 , device 500 may receive an alert from a source and display notification 606. In this example, while displaying the notification, device 500 detects a contact with touchscreen 504 having a characteristic intensity above a threshold intensity. In response to detecting a contact having a characteristic intensity above the threshold intensity, device 500 may display a mute affordance 2204 for muting subsequent alerts received from the same source or alerts associated with the same application. In response to detecting selection of mute affordance 2204, device 500 may disable sensory output and notifications for alerts received from the same source or application indefinitely or for a predetermined period of time.

4. Group notifications

In some cases, device 500 may receive multiple alerts simultaneously or within a short period of time. This may occur, for example, if device 500 has been turned off for a period of time. When device 500 is subsequently turned on, it may receive all of the alerts that would have been received if device 500 had not been turned off. In this case, the user may be annoyed by having to view and dismiss multiple consecutive notifications.

Thus, in some embodiments, in response to receiving multiple alerts, the device 500 may display a single grouped notification representing the multiple alerts, rather than displaying a single notification for each received alert. The device 500 may determine whether to display a grouped notification representing the multiple alerts based on grouping criteria. For example, the device 500 may group alerts for representation by a single notification based on whether the alerts were received within a predetermined time interval, whether they were received from the same source, whether they were associated with the same application, or some combination of these criteria. In some embodiments, the device 500 may exclude time-sensitive alerts from being included in the grouped notifications and instead display a single notification for each time-sensitive alert. For example, such time-sensitive alerts may include system alerts (such as a battery alert) or urgent calendar reminders.

Figures 23A-C depict examples of grouped notifications 2302, 2304, 2306 representing multiple alerts. As depicted in Figures 23A-C, in some embodiments, when displaying grouped notifications, the device 500 may respond differently to user input than when displaying notifications representing a single alert. For example, as previously described with respect to Figure 8, in response to detecting contact (such as swiping upward) on a notification representing a single alert, the device 500 may display the alert content. Conversely, in response to detecting contact on a grouped notification representing multiple alerts, the device 500 may display an inbox for the application associated with the multiple alerts (if the alerts are all associated with a single application and the application has an inbox), or may display a list of notifications including a separate notification for each of the received alerts represented by the grouped alerts. Figures 23A-C depict examples of grouped notification screens and responses to user input.

In the exemplary screen sequence depicted in FIG23A , device 500 receives three text messages from the same source, Jason Jones, and displays a notification 2302 representing a grouping of the text messages. In response to detecting a contact on the grouped notification, device 500 may display a text message inbox 2308 for Jason Jones, along with a list of the received messages. For example, the contact may be a tap or a swipe. In response to detecting a selection of one of the messages in the list, device 500 may display the associated alert content.

In the exemplary screen sequence depicted in FIG23B , device 500 receives two alerts from two different sources, Chris Black and Jason Jones. Both alerts are associated with the same application. In this example, the application is a text messaging application. In response to receiving the two alerts, device 500 may display a grouped notification 2304 representing the two alerts. In response to detecting a contact on grouped notification 2304, device 500 may display a text message inbox 2310 listing the two messages. In response to detecting a selection of one of the messages in the list, device 500 may display the associated alert content.

In yet another example, as depicted in FIG23C , device 500 receives multiple alerts associated with multiple applications. Device 500 may display grouped notification 2306 representing the multiple alerts. In response to detecting a contact on grouped notification 2306, device 500 may display a list 2312 of notifications that includes a separate notification for each of the received alerts represented by the grouped notifications. In response to detecting a selection of one of the notifications, device 500 may display the associated alert content.

In some embodiments, in response to receiving multiple alerts that meet the grouping criteria, device 500 may issue multiple sensory outputs. In some embodiments, in response to receiving multiple alerts that meet the grouping criteria, device 500 may issue a single sensory output rather than issuing a sensory output for each alert.

5. Indication of unread alerts

As previously discussed with respect to Figures 6B, 7, and 15, in some examples, a displayed clock face or home screen may include a user interface object that provides an indication of unread alarms. Unread alarms may correspond to alarms that have been received but not yet viewed by the user, or may correspond to alarms that have been marked as "unread" by the user. For example, the device 500 may determine whether an alarm has been viewed based on whether some or all of the alarm content has been displayed on the touch screen 504, how long the alarm content has been displayed on the touch screen 504, whether any audio content associated with the alarm has been played, and/or whether the alarm content has been automatically displayed (e.g., in response to a signal indicating that the user raised their wrist) or, for example, in response to contact with the touch screen 504. In some embodiments, if the alarm does not include any alarm content (e.g., a clock alarm), the device 500 may consider the alarm to be read when a notification representing the alarm has been displayed.

In some embodiments, the device 500 may receive an alert that generates an instantaneous notification. Such a notification may only be useful to the user for a relatively short period of time. For example, if a user is exercising and reaches a fitness milestone (such as halfway through a full workout), the device 500 may receive an instantaneous alert that notifies the user of the milestone. In this case, if the user raises their wrist within a predetermined time interval after the device 500 issues a sensory output for the instantaneous alert, the device 500 may display a notification indicating the alert. However, if the user raises their wrist after a period of time, the device 500 may display a clock face or home screen, and the clock face or home screen may not include an indication of unread alerts corresponding to the alert, because the alert may no longer be relevant to the user.

7 , in the exemplary home screen 706 , the user interface object 708 provides an indication of unread alerts by displaying the number of unread alerts. In other examples, the user interface object can provide an indication of unread alerts in a different manner, such as by displaying a colored banner in which the color provides an indication of the number of unread alerts (e.g., a darker banner indicates more unread alerts). In some embodiments, the user interface object can provide an indication of the presence of unread alerts without providing any indication of the number of unread alerts.

In some embodiments, as depicted in Figures 6B, 6C, and 15, device 500 can provide an indication of unread alerts, such as indication 614, by displaying a dot, a herringbone, or other shape. In some embodiments, the color of the dot, herringbone, or other shape can indicate the presence of unread alerts; for example, a red shape can indicate the presence of an unread alert, while a green shape can indicate the absence of an unread alert. In some embodiments, the shape can flash, glow, or fluctuate in size at a frequency that indicates the number of unread alerts. For example, a higher flashing frequency can indicate more unread alerts. In some embodiments, the size of the shape can provide an indication of the number of unread alerts. For example, a small shape can indicate a single unread alert (as in Figure 6B), while a larger shape can indicate more unread alerts (as in Figure 15). Those skilled in the art will appreciate that these methods for indicating the number of unread alerts can be combined in many different ways.

In some embodiments, the display of a shape includes an effect. For example, the shape can fade or slide into position on the touch screen 504 (e.g., sliding in from the top edge of the screen). Optionally, the effect is animated. In some embodiments, the effect can be executed in response to user input (e.g., the user raising their wrist).

In some embodiments, the display of a shape is removed based on removal criteria. For example, a shape can be removed after it has been displayed for a predetermined period of time or in response to user input (e.g., the user lowers their wrist). In some embodiments, the removal of a shape includes an effect. For example, the shape can fade or slide off the touch screen 504 (e.g., sliding off the top edge of the screen). Optionally, the removal of the shape is animated.

The features and/or effects associated with the indication of unread alerts described above can indicate to the user that there are unread alerts. For example, an animation of the appearance or fluctuation of the size of the indication can draw the user's attention to the fact that there are unread alerts.

In addition, some shapes can provide additional technical effects. In some embodiments, arrows, triangles, herringbone marks (e.g., 614 in Figure 6 C) or other graphic objects providing directional indications can provide a visual prompt to the user that input will cause the device 500 to perform an operation associated with unread alarms. For example, a graphic object providing an indication of direction, such as the herringbone mark 614 depicted in Figure 6 C, can indicate to the user that a sweep, drag or swipe in the direction (e.g., downward in the case of the herringbone mark 614 in Figure 6 C) of the object on the touch screen 504 will cause the device 500 to perform an action associated with unread alarms. In one embodiment, the sweep in the direction that the directional object is pointing to causes the device 500 to display the content of the unread alarms, such as, for example, the alarm content 804 on the screen 802 in Figure 8. In another embodiment, the sweep in the direction indicated by the object causes the device 500 to display a notification of the alarm, such as, for example, the notification 606 in Figure 6A. In yet another embodiment, a sweep in the direction indicated by the object causes the device 500 to display a list of one or more notifications, which may include notifications of unread alerts, or to launch an application corresponding to an unread alert. For example, as described in co-pending U.S. Provisional Patent Application No. 62/044,953, “Reduced-size Notification Interface,” filed on September 2, 2014, the contents of which are incorporated herein by reference, the device 500 may display multiple notifications or launch an application corresponding to an unread alert.

Those skilled in the art will appreciate that various positions and orientations of the shape or object indicating unread alerts are possible. For example, the indication at the bottom of touch screen 504 may include an upward-pointing arrow, triangle, chevron, or other graphical object that provides an upward directional indication to indicate the presence of unread alerts, and an upward swipe on touch screen 504 will cause device 500 to display the content of the unread alert, a notification of the alert, a list of notifications, or another display associated with the alerts and/or notifications.

6. Interact with event reminders

In some embodiments, the alert is associated with an event (e.g., a party, a meeting, a game, etc.). The alert content may include information associated with the event, such as the date, time, and location of the event. In some embodiments, a reminder for the event is displayed based on an estimate of the amount of time it will take for the user to arrive at the event. The estimated amount of time may optionally depend on the user's location and the location associated with the event. For example, the amount of time may be an estimated walking, bicycling, public transportation, or driving time generated by a map application, a navigation application, or the like. In some embodiments, the reminder is displayed for the estimated amount of time it will take for the user to arrive at the event earlier than the time of the event. In some embodiments, the reminder is displayed for the estimated amount of time it will take for the user to arrive at the event earlier than the time of the event plus a predetermined amount of time that gives the user time to prepare to travel to the event in order to arrive on time.

In some embodiments, the notification or reminder of an event includes an affordance. In response to detecting selection of an affordance, the device 500 can activate a messaging application that prepares a message to be sent to a person associated with the event (e.g., the organizer of the event or the person who invited the user to the event). In this way, the user can easily provide updates on the user's status to people associated with the event (e.g., "I haven't left yet. I'll be there in 10 minutes."). In some embodiments, in response to detecting selection of an affordance associated with a notification or reminder of an event, the device 500 can activate a map application, a navigation application, etc., which provides or displays directions to the event. The directions can include directions from the user's current location to a location associated with the event.

7. Process for managing notifications and alerts

Figure 25 is a flow chart illustrating a process 2500 for managing notifications and alerts. Process 2500 can be performed at an electronic device with a touch-sensitive display, such as device 500 (Figure 5A). At block 2502, the device receives an alert including information. At block 2504, in response to receiving the alert, the device issues a sensory output (e.g., using tactile mechanism 542). At block 2506, the device detects user input. At block 2508, in response to detecting the user input, the device determines whether the user input is detected within a predetermined time interval following the sensory output. Based on determining that the user input is received within the predetermined time interval, at block 2510, the device displays a notification including a first portion of the information. Optionally, the device determines whether user input continues to be detected after a second predetermined time interval after displaying the notification. Based on determining that user input continues to be detected, the device displays a second portion of the information, where the second portion is different from the first portion.

Note that the details of the processes described above with respect to process 2500 (e.g., Figures 25 and 6A-8) are also applicable in a similar manner to the other processes described herein. For example, processes 2600 and 2700 may include one or more of the features of the various processes described above with respect to process 2500. For the sake of brevity, these details are not repeated in the descriptions of the other processes. The various methods and techniques described above with respect to method 2500 may optionally be implemented as one or more hardware units, such as those described with respect to Figure 5B.

FIG26 is a flow chart illustrating a process 2600 for managing notifications and alerts. Process 2600 can be performed at an electronic device with a touch-sensitive display, such as device 500 ( FIG5A ). At block 2602, the device receives multiple alerts. At block 2604, in response to receiving the alerts, device 500 determines whether the multiple alerts meet grouping criteria. At block 2606, the device detects user input. At block 2608, based on determining that the multiple alerts meet the grouping criteria and in response to detecting the user input, the device displays a notification representing the grouping of the multiple alerts. Based on determining that the multiple alerts do not meet the grouping criteria and in response to detecting the user input, at block 2610, the device displays multiple notifications representing the multiple alerts. Optionally, the grouping criteria are based on whether the multiple alerts are received from the same source, whether the multiple alerts exceed a threshold number of alerts, whether the multiple alerts are associated with the same application, and/or whether the multiple alerts are received within a predetermined time interval.

Note that the details of the processes described above with respect to process 2600 (e.g., Figures 26 and 23) are also applicable to the other processes described herein in a similar manner. For example, processes 2500 and 2700 may include one or more of the features of the various processes described above with respect to process 2600. For the sake of brevity, these details are not repeated in the description of the other processes. The various methods and techniques described above with respect to method 2600 may optionally be implemented as one or more hardware units, such as those described with respect to Figure 5B.

Figure 27 is a flow chart illustrating a process 2700 for managing notifications and alerts. Process 2700 can be performed at an electronic device with a touch-sensitive display screen, such as device 500 (Figure 5A). At box 2702, while displaying content, the device receives an alert including information. At box 2704, in response to receiving the alert, device 500 displays a notification banner across the display. The banner includes a portion of the information. At least a portion of the content continues to be displayed on the display. At box 2706, the device detects contact on the banner. In response to detecting the contact, at box 2708, the device displays a second portion of the information. The second portion is different from the first portion.

Note that the details of the processes described above with respect to process 2700 (e.g., Figures 27 and 24) are also applicable in a similar manner to the other processes described herein. For example, processes 2500 and 2600 may include one or more of the features of the various processes described above with respect to process 2700. For the sake of brevity, these details are not repeated in the descriptions of the other processes. The various methods and techniques described above with respect to method 2700 may optionally be implemented as one or more hardware units, such as those described with respect to Figure 5B.

The elements of FIG. 28 may be used to implement the various techniques and methods described above with respect to FIGs. 25-27 .

As shown in FIG28 , electronic device 2800 includes a display unit 2802 configured to display a user interface and, optionally, a touch-sensitive surface unit 2804 configured to receive user contact; one or more sensor units 2806 configured to detect the intensity of a touch using the touch-sensitive surface unit; and a processing unit 2808 coupled to display unit 2802, touch-sensitive surface unit 2804, and sensor unit 2806. In some embodiments, processing unit 2808 includes a display enabling unit 2810, a receiving unit 2812, and a determining unit 2814.

In some embodiments, the display enabling unit 2810 is configured to enable a notification, alert information, or user interface (or portion of a user interface) to be displayed in conjunction with the display unit 2802. For example, the display enabling unit 2810 can be used to: display a notification, replace a first notification with a second notification on the display, or display a user interface for selecting one of a plurality of message handling operations.

In some embodiments, the receiving unit 2812 is configured to receive an alert, data, or information. For example, the receiving unit 2812 can be used to receive an alert including information.

In some embodiments, determination unit 2814 is configured to make a determination. For example, determination unit 2814 can be used to determine whether a signal has been received within a predetermined time interval after the sensory output; and whether the characteristic intensity of the second contact is greater than a threshold intensity.

Figure 29 shows a functional block diagram of an electronic device 2900 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 29 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, separation, or further limitation of the functional blocks described herein.

As shown in FIG29 , electronic device 2900 includes a display unit 2902 configured to display a graphical user interface, a haptic mechanism unit 2904 configured to emit tactile output, and a processing unit 2908 coupled to display unit 2902 and tactile mechanism unit 2904. In some embodiments, the electronic device optionally includes a touch-sensitive surface unit 2926 configured to receive touch input and coupled to display unit 2902, and the processing unit 2908. In some embodiments, electronic device 2900 optionally includes a rotatable and depressible input unit 2906, a microphone unit 2926, and a button unit 2928. In some embodiments, processing unit 2908 optionally includes a receiving unit 2910, a sensory output enabling unit 2912, a detecting unit 2914, a determining unit 2916, a display enabling unit 2918, an initiating unit 2920, a transmitting enabling unit 2922, and an audio enabling unit 2924.

Processing unit 2908 is configured to receive (e.g., using receiving unit 2910) an alert including information, and in response to receiving the alert, enable (e.g., using sensory output enabling unit 2912) a sensory output. Processing unit 2908 is further configured to detect (e.g., using detecting unit 2914) a user input, determine (e.g., using determining unit 2916) whether the user input is detected within a predetermined time interval after the sensory output, and enable (e.g., using display enabling unit 2918) a notification to be displayed on display unit 2902 based on determining that the user input is detected within the predetermined time interval, wherein the notification includes the first portion of the information.

In some embodiments, enabling sensory output includes causing tactile mechanism unit 2904 to emit tactile output.

In some embodiments, processing unit 2908 is further configured to, based on determining that user input is detected after a predetermined time interval after the sensory output, enable display (e.g., using display enabling unit 2918) of a clock face, wherein the clock face includes an indication that the alarm is unread.

In some embodiments, the processing unit 2908 is further configured to enable (e.g., using the display enabling unit 2918) displaying a home screen on the display unit 2902 based on determining that user input is detected after a predetermined time interval after the perceived output, wherein the home screen includes multiple user interface objects representing multiple applications, which user interface objects launch the corresponding applications when activated, and wherein the home screen includes an indication that the alert is unread.

In some embodiments, enabling display of the notification includes activating display unit 2902 from an inactive state. In some embodiments, displaying the notification includes replacing display of the home screen with display of the notification. In some embodiments, enabling display of the notification includes enabling display of an animation that translates the notification onto the display in a first direction.

In some embodiments, the notification includes an application affordance for launching an application associated with the alert, and processing unit 2908 is further configured to detect (e.g., using detection unit 2914) selection of the application affordance and, in response to detecting the selection, launch (e.g., using launch unit 2920) the application associated with the alert.

In some embodiments, processing unit 2908 is further configured to, in response to receiving the alert, determine (e.g., using determination unit 2916) whether the user activity level meets the activity criteria, wherein issuing the perceptual output is delayed until the user activity level meets the activity criteria.

In some embodiments, the electronic device is configured to detect (e.g., using detection unit 2914) the intensity of a contact on a touch-sensitive display (e.g., on touch-sensitive surface unit 2926), and processing unit 2908 is further configured to detect (e.g., using detection unit 2914) the contact on the touch-sensitive display while the notification is displayed on display unit 2902, and determine (e.g., using determination unit 2916) whether the characteristic intensity of the contact is above a threshold intensity. In some embodiments, processing unit 2908 is further configured to, based on determining that the characteristic intensity of the contact is above the threshold intensity, enable (e.g., using display enabling unit 2918) display of an option to suppress one or more subsequent alerts that meet the muting criteria. In some embodiments, processing unit 2908 is further configured to, based on determining that the characteristic intensity of the contact is below the threshold intensity and based on determining that the contact is at a location on the touch-sensitive display corresponding to an application affordance, launch (e.g., using launching unit 2920) an application associated with the alert. In some embodiments, the muting criteria are based on the source of the alert.

In some embodiments, processing unit 2908 is further configured to detect (e.g., using detection unit 2914) a second contact on the touch-sensitive display while the notification is displayed, determine (e.g., using determination unit 2916) whether the second contact satisfies a dismissal criterion, and enable (e.g., using display enabling unit 2918) removal of the notification from the display based on determining that the second contact satisfies the dismissal criterion. In some embodiments, the second contact satisfies the dismissal criterion when the second contact comprises a swipe. In some embodiments, the second contact satisfies the dismissal criterion when the second contact comprises a movement of the second contact that exceeds a threshold distance.

In some embodiments, enabling display of the notification includes enabling display of an animation translating the notification onto the display unit in a first direction, and the second contact satisfies the dismissal criteria when the second contact includes movement of the contact in a second direction opposite the first direction.

In some embodiments, the second contact includes movement of the second contact and release of the second contact, and processing unit 2908 is further configured to, in response to detecting movement of the second contact: enable (e.g., using display enabling unit 2918) sliding the notification on the display in accordance with the movement of the second contact, and enable (e.g., using display enabling unit 2918) displaying a dismiss indicator adjacent to the notification. Optionally, processing unit 2908 is further configured to, based on determining that the second contact meets the dismiss criteria and in response to detecting the release of the second contact, enable (e.g., using display enabling unit 2918) removal of the dismiss indicator and the notification from the display. Optionally, processing unit 2908 is further configured to, based on determining that the second contact does not meet the dismiss criteria and in response to detecting the release of the second contact, enable (e.g., using display enabling unit 2918) displaying an animation on the display that translates the notification back to its initial position and enable removal of the dismiss indicator from the display.

In some embodiments, removing the notification includes displaying an animation that translates the notification off the display in the second direction. In some embodiments, removing the notification from the display includes deactivating the display. In some embodiments, removing the notification from the display includes replacing the display of the notification with display of a home screen, and the home screen includes an indication that the alarm is unread. In some embodiments, removing the notification from the display includes replacing the display of the notification with display of a clock face, and the clock face includes an indication that the alarm is unread.

In some embodiments, the processing unit 2908 is further configured to: determine (e.g., using the determination unit 2916) whether a second user input has been detected within a second predetermined time interval after displaying the notification; enable (e.g., using the display enabling unit 2918) to remove the notification from the display based on determining that the second user input has been detected within the second predetermined time interval; and enable (e.g., using the display enabling unit 2918) to display a second portion of the information based on determining that the second user input has not been detected within the second predetermined time interval, wherein the second portion is different from the first portion.

In some embodiments, the processing unit 2908 is further configured to: determine (e.g., using the determination unit 2916) whether user input continues to be detected after a second predetermined time interval after the notification is displayed; enable (e.g., using the display enabling unit 2918) to display a second portion of the information on the display unit based on determining that user input continues to be detected after the second predetermined time interval, wherein the second portion is different from the first portion; and enable (e.g., using the display enabling unit 2918) to remove the notification from the display unit based on determining that user input does not continue to be detected after the second predetermined time interval.

In some embodiments, processing unit 2908 is further configured to detect (e.g., using detection unit 2914) a third contact on the touch-sensitive display (e.g., on touch-sensitive surface unit 2926) while displaying the notification, and in response to detecting the third contact, enable (e.g., using display enabling unit 2918) display of a second portion of the information on display unit 2902, where the second portion is different from the first portion. In some embodiments, the second portion is displayed adjacent to the notification. In some embodiments, the third contact is a swipe in the first direction, and enabling display of the second portion of the information includes sliding the second portion of the information onto the screen in the first direction.

In some embodiments, enabling display of the second portion of the information further includes obtaining (e.g., using receiving unit 2910) configuration data indicating whether the second portion of the information is to be displayed and enabling display of the second portion of the information in response to determining that the configuration data indicates that the second portion of the information should be displayed.

In some embodiments, processing unit 2908 is further configured to detect (e.g., using detection unit 2914) selection of an application available when displaying the notification, and to launch (e.g., using launch unit 2920) an application associated with the alert in response to detecting the fourth contact.

In some embodiments, the alert is an electronic message, and the processing unit is further configured to detect (e.g., using detection unit 2914) a fourth contact on the touch-sensitive display while the second portion of the information is displayed, and in response to detecting the fourth contact, enable (e.g., using display enabling unit 2918) display on the display unit of at least a portion of the message conversation including electronic messages sent to and received from the source of the electronic messages.

In some embodiments, the alert includes audio content, the second portion of the displayed information includes displaying an option to play the audio content, and processing unit 2908 is further configured to: detect (e.g., using detection unit 2914) selection of the option to play the audio content; and in response to detecting the selection, enable (e.g., using audio enabling unit 2924) the playback of the audio content. In some embodiments, the audio content is first audio content, and processing unit 2908 is further configured to receive (e.g., using reception unit 2910) a second alert including second audio content after detecting the selection of the option to play the first audio content, and in response to receiving the second alert, enable (e.g., using audio enabling unit 2924) the playback of the second audio content.

In some embodiments, processing unit 2908 is further configured to detect (e.g., using detection unit 2914) a third user input while displaying the second portion of the information, and in response to detecting the third user input, enable (e.g., using display enabling unit 2918) scrolling the second portion of the information according to the third user input. In some embodiments, the third user input is a swipe on the touch-sensitive display (e.g., on the touch-sensitive surface unit 2926). In some embodiments, the third user input is a rotation of the rotatable and depressible input unit 2906.

In some embodiments, the third user input is associated with a downward direction, and the processing unit 2908 is further configured to determine (e.g., using the determination unit 2916) whether the beginning of the information is displayed on the display unit 2902, and based on determining that the beginning of the information is displayed and in response to detecting the third user input, enable (e.g., using the display enable unit 2918) to remove the second portion of the information from the display unit.

In some embodiments, the third user input is associated with an upward direction, and processing unit 2908 is further configured to determine (e.g., using determining unit 2916) whether the end of the information is displayed on display unit 2902, and based on determining that the end of the information is displayed on display unit 2902 and in response to detecting the third user input, enable (e.g., using display enabling unit 2918) display of the first plurality of user interface objects on the display unit. Optionally, the user interface objects are associated with actions corresponding to the application associated with the alert. In some embodiments, as the information is scrolled upward on the display unit, the first plurality of user interface objects are scrolled upward below the end of the information on the display.

In some embodiments, enabling removal of the second portion of the notification from the display unit includes enabling display of the second portion of the notification on the display unit to be replaced with display of a home screen on the display unit including an indication of the time, with the home screen displayed with no indication that the alert is unread. In some embodiments, enabling removal of the second portion of the notification includes enabling sliding the second portion of the notification off the display unit in the second direction.

In some embodiments, the electronic device is configured to detect intensity of a contact on the touch-sensitive display (e.g., on touch-sensitive surface unit 2926), and processing unit 2908 is further configured to detect (e.g., using receiving unit 2914) a fifth contact on the touch-sensitive display and determine (e.g., using determining unit 2916) whether a characteristic intensity of the fifth contact is greater than a threshold intensity. In some embodiments, processing unit 2908 is further configured to: based on determining that the characteristic intensity of the fifth contact is greater than the threshold intensity, enable (e.g., using display enabling unit 2918) display of a first plurality of user interface objects on display unit 2902, wherein the user interface objects are associated with actions corresponding to an application associated with the alert; and based on determining that the characteristic intensity of the fifth contact is less than the threshold intensity, launch (e.g., using launching unit 2920) the application associated with the alert.

In some embodiments, the processing unit 2908 is further configured to detect (e.g., using the detection unit 2914) the selection of a first user interface object from the first plurality of user interface objects, and in response to detecting the selection of the first user interface object, enable (e.g., using the send enable unit 2922) the sending of data to the external electronic device so that the external electronic device starts (e.g., using the start unit 2920) the application associated with the alarm.

In some embodiments, the processing unit 2908 is further configured to determine (e.g., using the determination unit 2916) whether user input has been received within a third predetermined time interval when the second portion of the information is displayed, and to deactivate the display unit 2902 (e.g., using the display enable unit 2918) based on determining that no user input has been received within the third predetermined time interval.

In some embodiments, a notification is displayed on display unit 2902 adjacent to a second portion of the information, the notification includes an application affordance, and processing unit 2908 is further configured to detect (e.g., using receiving unit 2914) selection of the application affordance when the second portion of the information is displayed, and in response to detecting selection of the application affordance, enable (e.g., using display enabling unit 2918) display of a second plurality of user interface objects on the display unit.

In some embodiments, processing unit 2908 is further configured to detect (e.g., using receiving unit 2914) a selection of a first user interface object from a second plurality of user interface objects, and in response to detecting the selection of the first user interface object, enable (e.g., using display enabling unit 2918) the display of a third plurality of user interface objects on the display unit.

In some embodiments, the processing unit 2908 is further configured to detect input on the button unit 2928, and in response to detecting the input on the button unit 2928, enable (e.g., using the display enable unit 2918) the display of a third plurality of user interface objects on the display unit.

In some embodiments, the processing unit 2908 is further configured to detect (e.g., using the receiving unit 2914) the selection of a first user interface object among a third plurality of user interface objects, and in response to detecting the selection of the first user interface object among the third plurality of user interface objects, enable (e.g., using the display enabling unit 2918) the display of a user interface for selecting a predetermined response message on the display unit.

In some embodiments, the processing unit 2908 is further configured to detect (e.g., using the receiving unit 2914) the selection of the first predetermined response message, and in response to detecting the selection of the first predetermined response message, enable (e.g., using the sending enabling unit 2922) the sending of the first predetermined response message to the alarm source.

In some embodiments, sending the first predetermined response message to the alert source includes displaying a confirmation affordance, detecting selection of the confirmation affordance, and enabling sending the first predetermined response message to the alert source in response to detecting selection of the confirmation affordance.

In some embodiments, the processing unit 2908 is further configured to, after enabling the first predetermined response message to be sent to the source, enable (for example, using the display enabling unit 2918) the display of a message sent confirmation screen on the display unit and enable the display of the message sent confirmation screen to be replaced with the display of the main screen, wherein the main screen is displayed on the display unit as an indication that no alerts are unread.

In some embodiments, processing unit 2908 is further configured to detect (e.g., using receiving unit 2914) a selection of a second user interface object from a third plurality of user interface objects, and in response to detecting the selection of the second user interface object from the third plurality of user interface objects, enable (e.g., using display enabling unit 2918) display of a user interface for selecting an emoji icon on the display unit.

In some embodiments, processing unit 2908 is further configured to detect (e.g., using receiving unit 2914) a first emoji icon, and in response to detecting selection of the first emoji icon, enable sending (e.g., using sending enabling unit 2922) the first emoji icon to the alert source. In some embodiments, enabling sending the emoji icon to the alert source includes enabling display of a confirmation affordance on display unit 2902, detecting selection of the confirmation affordance, and in response to detecting selection of the confirmation affordance, enabling sending the emoji icon to the alert source.

In some embodiments, the processing unit 2908 is further configured to detect (e.g., using the receiving unit 2914) a selection of a second user interface object in a second plurality of user interface objects, and in response to detecting the selection of the second user interface object in the second plurality of user interface objects: determine (e.g., using the determining unit 2916) whether the second portion of the information is displayed on the display unit 2902; based on determining that the second portion of the information is displayed, enable (e.g., using the display enabling unit 2918) the display of a home screen on the display unit, wherein the home screen is displayed as having no indication that the alert is unread; and based on determining that the second portion of the information is not displayed, enable (e.g., using the display enabling unit 2918) the display of the home screen, wherein the home screen includes an indication that the alert is unread.

In some embodiments, the processing unit 2908 is further configured to detect (e.g., using the receiving unit 2914) a selection of a second user interface object in a second plurality of user interface objects, and in response to detecting the selection of the second user interface object in the second plurality of user interface objects: determine (e.g., using the determining unit 2916) whether a second portion of the information is displayed on the display unit 2902; based on determining that the second portion of the information is displayed, enable (e.g., using the display enabling unit 2918) display of a clock face, wherein the clock face is displayed as having no indication that the alarm is unread; and based on determining that the second portion of the information is not displayed, enable (e.g., using the display enabling unit 2918) display of a clock face, wherein the clock face includes an indication that the alarm is unread.

In some embodiments, the processing unit 2908 is further configured to detect (e.g., using the receiving unit 2914) a selection of a third user interface object in the second plurality of user interface objects, and in response to detecting the selection of the third user interface object in the second plurality of user interface objects, enable (e.g., using the display enabling unit 2918) the display of a virtual keyboard on the display.

In some embodiments, the processing unit 2908 is further configured to detect (e.g., using the detection unit 2914) the selection of a fourth user interface object in the second plurality of user interface objects, and in response to detecting the selection of the fourth user interface object in the second plurality of user interface objects: enable (e.g., using the audio enable unit 2924) the recording of audio input from the microphone unit and enable (e.g., using the send enable unit 2922) the sending of data corresponding to the recorded audio input to the alarm source.

In some embodiments, enabling sending of data corresponding to the recorded audio input includes enabling display of an indication of the recorded audio input and a send affordance on a display unit (e.g., using display enabling unit 2918), detecting selection of the send affordance, and in response to detecting selection of the send affordance, enabling sending of data corresponding to the recorded audio input to an alarm source.

In some embodiments, the processing unit 2908 is further configured to detect (e.g., using the detection unit 2914) a press of the rotatable and depressible input unit 2906 after launching the application, and in response to detecting the press, enable (e.g., using the display enabling unit 2918) the display of the home screen on the display unit.

In some embodiments, the rotatable and depressible input unit 2906 is a rotatable mechanical button, and pressing represents pressing on the mechanical button. In some embodiments, the rotatable and depressible input unit 2906 is a rotatable capacitive button, and pressing represents touching on the capacitive button.

In some embodiments, the notification is a first notification, and the processing unit 2908 is further configured to receive (e.g., using the receiving unit 2910) a second alert including second information when the first notification is displayed on the display unit 2902, and in response to receiving the second alert, enable (e.g., using the display enabling unit 2918) the display of the first notification to be replaced with the display of the second notification on the display unit, wherein the second notification includes the first portion of the second information.

In some embodiments, the processing unit 2908 is further configured to enable (eg, using the sensory output enabling unit 2912 ) a second sensory output in response to receiving the second alert.

In some embodiments, processing unit 2908 is further configured to detect (e.g., using detection unit 2914) a request to dismiss the second notification, and in response to detecting the request, enable (e.g., using display enabling unit 2918) the dismissal of the second notification and enable the redisplay of the first notification on display unit 2902.

In some embodiments, the processing unit 2908 is further configured to detect (e.g., using the detection unit 2914) a request to dismiss the second notification, and in response to detecting the request, enable the second notification to be dismissed and enable (e.g., using the display enabling unit 2918) the display of a home screen on the display unit, wherein the home screen includes an indication that the first alert and the second alert are unread.

In some embodiments, processing unit 2908 is further configured to detect (e.g., using detection unit 2914) a request to dismiss the second notification, and in response to detecting the request, enable dismissal of the second notification and enable display of a clock face on display unit 2902 (e.g., using display enabling unit 2918), wherein the clock face includes an indication that the first alarm and the second alarm are unread.

In some embodiments, the processing unit 2908 is further configured to receive (e.g., using the receiving unit 2910) a second alert including the second information when displaying the second portion of the information, and in response to receiving the second alert, enable (e.g., using the display enabling unit 2918) the display of the second portion of the information to be replaced with the display of a second notification on the display unit 2902, wherein the second notification includes the first portion of the second information.

In some embodiments, the alert is a first alert received from a source, and processing unit 2908 is further configured to receive (e.g., using receiving unit 2910) a second alert from the source while displaying the second portion of information, and in response to receiving the second alert, enable (e.g., using display enabling unit 2918) display of a notification representing a grouping of the first alert and the second alert. In some embodiments, the first alert and the second alert are associated with the same application.

In some embodiments, processing unit 2908 is further configured to detect (e.g., using detection unit 2914) a sixth contact on the grouped notifications, and in response to detecting the sixth contact, enable (e.g., using display enabling unit 2918) display on the display unit a list of alerts received from the source, wherein the list of alerts is associated with the same application.

In some embodiments, the alert is a fitness alert, and the processing unit 2908 is further configured to, after a second predetermined time interval, enable (e.g., using the display enabling unit 2918) replacement of the display of the notification on the display unit 1902 with the display of a user interface object representing a fitness achievement, and after a third predetermined time interval, enable (e.g., using the display enabling unit 2918) replacement of the display of the user interface object on the display unit with the display of a second portion of the information, where the second portion is different from the first portion.

The operations described above with respect to FIG. 25 may optionally be implemented by the components depicted in FIG. 1A-1B or FIG. 29 . For example, receiving operation 2502 , issuing operation 2504 , detecting operation 2506 , determining operation 2508 , and displaying operation 2510 may optionally be implemented by event classifier 170 , event recognizer 180 , and event handler 190 . An event monitor 171 in event classifier 170 detects contact on touch-sensitive 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 touch at a first location on the touch-sensitive surface (or rotation or other movement of the device) corresponds to a predetermined event or sub-event, such as the selection of an object on a user interface or the rotation of the device from one orientation to another. Upon detecting a corresponding predetermined event or sub-event, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally uses or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses the corresponding GUI updater 178 to update objects 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 30 shows a functional block diagram of an electronic device 3000 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 30 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 limitation of the functional blocks described herein.

30 , electronic device 3000 includes a display unit 3002 configured to display a graphical user interface and a processing unit 3004 coupled to display unit 3002. In some embodiments, the electronic device optionally includes a touch-sensitive surface unit 3016 and processing unit 3004, where touch-sensitive surface unit 3016 is configured to receive touch input and is coupled to display unit 3002. In some embodiments, processing unit 3004 optionally includes a receiving unit 3006, a determining unit 3008, a display enabling unit 3010, a detecting unit 3012, and a sensory output enabling unit 3014.

The processing unit 3004 is configured to receive (e.g., using the receiving unit 3006) a plurality of alarms, and in response to receiving the plurality of alarms, determine (e.g., using the determining unit 3008) whether the plurality of alarms meet a grouping criterion. The processing unit 3004 is further configured to, in response to determining that the plurality of alarms meet the grouping criterion, enable (e.g., using the display enabling unit 3010) the display of a notification representing the grouping of the plurality of alarms on the display unit 3002, and in response to determining that the plurality of alarms do not meet the grouping criterion, enable (e.g., using the display enabling unit 3010) the display of a plurality of notifications representing the plurality of alarms on the display unit.

In some embodiments, the grouping criteria is based on one or more criteria selected from a group consisting of: whether multiple alerts are received from the same source, whether multiple alerts exceed a threshold number of alerts, whether multiple alerts are associated with the same application, and whether multiple alerts are received within a predetermined time period.

In some embodiments, the plurality of alerts include a first alert and a second alert received from the same source and associated with the same application, the first alert and the second alert satisfy a grouping criterion, the first alert includes the first information and the second alert includes the second information, and the display unit is a touch-sensitive display unit. In some embodiments, the processing unit 3004 is further configured to detect (e.g., using the detection unit 3012) a seventh contact on the touch-sensitive display unit (e.g., on the touch-sensitive surface unit 3016) at a location corresponding to the grouped notifications, and in response to detecting the seventh contact, enable (e.g., using the display enabling unit 3010) display of the first information and the second information on the display unit 3002.

In some embodiments, the first alert and the second alert are received from different sources and are associated with the same application, and the processing unit 3004 is further configured to detect (e.g., using the detection unit 3012) an eighth contact at a location on the touch-sensitive display unit (e.g., on the touch-sensitive surface unit 3016) corresponding to the grouped notifications, and in response to detecting the eighth contact, enable (e.g., using the display enabling unit 3010) the display of a list of alerts associated with the application on the display unit 3002, wherein the list of alerts includes the first alert and the second alert.

In some embodiments, multiple alerts are associated with multiple applications, and wherein the multiple alerts meet the grouping criteria, wherein the display unit is a touch-sensitive display unit, and the processing unit 3004 is further configured to enable (e.g., using the display enabling unit 3010) display of notifications representing a group of the multiple alerts, detect (e.g., using the detection unit 3012) a ninth contact at a location on the touch-sensitive display corresponding to the grouped notifications, and in response to detecting the ninth contact, enable (e.g., using the display enabling unit 3010) display of a list of notifications representing the multiple alerts, wherein the received alerts include a first alert and a second alert.

In some embodiments, the processing unit 3004 is further configured to enable (e.g., using the sensory output enabling unit 3014) a sensory output further in response to receiving the plurality of alerts. In some embodiments, the processing unit 3004 is further configured to enable (e.g., using the sensory output enabling unit 3014) a single sensory output further based on determining that the plurality of alerts meet the grouping criteria, and to enable (e.g., using the sensory output enabling unit 3014) a plurality of sensory outputs corresponding to the plurality of alerts further based on determining that the plurality of alerts do not meet the grouping criteria.

The operations described above with respect to FIG. 26 may optionally be implemented by the components depicted in FIG. 1A-1B or FIG. 30 . For example, receiving operation 2602 , determining operation 2604 , detecting operation 2606 , and displaying operations 2608 and 2610 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 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 (or a rotation or other movement of the device) corresponds to a predetermined event or sub-event, such as the selection of an object on a user interface or the rotation of the device from one orientation to another. Upon detecting a corresponding predetermined event or sub-event, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally uses or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses the corresponding GUI updater 178 to update objects 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 31 shows a functional block diagram of an electronic device 3100 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 31 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 limitation of the functional blocks described herein.

31 , the electronic device 3100 includes a touch-sensitive display unit 3102 configured to receive contact and display a graphical user interface, and a processing unit 3104 coupled to the display unit 3102. In some embodiments, the processing unit 3104 optionally includes a receiving unit 3106, a display enabling unit 3108, and a detecting unit 3110.

Processing unit 3104 is configured to receive (e.g., using receiving unit 3106) an alert including information while the display unit is actively displaying content, and in response to receiving the alert, enable (e.g., using display enabling unit 3108) display of a notification banner across a portion of touch-sensitive display unit 3102, wherein the notification banner includes a first portion of the information and wherein at least a portion of the content continues to be displayed. Processing unit 3104 is further configured to detect (e.g., using detecting unit 3110) a contact on the touch-sensitive display unit at a location corresponding to the notification banner, and in response to detecting the contact, enable (e.g., using display enabling unit 3108) display of a second portion of the information on the display unit, wherein the second portion is different from the first portion.

The operations described above with respect to FIG. 27 may optionally be implemented by the components depicted in FIG. 1A-1B or FIG. 31 . For example, receiving operation 2702 , display operations 2704 and 2708 , and detecting operation 2706 may optionally be implemented by event classifier 170 , event recognizer 180 , and event handler 190 . An event monitor 171 in event classifier 170 detects contact on touch-sensitive 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 (or rotation or other movement of the device) corresponds to a predetermined event or sub-event, such as the selection of an object on a user interface or the rotation of the device from one orientation to another. Upon detecting a corresponding predetermined event or sub-event, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally uses or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses the corresponding GUI updater 178 to update objects displayed by the application. Similarly, it will be clear to those skilled in the art how other processes can be implemented based on the components depicted in Figures 1A-1B.

For purposes of illustration, the foregoing description has been made with reference to specific embodiments. However, the above illustrative discussion is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teachings. These embodiments have been chosen and described in order to best illustrate the principles of the invention and its practical application, thereby enabling those skilled in the art to best utilize the invention and to adapt the various described embodiments to the specific use contemplated.

Claims (142)

1. A method for conditionally displaying a notification, comprising: In electronic devices with displays: Receive alarms including information; In response to receiving the alarm, a sensing output is issued; Detect user input; Determine whether the user input was detected within a predetermined time interval after the perceived output; and Based on the determination that the user input was detected within the predetermined time interval, a notification is displayed on the display, wherein the notification includes a first portion of the information, and wherein displaying the notification includes activating the display from an inactive state. 2. The method of claim 1, wherein the electronic device includes a tactile mechanism, and wherein emitting the sensory output includes causing the tactile mechanism to emit a tactile output. 3. The method according to any one of claims 1-2, further comprising: Based on the determination that the user input is detected after the predetermined time interval following the perception output, a clock face is displayed, wherein the clock face includes an indication that the alarm has not been read. 4. The method according to any one of claims 1-2, further comprising: Based on the determination that the user input is detected after the predetermined time interval following the perception output, a main screen is displayed, wherein the main screen includes multiple user interface objects representing multiple applications, and when the user interface objects are activated, the corresponding applications are launched, and wherein the main screen includes an indication that the alarm has not been read. 5. The method according to any one of claims 1-2, wherein displaying the notification includes replacing the display of the home screen with the display of the notification. 6. The method according to any one of claims 1-2, wherein displaying the notification includes displaying an animation that translates the notification onto the display in a first direction. 7. The method according to any one of claims 1-2, wherein the notification includes an application enabler for launching an application associated with the alarm, the method further comprising: The selection of available components for the application is detected; and In response to the detection of the selection, the application associated with the alert is launched. 8. The method according to any one of claims 1-2, further comprising: In response to receiving the alarm, determine whether the user's activity level meets the activity criteria. The perception output is delayed until the user's activity level meets the activity criteria. 9. The method according to any one of claims 1-2, wherein the display is a touch-sensitive display and the device is configured to detect the intensity of a touch on the touch-sensitive display, the method further comprising: When the notification is displayed, a touch on the display is detected; Determine whether the characteristic intensity of the contact is higher than the threshold intensity; Based on the determination that the characteristic intensity of the contact is higher than the threshold intensity, options are displayed for disabling one or more subsequent alarms that meet the silence criteria; and Based on determining that the characteristic intensity of the contact is lower than the threshold intensity, and based on determining that the contact is located on the display corresponding to an application available element, the application associated with the alarm is activated. 10. The method of claim 9, wherein the silence criterion is based on the source of the alarm. 11. The method according to any one of claims 1-2, wherein the display is a touch-sensitive display, the method further comprising: When the notification is displayed, a second contact is detected on the touch-sensitive display; Determine whether the second contact meets the release criteria; and The notification is removed from the display once it is determined that the second contact meets the release criteria. 12. The method of claim 11, wherein when the second contact includes sweeping, the second contact satisfies the release criterion. 13. The method of claim 11, wherein the second contact satisfies the release criterion when the second contact includes movement of the second contact exceeding a threshold distance. 14. The method of claim 11, wherein displaying the notification includes displaying an animation of translating the notification onto the display in a first direction, and wherein the second contact satisfies the release criterion when the second contact includes movement of the contact in a second direction opposite to the first direction. 15. The method of claim 11, wherein the second contact includes movement of the second contact and release of the second contact, the method further comprising: In response to the movement detected by the second contact: The notification is slid on the display according to the movement of the second contact, and Display the release indicator adjacent to the notification; Based on determining that the second contact meets the release criterion and in response to detecting the release of the second contact, the release indicator and the notification are removed from the display; and Based on determining that the second contact does not meet the release criterion and in response to detecting the release of the second contact: An animation is displayed on the monitor showing the notification being panned back to its initial position, and Remove the release indicator from the display. 16. The method of claim 14, wherein removing the notification includes displaying an animation of translating the notification off the display in the second direction. 17. The method of claim 11, wherein removing the notification from the display comprises deactivating the display. 18. The method of claim 11, wherein removing the notification from the display comprises replacing the display of the notification with a display of a main screen, wherein the main screen includes an indication that the alert has not been read. 19. The method of claim 11, wherein removing the notification from the display comprises replacing the display of the notification with a clock face display, wherein the clock face includes an indication that the alarm has not been read. 20. The method according to any one of claims 1-2, further comprising: Determine whether a second user input has been detected within a second predetermined time interval after the notification is displayed; Based on the determination that the second user input has been detected within the second predetermined time interval, the notification is removed from the display; and If it is determined that the second user input has not been detected within the second predetermined time interval, a second portion of the information is displayed, wherein the second portion is different from the first portion. 21. The method according to any one of claims 1-2, further comprising: Determine whether to continue detecting the user input after a second predetermined time interval following the display of the notification; Based on the determination that the user input continues to be detected after the second predetermined time interval, a second portion of the information is displayed, wherein the second portion is different from the first portion; and The notification is removed from the display if no further user input is detected after the second predetermined time interval. 22. The method according to any one of claims 1-2, further comprising: When the notification is displayed, a third contact on the display is detected; and In response to the detection of the third contact, a second portion of the information is displayed, wherein the second portion is different from the first portion. 23. The method of claim 21, wherein the second portion is displayed adjacent to the notification. 24. The method of claim 22, wherein the third contact is a sweep in a first direction, and wherein displaying the second portion of the information includes sliding the second portion of the information onto the main screen in the first direction. 25. The method of claim 20, wherein the second portion displaying the information further comprises: Obtain configuration data, which indicates whether to display the second part of the information; and In response to determining that the configuration data indicates the second part of the information should be displayed, the second part of the information is displayed. 26. The method according to any one of claims 1-2, further comprising: When the notification is displayed, the selection of available application components is detected; and In response to the detection of a fourth contact, the application associated with the alarm is launched. 27. The method of claim 20, wherein the alarm is an electronic message, the method further comprising: When the second portion of the information is displayed, a fourth contact on the display is detected; and In response to the detection of the fourth contact, at least a portion of a messaging session is displayed, the at least a portion of the messaging session including electronic messages sent to and received from the source of the electronic message. 28. The method of claim 20, wherein the alarm comprises audio content, and wherein the second portion of displaying the information comprises displaying options for playing the audio content, and wherein the method further comprises: Detecting the selection of the option used to play the audio content; and In response to the detection of the selection, the audio content is played. 29. The method of claim 28, wherein the audio content is first audio content, the method further comprising: Upon detecting the selection of the option for playing the first audio content, a second alarm including the second audio content is received; and In response to receiving the second alarm, the second audio content is played. 30. The method of claim 20, further comprising: When the second part of the information is displayed, third user input is detected; and In response to the detection of the third user input, the second part of the information is scrolled according to the third user input. 31. The method of claim 30, wherein the third user input is a sweep on the display. 32. The method of claim 30, wherein the device includes a rotatable input mechanism, and wherein the third user input is a rotation of the rotatable input mechanism. 33. The method of claim 30, wherein the third user input is associated with a downward direction, the method further comprising: Determine whether the start of the information is displayed; and The second portion of the information is removed from the display in response to the detection of the third user input, based on the determination that the information has begun to be displayed. 34. The method of claim 30, wherein the third user input is associated with an upward direction, the method further comprising: Determine whether the end of the information is displayed; and Based on the determination that the end of the information is displayed and in response to the detection of the third user input, a first plurality of user interface objects are displayed on the display, wherein the user interface objects are associated with actions corresponding to the application associated with the alarm. 35. The method of claim 34, wherein as the information is scrolled up on the display, the first plurality of user interface objects are scrolled up below the end of the information on the display. 36. The method of claim 33, wherein removing the second portion of the information from the display comprises replacing the display of the second portion of the notification with a display of a main screen including a time indication, wherein the main screen is displayed without an indication that the alarm has not been read. 37. The method of claim 33, wherein removing the second portion of the information comprises sliding the second portion of the information off the display in a second direction. 38. The method of claim 20, wherein the display is a touch-sensitive display and the device is configured to detect the intensity of a touch on the touch-sensitive display, the method further comprising: Detect the fifth contact on the display; Determine whether the characteristic intensity of the fifth contact is higher than the threshold intensity; Based on the determination that the feature intensity of the fifth contact is higher than the threshold intensity, a first plurality of user interface objects are displayed, wherein the user interface objects are associated with actions corresponding to applications associated with the alarm; and If the intensity of the feature of the fifth contact is determined to be lower than the threshold intensity, the application associated with the alarm is activated. 39. The method of claim 34, further comprising: Detecting the selection of a first user interface object among the first plurality of user interface objects; and In response to detecting the selection by the first user interface object, data is sent to an external electronic device to cause the external electronic device to launch the application associated with the alarm. 40. The method of claim 20, further comprising: When the second part of the information is displayed, determine whether user input has been received within a third predetermined time interval; and The display is deactivated if it is determined that no user input has been received within the third predetermined time interval. 41. The method of claim 20, wherein the notification is displayed adjacent to the second portion of the information, and wherein the notification includes application-available elements, the method further comprising: When the second portion of the information is displayed, the selection of the available application components is detected; and In response to the detection of the selection of the application available, a second plurality of user interface objects are displayed. 42. The method of claim 41, further comprising: Detecting the selection of the first user interface object among the second plurality of user interface objects; and In response to detecting the selection of the first user interface object, a third plurality of user interface objects are displayed. 43. The method according to any one of claims 1-2, wherein the electronic device includes a hardware button, the method further comprising: Detecting input on the hardware button; and In response to the detection of the input on the hardware button, a third or more user interface objects are displayed. 44. The method of claim 42, further comprising: Detecting the selection of the first user interface object among the third plurality of user interface objects; and In response to detecting the selection of the first user interface object among the third plurality of user interface objects, a user interface for selecting a predetermined response message is displayed. 45. The method of claim 44, further comprising: The selection of the first pre-defined response message; and In response to the detection of the selection of the first predetermined response message, the first predetermined response message is sent to the source of the alarm. 46. The method of claim 45, wherein sending the first predetermined response message to the source of the alarm comprises: The system confirms that the item is available. The selection of the confirmed available component is detected; and In response to detecting the selection of the confirmed availability, the first predetermined response message is sent to the source of the alarm. 47. The method of claim 45, further comprising: After sending the first predetermined response message to the source A confirmation screen indicating that a message has been sent is displayed on the monitor; and The display of the message sent confirmation screen is replaced with the display of the main screen, wherein the main screen is displayed without an indication that the alarm has not been read. 48. The method of claim 42, further comprising: Detecting the selection of the second user interface object among the third plurality of user interface objects; and In response to detecting the selection of the second user interface object among the third plurality of user interface objects, a user interface for selecting an emoji icon is displayed. 49. The method of claim 48, further comprising: Detecting the selection of the first emoji icon; and In response to the detection of the selection of the first emoji icon, the first emoji icon is sent to the source of the alert. 50. The method of claim 49, wherein sending the emoji icon to the source of the alert comprises: The system confirms that the item is available. The selection of the confirmed available component is detected; and In response to detecting the selection of the confirmed availability, the emoji icon is sent to the source of the alert. 51. The method of claim 41, further comprising: Detecting the selection of the second user interface object among the second plurality of user interface objects; and In response to detecting the selection of the second user interface object in the second plurality of user interface objects: Determine whether the second part of the information is displayed; Based on the second portion of the information being determined, a main screen is displayed, wherein the main screen is displayed with no indication that the alarm has not been read; and If the second part of the information is determined not to be displayed, the main screen is displayed, wherein the main screen includes an indication that the alarm has not been read. 52. The method of claim 41, further comprising: Detecting the selection of the second user interface object among the second plurality of user interface objects; and In response to detecting the selection of the second user interface object in the second plurality of user interface objects: Determine whether the second part of the information is displayed; The second portion of the information is displayed, and a clock face is displayed, wherein the clock face is displayed as if there is no indication that the alarm has not been read; and If the second part of the information is determined not to be displayed, the clock face is displayed, wherein the clock face includes an indication that the alarm has not been read. 53. The method of claim 41, further comprising: Detecting the selection of a third user interface object among the second plurality of user interface objects; and In response to detecting the selection of the third user interface object in the second plurality of user interface objects: A virtual keyboard is displayed on the monitor. 54. The method of claim 41, wherein the device includes a microphone, and the method further comprises: Detecting the selection of the fourth user interface object among the second plurality of user interface objects; and In response to detecting the selection of the fourth user interface object in the second plurality of user interface objects: Record audio input from the microphone, and Send data corresponding to the recorded audio input to the source of the alarm. 55. The method of claim 54, wherein sending data corresponding to the recorded audio input comprises: The recorded audio input is displayed on the monitor, along with instructions and transmission options. Detecting the selection of the transmitable component; and In response to detecting the selection of the sender, the data corresponding to the recorded audio input is sent to the source of the alarm. 56. The method of claim 7, wherein the electronic device includes a rotatable and pressable input mechanism, the method further comprising: After the application is launched, the press of the rotatable and pressable input mechanism is detected; and In response to the detection of the press, the main screen is displayed on the display. 57. The method of claim 56, wherein the rotatable and pressable input mechanism is a rotatable mechanical button, and wherein the pressing refers to pressing on the mechanical button. 58. The method of claim 57, wherein the rotatable and pressable input mechanism is a rotatable capacitive button, and wherein the pressing represents a touch on the capacitive button. 59. The method according to any one of claims 1-2, wherein the notification is a first notification, the method further comprising: When the first notification is displayed, a second alarm is received, including the second information; and In response to receiving the second alarm, the display of the first notification is replaced by the display of the second notification, wherein the second notification includes a first portion of the second information. 60. The method of claim 59, further comprising: In response to receiving the second alarm, a second sensing output is issued. 61. The method of claim 59, further comprising: The test is conducted in response to the request to release the second notification; In response to the detection of the request: Release the second notification, and Redisplay the first notification. 62. The method of claim 59, further comprising: The test is conducted in response to the request to release the second notification; In response to the detection of the request: Release the second notification, and Display the main screen, which includes a first alarm and an indication that the second alarm has not been read. 63. The method of claim 59, further comprising: The test is conducted in response to the request to release the second notification; In response to the detection of the request: Release the second notification, and Display clock face, wherein the clock face includes indications of a first alarm and a second alarm not read. 64. The method of claim 20, further comprising: When the second part of the information is displayed, a second alarm including the second information is received; and In response to receiving the second alarm, the display of the second portion of the information is replaced with the display of a second notification, wherein the second notification includes the first portion of the second information. 65. The method of claim 20, wherein the alarm is a first alarm received from a source, the method further comprising: When the second part of the information is displayed, a second alarm is received from the source; and In response to receiving the second alarm, a notification representing the grouping of the first alarm and the second alarm is displayed. 66. The method of claim 65, wherein the first alarm and the second alarm are associated with the same application. 67. The method of claim 66, further comprising: The sixth contact on the notification of the group is detected; and In response to the detection of the sixth contact, a list of alerts received from the source is displayed, wherein the list of alerts is associated with the same application. 68. The method according to any one of claims 1-2, wherein the alarm is a fitness alarm, the method further comprising: After a second predetermined time interval, the display of the notification will be replaced by the display of a user interface object representing fitness achievements; and After a third predetermined time interval, the display of the user interface object is replaced with the display of a second portion of the information, wherein the second portion is different from the first portion. 69. The method of claim 3, wherein the indication that the alarm is unread includes the display of a herringbone mark. 70. The method of claim 69, wherein the display of the herringbone mark is animated. 71. The method of claim 69, wherein the herringbone mark points in a first direction and the display is a touch-sensitive display, the method further comprising: In response to detecting a sweep in the first direction on the display, the notification is displayed on the display. 72. An electronic device for conditionally displaying notifications, comprising: Display unit; and A processing unit, coupled to the display unit, is configured to: Receive alarms including information; In response to receiving the alarm, enable the sensing output; Detect user input; Determine whether the user input was detected within a predetermined time interval after the perceived output; and Based on the determination that the user input was detected within the predetermined time interval, a notification is enabled to be displayed on the display unit, wherein the notification includes a first portion of the information, and wherein enabling the display of the notification includes activating the display unit from an inactive state. 73. The electronic device of claim 72, wherein the electronic device includes a tactile mechanism unit, and wherein enabling the sensing output includes causing the tactile mechanism unit to emit a tactile output. 74. The electronic device according to any one of claims 72-73, wherein the processing unit is further configured to: Based on the determination that the user input is detected after the predetermined time interval following the perception output, a clock face is displayed on the display unit, wherein the clock face includes an indication that the alarm has not been read. 75. The electronic device according to any one of claims 72-73, wherein the processing unit is further configured to: Based on the determination that the user input is detected after the predetermined time interval following the perception output, a main screen can be displayed on the display unit, wherein the main screen includes multiple user interface objects representing multiple applications, which launch the corresponding application when activated, and wherein the main screen includes an indication that the alarm has not been read. 76. The electronic device according to any one of claims 72-73, wherein displaying the notification includes replacing the display of the main screen on the display unit with the display of the notification. 77. The electronic device according to any one of claims 72-73, wherein enabling the display of the notification includes enabling the display of an animation that translates the notification onto the display unit in a first direction. 78. The electronic device according to any one of claims 72-73, wherein the notification includes an application enabler for launching an application associated with the alarm, wherein the processing unit is further configured to: The selection of available components for the application is detected; and In response to the detection of the selection, the application associated with the alert is launched. 79. The electronic device according to any one of claims 72-73, wherein the processing unit is further configured to: In response to receiving the alarm, determine whether the user's activity level meets the activity criteria. The perception output is delayed until the user's activity level meets the activity criteria. 80. The electronic device according to any one of claims 72-73, wherein the display unit is a touch-sensitive display unit, wherein the electronic device is configured to detect the intensity of a contact on the touch-sensitive display unit, and wherein the processing unit is further configured to: When the notification is displayed on the touch-sensitive display unit, a touch on the touch-sensitive display unit is detected; Determine whether the characteristic intensity of the contact is higher than the threshold intensity; Based on the determination that the characteristic intensity of the contact is higher than the threshold intensity, an option for disabling one or more subsequent alarms that meet the silence criterion can be displayed on the touch-sensitive display unit; and Based on determining that the characteristic intensity of the contact is lower than the threshold intensity, and based on determining that the contact is located on the touch-sensitive display unit at a position corresponding to an application available element, the application associated with the alarm is activated. 81. The electronic device of claim 80, wherein the mute criterion is based on the source of the alarm. 82. The electronic device according to any one of claims 72-73, wherein the display unit is a touch-sensitive display unit, and wherein the processing unit is further configured to: When the notification is displayed on the touch-sensitive display unit, a second contact on the touch-sensitive display unit is detected; Determine whether the second contact meets the release criteria; and Based on the determination that the second contact meets the release criterion, the notification can be removed from the touch-sensitive display unit. 83. The electronic device of claim 82, wherein when the second contact includes sweeping, the second contact satisfies the release criterion. 84. The electronic device of claim 82, wherein the second contact satisfies the release criterion when the second contact includes movement of the second contact exceeding a threshold distance. 85. The electronic device of claim 82, wherein enabling the display of the notification includes enabling the display of an animation that translates the notification onto the display unit in a first direction, and wherein the second contact satisfies the release criterion when the second contact includes movement of the contact in a second direction opposite to the first direction. 86. The electronic device of claim 82, wherein the second contact includes movement of the second contact and release of the second contact, wherein the processing unit is further configured to: In response to the movement detected by the second contact: The movement of the second contact enables the notification to be swiped on the display unit, and This allows the release indicator to be displayed on the display unit adjacent to the notification; Based on determining that the second contact meets the release criterion and in response to detecting the release of the second contact, the release indicator and the notification can be removed from the display unit; and Based on determining that the second contact does not meet the release criterion and in response to detecting the release of the second contact: This enables the display unit to show an animation that translates the notification back to its initial position on the display unit, and This allows the release indicator to be removed from the display unit. 87. The electronic device of claim 85, wherein enabling the removal of the notification includes enabling the display to show an animation of translating the notification out of the display unit in the second direction. 88. The electronic device of claim 82, wherein enabling the removal of the notification from the display unit includes deactivating the display unit. 89. The electronic device of claim 82, wherein enabling the removal of the notification from the display unit includes enabling the display of the notification to be replaced by a display of a main screen, wherein the main screen includes an indication that the alarm has not been read. 90. The electronic device of claim 82, wherein enabling the removal of the notification from the display unit includes enabling the display of the notification to be replaced by a clock face display, wherein the clock face includes an indication that the alarm has not been read. 91. The electronic device according to any one of claims 72-73, wherein the processing unit is further configured to: Determine whether a second user input has been detected within a second predetermined time interval after the notification is displayed; Based on the determination that the second user input has been detected within the second predetermined time interval, the notification can be removed from the display unit; and Based on the determination that the second user input has not been detected within the second predetermined time interval, a second portion of the information, which is different from the first portion, can be displayed on the display unit. 92. The electronic device according to any one of claims 72-73, wherein the processing unit is further configured to: Determine whether to continue detecting the user input after a second predetermined time interval following the display of the notification; Based on the determination that the user input continues to be detected after the second predetermined time interval, a second portion of the information, wherein the second portion is different from the first portion, can be displayed on the display unit; and Based on the determination that no further user input is detected after the second predetermined time interval, the notification can be removed from the display unit. 93. The electronic device according to any one of claims 72-73, wherein the processing unit is further configured to: When the notification is displayed, a third contact on the display unit is detected; and In response to the detection of the third contact, a second portion of the information is made available to be displayed on the display unit, wherein the second portion is different from the first portion. 94. The electronic device of claim 92, wherein the second portion is displayed adjacent to the notification. 95. The electronic device of claim 93, wherein the third contact is a sweep in a first direction, and wherein the second portion enabling the display of the information includes enabling the second portion of the information to be slid onto the display unit in the first direction. 96. The electronic device of claim 91, wherein the second portion enabling the display of the information further comprises: Obtain configuration data, which indicates whether to display the second part of the information; and In response to determining that the configuration data indicates that the second part of the information should be displayed, the second part of the information is made possible. 97. The electronic device according to any one of claims 72-73, wherein the processing unit is further configured to: When the notification is displayed, the selection of available application components is detected; and In response to the detection of the selected application availability, the application associated with the alarm is launched. 98. The electronic device of claim 91, wherein the alarm is an electronic message, and wherein the processing unit is further configured to: When the second portion of the information is displayed on the display unit, a fourth contact on the display unit is detected; and In response to the detection of the fourth contact, at least a portion of a message session is made available to be displayed on the display unit, the at least a portion of the message session including electronic messages sent to and received from the source of the electronic message. 99. The electronic device of claim 91, wherein the alarm includes audio content, and wherein the second portion enabling the display of the information includes enabling the display of an option for playing the audio content, and wherein the processing unit is further configured to: Detecting the selection of the option used to play the audio content; and In response to the detection of the selection, the audio content can be played. 100. The electronic device of claim 99, wherein the audio content is first audio content, and wherein the processing unit is further configured to: Upon detecting the selection of the option for playing the first audio content, a second alarm including the second audio content is received; and In response to receiving the second alarm, the second audio content can be played. 101. The electronic device of claim 91, wherein the processing unit is further configured to: When the second part of the information is displayed, third user input is detected; and In response to the detection of the third user input, the second portion of the information can be scrolled on the display unit according to the third user input. 102. The electronic device of claim 101, wherein the third user input is a sweep on the display unit. 103. The electronic device of claim 101, wherein the electronic device further comprises a rotatable input unit, and wherein the third user input is a rotation of the rotatable input unit. 104. The electronic device of claim 101, wherein the third user input is associated with a downward direction, wherein the processing unit is further configured to: Determine whether the start of the information is displayed on the display unit; and Based on the determination that the information is being displayed from the beginning and in response to the detection of the third user input, the second portion of the information can be removed from the display unit. 105. The electronic device of claim 101, wherein the third user input is associated with an upward direction, wherein the processing unit is further configured to: Determine whether the end of the information is displayed on the display unit; and Based on the determination that the end of the information is displayed and in response to the detection of the third user input, a first plurality of user interface objects are made to be displayed on the display unit, wherein the user interface objects are associated with actions corresponding to applications associated with the alarm. 106. The electronic device of claim 105, wherein as the information is scrolled upward on the display unit, the first plurality of user interface objects are scrolled upward below the end of the information on the display unit. 107. The electronic device of claim 104, wherein the second portion enabling removal of the information from the display unit includes enabling the display of the second portion of the notification on the display unit to be replaced by a display of a main screen including a time indication, wherein the main screen is displayed as having no indication that the alarm has not been read. 108. The electronic device of claim 104, wherein enabling the removal of the second portion of the information comprises sliding the second portion of the information out of the display in a second direction. 109. The electronic device of claim 91, wherein the display unit is a touch-sensitive display unit, and wherein the electronic device is configured to detect the intensity of a contact on the touch-sensitive display unit, and wherein the processing unit is further configured to: Detect the fifth contact on the touch-sensitive display unit; Determine whether the characteristic intensity of the fifth contact is higher than the threshold intensity; Based on the determination that the characteristic intensity of the fifth contact is higher than the threshold intensity, a first plurality of user interface objects can be displayed on the touch-sensitive display unit, wherein the user interface objects are associated with actions corresponding to applications associated with the alarm; and If the intensity of the feature of the fifth contact is determined to be lower than the threshold intensity, the application associated with the alarm is activated. 110. The electronic device of claim 105, wherein the processing unit is further configured to: Detecting the selection of a first user interface object among the first plurality of user interface objects; and In response to detecting the selection of the first user interface object, data can be sent to an external electronic device to cause the external electronic device to launch the application associated with the alarm. 111. The electronic device of claim 91, wherein the processing unit is further configured to: When the second portion of the information is displayed on the display unit, it is determined whether user input has been received within a third predetermined time interval; and The display unit is deactivated if it is determined that no user input has been received within the third predetermined time interval. 112. The electronic device of claim 91, wherein the notification is displayed adjacent to the second portion of the information, and wherein the notification includes application-available elements, wherein the processing unit is further configured to: When the second portion of the information is displayed on the display unit, the selection of the available application is detected; and In response to detecting the selection of the application available, a second plurality of user interface objects are made to be displayed on the display unit. 113. The electronic device of claim 112, wherein the processing unit is further configured to: Detecting the selection of the first user interface object among the second plurality of user interface objects; and In response to detecting the selection of the first user interface object, a third plurality of user interface objects are made to be displayed on the display unit. 114. The electronic device according to any one of claims 72-73, wherein the electronic device includes a button unit, and wherein the processing unit is further configured to: Detecting input on the button unit; and In response to detecting the input on the button unit, a third or more user interface objects can be displayed on the display unit. 115. The electronic device of claim 113, wherein the processing unit is further configured to: Detecting the selection of the first user interface object among the third plurality of user interface objects; and In response to detecting the selection of the first user interface object among the third plurality of user interface objects, a user interface for selecting a predetermined response message is displayed on the display unit. 116. The electronic device of claim 115, wherein the processing unit is further configured to: The selection of the first pre-defined response message; and In response to the selection of detecting the first predetermined response message, the first predetermined response message is enabled to be sent to the source of the alarm. 117. The electronic device of claim 116, wherein enabling the sending of the first predetermined response message to the source of the alarm comprises: This enables the display unit to show confirmation of availability; The selection of the confirmed available component is detected; and In response to the detection of the selection of the confirmed availability, the first predetermined response message is sent to the source of the alarm. 118. The electronic device of claim 116, wherein the processing unit is further configured to: After sending the first predetermined response message to the source This enables the display unit to show a message confirmation screen; and This enables the display of the message sent confirmation screen on the display unit to replace the display of the main screen, wherein the main screen is displayed without an indication that the alarm has not been read. 119. The electronic device of claim 113, wherein the processing unit is further configured to: Detecting the selection of the second user interface object among the third plurality of user interface objects; and In response to detecting the selection of the second user interface object among the third plurality of user interface objects, a user interface for selecting an emoji icon is displayed on the display unit. 120. The electronic device of claim 119, wherein the processing unit is further configured to: Detecting the selection of the first emoji icon; and In response to the detection of the selection of the first emoji icon, the first emoji icon is enabled to be sent to the source of the alert. 121. The electronic device of claim 120, wherein enabling the sending of the emoji icon to the source of the alarm comprises: This enables the display unit to show confirmation of availability; The selection of the confirmed available component is detected; and In response to the detection of the selection of the confirmed availability, the emoji icon is sent to the source of the alarm. 122. The electronic device of claim 112, wherein the processing unit is further configured to: Detecting the selection of the second user interface object among the second plurality of user interface objects; and In response to detecting the selection of the second user interface object in the second plurality of user interface objects: Determine whether the second part of the information is displayed on the display unit; The second portion of the determined information is displayed on the display unit, enabling the display of a main screen on the display unit, wherein the main screen is displayed as an indication that no alarm has been read; and Based on the determination that the second portion of the information is not displayed on the display unit, the main screen can be displayed on the display unit, wherein the main screen includes an indication that the alarm has not been read. 123. The electronic device of claim 112, wherein the processing unit is further configured to: Detecting the selection of the second user interface object among the second plurality of user interface objects; and In response to detecting the selection of the second user interface object in the second plurality of user interface objects: Determine whether the second part of the information is displayed on the display unit; The second portion of the determined information is displayed on the display unit, enabling a clock face to be displayed on the display unit, wherein the clock face is displayed as an indication that the alarm has not been read; and Based on the determination that the second part of the information is not displayed on the display unit, it is possible to display the clock face on the display unit, wherein the clock face includes an indication that the alarm has not been read. 124. The electronic device of claim 112, wherein the processing unit is further configured to: Detecting the selection of a third user interface object among the second plurality of user interface objects; and In response to detecting the selection of the third user interface object among the second plurality of user interface objects, a virtual keyboard is enabled to be displayed on the display unit. 125. The electronic device of claim 112, wherein the electronic device further comprises a microphone unit, and wherein the processing unit is further configured to: Detecting the selection of the fourth user interface object among the second plurality of user interface objects; and In response to detecting the selection of the fourth user interface object in the second plurality of user interface objects: This enables the recording of audio input from the microphone unit, and This enables the sending of data corresponding to the recorded audio input to the source of the alarm. 126. The electronic device of claim 125, wherein enabling the transmission of the data corresponding to the recorded audio input comprises: This enables the display unit to show the recorded audio input indication and transmission availability; Detecting the selection of the transmitable component; and In response to detecting the selection of the transmission available element, it becomes possible to send the data corresponding to the recorded audio input to the source of the alarm. 127. The electronic device of claim 78, wherein the electronic device further includes a rotatable and pressable input unit, wherein the processing unit is further configured to: After the application is launched, the pressing of the rotatable and pressable input unit is detected; and In response to the detection of the press, the main screen can be displayed on the display unit. 128. The electronic device of claim 127, wherein the rotatable and pressable input unit comprises a rotatable mechanical button, and wherein the pressing refers to a press on the mechanical button. 129. The electronic device of claim 128, wherein the rotatable and pressable input unit comprises a rotatable capacitive button, and wherein the pressing represents a touch on the capacitive button. 130. The electronic device according to any one of claims 72-73, wherein the notification is a first notification, and wherein the processing unit is further configured to: When the first notification is displayed on the display unit, a second alarm including second information is received; and In response to receiving the second alarm, the display of the first notification can be replaced by the display of a second notification on the display unit, wherein the second notification includes a first portion of the second information. 131. The electronic device of claim 130, wherein the processing unit is further configured to: In response to receiving the second alarm, enable the second sensing output. 132. The electronic device of claim 130, wherein the processing unit is further configured to: The test is conducted in response to the request to release the second notification; In response to the detection of the request: This enables the second notification to be deactivated from the display unit, and This enables the first notification to be redisplayed on the display unit. 133. The electronic device of claim 130, wherein the processing unit is further configured to: The test is conducted in response to the request to release the second notification; In response to the detection of the request: This enables the second notification to be deactivated from the display unit, and This enables the display of a main screen on the display unit, wherein the main screen includes indications that a first alarm and a second alarm have not been read. 134. The electronic device of claim 130, wherein the processing unit is further configured to: The test is conducted in response to the request to release the second notification; In response to the detection of the request: This enables the second notification to be deactivated from the display unit; and This enables the display unit to display a clock face, wherein the clock face includes indications of a first alarm and a second alarm not being read. 135. The electronic device of claim 91, wherein the processing unit is further configured to: When the second portion of the information is displayed on the display unit, a second alarm including the second information is received; and In response to receiving the second alarm, the display of the second portion of the information is replaced with the display of a second notification on the display unit, wherein the second notification includes the first portion of the second information. 136. The electronic device of claim 91, wherein the alarm is a first alarm received from a source, wherein the processing unit is further configured to: When the second portion of the information is displayed on the display unit, a second alarm is received from the source; and In response to receiving the second alarm, a notification representing a group of the first alarm and the second alarm can be displayed on the display unit. 137. The electronic device of claim 136, wherein the first alarm and the second alarm are associated with the same application. 138. The electronic device of claim 137, wherein the processing unit is further configured to: The sixth contact on the notification of the group is detected; and In response to the detection of the sixth contact, a list of alarms received from the source can be displayed on the display unit, wherein the list of alarms is associated with the same application. 139. The electronic device according to any one of claims 72-73, wherein the alarm is a fitness alarm, and wherein the processing unit is further configured to: After a second predetermined time interval, it becomes possible to replace the display of the notification on the display unit with the display of a user interface object representing fitness achievements; and After a third predetermined time interval, it becomes possible to replace the display of the user interface object on the display unit with the display of a second portion of the information, wherein the second portion is different from the first portion. 140. The electronic device of claim 74, wherein the indication that the alarm is unread includes a display of a herringbone mark. 141. The electronic device of claim 140, wherein the display of the herringbone mark is animated. 142. The electronic device of claim 140, wherein the herringbone mark points in a first direction and the display is a touch-sensitive display, the method further comprising: In response to detecting a sweep in the first direction on the display, the notification is displayed on the display.