KR102333461B1 - Displaying options, assigning notification, ignoring messages, and simultaneous user interface displays in a messaging application - Google Patents

Abstract

An electronic device having a touch-sensitive surface and display may execute a messaging application. Within the messaging application, swipe options may be displayed for messages and threads. Swipe options correspond to actions that can be taken on messages or threads. Messages and threads can be ignored as well as associated with notification rules. Composing interfaces and messages can be presented simultaneously within the messaging application. A messaging application may display a conversation view of a message thread with a common header that may include subject information and names of participants within the threads. The messaging application allows the addition and removal of participants to the conversation view. A messaging application allows grouping of search results from a search of messages using a search term. Grouping is based on the location of the search term within the messages.

Description

DISPLAYING OPTIONS, ASSIGNING NOTIFICATION, IGNORING MESSAGES, AND SIMULTANEOUS USER INTERFACE DISPLAYS IN A MESSAGING APPLICATION}

Embodiments herein relate generally to electronic devices with touch screen displays. More specifically, embodiments relate to user interfaces and gestures on a touch screen display.

As portable electronic devices become more compact and the functions of the devices increase, it becomes increasingly difficult to design a user interface that allows users to easily interact with multifunction devices. This challenge is particularly important for palm-sized portable devices, with screens much smaller than desktop or laptop computers. This situation is unfortunate because the user interface is the gateway through which users receive responses to user actions or actions, including not only content, but also user attempts to access features, tools, and functions of the device. It's nice.

To improve the user's interaction with portable electronic devices, some portable devices each are associated with a specific function and assign multiple functions to each pushbutton, or complex devices that allow users to access various functions of the device. Includes more pushbuttons using menu systems. These conventional user interfaces often result in complex key sequences and menu hierarchies that must be memorized by the user.

Electronic devices and displays with touch-sensitive surfaces may perform messaging applications. A method for displaying swipe options within a messaging application includes displaying a list of information corresponding to email messages. A contact is sensed over the touch-sensitive surface of the electronic device, and at a location on the display corresponding to one of the plurality of email messages, the continuous movement of the contact, without releasing the contact with the touch-sensitive surface, occurs in the first direction is detected as One or more parameters of movement of the contact are determined, and upon determining that the parameter of movement meets a first criterion, the user interface elements indicate actions to be taken on the email message. The parameters include distance, speed, and a combination thereof, and the first and second criteria may be a threshold distance, a threshold speed, or a combination thereof. User interface elements representing actions may be selected and the action corresponding to the selected user interface element may be an email message, later received email messages of the email message, an email thread associated with the email message, or a combination thereof. User interface elements may be indicated by a visual sliding out from the side of the email message. A default action is performed on the email message according to a determination that the parameters of the movement satisfy a second criterion that is different from the first criterion.

Within a messaging application, a method for associating an email message or subsequently received email messages with notification rules includes, in response to receiving an action to compose a message, displaying a compose interface within the messaging application. Inside the compose interface, a selectable user interface element is displayed that, when selected, changes notification rules for replies to messages. The selectable user interface element may be a symbol such as a bell. A touch is detected on the touch-sensitive surface at a location on the display corresponding to the selectable user interface element within the composing interface and the contact is indicative of selection of the selectable user interface element. In response to detecting the selection, a change in the appearance of a selectable user interface element within the composing interface indicates activation of a notification rule that a subsequently received message within the conversation thread corresponding to the message will trigger a conversation notification. For example, the changed appearance of a selectable user interface element is visually distinct from its previous state (eg, outline of a bell) in a graphical representation such as color, size, and position. In messages received at a later time, the notification rule may display a VIP indicator, indicating selection of a selectable user interface element adjacent to messages received at a later time. Also, another notification rule displays conversation notifications, including push notifications, when received messages are subsequently received.

A method for ignoring a message or subsequently received messages includes displaying information corresponding to a plurality of messages in a messaging application. An input is received at a location on the display corresponding to the displayed message and the input indicates deletion of the displayed message. For example, the location may include a selectable user interface element associated with a discard option. In response to receiving the input, selectable user interface elements representing a delete action to be taken on subsequent messages of the conversation thread corresponding to the displayed message are displayed proximate to the location of the displayed message. For example, selectable user interface elements are displayed on a sheet. In another embodiment, a prompt is displayed in response to receiving input and may include options for discarding the displayed message or displaying additional delete actions. In response to one selection of the plurality of selectable user interface elements, the displayed message is deleted and a delete action is established for subsequently received messages within the conversation thread.

A method for displaying a composing interface with email messages includes displaying a first composing interface within a messaging application when the first composing interface includes a first message. While displaying the first composing interface, an action for composing a second message is received. In response to receiving the action, a second composition interface is displayed, a first composition interface is displayed within the first portion, and a second composition interface is displayed within the second portion. For example, the first and second portions are displayed below a list of information corresponding to a plurality of messages in the messaging application. Alternatively, the first and second composition interfaces are displayed in a third portion below the list of information corresponding to the plurality of messages in the messaging application.

A method for displaying composing interfaces with email messages, in response to selecting a conversation view in a messaging application configured to display a plurality of email messages in a conversation view, includes the following steps. One step includes identifying a plurality of email messages in a conversation thread that includes email messages from the plurality of email messages. Another step includes determining information common to the email messages within the conversation thread. The common information includes a conversation subject that is based, at least in part, on a subject of at least one or more email messages within the conversation thread. The following steps include displaying a header comprising common information within the header portion of the conversation view, and displaying a message region that is visually distinct from the header region and contains one or more email messages of the conversation thread. Each of the two or more e-mail messages includes sender information and content information.

A method for displaying a composing interface with email messages includes receiving a search query that includes at least one term for searching for email messages in a messaging application. In response to receiving the search query, one step of the method includes determining whether one or more email messages in the messaging application include at least one search term. Another step includes determining, for each of the one or more email messages in the messaging application that includes the search term, a field within the email message in which the search term was found. In determining the field, the search term may appear within a plurality of other one or more predetermined locations. The method further includes displaying one or more email message query result groups, each containing one or more email messages in the messaging application based on the other predetermined location and including the search term at the corresponding predetermined location.

For a better understanding of the variously described embodiments, reference should be made to the following detailed description of the invention, along with the accompanying drawings in which like reference signs refer to corresponding parts throughout.
1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display, in accordance with some embodiments.
1B is a block diagram illustrating example components for event processing, in accordance with some embodiments.
2 illustrates a portable multifunction device with a touch screen, in accordance with some embodiments.
3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface, in accordance with some embodiments.
4A illustrates an example user interface for a menu of applications on a portable multifunction device, in accordance with some embodiments.
4B illustrates an example user interface for a multifunction device having a touch-sensitive surface separate from a display, in accordance with some embodiments.
5A illustrates a portrait view of icons for applications on a device, according to one embodiment.
5B illustrates a mail application view of an email application, according to one embodiment.
5C, 5D, 5E, 5F, 5G, and 5H illustrate gestures for displaying and closing swipe options within an email application, according to one embodiment.
6A, 6B, 6C, 6D, 6E, 6F, and 6G illustrate gestures for displaying and closing extended swipe options within an email application, according to one embodiment.
7A, 7B, 7C, 7D, and 7E illustrate gestures for displaying and closing a swipe option within an email application, according to one embodiment.
8A illustrates a gesture for displaying a sheet for one option within swipe options within an email application, according to one embodiment.
8B illustrates a sheet for one option within swipe options within an email application, according to one embodiment.
9A, 9B, 9C, 9D, 9E, 9F illustrate pages of an application view of a settings application, according to an embodiment.
10 is a flowchart of a method for displaying one or more swipe options within an email application, according to one embodiment.
11A, 11B, 11C, 11D, and 11E illustrate the state of a notification element for email threads within an email application, according to one embodiment.
11F illustrates a gesture for associating with a notification element with a new email in an email application, according to one embodiment.
12 illustrates a push notification for an email thread associated with a notification element, according to one embodiment.
13A, 13B, 13C, and 13D illustrate gestures for associating with a notification element with an email thread existing within an email application, according to one embodiment.
14A, 14B, 14C, 14D, and 14E illustrate a gesture for disconnecting from a notification element having an email thread existing within an email application, according to one embodiment.
15 is a flowchart of a method for associating a notification element with an email thread in an email application, according to one embodiment.
16A illustrates a gesture for selecting an enlarged swipe option within an email application, according to one embodiment.
16B illustrates a prompt in response to selection of an enlarged swipe option within an email application, according to one embodiment.
16C illustrates a sheet for additional options related to an enlarged swipe option within an email application, according to one embodiment.
17A, 17B, 17C, and 17D illustrate pages within an application view of a settings application, according to one embodiment.
18 is a flowchart of a method for ignoring an email thread within an email application, according to one embodiment.
19A and 19B illustrate a drafting UI within an email application, according to one embodiment.
19C illustrates overlaid draft emails within an email application, according to one embodiment.
19D and 19E illustrate a gesture for minimizing overlaid draft emails within an email application, according to one embodiment.
20A, 20B, and 20C illustrate a gesture for removing overlaid draft emails within an email application, according to one embodiment.
21A, 21B, and 21C illustrate a gesture for enlarging a minimized and overlaid draft email within an email application, according to one embodiment.
22A and 22B illustrate a gesture for enlarging an email thread existing within an email application with overlaid draft emails, according to one embodiment.
23A illustrates a landscape view of an icon view of a computing device, according to one embodiment.
23B illustrates an application view of an email application, according to one embodiment.
23C, 23D, and 23E illustrate an overlaid draft email and overlaid draft emails in an email application, according to one embodiment.
23F and 23G illustrate an overlaid draft email and overlaid draft emails within an email application, according to one embodiment.
23H and 23I illustrate an overlaid draft email and overlaid draft emails in an email application, according to one embodiment.
24A and 24B illustrate a gesture for minimizing overlaid draft emails within an email application, according to one embodiment.
25A, 25B, and 25C illustrate a gesture for removing an overlaid draft email within an email application, according to one embodiment.
26A, 26B, and 26C illustrate a gesture for enlarging a minimized overlaid draft email within an email application, according to one embodiment.
27A and 27B illustrate gestures for enlarging an email thread existing within an email application with overlaid draft emails, according to one embodiment.
28 is a flowchart of a method for displaying message composition interfaces within an email thread within an email application, according to one embodiment.
29A-29E illustrate gestures and example user interfaces for viewing an email thread within a conversation view with a common header including subject and participant information, in accordance with some embodiments.
30A and 30B illustrate example user interfaces and gestures for viewing an email thread in a conversation view with a common header including subject and participant information, in accordance with some embodiments.
31 illustrates a toggle option between a conversation and message view of an email thread within an email application, according to one embodiment.
32 is a flowchart of a method for viewing email threads within an email application, according to one embodiment.
33A-33E illustrate gestures and example user interfaces for grouping and displaying results from a search of email messages within an email application, in accordance with some embodiments.
34 is a flowchart of a method for grouping and displaying results from a search of email messages within an email application, according to one embodiment.
For illustrative purposes only, the drawings depict many non-limiting embodiments, and the detailed description describes. Those skilled in the art will readily recognize that alternative embodiments of the structures and methods described herein may be employed without departing from the principles disclosed herein.

Many electronic devices are graphical users that include multiple content units, such as electronic messages, photos, audio files, video files, text, hyperlinks, icons, control elements, and/or visual representations thereof. have interfaces. Many of these content units have associated metadata (eg, time and/or date stamps, file sizes, author identification, status identifier, and security settings) that may be useful to the user. To simplify the user's interaction with user interfaces comprising multiple content units, electronic devices may present on the display only a subset of all content units and/or associated metadata at any time. The user needs to access content units and/or associated metadata contained within a given user interface but not displayed at the time.

Some methods for accessing additional content units and/or metadata associated with displayed content units require a sequence of user inputs to navigate within the menu system. For example, using these methods, a user may need to select a user-interface object to display a menu. The displayed menu may or may not include a menu option for accessing additional content units and/or metadata associated with the displayed content units. When the displayed menu does not contain the desired menu option, the user needs to search through multiple menus and/or sub-menus with the menu modification option. After displaying the menu with the desired menu option, the user needs to select the menu option to start accessing the desired content. Alternatively, the electronic device may, by default, continuously display multiple content units and/or metadata associated with the displayed content units. This can clutter the display and distract users, and reduce the user's effectiveness when using the device.

In the embodiments described below, improved methods for accessing additional content units, which are present in a graphical user interface, but not displayed, use simple user contacts on a touch-sensitive surface to open a predetermined navigation direction. This is achieved by providing user interfaces that allow unlocking (e.g., there is a preferred navigation axis, but some additional, occasionally accessed, such as metadata that is available in response to navigation in a direction different from the preferred navigation axis). of information). In other embodiments described below, improved methods for accessing metadata associated with displayed content units reveal hidden metadata when detecting simple user inputs, related to traditional navigation inputs, on a touch-sensitive surface. This is achieved by the provision of visible user interfaces. These methods simplify the process of accessing additional user interface content units and/or metadata associated with the displayed content units without unduly cluttering the user interface display.

details

Exemplary devices

Hereinafter, embodiments will be described in detail with reference to examples shown in the accompanying drawings. In the detailed description that follows, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. It will be apparent, however, to one skilled in the art, that the variously described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

It will also be understood that, although in some instances, the terms first, second, etc. are used herein to describe various elements, these elements should not be limited to these terms. These terms are only used to distinguish one element from another. For example, a first contact may be referred to as a second contact, and similarly, a second contact may be referred to as a first contact, without departing from the scope of the variously described embodiments. The first contact and the second contact are both contacts, but they are not the same contact.

The terminology used in the description of the variously described embodiments herein is for the purpose of describing the specific embodiments only, and is not intended to be limiting. As used in the description of the various embodiments described and in the appended claims, the singular form is intended to include the plural form as well, unless the context clearly dictates otherwise. It will also be understood that the term “and/or” as used herein represents and encompasses any and all possible combinations of one or more of the listed associated items. The terms “include,” “including,” “comprise,” and/or “comprising,” as used herein, refer to the stated features, integers, Specifies the presence of steps, actions, elements, and/or components, but the presence or addition of one or more other features, integers, steps, actions, elements, components, and/or groups thereof. It will be further understood that the exclusion of

As used herein, the term "if" is, optionally, depending on the context, "when" or "upon" or "in response to determining ( It is interpreted to mean "in response to determining" or "in response to detecting". Similarly, the phrases “if determined” or “if [the stated condition or event] is sensed” are, optionally, depending on the context, “on determining” or “in response to determining” or “[the stated condition or event] event] be construed to mean "on detection" or "in response to detecting [the stated state or event]".

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions such as PDA and/or music player functions. Illustrative embodiments of portable multifunction devices include, but are not limited to, iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, CA. Other portable electronic devices such as laptop or tablet computers with touch-sensitive surfaces (eg, touch screen displays and/or touchpads) are optionally used. It will also be appreciated that, in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (eg, a touch screen display and/or a touchpad).

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

Devices are typically, for example, drawing applications, presentation applications, word processing applications, website creation applications, disk authoring applications, spreadsheet applications, gaming applications, phone applications, video conferencing applications, email applications, instant messaging applications, workout support applications , a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

The various applications running 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 as well as corresponding information displayed on the device are optionally adjusted and/or changed from one application to the next and/or within a respective application. In this way, the common physical architecture (eg, touch-sensitive surface) of the device supports various applications, optionally with user interfaces that are intuitive and clear to the user.

We now turn to embodiments of portable devices with touch-sensitive displays. 1A is a block diagram illustrating a portable multifunction device 100 with touch-sensitive displays 112 , in accordance with some embodiments. Touch-sensitive display 112 is sometimes referred to as a “touch screen” for convenience, and is sometimes known or referred to as a touch-sensitive display system. Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122 , one or more processing units (CPUs) 120 , peripherals interface 118 , RF circuitry 108 , audio circuitry 110 , speaker 111 , microphone 113 , input/output (I/O) subsystem 106 , other input or control devices 116 , and external port 124 . includes Device 100 optionally includes one or more optical sensors 164 . Device 100 may optionally include one or more intensity sensors 165 for sensing the intensity of contacts on device 100 (eg, touch-sensitive, such as touch-sensitive display system 112 of device 100 ). surface) is included. Device 100 optionally includes a touch-sensitive display system 112 of device 100 or a touchpad 355 of device 300 for generating tactile outputs on device 100 (eg, with touch-sensitive display system 112 of device 100 ) one or more tactile output generators 167 (for generating tactile outputs on the same touch-sensitive surface). These components optionally communicate via one or more communication buses or signal lines 103 .

As used in the specification and claims, the term “strength” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (eg, finger contact) on the touch-sensitive surface, or touch- Refers to replacing (substituting) the force or pressure of contact on a sensitive surface. The intensity of the contact has a range of values including at least four distinct values and more typically including hundreds (eg, at least 256) distinct values. The intensity of the contact is optionally determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (eg, weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of the stylus is optionally used to determine the pressure of the stylus over the touch-sensitive surface. Alternatively, the size and/or changes thereto of the sensed contact area at the touch-sensitive surface, the capacitance and/or changes thereto of the touch-sensitive surface in the vicinity of the contact, and/or the touch-sensitive surface in the vicinity of the contact The resistance of and/or changes thereto are optionally used as a substitute for the force or pressure of contact on the touch-sensitive surface. In some implementations, the surrogate measurements for contact force or pressure are used directly to determine whether a threshold intensity has been exceeded (eg, a threshold intensity is described in units corresponding to the surrogate measurements). In some implementations, alternative measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether a threshold strength has been exceeded (eg, the threshold strength is the critical pressure measured in units).

As used in the specification and claims, the term “tactile output” refers to the physical displacement of the device relative to its previous position, one component of the device (eg, the housing) relative to another component of the device (eg, touch- It refers to the physical displacement of the sensitive surface), or the displacement of the component with respect to the center of mass of the device to be sensed by the user by the user's sense of touch. For example, in a situation where a device or component of a device is in contact with a touch-sensitive user's surface (eg, a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement may be , will be interpreted as a tactile sensation corresponding to a perceived change in physical properties of a device or a component of a device. For example, movement of a touch-sensitive surface (eg, a touch-sensitive display or trackpad) can optionally be performed by a user as a “down click” or “up click” of a physical actuator button. is interpreted by In some cases, the user may feel a tactile sensation such as a "down click" or "up click" even in the absence of movement of the physical actuator button associated with the touch-sensitive surface that is physically depressed (eg, displaced) by movement of the user. will be. As another example, movement of the touch-sensitive surface is optionally interpreted or sensed by the user as "roughness" of the touch-sensitive surface, even if there is no change in smoothness of the touch-sensitive surface. Such interpretation of touch by a user will be susceptible to the user's individualized sensory perceptions, but there are many touch sensory perceptions that are common to the majority of users. Thus, when tactile output is described as corresponding to a user's specific sensory perception (eg, "up click", "down click", "illuminance"), unless stated otherwise, the tactile output generated is typical ( or average) corresponding to the physical displacement of the device or component thereof that will generate the described sensory perception for the user.

Device 100 is but one example of a portable multifunction device and device 100 optionally has more or fewer components than shown, optionally, a combination of two or more components, or optionally, It will be appreciated that they have different configurations or arrangements of components. The various components shown in FIG. 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application specific integrated circuits.

Memory 102 optionally includes high-speed random access memory, and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state memory devices. Access by other components of device 100 to memory 102 , such as CPU 120 and peripherals interface 118 , is optionally controlled by memory controller 122 .

Peripheral interface 118 may be used to connect input and output peripherals of the device to CPU 120 and memory 102 . One or more processors 120 run or execute various software programs and/or sets of instructions 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 are optionally implemented on a single chip, such as chip 104 . In some other embodiments, they are optionally implemented on separate chips.

Radio frequency (RF) circuitry 108 receives and transmits RF signals, also called electromagnetic signals. The RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communication networks and other communication devices via the electromagnetic signals. RF circuitry 108 optionally includes 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, etc. It includes, but is not limited to, well-known circuitry for performing these functions. RF circuitry 108 may optionally be connected to networks (such as the Internet, also referred to as the World Wide Web (WWW)), intranets and/or wireless networks (cellular telephone networks, wireless local area networks (LANs) and/or metropolitan networks). Communicates by wireless communication with a metropolitan area network (MAN), and other devices. Wireless communication, optionally, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink (HSDPA), packet access), HSUPA (high-speed uplink packet access), EV-DO (Evolution, Data-Only), HSPA, HSPA+, DC-HSPDA (Dual-Cell HSPA), LTE (long term evolution), NFC (near field) communication), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (eg, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (eg, Internet message access protocol (IMAP) and/or post office protocol (POP)); Instant messaging (eg, extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Lever (SIMPLE) aging Extensions), Instant Messaging and Presence Service (IMPS), and/or Short Message Service (SMS), or other suitable communication protocols including communication protocols not yet developed as of the filing date of this document. It uses any of a plurality of communication standards, protocols and technologies that do not

The audio circuit 110 , the speaker 111 , and the microphone 113 provide an audio interface between the user and the device 100 . The audio circuit 110 receives audio data from the peripheral 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 humans. The audio circuit 110 also receives an electrical signal converted by the microphone 113 from the sound wave. Audio circuitry 110 converts electrical signals into audio data and sends the audio data to peripherals interface 118 for processing. Audio data is optionally retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118 . In some embodiments, audio circuitry 110 also includes a headset jack (eg, 212 in FIG. 2 ). The headset jack can be used for audio circuitry 110 and removable audio input/output peripherals, such as output-only headphones, or a headset that has both an output (eg, headphones for one or both ears) and an input (eg, a microphone). It provides an interface between

I/O subsystem 106 connects input/output peripherals of device 100 , such as touch screen 112 and other input control devices 116 , to peripherals interface 118 . I/O subsystem 106 optionally includes one or more input controllers for display controller 156 , light sensor controller 158 , intensity sensor controller 159 , haptic feedback controller 161 , and other input or control devices. includes 160 . One or more input controllers 160 receive/transmit electrical signals to/from other input or control devices 116 . Other input control devices 116 optionally include physical buttons (eg, push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and the like. In some alternative embodiments, input controller(s) 160 is optionally coupled to (or not coupled to) any of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. One or more buttons (eg, 208 in FIG. 2 ) optionally include an up/down button for volume control of the speaker 111 and/or the microphone 113 . The one or more buttons optionally include a push button (eg, 206 in FIG. 2 ).

The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. Display controller 156 receives and/or sends electrical signals to/from touch screen 112 . Touch screen 112 displays a visual output to the user. The visual output optionally includes graphics, text, icons, video, and combinations thereof (collectively referred to as “graphics”). In some embodiments, some or all of the visual output corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that receives input from a user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with associated modules and/or sets of instructions within memory 102 ) sense contact (and movement or release of contact) on touch screen 112 , and , translates the sensed contact into interaction with user-interface objects (eg, 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.

Touch screen 112 optionally uses LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally include 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 touch screen 112 . Sensing a contact and its movement or release using any of a plurality of currently known or later developed touch sensing technologies, including but not limited to In an exemplary embodiment, a projected mutual capacitance sensing technology such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, CA is used.

Touch screen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with the touch screen 112 using a suitable object or accessory, such as a stylus, finger, or the like. In some embodiments, the user interface is primarily designed to operate using finger-based contacts and gestures, which may be less precise than stylus-based input due to the larger contact area of the finger on the touch screen. In some embodiments, the device converts coarse finger-based input into precise pointer/cursor positions or commands for performing actions desired by the user.

In some embodiments, in addition to a touch screen, device 100 includes a touch pad (not shown) for selectively activating or deactivating certain functions. In some embodiments, the touch pad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touch pad is, optionally, a touch-sensitive surface separate from the 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 optionally include a power management system, one or more power sources (eg, a battery, alternating current (AC)), a recharge system, a power failure detection circuit, a power converter or inverter, a power status indicator (eg, , light emitting diodes (LEDs), and other components associated with the generation, management, and distribution of power in portable devices.

Device 100 also optionally includes one or more optical sensors 164 . 1A shows a light sensor coupled to a light sensor controller 158 in the I/O subsystem 106 . Optical sensor 164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Light 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 referred to as camera module), optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the back of the device 100 , opposite the touch screen display 112 on the front of the device, such that the touch screen display is used as a viewfinder for still and/or video image acquisition. it becomes possible In some embodiments, the other optical sensor is positioned on the front of the device such that an image of the user is optionally acquired for the videoconference while the user views other videoconference participants over the touch screen display.

Device 100 also optionally includes one or more contact intensity sensors 165 . 1A shows a contact intensity sensor coupled to an intensity sensor controller 159 of the I/O subsystem 106 . Contact intensity sensor 165 may optionally include one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensor. sensors (eg, sensors used to measure contact force (or pressure) on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (eg, pressure information or a surrogate for pressure information) from the environment. In some embodiments, the at least one contact intensity sensor is positioned alongside or proximate to a touch-sensitive surface (eg, touch-sensitive display system 112 ). In some embodiments, the at least one contact intensity sensor is located on the back side of the device 100 , opposite the touch screen display 112 located on the front side of the device 100 .

Device 100 also optionally includes one or more proximity sensors 166 . 1A shows a proximity sensor 166 coupled to a peripherals interface 118 . Alternatively, the proximity sensor 166 is coupled to the input controller 160 of the I/O subsystem 106 . In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is placed near the user's ear (eg, when the user is on a phone call).

Device 100 also optionally includes one or more tactile output generators 167 . 1A shows a tactile output generator coupled to a haptic feedback controller 161 within the I/O subsystem 106 . Tactile output generator 167 may optionally include one or more electroacoustic devices such as speakers or other audio components and/or a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component ( Examples include electromechanical devices that convert energy into linear motion, such as a component that converts electrical signals into tactile outputs of the device. The contact intensity sensor 165 receives tactile feedback generation instructions from the haptic feedback module 133 to generate tactile outputs on the device 100 that can be sensed by a user of the device 100 . In some embodiments, the at least one tactile output generator is positioned alongside or proximate a touch-sensitive surface (eg, touch-sensitive display system 112 ), and optionally, vertically (eg, vertically) the touch-sensitive surface. , generate a tactile output by moving in/out of the surface of the device 100 ) or laterally (eg, back and forth within the same plane as the surface of the device 100 ). In some embodiments, the at least one tactile output generator sensor is located on the back of the device 100 , opposite the touch screen display 112 positioned on the front of the device 100 .

Device 100 also optionally includes one or more accelerometers 168 . 1A shows an accelerometer 168 coupled to a peripherals interface 118 . Alternatively, the accelerometer 168 is optionally coupled to the input controller 160 of the I/O subsystem 106 . In some embodiments, the information is displayed in a portrait view or a landscape view over the touch screen display based on analysis of data received from one or more accelerometers. In addition to the accelerometer(s) 168 , device 100 may include a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) optionally including a receiver (not shown).

In some embodiments, software components stored in memory 102 include operating system 126 , communication module (or set of instructions) 128 , contact/motion module (or set of instructions) 130 , graphics module ( or set of instructions) 132 , a text input module (or set of instructions) 134 , a Global Positioning System (GPS) module (or set of instructions) 135 , and applications (or sets of instructions) ( 136). Furthermore, in some embodiments, memory 102 stores device/global internal state 157 as shown in FIGS. 1A and 3 . Device/global internal state 157 includes an active application state indicating which applications (if any) are currently active; a display state indicating which applications, views, or other information occupy the various areas of the touch screen display 112 ; sensor status, including information obtained from various sensors and input control devices 116 of the device; and location information regarding the location and/or posture of the device.

Operating system 126 (eg, an embedded operating system such as Darwin, RTXC, Linux, UNIX, OS X, WINDOWS, or VxWorks) performs general system tasks (eg, memory management, storage device control, power management, etc.) and includes various software components and/or drivers for controlling and managing, and enables communication between the various hardware and software components.

The communication module 128 is configured to facilitate communication with other devices via one or more external ports 124 , and also to process data received by the RF circuitry 108 and/or external port 124 . Includes various software components. External port 124 (eg, Universal Serial Bus (USB), FIREWIRE, etc.) provides connection to other devices directly or indirectly through a network (eg, Internet, wireless LAN, etc.). is composed In some embodiments, the external port is a multi-pin (eg, 30-pin) connector that is the same as or similar to and/or compatible with the 30-pin connector used in iPod (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally senses contact with touch screen 112 (in conjunction with display controller 156 ), and other touch sensitive devices (eg, a touchpad or physical click wheel). The contact/motion module 130 determines whether a contact occurs (eg, detection of a finger-down event), a strength of a contact (eg, a force or pressure of a contact, or a force or pressure of a contact) substitute), determining whether a contact has moved and tracking movement across a touch-sensitive-surface (e.g., detection of one or more finger-dragging events), and determining whether to cease contact (e.g., , detection of a finger-up event or release of a contact), and includes various software components for performing various operations related to detection of a contact. The contact/motion module 130 receives contact data from the touch-sensitive surface. Determination of movement of the contact point represented by the set of contact data optionally includes determination of a speed (magnitude), velocity (magnitude and direction), and/or acceleration (change in magnitude and/or direction) of the contact point. These operations are optionally applied to single contacts (eg, one finger contacts) or to multiple simultaneous contacts (eg, "multi-touch"/multiple finger contacts). In some embodiments, the contact/motion module 130 and display controller 156 sense a contact over the touch pad.

In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an action was performed by a user (eg, determine whether a user "clicked" on an icon). . In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (eg, the intensity thresholds are not determined by activation thresholds of particular physical actuators, device 100 ) can be adjusted without changing the physical hardware of the For example, the mouse "click" threshold of a trackpad or touch screen display can be set to a large range of predetermined thresholds without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device may be required to adjust intensity thresholds (eg, by adjusting individual intensity thresholds and/or adjusting a plurality of intensity thresholds at once with a system-level click “Intensity” parameter). Software settings for adjusting one or more sets of ) are provided.

The contact/motion module 130 selectively detects a gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (eg, different movements, timings, and/or intensities of sensed contacts). Thus, the gesture is, optionally, detected by detection of a specific contact pattern. For example, detection of a tap gesture may detect a finger-down event followed by a finger-up (lift-off) at the same (or substantially the same location) as the finger-down event (eg, at the location of the icon). (lift off)) event detection. As another example, detection of a finger swipe gesture on a touch-sensitive surface detects a finger-down event, then detects one or more finger-drag events, followed by a finger-up (lift-off) event. includes sensing.

Graphics module 132 renders and displays graphics on touch screen 112 or other display, including components for changing a visual effect (eg, brightness, transparency, saturation, contrast, or other visual property) of the displayed graphic. It includes various known software components for As used herein, the term “graphic” includes without limitation text, web pages, icons (eg, user-interface objects including soft keys), digital images, videos, animations, and the like. , which includes objects that can be displayed to the user.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. Graphics module 132 receives one or more codes from applications, etc. that specify graphics to be displayed along with coordinate data and other graphics property data, if necessary, and then generates screen image data to output to display controller 156 . do.

The haptic feedback module 133 is an instruction used by the tactile output generator(s) 167 to generate tactile outputs at one or more locations on the device 100 in response to user interactions with the device 100 . It includes various software components for creating

Optionally, a component of graphics module 132 , text input module 134 , accepts various applications (eg, contacts 137 , email 140 , IM 141 , browser 147 , and text input). It provides soft keyboards for entering text into other applications that require it.

The GPS module 135 determines the device's location and uses this information to various applications (eg, to the phone 138 for use in location-based dialing), to the camera 143 as photo/video metadata, and to weather widgets, local yellow page widgets, and applications that provide location-based services such as map/navigation widgets).

Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:

연락처 모듈(137)(때때로 주소록 또는 연락처 목록이라고 지칭됨);

Contacts module 137 (sometimes referred to as an address book or contact list);

전화 모듈(138);

phone module 138;

화상 회의 모듈(139);

video conferencing module 139;

이메일 또는 이메일 클라이언트 모듈(140);

e-mail or e-mail client module 140;

인스턴트 메시징(IM) 모듈(141);

an instant messaging (IM) module 141;

운동 지원 모듈(142);

exercise support module 142;

정지 및/또는 비디오 이미지들을 위한 카메라 모듈(143);

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

이미지 관리 모듈(144);

image management module 144;

브라우저 모듈(147);

browser module 147;

캘린더 모듈(148);

calendar module 148;

날씨 위젯(149-1), 주식 위젯(149-2), 계산기 위젯(149-3), 알람 시계 위젯(149-4), 사전 위젯(149-5), 및 사용자에 의해 획득되는 다른 위젯들뿐만 아니라, 사용자-생성 위젯들(149-6) 중 하나 이상을 선택적으로 포함하는 위젯 모듈들(149);

Weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user as well as widget modules 149 that optionally include one or more of user-created widgets 149-6;

사용자-생성 위젯들(149-6)을 만들기 위한 위젯 생성기 모듈(150);

a widget generator module 150 for creating user-created widgets 149-6;

검색 모듈(151);

search module 151;

선택적으로, 비디오 플레이어 모듈 및 음악 플레이어 모듈로 구성된 비디오 및 음악 플레이어 모듈(152);

Optionally, a video and music player module 152 consisting of a video player module and a music player module;

메모 모듈(153);

memo module 153;

지도 모듈(154); 및/또는

map module 154; and/or

온라인 비디오 모듈(155).

Online video module (155).

Optionally, examples of other applications 136 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.

Along with the touch screen 112 , the display controller 156 , the contact module 130 , the graphics module 132 and the text input module 134 , the contacts module 137 can be configured to: add name(s) to an address book; delete name(s) from address book; associating a name with a phone number(s), email address(es), physical address(es), or other information; associating an image with a name; sorting and sorting names; address book or contact list, including providing phone numbers or email addresses to initiate and/or facilitate communication by phone 138 , video conferencing 139 , email 140 , or IM 141 , etc. (eg, stored in application internal state 192 of contacts module 137 in memory 102 or memory 370 ).

RF circuit 108 , audio circuit 110 , speaker 111 , microphone 113 , touch screen 112 , display controller 156 , contact module 130 , graphics module 132 , and text input module In conjunction with 134, phone module 138, optionally, enters a sequence of characters corresponding to a phone number, accesses one or more phone numbers in address book 137, modifies the entered phone number, and each It is used to dial the phone number of a person, conduct a conversation, and disconnect or hang up when the conversation is complete. As noted above, wireless communication optionally uses any of a plurality of communication standards, protocols and technologies.

RF circuit 108 , audio circuit 110 , speaker 111 , microphone 113 , touch screen 112 , display controller 156 , optical sensor 164 , optical sensor controller 158 , contact module ( 130 ), along with graphics module 132 , text input module 134 , contact list 137 and phone module 138 , video conferencing module 139 , according to user instructions, allows the user and one or more other participants to participate. executable instructions for initiating, conducting, and terminating a video conference between

Along with RF circuitry 108 , touch screen 112 , display controller 156 , contact module 130 , graphics module 132 and text input module 134 , email client module 140 responds to user instructions. and executable instructions for composing, sending, receiving, and managing email in response. Together with the image management module 144 , the email client module 140 makes it very easy to create and send emails with still or video images captured with the camera module 143 .

The instant messaging module 141, along with the RF circuitry 108, the touch screen 112, the display controller 156, the contact module 130, the graphics module 132, and the text input module 134, are configured to respond to instant messages. Enter a sequence of corresponding characters, modify previously entered characters, send respective instant messages (eg, SMS for phone-based instant messages or Multimedia Message Service; MMS) protocol, or using XMPP, SIMPLE or IMPS for Internet-based instant messages), receive instant messages, and view received instant messages. In some embodiments, the transmitted and/or received instant messages are optionally graphics, photos, audio files, video files and/or other attachments supported by MMS and/or Enhanced Messaging Service (EMS). include those As used herein, “instant messaging” refers to phone-based messages (eg, messages sent using SMS or MMS) and internet-based messages (eg, sent using XMPP, SIMPLE or IMPS). messages) refer to both.

RF circuit 108 , touch screen 112 , display controller 156 , contact module 130 , graphics module 132 , text input module 134 , GPS module 135 , map module 154 , and In conjunction with the music player module 146 , the workout support module 142 creates workouts (eg, along with time, distance, and/or calorie expenditure goals); communicate with motion sensors (sports devices); receive motion sensor data; calibrate sensors used to monitor movement; select and play music during exercise; executable instructions to display, store, and transmit athletic data.

camera, along with touch screen 112 , display controller 156 , optical sensor(s) 164 , optical sensor controller 158 , contact module 130 , graphics module 132 and image management module 144 . The module 143 is configured to capture still images or video (including a video stream) and store them in the memory 102 , modify characteristics of the still image or video, or retrieve the still image or video from the memory 102 . Contains executable commands to delete.

Along with the touch screen 112 , the display controller 156 , the contact module 130 , the graphics module 132 , the text input module 134 and the camera module 143 , the image management module 144 is configured to freeze and/or executable instructions for arranging, modifying (eg, editing), or otherwise manipulating, labeling, deleting, presenting (eg, in a digital slide show or album), and storing video images.

Browser module 147, along with RF circuitry 108 , touch screen 112 , display system controller 156 , contact module 130 , graphics module 132 and text input module 134 , provides web pages or portions thereof, as well as executable instructions for browsing the Internet according to user instructions, including retrieving, linking to, receiving, and displaying attachments and other files linked to web pages. .

RF circuit 108 , touch screen 112 , display system controller 156 , contact module 130 , graphics module 132 , text input module 134 , email client module 140 , and browser module 147 . ), calendar module 148 executes executable instructions for creating, displaying, modifying, and storing calendars and data associated with calendars (eg, calendar entries, to-do lists, etc.) according to user instructions. include

Widget modules (with RF circuit 108 , touch screen 112 , display system controller 156 , contact module 130 , graphics module 132 , text input module 134 and browser module 147 ) 149 is, optionally, downloaded and used by the user (eg, weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary). widgets 149-5) or created by the user (eg, user-created widgets 149-6), mini-applications. In some embodiments, the widget includes a Hypertext Markup Language (HTML) file, a Cascading Style Sheets (CSS) file, and a JavaScript file. In some embodiments, a widget includes an Extensible Markup Language (XML) file and a JavaScript file (eg, Yahoo! widgets).

A widget generator module ( 150) is optionally used by the user to create widgets (eg, change a user-specific portion of a web page into a widget).

With touch screen 112 , display system controller 156 , contact module 130 , graphics module 132 , and text input module 134 , search module 151 may perform one or more search criteria in accordance with user instructions. executable instructions for searching text, music, sound, image, video, and/or other files in memory 102 that match (eg, one or more user-specific search terms).

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

Together with the touch screen 112 , the display controller 156 , the contact module 130 , the graphics module 132 , and the text input module 134 , the memo module 153 is configured to take notes, a to-do list according to user instructions. and executable instructions for creating and managing files and the like.

RF circuit 108 , touch screen 112 , display system controller 156 , contact module 130 , graphics module 132 , text input module 134 , GPS module 135 , and browser module 147 . In conjunction with, the map module 154 may optionally provide maps and data associated with the maps according to user instructions (eg, driving directions; data regarding shops and other points of interest at or near a particular location; and other location-based data) to receive, display, modify, and store.

Touch screen 112 , display system controller 156 , contact module 130 , graphics module 132 , audio circuit 110 , speaker 111 , RF circuit 108 , text input module 134 , email In conjunction with the client module 140 and browser module 147, the online video module 155 allows a user to access, browse, receive (eg, by streaming and/or download) email with a link to a particular online video; instructions for playing (eg, on a touch screen or on an externally connected display via external port 124 ), sending, and otherwise managing 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.

Each of the modules and applications identified above is executable for performing one or more of the functions described above and the methods described herein (eg, the computer-implemented methods and other information processing methods described herein). Corresponds to a set of instructions. Such modules (ie, sets of instructions) need not be implemented as separate software programs, procedures or modules, so that various subsets of such modules are, optionally, combined or otherwise in various embodiments, in various embodiments. are rearranged to In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Also, memory 102 optionally stores additional modules and data structures not described above.

In some embodiments, device 100 is a device in which operation of a predefined set of functions of the device is performed exclusively via a touch screen and/or touchpad. By using a touch screen and/or a touch pad as the primary input control device for operation of device 100 , the number of physical input control devices (eg, push buttons, dials, etc.) of device 100 is optional , is reduced.

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

1B is a block diagram illustrating example components for event processing, in accordance with some embodiments. In some embodiments, memory (102 in FIG. 1A or 370 in FIG. 3 ) includes event sorter 170 (eg, within operating system 126 ) and each application 136 - 1 (eg, the application described above). 137-13, 155, 380-390).

The event arranger 170 receives the event information and determines the application 136 - 1 to which to forward the event information, and the application view 191 of the application 136 - 1 . The event arranger 170 includes an event monitor 171 and an event dispatcher module 174 . In some embodiments, application 136 - 1 includes an application internal state 192 that, when the application is active or running, represents the current application view(s) displayed over touch-sensitive display 112 . In some embodiments, the device/global internal state 157 is used by the event sorter 170 to determine which application(s) is currently active, and the application internal state 192 is the event sorter 170 . ) to determine the application views 191 to which the event information will be delivered.

In some embodiments, application internal state 192 indicates resume information to be used when application 136-1 resumes execution, information being displayed, or a user interface ready for display by application 136-1. one or more of state information, a status queue that allows the user to return to a previous state or view of the application 136-1, and a redo/undo queue of previous actions taken by the user; including additional information such as

The event monitor 171 receives event information from the peripheral interface 118 . The event information includes information regarding a sub-event (eg, a user touch on the touch-sensitive display 112 as part of a multi-touch gesture). Peripheral interface 118 may include I/O subsystem 106 or a sensor (eg, proximity sensor 166 ), accelerometer(s) 168 , and/or microphone 113 (via audio circuitry 110 ). etc.) to transmit information received from 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 transmits event information only when there is a significant event (eg, accepting input exceeding a predetermined noise threshold and/or input for exceeding a predetermined duration). do.

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

The hit view determination module 172 provides software procedures for determining where a sub-event occurred within the one or more views when the touch-sensitive display 112 displays one or more views. Views are made up of controls and other elements that the user can see on the display.

Another aspect of a 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 views (of each application) for which touch is sensed optionally correspond to program levels within the application's program or view hierarchy. For example, the lowest-level view in which a touch is sensed is optionally referred to as a hit view, and the set of events recognized as appropriate inputs is, optionally, at least in the hit view of the initial touch that initiates the touch-based gesture. In part, it is determined on the basis of

The hit view determination module 172 receives information related to sub-events of the touch-based gesture. If the application has multiple views organized in a hierarchy, the hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should handle the sub-event. In most situations, the hit view is the lowest level view in which the initiated sub-event (ie, the first sub-event in the sequence of sub-events forming the event or potential event) occurs. Once a hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source that caused it to be identified as a hit view.

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

The event dispatcher module 174 dispatches event information to an event recognizer (eg, event recognizer 180 ). In embodiments that include an active event recognizer determination module 173 , the event dispatcher module 174 communicates event information to the event recognizer determined by the active event recognizer determination module 173 . In some embodiments, the event dispatcher module 174 stores event information, retrieved by the respective event receiver module 182 , in an event queue.

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

In some embodiments, application 136 - 1 includes a plurality of event handlers 190 and one or more application views 191 , each of which is a touch event occurring within a respective view of the application's user interface. Includes instructions for processing them. Each application view 191 of application 136 - 1 includes one or more event recognizers 180 . Typically, each application view 191 includes a plurality of event recognizers 180 . In other embodiments, one or more of the event recognizers 180 may be part of a separate module, such as a user interface kit (not shown) or a higher-level object from which the application 136 - 1 will inherit methods and other properties. am. In some embodiments, each event handler 190 may include one of event data 179 received from data updater 176 , object updater 177 , GUI updater 178 , and/or event arranger 170 . contains more than one. Event handler 190 optionally uses or calls data updater 176 , object updater 177 or GUI updater 178 to update application internal state 192 . Alternatively, one or more of the application views 191 include one or more respective event handlers 190 . Also, in some embodiments, one or more of data updater 176 , object updater 177 , and GUI updater 178 are included in each application view 191 .

Each event recognizer 180 receives event information (eg, event data 179 ) from the event sorter 170 , and identifies an event from the event information. The event recognizer 180 includes an event receiver 182 and an event comparator 184 . In some embodiments, event recognizer 180 also includes at least a subset of metadata 183 and event delivery instructions 188 (optionally including sub-event delivery instructions).

The event receiver 182 receives event information from the event sorter 170 . The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information such as the location of the sub-event. If the sub-event relates to motion of the touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the events include rotation of the device from one orientation to another (eg, from a portrait orientation to a landscape orientation, or vice versa), and the event information is the current orientation of the device (also referred to as device pose). ) and corresponding information about

The event comparator 184 compares the event information to predefined event or sub-event definitions and determines an event or sub-event based on the comparison, or determines or updates the status of the event or sub-event. In some embodiments, event comparator 184 includes event definitions 186 . Event definitions 186 include definitions of events (eg, predefined sequences of sub-events), eg, Event 1 187-1, Event 2 187-2, and the like. In some embodiments, sub-events within event 187 include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition for event 1 (187-1) is a double tap on the displayed object. A double tap is, for example, a first touch on the displayed object during a predetermined phase (touch start), a first lift-off during a predetermined phase (touch end), during a predetermined phase a second touch on the displayed object (touch start), and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 187 - 2 is dragging on the displayed object. Dragging includes, for example, a touch (or contact) over a displayed object during a predetermined phase, movement of the touch across the touch-sensitive display 112 , and liftoff of the touch (touch termination). In some embodiments, the event also includes information about one or more associated event handlers 190 .

In some embodiments, event definition 187 includes a definition of an event for each user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is 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 may - Perform a hit test to determine which of the interface objects are associated with a touch (sub-event). When each displayed object is associated with a respective event handler 190 , the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, the event comparator 184 selects the event handler associated with the sub-event and the object that triggers the hit test.

In some embodiments, the definition for each event 187 also includes deferred actions that delay delivery of event information until after it is determined whether the sequence of sub-events corresponds to or does not correspond to an event type of the event recognizer. do.

When each event recognizer 180 determines that the set of sub-events does not match any of the events in event definitions 186 , each event recognizer 180 determines whether an event is impossible, event failed, or event An end state is entered, after which each event recognizer ignores subsequent sub-events of the touch-based gesture. In this situation, other event recognizers (if any) that remain active on the hit view continue to track and process sub-events of the touch-based gestures in progress.

In some embodiments, each event recognizer 180 has configurable properties, flags, and configurable properties indicating how the event delivery system should perform sub-event delivery to actively engaged event recognizers, and and/or metadata 183 with lists. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how, or can interact with, event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to changing levels within a view or program hierarchy.

In some embodiments, each event recognizer 180 activates an event handler 190 associated with the event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognizer 180 passes event information associated with the event to an event handler 190 . Activation of event handler 190 is distinct from dispatching (and delayed dispatching) of sub-events to each hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with that 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 the sub-event without activating an event handler. Instead, sub-event delivery instructions deliver event information to event handlers associated with a series of sub-events or to actively engaged views. Event handlers associated with a series of sub-events or actively engaged views receive event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used within application 136 - 1 . For example, the data updater 176 updates a phone number used in the contacts module 137 or stores a video file used in the video player module 145 . In some embodiments, object updater 177 creates and updates objects used within application 136 - 1 . For example, object updater 176 creates a new user-interface object or updates the location of a user-interface object. 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 includes or accesses 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 each application 136 - 1 or application view 191 . In other embodiments, they are included in two or more software modules.

The discussion above regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs for operating multifunction devices 100 having input devices, but not all on touch screens. It should be understood that this is not disclosed. mouse movement and mouse button presses, eg, selectively cooperating with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on the touchpad; pen stylus inputs; movement of the device; verbal commands; detected eye movements; biometric inputs; and/or combinations thereof are optionally used as inputs corresponding to sub-events defining the event to be recognized.

2 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 user interface (UI) 200 . In this embodiment, as well as other embodiments described below, the user may, for example, use one or more fingers 202 (not to scale in the figures) or one or more styluses 203 (in the figures to scale). not shown), to select one or more of the graphics by gesturing on the graphics. 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 may optionally include one or more taps, one or more swipes (left to right, right to left, up and/or down) and/or rolling of a finger (right) contacted with device 100 . to left, left to right, up and/or down). In some implementations or situations, inadvertent contact with the graphic does not select the graphic. For example, a swipe gesture passing over an application icon optionally does not select a corresponding application when the gesture corresponding to the selection is a tap.

Device 100 also optionally includes one or more physical buttons, such as a “home” or menu button 204 . As noted above, the menu button 204 is used to navigate to an application 136 of a set of applications, optionally running selectively on the device 100 . Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112 .

In one embodiment, device 100 includes a touch screen 112 , a menu button 204 , a push button 206 for powering on/off the device and locking the device, a volume control button(s) 208 , a subscriber identity module (SIM) card slot 210 , a headset jack 212 , and a docking/charging external port 124 . Push button 206 optionally powers on/off the device by pressing the button and holding the button in a depressed state for a predefined time interval; lock the device by pressing the button and releasing the button before a predefined time interval elapses; and/or unlocking the device or initiating an unlocking process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions via microphone 113 . Device 100 may also, optionally, generate tactile outputs for a user of device 100 and/or one or more contact intensity sensors 165 to sense the intensity of contacts on touch screen 112 . one or more tactile output generators 167 for

3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (eg, children's learning toy), gaming system, or control device (eg, home or industrial use). controller). Device 300 typically includes one or more processing units (CPU) 310 , one or more network or other communication interfaces 360 , memory 370 , and one or more communication buses to interconnect these components ( 320). Communication buses 320 optionally include circuitry (sometimes referred to as a chipset) that interconnects system components and controls communication between them. Device 300 includes an input/output (I/O) interface 330 that includes a display 340 , which is typically a touch screen display. I/O interface 330 may also optionally include a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, a tactile output generator for generating tactile outputs on device 300 ( 357 (eg, similar to tactile output generator(s) 167 described above with reference to FIG. 1A ), sensors 359 (eg, contact intensity sensor(s) 165 described above with reference to FIG. 1A ) ) and light, acceleration, proximity, touch-sensitive, and/or contact intensity sensors). memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; optionally including 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 located remotely from CPU 310(s). In some embodiments, memory 370 includes programs, modules, and data structures similar to programs, modules, and data structures stored in memory 102 of portable multifunction device 100 ( FIG. 1A ). or a subset thereof. In addition, the memory 370 optionally stores additional programs, modules and data structures not present in the memory 102 of the portable multifunction device 100 . For example, memory 370 of device 300 may optionally include drawing module 380 , presentation module 382 , word processing module 384 , website creation module 386 , disk authoring module 388 , and/or the spreadsheet module 390 , while the memory 102 of the portable multifunction device 100 ( FIG. 1A ) optionally does not store these modules.

Each of the above elements identified in FIG. 3 is optionally stored in one or more of the aforementioned memory devices. Each of the previously identified modules corresponds to a set of instructions for performing the aforementioned function. The modules or programs identified above (ie, sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus, in various embodiments, various subsets of these modules may optionally , combined or otherwise rearranged. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. In addition, memory 370 optionally stores additional modules and data structures not described above.

Attention is now directed to embodiments of user interfaces (“UI”) implemented on portable multifunction device 100 , optionally.

4A illustrates an example user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces are optionally implemented on device 300 . In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

셀룰러 및 Wi-Fi 신호들과 같은 무선 통신(들)에 대한 신호 세기 표시자(들)(402);

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

시간(404);

time 404;

블루투스 표시자(405);

Bluetooth indicator 405;

배터리 상태 표시자(406);

battery status indicator 406 ;

다음과 같은, 빈번하게 사용되는 애플리케이션들을 위한 아이콘들을 가진 트레이(408):

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

부재 중 전화들 또는 음성메일 메시지들의 개수의 표시자(414)를 선택적으로 포함하는, "전화"로 라벨링된, 전화 모듈(138)용 아이콘(416);

an icon 416 for the phone module 138, labeled “Call”, optionally including an indicator 414 of the number of missed calls or voicemail messages;

읽지 않은 이메일들의 개수의 표시자(410)를 선택적으로 포함하는, "메일"로 라벨링된, 이메일 클라이언트 모듈(140)용 아이콘(418);

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

"브라우저"로 라벨링된, 브라우저 모듈(147)용 아이콘(420); 및

icon 420 for browser module 147, labeled “Browser”; and

아이팟(애플 인크.의 상표) 모듈(152)로도 지칭되는, "아이팟"으로 라벨링된, 비디오 및 음악 플레이어 모듈(152)용 아이콘(422); 및

icon 422 for video and music player module 152, labeled "iPod", also referred to as iPod (trademark of Apple Inc.) module 152; and

다음과 같은, 다른 애플리케이션들용 아이콘들:

Icons for different applications, such as:

"텍스트"로 라벨링된, IM 모듈(141)용 아이콘(424);

icon 424 for IM module 141, labeled "Text";

"캘린더"로 라벨링된, 캘린더 모듈(148)용 아이콘(426);

icon 426 for calendar module 148, labeled “Calendar”;

"사진"으로 라벨링된, 이미지 관리 모듈(144)용 아이콘(428);

icon 428 for image management module 144, labeled "Photo";

"카메라"로 라벨링된, 카메라 모듈(143)용 아이콘(430);

icon 430 for camera module 143, labeled “camera”;

"온라인 비디오"로 라벨링된, 온라인 비디오 모듈(155)용 아이콘(432);

icon 432 for online video module 155, labeled “Online Video”;

"주식"으로 라벨링된, 주식 위젯(149-2)용 아이콘(434);

icon 434 for stock widget 149-2, labeled "Stocks";

"지도"로 라벨링된, 지도 모듈(154)용 아이콘(436);

icon 436 for map module 154, labeled “Map”;

"날씨"로 라벨링된, 날씨 위젯(149-1)용 아이콘(438);

icon 438 for weather widget 149-1, labeled "weather";

"시계"로 라벨링된 알람 시계 위젯(149-4)용 아이콘(440);

icon 440 for alarm clock widget 149-4 labeled "Clock";

"운동 지원"으로 라벨링된, 운동 지원 모듈(142)용 아이콘(442);

icon 442 for exercise support module 142, labeled "Workout Support";

"메모"로 라벨링된, 메모 모듈(153)용 아이콘(444); 및

icon 444 for notes module 153, labeled “Notes”; and

디바이스(100) 및 그의 다양한 애플리케이션들(136)을 위한 설정에의 엑세스를 제공하는, 설정 애플리케이션 또는 모듈용 아이콘(446).

Icon 446 for a settings application or module, providing access to settings for device 100 and its various applications 136 .

It should be noted that the icon labels illustrated in FIG. 4A are exemplary only. For example, icon 422 for video and music player module 152 is labeled "Music" or "Music Player". Other labels are, optionally, used for various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to each application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to the particular application icon.

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

Although some of the examples that follow will be given with reference to inputs on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device includes a display and a display as shown in FIG. 4B . It senses inputs on a separate touch-sensitive surface. In some embodiments, the touch-sensitive surface (eg, 451 in FIG. 4B ) has a major axis (eg, 452 in FIG. 4B ) that corresponds to a major axis (eg, 453 in FIG. 4B ) on the display (eg, 450 ). According to these embodiments, the device senses contacts (eg, 460 and 462 in FIG. 4B ) with the touch-sensitive surface 451 at locations corresponding to respective locations on the display (eg, FIG. 4B ). , 460 corresponds to 468 and 462 corresponds to 470). In this way, user inputs (eg, contacts 460 , 462 and their movements) sensed by the device on the touch-sensitive surface (eg, 451 in FIG. 4B ) can be detected as the touch-sensitive surfaces are separate from the display. Used to manipulate the user interface on the multifunction device's display (eg, 450 in FIG. 4B ) by the device in the individual case. It should be understood that similar methods are, optionally, used with other user interfaces described herein.

Additionally, although the examples that follow are given primarily with reference to finger inputs (eg, finger contacts, tap gestures, finger swipe gestures), in some embodiments, the one or more user inputs are other input device It should be understood that input from (eg mouse-based input or stylus input) is replaced. For example, a swipe gesture is optionally replaced with a mouse click (eg, instead of a contact) followed by movement of the cursor along the path of the swipe (eg, instead of movement of the contact). As another example, the tap gesture is, optionally, replaced with a mouse click while the cursor is positioned over the location of the tap gesture (eg, in lieu of detection of a contact and subsequent cessation of detection of the touch). Similarly, where multiple user inputs are sensed simultaneously, it should be understood that multiple computer mice are, optionally, used simultaneously, or mouse and finger contacts are, optionally, used simultaneously.

As used herein, the term “focus selector” refers to an input element that represents the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor is over a particular user interface element (eg, a button, window, slider, or other user interface element) while the input (eg, press input) is on a touch-sensitive surface (eg, The cursor acts as a “focus selector” such that when sensed on touch pad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B , for example, certain user interface elements are adjusted in accordance with the sensed input. . Some including a touch-screen display (eg, touch-sensitive display system 112 of FIG. 1A or touch screen 112 of FIG. 4A ) that enables direct interaction with user interface elements on the touch-screen display In implementations, a contact sensed on the touch screen acts as a “focus selector” such that an input (eg, a touch-pressed input) can be displayed on a specific user interface element (eg, a button, window, slider or other location of the user interface element), the particular user interface element is adjusted according to the sensed input. In some implementations, focus is moved from one area of the user interface to another area of the user interface without movement of a corresponding cursor or contact on the touch-screen display (eg, changing focus from one button to another button). by use of the moving tab key or arrow keys); In these implementations, the focus selector moves in response to movement of focus between different regions of the user interface. Regardless of the specific form taken by the focus selector, the focus selector is generally a user interface element (or contact on a touch-screen display) controlled by a user to convey the user's intended interaction with the user interface ( eg, by indicating to the device the element of the user interface with which the user would like to interact). For example, the position of a focus selector (eg, cursor, contact, or selection box) over each button while a press input is sensed on a touch-sensitive surface (eg, a touchpad or touch screen) can be determined by the user pressing each button. will indicate that it is about to be activated (as opposed to other user interface elements shown on the device's display).

Attention is now directed to embodiments of user interfaces (“UI”) and associated processes that may be implemented on an electronic device having a display and a touch-sensitive surface, such as device 300 or portable multifunction device 100 .

As noted above, device 100 includes a number of applications 136 configured to run on device 100 . One of the plurality of applications 136 is the email client module 140 and a user may interact with the application on the computing device 100 . As described further below, the email client module 140 has various user interfaces that enhance the user experience with the computing device 100 when using the application.

Swipe options and gestures within the email client module UI

5A illustrates a vertical view of icons, also termed a “Springboard” layout, for applications on device 100 , according to one embodiment. For example, tray 408 icons are for the following applications or modules:

"메시지들"로 라벨링된, IM 모듈(141)용 아이콘(424);

icon 424 for IM module 141, labeled "Messages";

읽지 않은 이메일들의 개수의 표시자(410)를 선택적으로 포함하는, "메일"로 라벨링된, 이메일 클라이언트 모듈(140)용 아이콘(418);

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

"브라우저"로 라벨링된, 브라우저 모듈(147)용 아이콘(420); 및

icon 420 for browser module 147, labeled “Browser”; and

"음악"으로 라벨링된, 비디오 및 음악 플레이어 모듈(152)용 아이콘(422); 및

icon 422 for video and music player module 152, labeled "Music"; and

Icons for other applications include:

"메시지들"로 라벨링된, IM 모듈(141)용 아이콘(424);

icon 424 for IM module 141, labeled "Messages";

"캘린더"로 라벨링된, 캘린더 모듈(148)용 아이콘(426),

icon 426 for calendar module 148, labeled "Calendar";

"음악"으로 라벨링된, 비디오 및 음악 플레이어 모듈(152)용 아이콘(422)

Icon 422 for video and music player module 152, labeled "Music"

읽지 않은 이메일들의 개수의 표시자(410)를 선택적으로 포함하는, "메일"로 라벨링된, 이메일 클라이언트 모듈(140)용 아이콘(418);

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

"날씨"로 라벨링된 날씨 위젯(149-1)용 아이콘(438);

icon 438 for weather widget 149-1 labeled "weather";

"브라우저"로 라벨링된, 브라우저 모듈(147)용 아이콘(420); 및

icon 420 for browser module 147, labeled “Browser”; and

"메모"로 라벨링된, 메모 모듈(153)용 아이콘(444).

Icon 444 for notes module 153, labeled "Notes".

In other embodiments, different and/or additional icons may be presented in the user interface 500 .

Also, Fig. 5A illustrates a gesture of executing or launching an application. The initiation gesture is directed towards the “mail” icon 418 representing a user request to execute the email client module 140 presented by the “mail” icon 418 . Although the initiation gesture is described for a portrait view of icons, the initiation gesture may also be received in a landscape view of icons.

In one embodiment, the initiating gesture or other suitable gesture herein includes a tap on the icon. In general, a gesture is considered to be an icon “on” when the user's finger(s) touches at least a portion of the icon displayed on the user interface 500 . In FIG. 5A , the initiating gesture is presented by contact 502 of the user's finger on the “mail” icon 418 , shown as a dashed ellipse. In response to the initiation gesture, device 100 ignores (ie, removes) the icons from the display on user interface 500 and in place the mail corresponding to “mail” icon 418 as shown in FIG. 5B . Displays the application view 504 . The application view 504 of the email client module 140 is the user interface of the email client module 140 . Mail application view 504 corresponding to “Mail” icon 418 contains email messages from the user's email account(s).

In response to a user selection of the menu button, for example, through contact of the menu button 204 , the device 100 displays the mail application view 504 of the “mail” icon 418 from the user interface 500 . Ignore and display the icons as shown in Fig. 5a. In one embodiment, ignoring the application simply removes the mail application view 504 from being displayed on the user interface 500 . Although the mail application view 504 of the application is no longer displayed over the user interface, the ignored application still runs in a background process on the device 100 . Accordingly, the email client module 140 shown in FIG. 5B is still running in the background of the device 100 even though the mail application view 504 of the email client module 140 has been ignored.

5B illustrates a mail application view 504 of an email application, according to one embodiment. Mail application view 504 displays portions of email messages in email threads 506A, 506B, 506C, 506D, 506E from the user's email account. Each marked portion of an email message in an email thread, referred to herein as message portion 506 , represents sender information 508 , subject information 510 , and a portion of the body of email 512 , and includes: Other suitable information associated with the portion 506 may be displayed. Additionally, the message portion 506 may display indicators such as an attachment indicator 514 and a VIP sender indicator 516 . Additional indicators include a VIP thread indicator, described further in conjunction with FIG. 11 , attachment indicator 514 indicating that an associated email thread or message portion is a picture, video, audio file, document, or email thread 506 . Indicates to have an attachment, such as any other suitable file that can be attached to an e-mail message in . For example, the attachment indicator 514 is a paper clip icon. VIP sender indicator 516 indicates that the received email is from a sender previously marked as a VIP sender. For example, the sender's indication as a VIP sender is a request to receive a notification (eg, via the VIP sender indicator 516 ) of an email sent from the sender. In the illustrated embodiment, the VIP sender indicator 516 is a star icon.

The mail application view 504 of the email application may include a return element 518 , an edit element 520 , a refresh element 522 , a new drafting element 524 , or any other suitable element that may be used within the email application. It includes additional user interface elements such as Return element 518, if selected, displays email accounts associated with the user or additional folders in the account. Edit element 520 , if selected, displays options for the user to remove one or more email threads from mail application view 504 . The refresh element 522, if selected, refreshes the mail application view 504 and displays, for example, new received emails. New drafting element 524, if selected, displays a new drafting email within the email application.

5C, 5D, and 5E illustrate receipt of a gesture to display swipe options 528 within an email application, according to one embodiment. The display gesture represents a user request to display swipe options 528 for an email thread 506 or message portion 506 within an email application. The display gesture may include a swipe on the touchscreen 112 in a direction substantially parallel to the email thread 506 , or at a location on the display that corresponds to an email message in the email thread 506 .

In one embodiment, the display gesture comprises dragging a contact (eg, a user's finger, stylus) from an initial position to a threshold distance from an initial position to a second position above the top of the email thread 506 displayed within the mail application view 504 . do. For example, as shown in FIG. 5C , contact 526 is sensed by device 100 at an initial location within email thread 506B. Contact 526 is continuous and drags, eg, in a direction substantially parallel to the width of email thread 506B, to a second location within email thread 506B, at least a threshold distance, eg, as shown in FIG. 5E . do. For example, contact 526 is a threshold from an initial position to a second position shown in FIGS. 5C , 5D , and 5E in continuous movement without release of contact with touch screen 112 of device 100 . kept at a distance. In another embodiment, instead of a threshold distance, the indication gesture includes dragging the contact at a threshold velocity atop the message portion 506 . Accordingly, contact 526 is held and dragged with a velocity in a direction substantially parallel to the width of message portion 506B. In other embodiments, other parameters of the maintained contact 526 are evaluated for the indication gesture. Other parameters may include the strength of the pressure of the contact 526 , or the number of contact points, or other measurable parameters of the contact and its movement.

After completion of the display gesture or a threshold distance or speed is reached, user interface elements, such as swipe options 528 , are displayed on one side (eg, left, right) of message portion 506B. In one embodiment, swipe options 528 slide out continuously and/or proportional to the distance reached or normalized by contact 526 . Thus, if contact 526 reaches half of the threshold distance, half of swipe options 528 is, for example, to the right of message portion 506B, as shown by swiping in progress in FIG. 5D . is displayed in If contact 526 reaches half the threshold distance, half of the threshold distance may be equal to 1/4 the length of swipe options 528 and then only 1/4 of swipe options 528 displayed to the right of the message portion 506B. In another embodiment, after contact 526 has reached a threshold distance, swipe options 528 do not slide out or are not displayed until snapped into place. In an embodiment where the display gesture includes a threshold speed, swipe options 528 slide out at a speed proportional to the speed of traversal of contact 526 .

In an embodiment where swipe options 528 are partially displayed when contact 526 is maintained, if contact 526 is not maintained until a threshold distance is reached and/or released, swipe options Fields 528 may be slid into the original view of message portion 506B out of view, hiding the “rubber band”, bounce back, or swipe options 528 .

In the illustrated example, once the threshold distance is reached, swipe options 528 are displayed to the right of message portion 506B and message portion 506B is displayed in the direction of the swipe but swipe options 528 displayed. move closer to In one embodiment as shown in FIG. 5E , for example, swipe options 528 include more option 528A, notification option 528B, and discard option 528C. do. 5A-5H, swipe options 528 include three options. Each option within the displayed swipe options 528 is selectable and, once selected, can perform an action on the message associated with the associated email thread or message portion, display a popup associated with the option, and You can display a sheet associated with options for additional actions to be taken on an email thread, and combinations thereof. The selection of options is further described in conjunction with FIGS. 8 and 13 . However, in other embodiments, the swipe options 528 may include one or more options 528 that select the settings application of device 100 , further described in conjunction with FIGS. 9 and 17 . It may be user-defined by the user of the device 100 through the

5F, 5G, and 5H illustrate receipt of a gesture to close swipe options 528 displayed within an email application, according to one embodiment. The close gesture represents a user request to close the swipe options for the message portion 506 within the email application. According to one embodiment, the close gesture may include a swipe in a direction substantially parallel to the message portion 506 , eg, in a direction opposite to that of the message portion 506 . For example, the other direction is opposite the direction of the display gesture for displaying the swipe options 528 shown in FIGS. 5C , 5D, and 5E .

In one embodiment, the close gesture comprises dragging the contact a threshold distance from an initial position to a second position on top of message portion 506 displaying swipe options 528 displayed within mail application view 504 . do. For example, contact 526 is sensed by device 100 at an initial location within message portion 506B, as shown in FIG. 5F . Contact 526 is held and dragged at a threshold distance to a second location within message portion 506B in another direction, such as a direction substantially parallel to the width of message portion 506B, as shown in FIG. 5H . . For example, contact 526 may be the result of contact with touch screen 112 of device 100 in successive movement at a threshold distance from an initial position to a second position shown in FIGS. 5F, 5G, and 5H. maintained without release. In another embodiment, instead of a threshold distance, the close gesture includes dragging the contact at a threshold speed on top of the message portion displayed within the mail application view 504 . Accordingly, contact 526 is held and dragged with a velocity in a direction substantially parallel to the width of message portion 506B. In other embodiments, other parameters of the maintained contact 526 are evaluated for the indication gesture. Other parameters may include the strength of the pressure of the contact or the number of contact points.

After completion of the close gesture or the threshold distance or speed has been reached, swipe options 528 are no longer displayed. In one embodiment, swipe options 528 slide in continuously and/or proportionally to a distance reached by contact 526 or a normalized distance, as described above and shown in FIG. 5G . ) or close. In another embodiment, the swipe options 528 do not slide in, do not close, or are not displayed after the contact 526 has reached a threshold distance until it disappears from view. In an embodiment where the close gesture includes a threshold speed, swipe options 528 slide in or close at a rate proportional to the speed of traversal of contact 526 .

In an embodiment where swipe options 528 are partially hidden when contact 526 is maintained, if contact 526 is not maintained until a threshold distance is reached and/or released, swipe options 528 ) may “rubber band” or bounce back out and display full swipe options 528 of message portion 506B, as shown in FIG. 5F . In the illustrated example, once the threshold distance or threshold speed is reached, the swipe options 528 are no longer visible, the message portion 506B is advanced in the other direction, and the message portion 506B is placed within the email application. can be seen in

In addition to displaying swipe options 528 , a default action may also be associated with a gesture, such as an enlarged swipe option 628 . 6A, 6B, 6C, and 6D illustrate receipt of a gesture to display an enlarged swipe option 628 within an email application, according to one embodiment. The display gesture represents a user request to display an enlarged swipe option 628 for the message portion 506B within the email application. The display gesture may include a swipe in a direction substantially parallel along the width of the message portion 506B. For example, the direction of the display gesture to display the enlarged swipe option 628 is the same direction of the display gesture to display the swipe options 528 .

In one embodiment, the display gesture comprises dragging the contact a threshold distance from the initial position to a second position on top of the message portion 506 displayed within the mail application view 504 . For example, contact 626 is sensed by device 100 at an initial location within message portion 506B, as shown in FIG. 6A . Contact 626 is held at a threshold velocity at its top and dragged or at a threshold distance in a direction substantially parallel to the width of message portion 506B, as shown in FIG. 6D in a manner similar to that described in FIG. 5 . dragged to a second position within the message portion 506B;

In one embodiment, the threshold distance for displaying the enlarged swipe option 628 is greater than the threshold distance for displaying the swipe options described in FIG. 5 , as shown in FIG. 6B . In this embodiment, if the direction of the swipe to display the enlarged swipe option 628 and the direction of the swipe to display the swipe options 528 are the same, if the swipe options 528 When the threshold distance to display is reached, swipe options 528 are shown, as shown in FIG. 6B . When the contact 626 is maintained and the threshold distance for displaying the enlarged swipe option 628 is reached, the enlarged swipe option 628 is shown, as shown in FIG. 6D .

In another embodiment, one or more threshold speeds may be used as indicators of a user request to indicate either swipe options 528 or enlarged swipe option 628 . For example, if the speed of movement of contact 626 is slower than a first threshold speed, swipe options 528 are displayed. If the speed of movement of the contact 626 is faster than the second threshold speed, an enlarged swipe option 628 is displayed. In one embodiment, the first threshold speed may be equal to or slower than the second threshold speed.

After completion of the display gesture or a threshold distance or velocity is reached, an enlarged swipe option 628 is displayed across the width of the message portion 506B, as shown in FIG. 6D . In one embodiment, the enlarged swipe option 628 slides out continuously and/or in proportion to the distance reached by the contact 626 in a manner similar to that previously described in FIG. 5 . In an embodiment where there are two threshold distances for displaying either the swipe options 528 or the enlarged swipe option 628 , once the contact 626 is the first for the swipe options 528 . If one threshold distance is exceeded, a portion of the enlarged swipe option 628 is shown proportional to the distance reached between the first threshold distance and the second threshold distance, as shown in FIG. 6C . If the half distance between the first threshold distance and the second threshold distance is reached, then half of the expanded swipe option 628 or half of the cropped swipe option 628 is to the right of the message portion 506B. is displayed The distance between the first threshold distance and the second threshold distance may be the length of the width of the message portion 506B or a distance normalized by the difference between the first and second threshold distances.

In another embodiment, the enlarged swipe option 628 does not slide out or display until snapped into place after the contact 626 has reached a threshold distance or a second threshold distance or threshold velocity from the preceding example. does not In an embodiment where the enlarged swipe option 628 is partially displayed when the contact 626 is maintained, if a threshold distance equal to the second threshold distance from the preceding example is, as shown in FIG. 6C , If the contact 626 is not maintained until reached and/or released, then the enlarged swipe option 628 is a “rubber band” or swipe options or to the original view of the message portion 506B, shown in FIG. 6A . It can bounce back to swipe options 528 , shown in FIG. 6B , which hides 528 .

In the illustrated example, once the threshold distance is reached, an enlarged swipe option 628 is displayed instead of message portion 506B and message portion 506B is no longer visible within the email application. For example, enlarged swipe option 628 may be an option included in swipe options 528, such as discard option 528C, or a default option or device, to be further described in conjunction with FIGS. 9 and 17 . It may be a different option that may be customized by the user of the device 100 through the settings application of 100 . The enlarged swipe option 628 is selectable and, once selected, can perform an action on the message associated with the associated email thread or message portion, display a popup associated with the option, and can perform actions taken over the associated email thread. It may display a sheet associated with an option for further actions, or a combination thereof. The selection of options is further described in conjunction with FIGS. 8 and 13 .

6E, 6F, and 6G illustrate receipt of a gesture to close an enlarged swipe option 628 within an email application, according to one embodiment. The close gesture represents a user request to close the expanded swipe option 628 for the message portion 506B within the email application. The close gesture may include a swipe in another direction substantially parallel to the width of the email thread 506B. For example, the other direction is the opposite of the direction of the swipe of the display gesture to display the enlarged swipe option 628 . Also, the closing gesture may be the same as the closing gesture described above with reference to FIG. 5 .

In one embodiment, the close gesture includes dragging the contact a threshold distance from the initial position to a second position on top of the message portion 506 displayed within the mail application view 504 . For example, as shown in FIG. 6E , contact 626 is sensed by device 100 at an initial location within message portion 506B. As shown in FIG. 6G in a manner similar to the close gesture described above in FIGS. 5 and 6A-6D , contact 626 is held at a threshold velocity on top of it and dragged or to a second position within message portion 506B. is dragged a threshold distance in a direction substantially parallel to the width of message portion 506B.

In one embodiment, in a manner similar to the threshold distance and threshold velocity described in FIGS. 6A, 6B, 6C, and 6D, as shown in FIG. 6F , the threshold distance for closing the enlarged swipe option 628 is FIG. longer than the threshold distance to close the swipe options described in 5. In this embodiment, if the direction of the swipe to display the enlarged swipe option 628 and the direction of the swipe to display the swipe options 528 are the same, as shown in Fig. 6f, if When the threshold distance for displaying swipe options 528 is reached, swipe options 528 are shown instead of the enlarged swipe option 628 shown in 6e. When contact 626 is maintained and the threshold distance for closing enlarged swipe option 628 is reached and the threshold distance for displaying swipe options 528 passes, swipe options 528 are also shown It is hidden in a manner similar to that described in 5.

In another embodiment, one or more threshold speeds may be used as indicators of a user request to close either swipe options 528 or expanded swipe option 628 . For example, if the speed of movement of contact 626 is faster than a first threshold speed, then enlarged swipe option 628 is closed and message portion 506B is displayed. If the speed of movement of the contact 626 is slower than the second threshold speed, the enlarged swipe option 628 is closed or hidden and the swipe options 528 are displayed. Then, if movement of contact 626 continues or repeats a longer length, swipe options 528 may also be closed or hidden and message portion 506 displayed. In this example, the first threshold speed may be greater than or equal to the second threshold speed.

After completion of the close gesture or the threshold distance or speed has been reached, the message portion 506B is displayed again. In one embodiment, the enlarged swipe option 628 slides in or continuously and/or contacts 626 as described in FIGS. 5, 6A, 6B, 6C, and 6D. ) closed in proportion to the distance reached by or normalized distance. There are two threshold distances for displaying either the swipe options 528 or the enlarged swipe option 628 , and the contact 626 is a second threshold for displaying the enlarged swipe option 628 . In an embodiment where there is no longer at , and not yet at the first threshold distance to display the swipe options 528, the enlarged swipe option 628 is reached between the first threshold distance and the second threshold distance. displayed in proportion to the distance.

In another embodiment, the enlarged swipe option 628 does not slide in or close until the contact 626 reaches a threshold distance, such as the first threshold distance from the previous example. In embodiments where the enlarged swipe option 628 is partially hidden when the contact 626 is maintained, the contact 626 is maintained until a threshold distance or a first threshold distance is reached and/or released. If not, the enlarged swipe option 628 may be “rubber band” or bounce back and displayed instead of the message portion 506B, as shown in FIG. 6E .

In the illustrated example, once the threshold distance to close the enlarged swipe option 528 is reached or the close gesture is complete, as shown in FIG. 6G , the enlarged swipe option 628 is Hidden and the message portion 506B is shown within the email application. For example, enlarged swipe option 628 may be an option included in swipe options 528, such as discard option 528C, or a default option or device, to be further described in conjunction with FIGS. 9 and 17 . It may be a different option that may be customized by the user of the device 100 through the settings application of 100 .

In addition to displaying swipe options 528 and enlarged swipe option 628 , additional one or more options may be displayed with a gesture on the other side of the message portion, such as swipe option 728 . 7A, 7B, and 7C illustrate a gesture for displaying a swipe option 728 within an email application and FIGS. 7D and 7E close a swipe option 728 within an email application, according to one embodiment. gestures for In one embodiment, the display and close gestures are the same as the display and close gestures described in conjunction with FIG. 5 for contact 726 and swipe option 728 . In one embodiment, the display gesture and/or close gesture differs from the display gesture and/or close gesture described in FIG. 5 in the direction of the swipe, a threshold distance, a threshold speed, or a combination thereof. For example, if swipe options 528 are displayed on a first side (eg, right) of message portion 506 , swipe option 728 is displayed on the other side or on the first side of message portion 506 . It is shown on the opposite side (eg, on the left). In this example, the direction of the swipe of the display gesture to display and/or close the swipe option 728 and/or the close gesture is an indicator to display or close the swipe options 528 and the enlarged swipe option 628 . The opposite direction of the swipe of the gesture and/or close gesture. In one embodiment, the threshold distance and/or threshold velocity for the display gesture and/or close gesture shown in FIGS. 7A, 7B, and 7C is the threshold distance for the display gesture and/or close gesture described in conjunction with FIG. 5 . and/or equal to the threshold speed.

In one embodiment, the displayed or closed swipe option 728 is presented and animated in a manner similar to the swipe options 528 described in conjunction with FIG. 5 . For example, swipe option 728 is a junk option. In the embodiment shown in FIG. 7 , swipe option 728 includes one option. However, in other embodiments, swipe option 728 may include multiple options, wherein one or more of the multiple options selects the settings application of device 100 , further described in conjunction with FIGS. 9 and 17 . It is user-defined by the user of the device 100 through the.

One or more of the aforementioned options (eg, swipe options 528 , enlarged swipe option 628 , and options within swipe option 728 ) may include a gesture that presents a sheet associated with the swipe option. can be selected through Once selected, an action is performed on the message associated with the associated email thread or message portion, displaying a popup associated with the option, displaying the sheet associated with the option for further actions to be taken on the associated email thread, or any combination thereof is also possible The selection of options is further described in conjunction with FIGS. 8 and 13 .

Indications and gestures of sheets for options in the email client module UI

8A illustrates receipt of a gesture to display a sheet for more options 528A within swipe options 528 within an email application and FIG. 8B illustrates a sheet for more options 528A, in accordance with one embodiment. 800) is exemplified. The gestures disclosed herein may also be applied to display a sheet for swipe options 528 , enlarged swipe option 628 , and other options displayed within swipe option 728 . In one embodiment, the gesture includes, for example, a tap over an option, such as more option 528A, shown as contact 826 (dotted ellipse) in FIG. 8A . In response to the gesture, device 100 displays sheet 800 of more options 528A as shown in FIG. 8B .

In one embodiment, the sheet 800 for more options 528A includes the following actions that can be taken with message portion 506B, as shown in FIG. 8B: Reply, Forward, Flag, Read. Mark as , show related messages, move messages, and cancel. The included actions may be customized by the user of the device 100 through a settings application of the device 100 , which will be further described with reference to FIG. 9 . If the user selects an action displayed on the sheet 800 , for example by contacting a portion of the display corresponding to an action on the sheet 800 , the action is displayed in a corresponding email thread 506B or message portion ( 506B).

Customization of swipe options within the email client module UI

Options within swipe options 528 , enlarged swipe option 628 , and swipe options 728 may be customized by the user within the settings application. 9A-9F illustrate pages 902 , 904 , 906 , 908 , 910 , 912 within an application view of a settings application, according to one embodiment. 9 describes swipe options 528 , enlarged swipe option 628 , swipe option 728 , and customization of options within the actions presented in the sheet for options. In alternative embodiments, an application(s) other than the settings applications or other page(s) within the settings applications may be used to customize the options and sheets.

9A illustrates a “zoom in” gesture within notification center 902 associated with a settings application. In one embodiment, the zoom in gesture includes a tap over the representation of the “mail” icon 418 , shown as contact 926 in FIG. 9A . In response to the zoom in gesture, as shown in FIG. 9B , a mail page 904 is displayed within the settings application. At mail page 904 , the user may swipe options within the email application (eg, options within swipe options 528 , enlarged swipe option 628 , swipe through, eg, via selection of a radio button). option 728) may be selected. In response to contact 926 with the radio button, according to one embodiment, a custom option may be made available as shown in the modified mail page 906 of FIG. 9C . In response to a magnification gesture sensed by the device 100 for the custom option, for example, via contact 926 with the custom option, a custom swipe options page 908 is displayed within the settings application. do. The custom swipe options page 908 includes options to customize options and customize alert settings associated with the swipe options. In response to a magnification gesture sensed by the device 100 for the options, for example, via contact 926 with the options, as shown in FIG. 9E , the options page 910 is displayed within the settings application. is displayed In the options page 910 , one or more of the options (eg, options within swipe options 528 , enlarged swipe option 628 , swipe option 728 ) can be customized or You can have default options. The characteristics of the options can also be customized, such as color. For example, more option 528A may be blue, alert option 528B may be orange, discard option 528C may be red, and junk option may be yellow. In response to a magnification gesture sensed by device 100 for option 1 , for example, via contact 926 of the option 1 option, an option 1 page 912 is displayed within the settings application as shown in FIG. 9F . do.

Method for Swipe Options in Email Client Module UI

10 is a flowchart of a method for displaying one or more swipe options within an email application, according to one embodiment. Embodiments of the process described herein may be implemented on an electronic device having a display and a touch-sensitive surface, such as apparatus 100 .

A list containing information corresponding to the plurality of email messages is displayed ( 1005 ). The list includes portions of an email message in email threads, as shown in FIG. 5B . The information includes sender information, subject information, and a portion of the email. The information may also include indicators such as an attachment indicator, a VIP sender indicator, and a VIP thread indicator.

A contact 526 on the touch-sensitive surface is sensed 1010 . 5C, 5D, and 5E, successive movement of contact 526 in a first direction results in a message of one of a plurality of email messages without breaking contact with the touch-sensitive surface. A position on the display corresponding to is detected (1015). A location above the display corresponding to the message of the plurality of email messages indicates a portion of the message, as shown by rows representing portions of the email messages of email threads 506 of FIGS. 5-7 . can be reduced Depending on the direction of continuous movement, the displayed user interface elements may change. For example, a first direction may display swipe options 528 and/or an enlarged swipe option 628 and a second direction may display swipe option 728 and/or additional options. can

One or more parameters of movement of the contact are determined ( 1020 ). As previously described in FIGS. 5 , 6 , and 7 , parameters of movement of contact 526 are distance, speed, intensity of pressure of contact 526 , number of points of contact, or other measurement of contact 526 . Possible parameters and their movements are included (1022).

In accordance with a determination that the parameter of the movement meets the first criterion, a plurality of user interface elements representing actions to be taken over the email message are displayed ( 1025 ). User interface elements representing actions to be taken may be selected and include 1029 swipe options 528 , enlarged swipe option 628 , or options displayed within swipe options 728 . For example, swipe options 528 include more option 528A, reminder option 528B, and discard option 528C. In one embodiment, the default action or expanded swipe option 628 is an option within swipe options 528 (eg, discard option 528C) ( 1034 ). The swipe options 528 , the enlarged swipe option 628 , and the options displayed within the swipe options 728 may be default actions as described in conjunction with FIG. 9 or may be personalized by the user. . Options are coded based on color (eg, red for delete or discard option 528C), orange for flag or notification option 528B, and blue for additional options such as more option 528A. color), the action associated with the option, graphical indications, or a combination thereof. The criteria of parameters include ( 1027 ) various threshold distances, threshold speeds, threshold strengths of pressure of the contact 526 , a threshold number of contact points, or other suitable threshold value for the parameter, like the first criterion.

In some embodiments, a plurality of user interface elements are displayed 1025 or a distance reached by contact 526 continuously and/or proportionally from one side (eg, right) or based on a first criterion or Visually slide out to a normalized distance. Thus, as a result, the portion of the email message of the email thread displayed within the line associated with the plurality of user interface elements being displayed will slide out of the display in the direction of continuous movement and the plurality of user interface elements will slide into the view above the line. When can slide out at the same time. In one embodiment, if the first criterion is not met, the plurality of user interface elements are not displayed ( 1025 ). In embodiments where a plurality of user interface elements slide out from one side successively and/or proportionally to a distance reached by contact 526 or a normalized distance, if the first criterion is not met, the plurality of user interface elements Elements are rubber banded back to one side and not shown. In some embodiments, the plurality of user interface elements is folded into a thin line along the bottom of the line displaying a portion of the email message of the email thread and also displaying the plurality of user interface elements. In one embodiment, when the contact is maintained by the user, whether the first criterion is met, for longer than a threshold period, the plurality of user interface elements are not displayed, rubber banded again, or faded away with a thin line. Folds.

In accordance with a determination that the parameters of the movement satisfy a second criterion that is different from the first criterion, a default action is performed on the email message ( 1030 ). Criteria, such as the first criterion and the second criterion of parameters, are, as described above, various threshold distances (eg, the threshold distance of the first criterion is shorter than the threshold distance of the second criterion), threshold velocities, contact 526 ), critical intensities of pressure, critical numbers of contact points, or other suitable threshold values for the parameter. In some embodiments, the default action is not performed ( 1030 ) until the user selects a displayed default action, such as an enlarged swipe option ( 628 ). For example, a user interface element associated with a default action is displayed across the entire line representing a portion of an email message in email thread 506 . According to one embodiment, the user interface element is a discard option 528C.

In one embodiment, the default action may be displayed, or reached by contact 526 continuously and/or proportionally from one side (eg, the same right side as the side on which the plurality of user interface elements are displayed 1025 ). Slide out up to a specified distance or a normalized distance, based on the second criterion, or only if the second criterion is met. In embodiments where the user interface element associated with the default action slides out from one side continuously and/or proportionally to a distance reached by contact 526 or a normalized distance, if the second criterion is not met, a plurality of The user interface elements rubber band back to the displayed plurality of user interface elements (eg, swipe options 528 ) or none of the options are displayed. In some embodiments, the user interface element associated with the default action is displaying a portion of the email message of the email thread and is folded into a thin line along the bottom of the line displaying the plurality of user interface elements. In one embodiment, when the contact is maintained by the user, regardless of whether the second criterion is longer than the threshold period, the user interface element is not displayed, and is rubber banded back into the plurality of user interface elements displayed previously; It becomes a rubber band and disappears, or folds into a thin line.

The displayed user interface elements are selectable, and in some embodiments, when the user interface is selected, a sheet is displayed that includes additional user interface elements associated with additional actions to take on the message. When a user interface element associated with a default action (eg, discard option 528C) is selected, a prompt is displayed requesting confirmation of the selection. Upon receiving confirmation of selection of a user interface element associated with a default action, a sheet containing additional user interface elements associated with additional actions to take on the message is also displayed.

VIP Threads and Gestures in Email Client Module UI

An email thread may be assigned a higher priority than other email threads by a user through marking the email thread as a VIP thread. 11A illustrates a mail application view 504 of an email application, according to one embodiment. Mail application view 504 displays email messages in email threads 506A, 506B, 506C, 506D, 506E from the user's email account's inbox, as shown in FIG. 5 . 11A also illustrates the receipt of a gesture indicating a request to open a drafting and composing interface of a new email. For example, a drafting gesture includes a contact 1126 sensed by the device 100 over a new drafting element 524 . In response to the sensed contact 1126 , a message composing interface or drafting user interface (UI) 1100 is shown, eg, as illustrated in FIG. 11B . By default, the cursor 1102 may appear on the drafting UI 1100, eg, by default in the “To” line.

11C illustrates a cursor 1102 within a subject line of a drafting UI 1100 . When the cursor 1102 is on the subject line, the notification element 1104 appears or is, for example, visually distinct from its previous state (not shown) in FIG. 11B . In the example shown, the notification element 1104 is the outline of a blue bell, but could be any other suitable element. Other suitable elements include different objects, different visual characteristics (eg, color, shape, size, location, style), or a combination thereof. When the notification element 1104 as shown by contact 1126 in FIG. 11C is selected, the notification element 1104 is updated to appear visually distinct from its previous state. A notification element may be visually distinguished as an object described above having different visual characteristics (eg, color, shape, size, location, style) or any combination thereof. For example, the notification element 1104 is a shaded blue bell, now shown in FIG. 11D .

11E shows a cursor 1102 within the body of the drafting UI 1100, and in response to the cursor 1102 that is no longer on the subject line of the drafting UI 1100, the notification element 1104 back from its previous state. It exemplifies visually distinct appearance. As above, the notification elements are visually distinct. 11E , the notification element 1104 is now a striped bell. In one embodiment, the notification element 1104 may be a shaded gray bell. Additional embodiments, as above, include a notification element 1104 as visually distinct.

Future emails or email messages received within email thread 1106A include VIP thread indicator 1108 as shown in FIG. 11F , indicating selection of notification element 1104 for email thread 1106A. . For example, an email message in an email thread with a subject line “Notify me of a thread,” also shown in FIG. 11E , is now a VIP thread. Selection of the notification element 1104 or associating the email thread as a VIP thread changes the notification rule for replies to messages in the email thread. The notification rule includes an indication of the VIP thread indicator 1108 for subsequent messages in the email thread.

In addition to the VIP thread indicator 1108 , additional notification rules may include an account receiving push notifications or otherwise configured notification form for an email thread with a VIP thread indicator 1108 , as shown in FIG. 12 . Includes associated users. 12 illustrates a locked or initial screen of device 100 , according to one embodiment. Message portion 1106A is shown on a locked or initial screen. In one embodiment, the message portion 1106A may include a VIP thread indicator 1108 (not shown).

VIPs and Gestures of Existing Threads in Email Client Module UI

Although previously described in terms of drafting a new email, existing email threads 1106 , 506 may also be associated with the VIP thread indicator 1108 . As shown in FIG. 13A , an existing email thread 506A is not currently associated with the VIP thread indicator 1108 . The user may display sheet options 528 for email thread 506A using a display gesture such as that previously described in FIG. 5 with contact 1326 . In response to completion of the display gesture or when a threshold distance or threshold speed is reached as shown in FIG. 13B , seat options 528 appear to the right of message portion 506A, according to this embodiment. In this embodiment, seat options 528 include reminder option 528B. Selecting notification option 528B, such as via a sheet gesture as previously described in FIG. 8, by contact 1326 with a user interface element associated with notification option 528B or notification option 528B of FIG. 13C As shown, sheet 1300 is displayed for notification option 528B. In one embodiment, sheet 1300 includes the following actions to take with message portion 506A or a message associated with message portion 506A: notify me, flag, go to settings, and cancel. The included actions may be customized by a user of the device 100 through a settings application of the device 100 , which will be further described with reference to FIG. 17 . As shown in FIG. 13D , the user has an action to turn off notifications in sheet 1300 to associate email thread 506A with notification element 1104 , and consequently VIP thread indicator 1108 . may select the “Turn off notifications” action, shown by contact 1326 with

In response to selection of an action to turn off notifications in sheet 1300 shown in FIG. 13D , email thread 506A and future messages associated with email thread 506A, such as message portion 1106B, display a VIP thread indicator ( 1108) is no longer included. In a manner similar to that described in FIG. 13 , email thread 1106B may also be de-associated with VIP thread indicator 1108 . The user may display seat options 528 using the display gesture and seat gesture with contact 1426 , shown in FIGS. 14A , 14B and 14C , in a manner similar to that described in FIGS. 5 , 6 , and 13 . ) and the sheet 1400 associated with the notification option 528B. If email thread 1106B is already associated with VIP thread indicator 1108 , sheet 1400 may display different actions than those shown in sheet 1300 . For example, as shown in FIG. 14D , sheet 1400 includes the following actions to take email thread 1106B: turn off notifications, flag, go to settings, and cancel. Again, the included actions may be user-defined by the user as described above with respect to FIG. 13 . As shown in FIG. 14D , the user may contact the Turn Off Notifications action in sheet 1400 to disassociate an email message in email thread 1106B or future email messages from VIP thread indicator 1108 ( 1426), the "Turn off notifications" action can be selected. As shown in FIG. 14E , past email messages associated with email thread 506A, such as message portion 1106B, do not have a VIP thread indicator 1108 , such as message portion 1106C , with a VIP thread indicator. 1108 and future emails. In alternative embodiments, email messages associated with message portion 1106B, email thread 1106C, email thread 506A, or a combination thereof may be disassociated with notification element 1104 .

Method for VIP Threads in Email Client Module UI

15 is a flowchart of a method for associating a notification element 1104 with an email thread 506 , 1106 within an email application, according to one embodiment. Embodiments of the process described herein may be implemented on an electronic device having a display and a touch-sensitive surface, such as apparatus 100 . Within the messaging application of the electronic device, in response to receiving a compose message action, a compose interface is displayed ( 1505 ) within the messaging application. For example, the action may be contact 1126 of a further user interface element (eg, new drafting element 524 ) and contacting the additional user interface element indicates display of the authoring interface. The compose interface is an interface for drafting new messages within the email application.

Within the compose interface, a selectable user interface element, when selected, is displayed ( 1510 ) to change the notification rule for replies to the message. In one embodiment, the selectable user interface element is displayed 1512 as a bell, a bell outline, a shaded bell, or other suitable graphically modified bell. Alternative embodiments of selectable user interface elements are further described in conjunction with FIGS. 11E and 11F . In one embodiment, the selectable user interface element is displayed on the subject line of the compose interface. For example, a selectable user interface element may appear, or a selectable user interface element (eg, a gray outline of a bell) previously displayed in response to presentation of a cursor within a compose interface within a subject line, as shown in FIG. 11C , as shown in FIG. 11C . ) and can be visually distinguished.

Notification rules, as further described in conjunction with FIGS. 11E and 11F , include display of additional user interface adjacent to messages received later in a conversation thread corresponding to a message, received later in a conversation thread corresponding to a message. receipt of push notifications for messages, and combinations thereof ( 1514 ). Additional user interface elements displayed adjacent to subsequently received messages may be bells, bell outlines, shaded bells, and other visually distinct elements described in conjunction with FIG. 11D . In one embodiment, the conversation notification may be the same as the displayed selectable user interface element, but the conversation notification is not selectable.

A contact 1126 on the touch-sensitive surface is sensed 1515 at a location on the display corresponding to a selectable user interface element within the composing interface. Contact 1126 represents selection of a selectable user interface element. 13A , in response to detecting a selection, the appearance of a selectable user interface element indicates activation of a notification rule that a message subsequently received within a conversation or email thread corresponding to the message will trigger a conversation notification. It changes (1520) within the composing interface that represents. The changed appearance of the selectable user interface element within the composition interface further includes a change in the graphical representation of the selectable user interface element ( 1522 ). The graphical representations include the color, shape, size, location, and combinations thereof of selectable user interface elements. The conversation notification may be a push notification indicating a message received at a later time on an electronic device external to the messaging application. Also, a push notification may be displayed when the electronic device is locked and the display is inactive.

In a manner similar to that described above with FIG. 10 , a user interface element may be displayed for subsequently received messages associated with the composed message. A further contact is sensed on the touch-sensitive surface, and, without release of contact with the touch-sensitive surface, successive movement of the contact at a location on the display corresponding to messages associated with the message is sensed in the first direction. One or more parameters of movement of the contact are determined, and in accordance with a determination that the parameter of movement meets the first criterion, take an action (eg, notify me of option 528B) to change notification rules for replies to the message. The representing user interface element is displayed. Then, a user interface element representing an action for changing the notification rule may be selected.

The selection of a user interface element representing an action to change the notification rules results in changed notification rules that are different or opposite to the notification rules described above. For example, notification rules do not indicate an additional user element adjacent to subsequently received messages in a conversation thread corresponding to a message, do not receive push notifications for later received messages in a conversation thread corresponding to a message; things, and combinations thereof. Alternatively, selection of the user interface element may display sheets 1300 , 1400 for further actions that change notification rules, as described in conjunction with FIGS. 13 and 14 . Additional actions displayed on the sheet include turning off notifications for messages received at a later time, flagging messages received at a later time, a go to settings action, and combinations thereof.

Ignoring Threads and Gestures in the Email Client Module UI

Email threads 506 may also be ignored. As shown in FIG. 16A , illustrated is a gesture for selection of an enlarged swipe option 628 within an email application, according to one embodiment. For example, the seat gesture with contact 1626 is a seat gesture as described above in FIGS. 8 and 14 . In the example, the enlarged swipe option 628 is a discard option 528C. In one embodiment, the expanded swipe option 628 is only available or provided if the email thread contains multiple email messages. In one embodiment, prompt 1600 is displayed in response to completion of a seat gesture or when a threshold distance or speed is reached, as shown in FIG. 16B . Prompt 1600 prompts the user to select to discard the e-mail message associated with message portion 506B or to instead apply ignore options, shown as buttons 1602 and 1604, respectively. Selection of button 1602 along with contact 1626 moves the email associated with message portion 1106B to the trash. In alternative embodiments, the email associated with message portion 1106B may be automatically discarded after completion of the sheet gesture or a threshold distance or speed is reached, and no prompt is displayed, or alternative prompt, or sheet 1606 . may be displayed. Selection of button 1604 along with contact 1626 displays sheet 1606 for override options, as shown in FIG. 16C . Sheet 1606 includes the following ignore options: Discard Thread, Archive Thread, Mark Thread as Read, Turn Off Alerts for Thread, Go to Settings, and Cancel. The ignore options included may be user defined as further described in conjunction with FIG. 17 .

Just as email threads can be ignored, email threads can also be un-ignored. In one embodiment, the email thread may be dismissed manually (eg, via the enlarged sheet option 628 ) or automatically. For example, a VIP sender replies to an email thread, a sender only replies to a user, a user's full name is mentioned within an email message in an email thread, or other user-specified information appears within an email thread. If the reengage) condition is met, the email thread can be automatically disregarded.

Customization of override options within the email client module UI

17A-17D illustrate pages 1702 , 1704 , 1706 , 1708 within an application view of a settings application, according to one embodiment. 17 describes the customization of override options within sheet 1606 . In alternative embodiments, a different application(s) other than the settings application or other page(s) within the settings application may be used to customize override options in sheet 1606 .

17A illustrates a “zoom in” gesture within notification center 1702 associated with a settings application. The zoom in with contact 1726 gesture is similar or identical to the zoom in with contact 926 gesture described above in FIG. 9A . In response to the magnification gesture with contact 1726 with representation of “mail” icon 418 , mail page 1704 is displayed within the settings application, as shown in FIG. 17B . In the mail page 1704, the user may select whether to activate override options within the email application, eg, via selection of a radio button. In response to contact 1726 with the radio button, customization of options may be made available as shown in modified mail page 1706 of FIG. 17C . In response to a magnification gesture sensed by device 100 for a custom option, for example, via contact 1726 with a custom option, a custom override options page 1708 is displayed within the settings application. Custom swipe options page 1708 includes options to customize seat options and custom alert settings associated with seat options. In a manner similar to that previously described in FIG. 9 , the user may customize the seat options, shown in FIG. 17D . For example, the options include Discard Thread, Archive Thread, Mark Thread as Read, and Go to Settings, as shown in FIG. 16C . Additional options include unsubscribe, no alerts, move to special folder (via filter in inbox), and demote (email threads are not presented chronologically and/or future email messages are not sent to email thread or email message portion 1106B associated with an ignore option, such as thread 1106B, and archived with the associated email message.

How to Ignore Threads in Email Client Module UI

18 is a flowchart of a method for ignoring an email thread within an email application, according to one embodiment. Embodiments of the process disclosed herein may be implemented on an electronic device having a display, such as device 100 . Information corresponding to the plurality of messages in the messaging application is displayed ( 1805 ), as described above in conjunction with FIG. 5B . The information includes sender information, subject information, and parts of an email or message. The information may also include indicators such as an attachment indicator, a VIP sender indicator, and a VIP thread indicator.

An input is received 1810 at a location on the display corresponding to the displayed message. Input indicates deletion of the displayed message. The input is, for example, contact 1626 with a location on the display corresponding to the displayed message. Additionally, a location on the display corresponding to the displayed message may indicate a selectable user interface element corresponding to a request for deletion of the displayed message. In one embodiment, the selectable user interface element is a displayed enlarged swipe option 628 instead of a displayed message, as shown and described in FIGS. 6D, 6E, and 16A .

In response to receiving the input, a plurality of selectable user interface elements representing delete actions to be taken on the next message in the conversation thread corresponding to the displayed message are displayed ( 1815 ) proximate to the location of the displayed message. A plurality of selectable user interface elements representing delete actions to be taken may be displayed within sheet 1606 as shown in FIG. 16C and include unsubscribe, move to designated folder, demote, and combinations thereof. In one embodiment, the selectable user interface element representing unsubscribing of a delete action includes discarding the displayed message, discarding messages received later in the displayed message, discarding the conversation thread corresponding to the displayed message (eg, discarding the thread), archiving the displayed message. , keep messages received in the future of the marked message, keep a conversation thread corresponding to the marked message (e.g. keep a thread), mark the marked message as read, mark the subsequently received messages of the marked message as read, by reading the conversation thread marking, turning off all alerts for messages received later in the marked message, turning off all alerts for a conversation thread, and combinations thereof. A selectable user interface element indicating demoting of a delete action includes an indication that subsequently received messages of the displayed message have been presented with the conversation thread and not as new messages in the conversation thread.

In one embodiment, in response to receipt of the input, a prompt 1600 is displayed 1817, as shown in Figure 16B, requesting confirmation of deletion of the displayed message. For example, as shown in FIG. 16B , the request may be a question such as "Apply the ignore option to all emails in a thread?" The prompt requesting confirmation of deletion of the displayed message includes selectable user interface elements, including deletion of the displayed message, deletion of a conversation thread corresponding to the displayed message, requesting additional delete actions, and combinations thereof. . For example, selectable user interface elements may be “No, Discard Thread” 1602 , and “Yes, Options…” 1604 , for the question shown on prompt 160 of FIG. 16B . . In response to receiving further input to the prompt, a plurality of selectable user interface elements representing delete actions to be taken on subsequent messages in the conversation thread corresponding to the displayed message are: It is displayed close to the location of the message (1819). In response to selection of one of the plurality of selectable user interface elements, the displayed message is deleted 1820 , and a delete action is set for subsequently received messages in the conversation thread, as described above in step 1815 .

In response to the reengagement status being satisfied by the subsequently received messages of the indicated message, the subsequently received additional messages of the subsequently received message and the delete action selected for the subsequently received message and the indicated message are removed ( 1822 ). As previously described in conjunction with FIG. 16 , the re-engagement states are defined as the sender previously designated when the VIP sender replies to an email thread, the sender replies to the user associated with the electronic device, the sender replies to the user associated only with the electronic device, and the Include the user's name mentioned in the email message, and combinations thereof.

Draft Emails UI

19A illustrates a mail application view 504 of an email application, according to one embodiment. Mail application view 504 displays portions of email messages in email threads 506A, 506B, 506C, 506D, 506E from the user's email account's inbox, as described in FIGS. 5B and 11A . Contact 1910 is sensed by device 100 over new drafting element 524 . In response to deleted contact 1910 , according to one embodiment, a message compose interface or first draft UI 1900A is shown, as illustrated in FIG. 19B . As indicated, the drafting UI 1900A is displayed on top of the mail application view 504 . 19B also illustrates again contact 1910 sensed by device 100 over new drafting element 524 . 19C , in one embodiment, in response to the sensed contact 1910 , a second drafting UI 1900B is displayed on top of the first drafting UI 1900A, the first and All of the second drafting UIs 1900A, 1900B are displayed on top of the mail application view 504 . Alternatively, in response to the contact 1910 sensed in FIG. 19B , the first drafting UI 1900A is displayed within the drafting area 1902 of the mail application view 504 , as shown in FIG. 19D . and a second drafting UI 1900B can be displayed on top of a mail application view 504 that includes a drafting area 1902 .

Although the first and second drafting UIs 1900A, 1900B are displayed at a width that is narrower than the width of the touchscreen 112 of the device 100 , in an alternative embodiment, the drafting UIs 1900A, 1900B ) may be displayed at the same full width and height as the width and height of the touch screen 112 . Further, according to one embodiment, the drafting UIs 1900 are also movable when displayed on top of other drafting UIs 1900 or the mail application view 504 . A user may touch-and-drag the drafting UIs 1900 through contact with a header or a portion of the drafting UIs 1900 .

According to one embodiment, the drafting UI 1900 is displayed at the top of the mail application view 504 or on the mail application view 504 and the drafting area 1902 uses gesture minimization, as shown in FIG. 19D . Thus, it can be minimized to the drafting area 1902 . 19D-19E illustrate a minimize gesture for minimizing a drafting UI 1900 within an email application, according to one embodiment. The minimize gesture represents a user request to minimize the drafting UI 1900 displayed on top of the mail application view 504 within the email application. The minimize gesture may include a swipe in a direction substantially orthogonal to the width of the message portion 506 . In one embodiment, the minimize gesture may be a swipe down all the way to the drafting area 1902 .

In one embodiment, the minimize gesture includes dragging the contact a threshold distance from an initial position to a second position on top of the mail application view 504 . For example, as shown in FIG. 19D , contact 1926 is sensed by device 100 at an initial location within message portion 506B. As shown in FIG. 19E , contact 1926 is message portion 506B. It is held and dragged to a second position within the message portion 506B at a threshold distance in a direction substantially orthogonal to the width of 506B. For example, contact 1926 is maintained in continuous movement without releasing contact with touch screen 112 of device 100 from an initial position to a second position shown in FIGS. 19D and 19E a threshold distance. In another embodiment, instead of a threshold distance, the minimize gesture includes dragging the contact at a threshold speed atop one or more drafting UIs 1900 displayed on top of the mail application view 504 . Accordingly, contact 1926 is held and dragged at a velocity in a direction substantially orthogonal to the width of message portion 506B. In other embodiments, other parameters of the contact 1926 maintained are evaluated for the minimize gesture. Parameters other than distance and speed may be the strength of the pressure of the contact or the number of contact points, or other measurable parameters.

After completion of the minimize gesture or a threshold distance or speed is reached, the drafting UIs 1900 displayed on top of the mail application view 504 are minimized or, as shown in FIG. 19E , the drafting area 1902 , as shown in FIG. 19E . falls down until In one embodiment, the drafting UIs 1900 are minimized or fall down into the drafting area 1902 , and the movement of the drafting UIs 1900 into the drafting area 1902 is continuous and/or or the distance reached by contact 1926 in a similar manner as the threshold distances and threshold velocities described in FIGS. 5 , 6 and 7 , or a normalized distance or predetermined velocity. In an embodiment where drafting UIs 1900 are partially displayed when contact 1926 is maintained, if contact 1926 is not maintained until a threshold distance is reached and/or released, it may still be visible Portions of the drafting UIs 1900 may be displayed on top of the mail application view 504 . In another embodiment, the drafting UIs 1900 may be a “rubber band” or snap to the drafting area 1902 after the threshold is crossed by the contact 1926 .

Drafting UIs 1900 displayed within drafting area 1902 or on top of mail application view 504 may be removed using a remove gesture as shown in FIG. 20A . Drafting UIs 1900 may be overridden based on threshold distances and threshold velocities of contact 2026 movement. 20A , 20B, and 20C , remove gestures ignore or cancel drafting UIs 1900A via contact 2026 with drafting UIs 1900A, a threshold distance or threshold It can be based on speed. Also, the remove gesture may reach a designated location (eg, the edge of screen 112 ) and thus ignore or cancel drafting UIs 1900A.

21A illustrates a mail application view 504 of an email application, according to one embodiment. For example, the illustrated mail application view 504 is similar to the mail application view 504 illustrated in FIG. 19A . For example, via a drafting gesture as described above in FIG. 11A , contact 2126 is detected by device 100 over new drafting element 524 . In response to the sensed contact 2126 , a message composing interface or third drafting UI 1900C is shown within the drafting area 1902 , as illustrated in FIG. 21B . In this embodiment, the drafting UI 1900C is displayed within the drafting area 1902 instead of over the top of the mail application view 504 . 19B also illustrates contact 1910 sensed over drafting UI 1900B by device 100 . In response to the sensed contact 1910 , a drafting UI 1900B is displayed on top of the mail application view 504 , as shown in FIG. 21C .

While the drafting UI 1900B is displayed on top of the mail application view 504 , the user can still access email messages associated with the message portions 506 within their account. 22A illustrates a “thread” gesture for enlarging an existing email message associated with a message portion within an email application, with the drafting UI 1900b displayed on top of the mail application view 504, according to one embodiment. exemplify In response to selection of an email message associated with message portion 506B, according to one embodiment, drafting UI 1900B is minimized to drafting area 1902 and message portion 506B is, as shown in FIG. 22B , As such, it is displayed within the thread area 2204 .

23A illustrates a horizontal view of icons for applications on device 100 , according to an embodiment. For example, the tray 408 icon and icons for other applications are similar to the icons displayed within the portrait view of device 100 shown in FIG. 5A . In a manner similar to that described in FIG. 5A , the initiating gesture is used to launch the email client module 140 , via contact 2326 with the “mail” icon 418 , shown in FIG. 23A .

23B illustrates a mail application view 504 of an email application, according to one embodiment. For example, mail application view 504 includes email messages in email threads 506A, 506B, 506C, 506D, 506E, 2306A, 2306B from an inbox of a user's email account. Each message portion 506 , 2306 displays sender information 508 , subject information 510 , and a portion of the body of the email 512 . Further, message portions 506 , 2306 may include an attachment indicator 514 and a VIP sender indicator 516 , as described in FIG. 5B , and message portions 506 , 2306 may also include VIP thread indicator 1108 (not shown) described in FIG. 11 . As also described in FIG. 5B , additional user interface elements are displayed within the mail application view 504 , a return element 518 , an edit element 520 , a refresh element 522 , and a new drafting element ( 524). Mail application view 504 may also include an archive element 2302 , a discard icon 2304 , and a reply action element 2306 . Archive element 2302 includes a selected email thread 506 , 2306 , a discard icon 2304 to discard the selected email thread 506 , 2306 , and a reply action element that allows the user to reply to the selected email thread 506 , 2306 . (2306) is kept.

In FIG. 23B , a gesture is illustrated to display an email message associated with message portion 506B, as previously described in FIG. 22B . In response to the thread gesture, an email message associated with message portion 506B is displayed within thread area 2204 , according to one embodiment, as shown in FIG. 23C . 23D , when a drafting gesture is received at new drafting element 524 via contact 2326 , as shown in FIG. 23C , as previously described in FIG. 11A , according to one embodiment. As shown, the first drafting UI 1900A is displayed on top of the threads area 2204 of the mail application view 504 . According to one embodiment, in FIG. 23D , an additional drafting gesture is received, and as shown in FIG. 23E , the second drafting UI 1900B is atop the thread area 2204 and the first drafting UI ( 1900A).

In an alternative embodiment, in response to receiving the drafting gesture via contact 2326 of FIG. 23C , a first drafting UI 1900A is displayed within the drafting area 1902 , in accordance with one embodiment, as shown in FIG. As shown in 23f , it may be displayed on the width of the touch screen 112 of the device 100 . In response to receiving another drafting gesture via contact 2326 of FIG. 23F , a second drafting UI 1900B is also displayed within the drafting area 1902 and the second drafting UI 1900A, and in one implementation According to an example, as shown in FIG. 23G , the display may be displayed on the width of the touch screen 112 or a width smaller than that of the touch screen 112 . Also, the width of the second drafting UI 1900B may be the width of the touch screen 112 or a width smaller than that of the touch screen 112 .

In another embodiment, in response to receiving a drafting gesture via contact 2326 of FIG. 23C , a first drafting UI 1900A is displayed within the drafting area 1902 , in accordance with one embodiment, as shown in FIG. As shown at 23h, the width of the thread region 2204 or less may be indicated. In response to receiving another drafting gesture via contact 2326 of FIG. 23H , second drafting UI 1900B is also displayed within drafting area 1902 and second drafting UI 1900A, in one implementation Depending on the example, as shown in FIG. 23I , the width of the thread region 2204 or a smaller width may also be indicated.

24A illustrates a minimize gesture for minimizing the drafting UI 1900 to a smaller drafting area 1902, according to one embodiment. According to an embodiment, the minimize gesture may be the same as the minimize gesture described above with reference to FIG. 19 . Contact 2426 is sensed by device 100 in the initial position and maintained in the second position, completing the minimize gesture, as shown in FIG. 24B , according to one embodiment.

25A illustrates a “remove” gesture for removing drafting UI 1900 , according to one embodiment. The removal gesture may be the same as the removal gesture described above with reference to FIG. 20 . According to one embodiment, as shown in FIGS. 25B and 25C , contact 2526 is sensed by device 100 in an initial position and maintained in a second position, and the removal gesture completes. Alternatively, the drafting UI 1900 may be removed through selection of "Cancel", similar to the "Close" element 1904 of FIG. 19 .

26A illustrates a “draft” gesture indicating a request to draft a new email, according to one embodiment. The drafting gesture may be the same as the drafting gesture described above in FIGS. 11A and 21A for contact 2626 . In response to completion of the drafting gesture or when a threshold distance or speed is reached, the third drafting UI 1900C, as shown in FIG. 26B , according to one embodiment, of the second drafting UI 1900B displayed within the drafting area 1902 on top.

26B illustrates contact 2626 sensed by device 100 with third drafting UI 1900C. In response to the sensed contact 2626 , a drafting UI 1900B is presented within a larger drafting area 1902 within the mail application view 504 , as shown in FIG. 26C , according to one embodiment. . In another embodiment, the drafting UI 1900B may be displayed on top of the threads area 2204 and the drafting area 1902 . The width of the drafting UIs 1900 within the drafting area 1902 may be the same as or smaller than the width of the threading area 2204 .

While the drafting UI 1900B is displayed on top of the larger drafting area 1902 or threads area 2204 and the drafting area 1902, users can access email threads 506, 2306 within their account. You can still access it. 27A illustrates a gesture for enlarging an email thread 506A residing within an email application, with the drafting UI 1900B displayed within the larger drafting area 1902, according to one embodiment. In response to selection of an email message associated with message portion 506A via contact 2726 , drafting UI 1900B opens to smaller drafting area 1902 , according to one embodiment, as shown in FIG. 27B , as shown in FIG. 27B . E-mail messages minimized to and associated with message portion 506A are displayed in enlarged thread area 2204 .

28 is a flowchart of a method for displaying message composing interfaces or drafting UIs within an email thread within an email application, according to one embodiment. Embodiments of the process described herein may be implemented on an electronic device having a display and a touch-sensitive surface, such as apparatus 100 . A first compose interface (eg, 1900A in FIG. 19B ) is displayed 2805 and the first compose interface includes a first message. A first composing interface, eg, including a first message, is displayed in response to receiving another action of composing the first message. While displaying the first composing interface, an action of composing a second message is received ( 2810 ). The action is contacting a further user interface element (eg, 1926 in FIG. 19 and 2326 in FIG. 23C ) and contacting the additional user interface element causes display of a composing interface (eg, first and second composing interfaces). indicates. For example, an additional user interface element is a new drafting element 524 , as shown in FIGS. 19B and 23C .

In response to receiving 2810 the action, a second composing interface (eg, 1900B of FIG. C) is displayed 2815, a first composing interface is displayed within the first portion 2820, and a second composing interface is Shown within 2 parts (2825). Also, the first and second composing interfaces are resizable. In various embodiments, the area of the first portion and the area of the second portion may be the same or different. For example, the area of the second portion is greater than the area of the first portion, which may be in response to the second portion displaying the second composition interface while displaying the first composition interface. Because the second composition interface was displayed while the first composition interface was displayed, the second composition interface may, in various embodiments, be displayed on top of the first composition interface.

A second contact (eg, 1926 and 2426) can be received on the touch-sensitive surface at a location corresponding to a compose interface (eg, a first compose interface or a second compose interface). 19D and 19E , continuous movement of the second contact in the first direction is sensed without releasing the second contact with the touch-sensitive surface. One or more parameters of movement of the second contact are determined, and in response to determining that the parameter of movement meets a first criterion, the first composition interface and the second composition interface are configured to: The information is displayed in a third portion (eg, drafting area 1902 in FIG. 20A ) below the list containing the information. Portions of a plurality of email messages may be displayed as shown in message portions 506A-506D of FIG. 20 .

In a similar manner, the third contact may be received on the touch-sensitive surface at a location corresponding to the third portion. Successive movement of the second contact in the second direction is sensed without releasing the third contact with the touch-sensitive surface. 26C , one or more parameters of the movement of the third conflict are determined, and in accordance with the determination that the parameter of the movement meets the first criterion, the first composition interface and the second composition interface are configured to: displayed in a fourth portion below the list including information corresponding to the plurality of e-mail messages, wherein an area of the fourth portion is greater than an area of the third portion.

Compose interfaces may also be removed. 20 and 25 , a fifth contact (eg, 2026 and 2526 ) is received on the touch-sensitive surface at a location corresponding to the first compose interface, and a succession of the fifth contact in a third direction Movement is sensed without releasing the fifth contact with the touch-sensitive surface. One or more parameters of movement of the fifth contact are determined, and upon determining that the parameter of movement meets the third criterion, the first compose interface is closed. Alternatively, a sixth contact is received 2822 on the touch-sensitive surface at a location corresponding to the selectable user interface element displayed on the first compose interface. In response to receiving the sixth contact at the location, the first compose interface is closed ( 2824 ).

In one embodiment, the first direction is a downward movement, substantially parallel to the orientation of the display, and the second direction is opposite and still substantially parallel to the orientation of the display. The third direction is then substantially orthogonal to the first and second directions and thus to the orientation of the display. As described above in conjunction with FIG. 10 , the one or more parameters include distance, speed, intensity of pressure of the contact, number of points of contact, and combinations thereof. Further, as also described above in conjunction with FIG. 10 , the criteria (eg, first, second, and third criteria) include a threshold distance, a threshold velocity, a threshold strength of the pressure of the contact, a threshold number of contact points, and their include combinations.

Conversation View within Email UI

29A illustrates an application view 504 of an email application, according to one embodiment. Application view 504 displays email messages or email threads 506A, 506B, 506C, 506D, 506E from the inbox of the user's email account. Each email message or thread 506 displays sender information 508 , subject information 510 , and a portion of the body of the email 512 . In one embodiment, the sender information includes the sender's full name, such as the sender's first or last name, and the time or date the email message was received. For an email thread, sender information 508B includes a list of names of senders who participated in the email thread. In this case, the time and date typically indicate when the last email message in the thread was received. In one embodiment, as shown in FIG. 29A , the list of names is truncated to fit within the line of the displayed email thread 506A. The displayed, truncated list may include the string "..." indicating truncation of the sender information 508B.

Contact 2910 is sensed by device 100 on email thread 506B. In one embodiment, contact 2910 is a tab on email thread 506B. 29B , in response to sensed contact 2910 , application view 504 of the email application displays email messages 2920A, 2920B, 2920C, from email thread 506B, according to one embodiment, as shown in FIG. 2920D, 2920E). Each email message 2920 displays sender information 508 and a portion of the body of the email 512 . The sender information 508 includes the name of the sender of the email message 2920 that participated in the email thread 506B. Email messages in email thread 506B that were not initially displayed in application view 504 after contact 2910 may be displayed following scrolling gesture 2921 . This scrolling gesture is applied in a direction substantially orthogonal to the text line of the displayed email messages, as shown in FIG. 29B . Application of this scrolling gesture displays email messages following email message 2920E in email thread 505B. When such subsequent email messages are displayed, reversing the direction of the scrolling gesture displays email messages that precede the currently displayed email messages in email thread 506B.

As indicated, an additional user interface element, which is a thread header element 2930 , is displayed in the application view 504 above the displayed email message 2920A. Thread header element 2930 may show the number of email messages (items) and a subject line common to email messages within email thread 506B. Subject element 2931 also displays the character string “thread” indicating to the user that an email thread has been displayed within application view 504 .

29B also illustrates a first zoom in gesture within application view 504 associated with email thread 506B, according to one embodiment. The first magnification gesture with contact 2932 is a tap on thread header element 2930 . In response to the first magnification gesture with contact 2932 sensed on device 100 , the thread header element expands to display a list of names of senders that have participated in email thread 506B. In one embodiment, the names displayed in the list include only the first names of the senders. As shown in FIG. 29C , if the email thread 506B includes senders with the same names, the list includes their initials and their last names. Alternatively, the list of sender names as indicated includes the first and last name of each sender. The order in which the first and last names are displayed can be varied and optionally selected by the user of the email application. If the last name is displayed first, a comma is placed after the last name to visually separate the last name from the sender's first name.

29C illustrates enlarging the thread header element 2930 within an email application, according to one embodiment. The first magnification gesture represents a user request to enlarge the thread header element 2930 into the thread participants area 2934 below the subject line area 2936 . Thread participants area 2934 contains the sender names of email messages within a thread, while subject line area 2936 contains a subject line, common to email messages within a thread, and a list of messages (items) within a thread. includes the number. Email messages 2920A, 29210B, 2920C, 2920D are displayed in application view 504 below thread header element 2930 . If the list of sender names in the email thread requires more than two lines to be displayed in the thread participants area 2934, then area 2934 is a list of additional lines containing sender names that were not displayed in the first two lines. and a more option 2938 to allow display.

29C also illustrates a second zoom in gesture within application view 504 associated with email thread 506B, according to one embodiment. The second magnification gesture with contact 2940 is similar or identical to the magnification gesture with contact 926 described above in FIG. 9A . In one embodiment, the second magnify gesture includes, for example, a tap or contact on more option 2938 , shown as contact 2940 in FIG. 29C . More options 2938 are displayed as part of thread participants area 2934 . In response to the second zoom in gesture with contact 2940 sensed by device 100 , area 2934 expands to display the names of all senders in the thread, as shown in FIG. 29D . More options 2938 along with display of all participant names are no longer displayed within thread participant area 2934 . In addition to the More option, a hide option 2944 is displayed in the thread participants area 2934 , as shown in FIG. 29D .

Similar to the first two lines in the thread participant area 2934 , only the first name of the senders may be displayed in additional lines. In other embodiments, for each participant a first and abbreviated or unshortened surname, or a surname following the first name with a comma, are indicated as described above. Senders who were not originally part of the email thread, but have been added to the thread by the user of the email application, have a "+" sign in front of their displayed names 2941 , as described below. In contrast, as described below, senders excluded from the email thread by the user have their displayed names 2942 crossed out (eg Mike) as shown in FIGS. 29C-29E .

29D illustrates a gesture within application view 504 associated with email thread 506B, according to one embodiment. In one embodiment, the hide gesture includes a tap or contact over hide option 2944 shown as contact 2946 , as shown in FIG. 19D . 29C , in response to a hide gesture with contact 2946 detected by device 100 on hide option 2944 displayed on thread participants area 2934 , area 2934 becomes It collapses again to show only the more option 2938 and the first two lines of sender names that joined within the email thread.

29D also illustrates a filter gesture within application view 504 associated with email thread 506B, according to one embodiment. The select-sender gesture includes a contact on a name in thread participant area 2934 , shown as contact 2948 in FIG. 19D . In the example of FIG. 19D , in response to a “select-sender” gesture with contact 2948 sensed by device 100 , a sender named “Andrew” is selected. Additional senders may be selected by a select-sender gesture including a tap on their corresponding names displayed within thread participant area 2934 (not shown). Once the sender's name is selected, the selected sender's name in the thread participant area 2934 is visually distinctly displayed. For example, as shown in FIG. 29E , the selected name 2950 is displayed in bold font within the area 2934 . The names of unselected senders appear distinct from the names of selected senders. As shown in FIG. 29E , the names of unselected senders are displayed in a normal font rather than a bold font.

The deselect-sender gesture in the application view 504 associated with the email thread 506B is displayed on the sender name in the thread participant area 2934 if the deselect-sender gestures follow the select-sender gesture for that particular sender name. Includes tabs. Subsequent to the first magnify gesture, alone or in combination with the second magnify gesture, without a preselect-sender gesture, all displayed names in the thread participant area 2934 are selected, and the deselect-sender gesture for these displayed names is It will have no effect, leaving all displayed names selected. In this case, selection of a displayed name using the select-sender gesture does not select all displayed and selected names that were not selected by the select-sender gesture. Unselected, marked names appear visually distinct from the selected sender name as described above. For the example shown in FIG. 29E, “Greg”, “Sam”, “Logan”, “+Chip T.”, “Chip D.” ", "David R", "Mike," "Roger", "Michelle", "Steve" and "Christine" are unselected senders These are their names and are displayed in regular font, not bold font.

29E illustrates the display of only selected sender's email messages associated with email thread 506B in response to a select-sender gesture within application view 504, according to one embodiment. In response to the select-sender gesture with the contact 2948 sensed by the device 100 , only the email messages 2960A, 2960B, 2960C, 2960D associated with the selected sender (“Andrew”) are within the application view 504 . is displayed As shown in Figure 29E, email messages from other senders in the email thread are not displayed unless those senders are selected.

30A illustrates an application view 504 of an email application, according to one embodiment. For example, application view 504 includes email messages 506A, 506C, 506D, 506E, 506F, 506G or email thread 506B from an inbox of a user's email account. Each email message or thread 506 displays sender information 508 , subject information 510 , and a portion of the body of the email 512 . Additionally, the email message or thread 506 may include indicators such as an attachment indicator 514 and a VIP sender indicator 516, as shown in FIG. 5B , and as shown in FIG. 11 . , in the case of an email thread 506 , a VIP thread indicator 1108 (not shown). As also described in FIGS. 5B and 23B , additional user interface elements are displayed within application view 504 and include a return element 518 , an edit element 520 , a refresh element 522 , and a new drafting element ( 524 ), a archive element 2302 , a discard icon 2304 , and a reply action element 2306 . In addition, the email thread 506 may include an item indicator 3010 that indicates the number of email messages contained within the thread.

30A also illustrates thread gesture 3011 displaying email thread 506B within threads area 3012 of application view 504 , as described above in FIG. 22B , according to one embodiment. In response to thread gesture 3011 detected by device 100 and including a tap on email thread 506B, the content of the email thread is displayed within thread area 3012 . 30A , the displayed content includes email messages 3020A, 3020B, 3020C from email thread 506B in the user's email's inbox. As indicated, an additional user interface element, which is a thread header element 3022 , is displayed in application view 504 above displayed email messages 3020A, 3020B, 3020C. Thread header element 3022 shows a subject line common to email messages and may also indicate the date and time the last email message was received within the email thread. Optionally, thread header element 3022 indicates the number of email messages (items) within email thread 506B.

30A illustrates enlarging a thread header element 3022 within an email application, according to one embodiment. As shown in FIG. 30B , the magnification gesture displays the names of participants in email thread 506B below subject line area 3026 including a subject line and a number of items common to email messages in email thread 506B. Represents a user request to enlarge a thread header element 3022 that displays the thread participants area 3024 that contains it. Email messages 3020A, 3020B, 3020C below thread header element 3022 are displayed in application view 504 .

As illustrated in FIG. 30A , email messages 3020A, 3020B, 3020C displayed in thread area 3012 include sender information 3026, a details option 3028 showing additional sender information, and a may include a header area 3025 containing a portion of the body of the email 3030 including more options 3032 showing the remainder of the body of the email. Responsive to an optional gesture including a tap (not shown), the detail option 3028 may include, but is not limited to, the recipient (original and copy), time, and date of the email in the header area 3025 in the email. Additional sender information about More option 3032 is similar to more option 2940 described above with respect to FIG. 29C .

30A also illustrates a zoom in gesture within application view 504 associated with email thread 506B, according to one embodiment. The zoom in with contact 3034 gesture is similar or identical to the zoom in with contact 926 gesture described above in FIG. 9A . In one embodiment, the magnify gesture includes a tap over the thread header element 3022 that enlarges the thread header element to include the sender names of the email thread. Alternatively, the magnify gesture with contact 3034 includes a swipe in a direction substantially orthogonal to the subject line of thread header element 3022 . For example, contact 3034 is sensed by the device in an initial position above thread header element 3022 . As shown in FIG. 30A , contact 3034 is initially above the top of email thread 506 displayed within thread area 3012 in continuous movement without breaking contact with touch screen 112 of device 100 . A threshold distance from the position to the second position is maintained and dragged. In another embodiment, instead of a threshold distance, the zoom in gesture includes dragging the contact at a threshold velocity atop the thread area 3012 displayed within the application view 504 . Accordingly, the contact 3034 is held and dragged at a velocity in a direction substantially orthogonal to the subject line of the thread header element 3022 . In other embodiments, other properties of the maintained contact 3034 evaluated for the magnification gesture other than distance and speed are the strength of the pressure of the contact or the number of points of contact.

30B is in response to a magnification gesture with contact 3034 sensed by device 100 to display a list of sender names in email thread 506B, as shown in FIG. 30A , according to one embodiment. It illustrates the expanded thread header element for This embodiment is automatically shown in the first instance of the conversation view. In one embodiment, the names displayed in the list include only the first and last sender names in the email thread 506B. Other embodiments of different displayed names of participants have been described above with respect to FIGS. 29B and 29C . As shown, the order of the first and last statements may optionally be selected by the user of the email application. In one embodiment the order is alphabetical, in other embodiments the order is based on the time and date of the last email message received from the participant with the latest time and the earliest listed date. Also, senders added to the email thread by the user are represented by a "+" sign in front of their displayed name, and senders excluded by the user have their displayed names crossed out as illustrated in FIG. 30B . If the list of sender names in the email thread 506B requires more than two lines to be displayed in the thread participants area 3024 of the thread header element 3022, then the area 3022 is the one described with respect to FIG. 29C. contains a more option that allows the display of additional lines containing names of a participant in the list not displayed on the first two lines as shown.

31 illustrates a radio button toggling between a conversation view and a message view. When the conversation view option 3100 is toggled on, the thread header element 3022 within the threads area 3012 of the application view 504 is displayed as described above with respect to FIGS. 29A-29E, 30A and 30B , displayed, whereas otherwise no thread header elements are displayed (message view).

32 is a flowchart of a method for displaying email messages in an email thread within conversation view interfaces of an email application, according to one embodiment. The email application first selects ( 3205 ) a conversation view in the messaging application configured to display a plurality of email messages in the conversation view. The email application then identifies ( 3210 ) a conversation thread from the plurality of email messages that includes the email messages within the plurality of email messages. The email application also determines ( 3215 ) information common to email messages within the conversation thread. The common information includes a conversation subject that is based, at least in part, on a subject of at least one or more email messages within the conversation thread. Next, the email application displays ( 3320 ) a header containing common information in the header portion of the conversation view, and displays ( 3225 ) a message section that is visually distinct from the header section and contains two or more email messages within the conversation thread. ). Each of the two or more e-mail messages includes sender information and content information.

Search result groups within the email UI

33A illustrates an application view 504 of an email application and a “pull-down” gesture, according to one embodiment. 5B and 11A , application view 504 displays email messages or email threads 506A, 506B, 506C, 506D, 506E from an inbox or other mailbox of a user's email account. . The pull-down gesture with contact 3310 includes a swipe in a direction substantially orthogonal to a line of text within email messages or threads. For example, contact 3310 is detected by device 100 at an initial location over email message 506A. As shown in FIG. 33A , contact 3310 is a threshold distance from an initial location on top of an email message or thread 506 displayed within application view 504 to a second location on touch screen 112 of device 100 . ) is maintained and dragged in continuous movement without release of contact. In another embodiment, instead of a threshold distance, the pull-down gesture includes dragging the contact at a threshold velocity on top of email messages or threads 506 displayed within the application view 504 . Accordingly, contact 3310 is held and dragged at a velocity in a direction substantially orthogonal to lines of text within email messages or threads. In other embodiments, other properties of the maintained contact 3310 evaluated for a pull-down gesture other than distance and speed are the strength of the pressure of the contact or the number of points of contact.

As illustrated in FIG. 33B , in response to the sensed contact 3310 and the pull-down gesture, the application view 504 of the email application displays an additional user interface within the application view 504 above the displayed email message 2920A. display elements. According to one embodiment, these additional user interface elements include a search box 3320 and a select-mailbox option 3330 over the email message 506A. Alternatively, additional user interface elements including a search box 3320 are displayed within the first instance of the application view 504 . Select-Mailbox option 3330 allows the user to choose between searching all mailboxes of the email application and searching only the current mailbox. The current mailbox is the mailbox in which email messages or threads are displayed within the application view 504 . A contact (not shown), including a tap, detected by device 100 on the area labeled "All Mailboxes" toggles on selection of all Mailboxes, while the area labeled "Current Mailboxes" Contact on top toggles the selection of the current mailbox only. A selected (toggled on) mailbox option 3340 is visually distinct from an unselected option. For example, selected mailbox options have a darker background color than unchecked ones.

Contact 3350 is detected by device 100 over search text input element 3360 within search box 3320 . Contact 3350 includes, but is not limited to, a tab on input element 3350 . In response to the sensed contact 3350 , a search string creation interface or drafting UI 3370 is shown, as illustrated in FIG. 33C according to one embodiment. As indicated, the drafting UI 3370 is displayed on top of the application view 504 . In one embodiment, the drafting UI 3370 may be displayed at a full width equal to the width of the touchscreen 112 . The drafting UI is used to enter search text 3372 into search text input element 3360 . In the example shown in FIG. 33C , the search text “Lore” is entered into the search text input element 3360 by the user.

In response to entering the search text, the email application searches for matches within the email messages of the selected mailbox. A mailbox is selected based on a selection-mailbox option 3330 . Email messages in the selected mailbox containing matches to the search text are automatically split into different search result groups based on the location of the search term in the email. The search result group includes sender information, recipient information, subject, and query result groups based on message body, labeled "From", "To/Cc", "Subject", and "Message" respectively. Association of an email message containing a match with a search result group is based on whether the matched text is part of each sender information, recipient information, subject, or message body. For example, if matching text is found within the sender information, the corresponding email message is associated with a search result group based on the sender information (eg, "sender"). Thus, each query result group indicates where the matched text is located in the email message. If the matching text occurs at multiple locations within the email message, eg, sender information and message body, the email message is associated with each corresponding search result group. Other search result groups may be defined by the user, for example, based on date, attachment size, sender location, or other attributes or fields available within the email message.

33C-33E, in response to matches within the email messages of the selected mailbox, the email application's application view 504 is displayed in search result groups 3374A, 3374B, 3374C, 3374D. Display matching email messages. Each search result group 3374 has a header element 3375 . Each header element 3375A, 3375B, 3375C, 3375D has a corresponding label ie. Display "From", "To/Cc", "Subject" and "Message" respectively. The displayed text of matching email messages within application view 504 is visually distinct from other displayed text of email messages. 33C-33E , for example, matching text is displayed in a bold, black font, while other text is displayed in a plain, gray font.

33D further illustrates a scrolling gesture 3385 for scrolling email messages matching search result groups within application view 504 . As shown in FIG. 33D , scrolling gesture 3385 is applied in a direction substantially orthogonal to a line of text in the displayed email messages. Application of this scrolling gesture displays search result groups and their email messages following the email message 3386 displayed at the bottom of the application view 504 . When these subsequent search result groups and their e-mail messages are displayed, the reversal of the direction of the scrolling gesture displays the currently displayed search result groups and search result groups preceding the e-mail messages and their e-mail messages.

Only three of the email messages matching the search text are initially displayed in each search results group within the application view 504 . If more than three email messages are included in the search results group, for example, more options 3387, labeled "Show More Results", are displayed at the bottom of the corresponding search results group in the application view 504 . do. More option 3387 allows for display of additional email messages that are included in the corresponding search result group and have not yet been displayed. In response to an optional gesture comprising a tap (not shown), more options 3387 displays those additional email messages within the search results group. More option 3387 is similar to more option 2940 described above with respect to FIG. 29C . Once all email messages have been displayed within the search results group, the More option 3387 is no longer displayed within the application view 504 . As shown in FIG. 33E , instead of the More option, a hide option 3388 is displayed within the application view 504 . Hide option 3388 is similar to hide option 2944 described above with respect to FIG. 29D , and in response to an optional gesture including a tap (not shown), with the remaining email messages in the search results group hidden from the display 3 Only two emails are displayed.

34 is a flowchart of a method for retrieving email messages within the messages view interfaces of an email application, according to one embodiment. The email application receives ( 3410 ) a search query that includes at least one term to search for email messages within the messaging application. In response to receiving the search query, the email application determines ( 3415 ) whether one or more email messages in the messaging application include at least one search term. Next, the email application determines ( 3420 ) whether each of the one or more email messages in the messaging application includes a search term, a field in which the search term is found within the email message. When the email application determines the field, the search term may appear in one or more of a plurality of different, predetermined locations. The email application then displays ( 3425 ) one or more email message query result groups, each containing one or more email messages in the messaging application based on a different predetermined location and including the search term in the corresponding predetermined location.

The disclosure herein has been described in particular detail with respect to possible embodiments. Those skilled in the art will appreciate that other embodiments may be practiced. First, the specific naming of components and variables, capitalization of terms, properties, data structures, or other programming or structural aspects are neither essential nor critical, and the mechanisms implementing the present invention or their characteristics may differ names, formats, or protocols. Moreover, the specific division of functionality among the various system components disclosed herein is illustrative only and not essential; Functions performed by a single system component may instead be performed by multiple components, and functions performed by multiple components may instead be performed by a single component.

Some portions of the detailed description above present features relating to algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations are used by those of ordinary skill in the data processing arts to most effectively convey the substance of their work to others skilled in the art. These operations, though described functionally or logically, are understood to be implemented by computer programs. Moreover, it has also proven convenient at times to apply these arrangements of operations, either as modules or by functional names, without loss of generality.

As is apparent from the discussion above, and unless stated otherwise specifically, throughout the detailed description, discussions using terms such as "determining" or "indicating", etc., refer to computer system memories or registers or other such information storage, transfer, etc. or to the operations and processes of a computer system, or similar electronic computing device, that manipulate and transform data expressed as physical (electronic) quantities within display devices.

Certain aspects of the embodiments disclosed herein include process steps and instructions described herein in the form of an algorithm. Note that the process steps and instructions may be implemented in software, firmware or hardware, and when implemented in software, may be downloaded to reside on and operated from different platforms used by real-time network operating systems. Should be.

The algorithms and operations presented herein are not inherently related to any particular computer or other device. Various general purpose systems may also be used with programs in accordance with the teachings herein, or it may prove convenient to construct a more specialized apparatus to perform the required method steps. The structure necessary for a variety of these systems will be apparent to those skilled in the art with equivalent modifications. In addition, the present invention has not been described with reference to a specific programming language. It will be appreciated that a variety of programming languages may be used to implement the disclosures of the invention as described herein, and references to specific languages are provided for the realization and disclosure of the best embodiment of the invention.

Embodiments disclosed herein are convenient for a wide variety of computer network systems across numerous topologies. Within the art, the configuration and management of large-scale networks includes storage devices and computers communicatively coupled to other computers and storage devices via a network, such as the Internet.

In conclusion, it should be noted that the language used herein has been chosen primarily for readability and educational purposes, and may not have been chosen to detail or limit the subject matter of the present invention. Accordingly, the disclosure of this specification is intended to illustrate rather than limit the scope of the invention as set forth in the claims that follow.

Claims (17)

As a method:
In an electronic device having a touch-sensitive surface and a display:
displaying a messaging application, wherein the messaging application is configured to display a plurality of email messages;
identifying a conversation thread in the plurality of email messages, the conversation thread including two or more email messages from the plurality of email messages;
determining information common to the two or more email messages in the conversation thread, the common information including a conversation title and a number indicating a number of email messages in the conversation thread;
in response to selection of at least one of the two or more email messages of the conversation thread, displaying a conversation view comprising a header section that is visually distinct from a message section, wherein the header section is located at a different location than the message section. a header to be displayed, wherein the header includes the common information, the message zone includes the two or more of the email messages in the conversation thread, each of the two or more email messages includes sender information and Contains content information - ;
detecting a swipe input within the messaging application while displaying the conversation view; and
in response to the swipe input in the messaging application, displaying additional common information in the header of the conversation view;
A method comprising The method of claim 1 , wherein in response to a request to view email messages within the conversation thread that are not displayed within the visible portion of the conversation view, display one or more additional email messages within the conversation thread, each additional email message comprising: A method comprising sender information and content information. The method of claim 1 , wherein the header further includes a number of email messages included in the conversation thread. The method of claim 1 , wherein the conversation title for the conversation thread is based, at least in part, on a subject line of each email message contained within the conversation thread. The method of claim 1 , wherein:
adding a participant to a plurality of participants in the conversation thread; and
in response to adding a participant to the plurality of participants,
displaying in the header the name of the added participant that is visually distinct from the names of other participants; and
and including in the conversation thread an email message associated with the added participant. The method of claim 1 , wherein:
in response to selecting a participant from among a plurality of participants in the conversation thread,
displaying the name of the selected participant in the header and removing the names of all other participants of the plurality of participants from display; and
displaying only the email messages associated with the selected participant under the header by indicating the sender of the email message without displaying for each displayed email message at least some of the common information of the email message. Way. The method of claim 1 , wherein:
removing a participant from a plurality of participants in the conversation thread; and
in response to removing a participant from the plurality of participants,
displaying the removed participant's name in the header that is visually distinct from other participants'names; and
and removing an email message associated with the removed participant from the conversation thread. The method of claim 1 , wherein names of only some of all participants of a plurality of participants in the conversation thread are displayed in the header. 2. The method of claim 1, wherein up to two lines in the header are occupied by names of one or more participants. The method of claim 1 , further comprising providing an option to display all names of a plurality of participants in the header when only at most two lines are occupied in the header by displayed names. The method of claim 1 , further comprising providing an option for displaying one of at least a portion of the two or more email messages. The method of claim 1 , wherein names indicated in the header include a first name. The method of claim 1 , wherein names indicated in the header include a first name and a last name initial. The method of claim 1 , wherein the names displayed in the header include a first name and if two or more of the names are the same, the displayed names of the same names include a first name and a last name initial. The method of claim 1 , wherein the statements displayed in the header are responsive to detection of a pull-down gesture. 16. A computer readable storage medium storing one or more programs, the one or more programs configured for execution by one or more processors of a device having a display and a touch-sensitive surface, the one or more programs comprising: A computer readable storage medium comprising instructions for performing the method of any one of the preceding claims. An electronic device comprising:
display;
touch-sensitive surfaces;
one or more processors; and
a memory storing one or more programs configured to be executed by the one or more processors
An electronic device comprising: the one or more programs comprising instructions for performing the method of any one of claims 1 to 15 .

Images