JP7344997B2 - DEVICES, METHODS, AND GRAPHICAL USER INTERFACE FOR PROVIDING NAVIGATION AND SEARCH FEATURES - Google Patents

Description

TECHNICAL FIELD This application relates generally to electronic devices with touch-sensitive surfaces, including, but not limited to, electronic devices with touch-sensitive surfaces that provide navigation and search functionality.

The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Exemplary touch-sensitive surfaces include touch pads and touch screen displays. Such surfaces are widely used to manipulate and navigate user interfaces.

A user can use touch input to navigate the user interface and perform searches. However, methods for performing these operations are cumbersome and inefficient. Additionally, these methods are unnecessarily time consuming, thereby wasting energy. This latter consideration is particularly important in battery powered devices.

Therefore, there is a need for electronic devices with faster and more efficient methods and interfaces for providing navigation and search functionality. Embodiments described herein provide superior integration of these features, allowing users to easily launch multi-page applications while making search input interfaces available on different pages of the multi-page application launch interface, for example. By also allowing you to navigate between different pages within the interface. Such methods and interfaces optionally complement or replace conventional methods for providing navigation and search functionality. Such methods and interfaces reduce the cognitive burden on users and create more efficient human-machine interfaces. For battery-powered devices, such methods and interfaces conserve power and extend the time interval between battery charging.

The above deficiencies and other problems associated with user interfaces for electronic devices with touch-sensitive surfaces are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (eg, a notebook computer, tablet computer, or handheld device). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a "touch screen" or "touch screen display"). In some embodiments, the device includes a graphical user interface (GUI), one or more processors, a memory, and one or more modules, programs, or modules stored in the memory to perform multiple functions. Has an instruction set. In some embodiments, the user interacts with the GUI primarily through finger contacts and gestures on the touch-sensitive surface. In some embodiments, those functions optionally include image editing, drawing, presenting, word processing, website creation, disc authoring, spreadsheet creation, game playing, making phone calls, These include videoconferencing, email sending, instant messaging, training support, digital photography, digital videography, web browsing, digital music playback, and/or digital video playback. Executable instructions for performing these functions are optionally contained within a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

According to some embodiments, the method is performed on an electronic device that includes a display and a touch-sensitive surface. The method includes displaying a first page of a multi-page application launch interface that includes multiple pages of application icons for launching an application, the first page including a first plurality of application icons. and detecting a first input on the touch-sensitive surface, including detecting a first contact and detecting movement of the first contact on the touch-sensitive surface. The method includes a criterion that is met when the first contact moves more than a predetermined amount in a first predetermined direction on the touch-sensitive surface in response to detecting a first input on the touch-sensitive surface. displaying the first page of the multi-page application launch interface in accordance with a determination that the first input satisfies display criteria for the next page, including displaying a second plurality of application icons that are different from the first plurality of application icons; and replacing the display of a second page of the multi-page application launch interface with a display of a second page of the multi-page application launch interface, and a criterion that is met when the first contact moves more than a predetermined amount in a second predetermined direction perpendicular to the first direction. and displaying a search interface including a search input field for inputting search criteria in accordance with a determination that the first input satisfies display criteria of the search interface, including: displaying a search interface.

According to some embodiments, the electronic device is a display unit configured to display a first page of a multi-page application launch interface that includes multiple pages of application icons for launching an application. , a display unit, the first page including a first plurality of application icons, a touch-sensitive surface unit configured to receive a user gesture, and a processing unit coupled to the display unit and the touch-sensitive surface unit. ,including. The processing unit is configured to detect a first input on the touch-sensitive surface unit, detecting a first contact on the touch-sensitive surface unit, and detecting movement of the first contact; including. The processing unit is satisfied when the first contact moves more than a predetermined amount in a first predetermined direction on the touch sensitive surface in response to detecting the first input on the touch sensitive surface unit. displaying a first page of a multi-page application launch interface in accordance with a determination that the first input satisfies display criteria for a next page, including a second plurality of application icons different from the first plurality of application icons; and is satisfied when the first contact moves more than a predetermined amount in a second predetermined direction perpendicular to the first direction. The search interface is further configured to enable display of a search interface including a search input field for inputting search criteria in accordance with a determination that the first input satisfies display criteria of the search interface, including criteria.

According to some embodiments, an electronic device includes a display, a touch-sensitive surface, one or more processors, a memory, and one or more programs, the one or more programs being stored in the memory. The one or more programs stored and configured to be executed by one or more processors include instructions for performing the operations of any of the methods described herein. According to some embodiments, the non-transitory computer-readable storage medium, when executed by an electronic device comprising a display and a touch-sensitive surface, causes the device to perform the methods mentioned and described herein. It stores therein an instruction to execute one of the following operations. According to some embodiments, a graphical user interface on an electronic device includes a display, a touch-sensitive surface, a memory, and one or more processors that execute one or more programs stored in the memory. , including one or more of the elements displayed in any of the methods described above, which are updated in response to input as described in any of the methods described herein. According to some embodiments, an electronic device includes a display, a touch-sensitive surface, and means for performing the operations of any of the methods described herein. According to some embodiments, an information processing apparatus for use in an electronic device comprising a display and a touch-sensitive surface includes means for performing the operations of any of the methods described herein. .

Thus, electronic devices with displays have faster and more efficient methods and interfaces for providing navigation and search functionality, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. You can increase the degree. Such methods and interfaces can complement or replace conventional methods for providing navigation and search functionality.

For a better understanding of the various embodiments described, please refer to the following description of the embodiments in conjunction with the following drawings, where like reference numbers refer to corresponding parts throughout the figures. Point.

1 is a block diagram illustrating a portable multifunction device with a touch-sensitive display, according to some embodiments. FIG.

FIG. 2 is a block diagram illustrating example components for event processing, according to some embodiments.

2 illustrates a portable multifunction device with a touch screen, according to some embodiments.

1 is a block diagram illustrating an example multifunction device with a display and a touch-sensitive surface, according to some embodiments. FIG.

4 illustrates an example user interface for a menu of applications on a portable multifunction device, according to some embodiments.

A display illustrates an example user interface for a multifunction device with a separate touch-sensitive surface, according to some embodiments.

4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 2 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments. 4 illustrates an example user interface for providing access to various functionality including navigation and search functionality, according to some embodiments.

3 is a flowchart illustrating a method of providing access to various functionality including navigation and search functionality, according to some embodiments. 1 is a flowchart illustrating a method of providing access to various functionality including navigation and search functionality, according to some embodiments. 1 is a flowchart illustrating a method of providing access to various functionality including navigation and search functionality, according to some embodiments. 3 is a flowchart illustrating a method of providing access to various functionality including navigation and search functionality, according to some embodiments.

1 is a functional block diagram of an electronic device, according to some embodiments. FIG.

Many electronic devices allow users to navigate user interfaces and perform navigation and search functions. The electronic devices described below improve upon these by providing faster, more efficient, and better integrated methods and interfaces for navigating multi-page application launch interfaces and searching for content. Improve your methods. For example, the device allows the search input interface to be accessed directly from multiple different pages of the multi-page application launch interface while also allowing the user to easily navigate between different pages within the multi-page application launch interface. do. The device also allows the user to access additional functionality directly from a multi-page application launch interface, such as a notifications interface, a multitasking interface, and/or a settings interface, using simple touch inputs.

In the following, FIGS. 1A-1B, 2, and 3 provide a description of exemplary devices. 4A-4B and 5A-5R illustrate example user interfaces. 6A-6D are flowcharts illustrating a method for providing access to various functionality including navigation and search functionality. FIG. 7 is a functional block diagram of the electronic device. The user interfaces of FIGS. 5A-5R are used to explain the processes of FIGS. 6A-6D.
exemplary device

Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. In the detailed description that follows, numerous specific details are set forth to provide a thorough understanding of the various embodiments described. However, it will be apparent to those skilled in the art that the various 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.

Although terms such as first, second, etc. are used herein in some instances to describe various elements, these elements should not be limited by those terms. will also be understood. These terms are only used to distinguish one element from another. For example, a first contact can be referred to as a second contact, and similarly, a second contact can be referred to as a first contact, without departing from the scope of the various described embodiments. will be possible. Although the first contact and the second contact are both contacts, they are not the same contact.

The terminology used in the description of various embodiments described herein is for the purpose of describing particular embodiments only and is not intended to be limiting. When used in the description of the various described embodiments and the appended claims, the singular forms "a," "an," and "the" refer to the singular forms "a," "an," and "the," unless the context clearly dictates otherwise. , plural forms are also intended to be included. It is also understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items. sea bream. The terms "includes," "including," "comprises," and/or "comprising" as used herein refer to the described features, integers, steps. , which specifies the presence of an action, element, and/or component, but excludes 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 this is not the case.

As used herein, the term "if" optionally includes "when", "upon", "in It is interpreted to mean "response to determining" or "in response to detecting." Similarly, the phrase "if it is determined" or "if (a stated condition or event) is detected" can be used depending on the context. ``upon determining'', ``in response to determining'', ``upon detecting'' (the stated condition or event) )" or "in response to detecting (the stated condition 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 functionality, such as PDA functionality and/or music playback functionality. Exemplary embodiments of portable multifunction devices are manufactured by Apple Inc. of Cupertino, California, without limitation. including the iPhone(R), iPod Touch(R), and iPad(R) devices. Other portable electronic devices are optionally used, such as laptop computers or tablet computers with touch-sensitive surfaces (eg, touch screen displays and/or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer with a touch-sensitive surface (eg, a touch screen display and/or touch pad).

The following discussion describes electronic devices that include displays and touch-sensitive surfaces. However, it should be understood that this electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse, and/or joystick.

This device typically includes drawing applications, presentation applications, word processing applications, website creation applications, disc authoring applications, spreadsheet applications, gaming applications, telephone applications, video conferencing applications, email applications, instant messaging applications, Various applications are supported, such as one or more of a training support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music playback application, and/or a digital video playback 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 and corresponding information displayed on the device are optionally adjusted and/or changed from application to application and/or within the corresponding application. In this way, the device's common physical architecture (such as a touch-sensitive surface) optionally supports a variety of applications with a user interface that is intuitive and transparent to the user.

Attention is now directed to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display 112, according to some embodiments. Touch-sensitive display 112 is sometimes conveniently referred to as a "touch screen" and may also be known or referred to as a "touch-sensitive display system." Device 100 includes a memory 102 (optionally including one or more computer readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, RF circuitry 108, and audio circuitry. It includes a mechanism 110, a speaker 111, a microphone 113, an input/output (I/O) subsystem 106, other input or control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more intensity sensors 165 for detecting the intensity of contact on device 100 (eg, a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 includes: for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface, such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300); One or more tactile output generators 167 are optionally included. These components optionally communicate via one or more communication buses or signal lines 103.

As used herein and in the claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on a touch-sensitive surface. ), or a substitute for the force or pressure of contact on a touch-sensitive surface. The intensity of contact has a range of values including at least four distinct values, and more typically hundreds of distinct values (eg, at least 256). The intensity of contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more sensors below or adjacent to the touch-sensitive surface are optionally used to measure forces at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (eg, a weighted average) to determine an estimated contact force. Similarly, the pressure sensitive tip of the stylus is optionally used to determine the pressure of the stylus on the touch sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or its change, the capacitance and/or change thereof of the touch-sensitive surface proximate the contact, and/or the resistance and/or change of the touch-sensitive surface proximate the contact. /or the variation thereof is optionally used as a substitute for contact force or pressure on the touch-sensitive surface. In some implementations, the surrogate measurement of contact force or pressure is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is in units corresponding to the surrogate measurement). described). In some implementations, the alternative measurement of contact force or pressure is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold is exceeded. (eg, the intensity threshold is a pressure threshold measured in units of pressure).

As used herein and in the claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a configuration of the device that would be detected by the user at the user's sense of touch. Refers to the physical displacement of an element (e.g., a touch-sensitive surface) relative to another component of the device (e.g., the housing), or the displacement of a component relative to the center of mass of the device. For example, in situations where the device, or a component of the device, is in contact with a user's touch-sensitive surface (e.g., fingers, palm, or other part of the user's hand), the tactile sensation generated by physical displacement may The intelligence output will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical properties of the device or a component of the device. For example, movement of a touch-sensitive surface (eg, a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down click" or "up click" of a physical actuator button. In some cases, the user may have a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement, even if there is no movement of the button. You will feel a tactile sensation such as a "down click" or "up click." As another example, motion of the touch-sensitive surface is optionally interpreted or interpreted by the user as "roughness" of the touch-sensitive surface, even if there is no change in the smoothness of the touch-sensitive surface. be sensed. Although a user's interpretation of such touch depends on the user's individual sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Therefore, when a tactile output is described as corresponding to a particular sensory perception of the user (e.g., "up click," "down click," "roughness"), the tactile output produced is The intellectual output corresponds to the physical displacement of the device or its components that produces the described sensory perception for a typical (or average) user.

Device 100 is only one example of a portable multifunction device, and device 100 may optionally have more or fewer components than those shown, or may optionally include two or more components. It is to be understood that combinations or optionally having different configurations or arrangements of the components may be used. The various components shown in FIG. 1A may be implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing circuits 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 semiconductor memory devices. . Access to memory 102 by other components of device 100, such as CPU 120 and peripheral interface 118, is optionally controlled by memory controller 122.

A peripheral interface 118 may be used to couple the device's input and output peripherals to the CPU 120 and memory 102. One or more processors 120 operate or execute various software programs and/or instruction sets stored in memory 102 to perform various functions and process data for device 100 .

In some embodiments, peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, these are optionally implemented on separate chips.

RF (radio frequency) circuitry 108 receives and transmits RF signals, also referred to as electromagnetic signals. The RF circuit 108 converts electrical signals to electromagnetic signals, or vice versa, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 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. Optionally includes well-known circuitry for performing the functions described above, including but not limited to. The RF circuit 108 is connected to an intranet and/or wireless network, such as a network such as the Internet, also referred to as the World Wide Web (WWW), a cellular telephone network, a wireless local area network (LAN), and/or a metropolitan area network (MAN). , as well as other devices, optionally by wireless communication. Wireless communications include Global System for Mobile Communications (GSM (registered trademark)), Enhanced Data GSM Environment (EDGE (registered trademark)), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), and Wideband Code Division. Multiple Access (W-CDMA®), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth®, Wireless Fidelity (Wi-Fi®) (e.g., IEEE 802 .11a, IEEE 802.11b, IEEE 802.11g, and/or IEEE 802.11n), Voice over Internet Protocol (VoIP), Wi-MAX®, protocols for email (e.g., Internet Message Access Protocol (EMAP) and/or Post Office Protocol (POP)), instant messaging (e.g. extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging g and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS) ), and/or any other suitable communication protocol, including Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this application. , and techniques.

Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between the user and device 100. Audio circuit 110 receives audio data from peripheral interface 118 , converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111 . Speaker 111 converts electrical signals into human audible sound waves. Audio circuit 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuit 110 converts the electrical signal to audio data and sends the audio data to peripheral interface 118 for processing. Audio data is optionally obtained from and/or transmitted to memory 102 and/or RF circuitry 108 by peripheral interface 118 . In some embodiments, audio circuit 110 further includes a headset jack (eg, 212 in FIG. 2). The headset jack connects the audio circuit 110 to a removable audio input/output peripheral, such as output-only headphones or a headset that has both an output (e.g., monaural or binaural headphones) and an input (e.g., a microphone). Provides an interface between

I/O subsystem 106 couples input and output peripherals of device 100, such as touch screen 112 and other input control devices 116, to peripheral interface 118. I/O subsystem 106 optionally includes a display controller 156, a light sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. include. One or more input controllers 160 receive/send electrical signals from/to 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 any of a keyboard, an infrared port, a USB port, and a pointer device, such as a mouse (or (not combined with either). The one or more buttons (eg, 208 in FIG. 2) optionally include up/down buttons for volume adjustment of speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (eg, 206 in FIG. 2).

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

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

The touch screen 112 optionally uses LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, although in other embodiments other display technologies are used. Ru. Touch screen 112 and display controller 156 optionally include one or more of, but are not limited to, capacitive technology, resistive technology, infrared technology, and surface ultrasound technology; Contact and any movement or interruption thereof using any of a number of touch-sensing technologies now known or developed in the future, including other proximity sensor arrays or other elements to determine the point of contact. Detect. In an exemplary embodiment, Apple Inc. Projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® by Co., Ltd. (Cupertino, California).

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. A user optionally contacts touch screen 112 using any suitable object or appendage, such as a stylus, finger, or the like. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which may be less precise than stylus-based input due to the larger contact area of a finger on a touch screen. In some embodiments, the device converts coarse finger-based input into precise pointer/cursor positions or commands to perform actions desired by the user.

In some embodiments, in addition to a touch screen, device 100 optionally includes a touch pad (not shown) for activating or deactivating certain features. In some embodiments, a touchpad is a touch-sensitive area of a device that, unlike a touchscreen, does not display visual output. The touchpad 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 various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power outage detection circuitry, power converters or inverters, power status indicators (e.g., luminescent diodes (LEDs)) and any other components associated with power generation, management, and distribution within a portable device.

Device 100 optionally also includes one or more optical sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 within I/O subsystem 106. Optical sensor 164 optionally includes a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. Light sensor 164 receives light from the environment that is 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 a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, a light sensor is located on the front side of the device opposite the touch screen display 112 so that the touch screen display can be used as a viewfinder for still and/or video image acquisition. It is located on the back of the device 100. In some embodiments, another light sensor is placed on the front of the device such that the user's image is optionally displayed while the user views other videoconference participants on the touchscreen display. will be obtained for a video conference.

Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 within I/O subsystem 106. Contact intensity sensor 165 may include one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezo force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., touch-sensitive surfaces). (a sensor used to measure the force (or pressure) of the contact). Contact intensity sensor 165 receives contact intensity information (eg, pressure information, or a surrogate for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is co-located with or proximate a touch-sensitive surface (eg, touch-sensitive display system 112). In some embodiments, 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. FIG. 1A shows a proximity sensor 166 coupled to peripheral interface 118. Alternatively, proximity sensor 166 is coupled to input controller 160 within 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 (e.g., when the user is making a phone call). .

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

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

In some embodiments, the software components stored within memory 102 include an operating system 126, a communication module (or instruction set) 128, a touch/movement module (or instruction set) 130, a graphics module (or instruction set) 132 , a text input module (or instruction set) 134 , a global positioning system (GPS) module (or instruction set) 135 , and an application (or instruction set) 136 . Additionally, in some embodiments, as shown in FIGS. 1A and 3, memory 102 stores device/global internal state 157. Device/global internal state 157 indicates which applications, if any, are currently active, including the active application state, which applications, views, or other information are displayed in various areas of touch screen display 112. display state, sensor state, including information obtained from various sensors and input control devices 116 of the device, and location information regarding the location and/or orientation of the device; .

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or VxWorks) Embedded operating systems (embedded operating systems) include various software components and/or drivers to control and manage common system tasks (e.g., memory management, storage device control, power management, etc.) Facilitates communication between components and software components.

Communication module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software for processing data received by RF circuitry 108 and/or external ports 124. Also includes constituent elements. External ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) can be coupled directly to other devices or indirectly via a network (e.g., the Internet, WLAN, etc.). adapted to do so. In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as or similar to the 30-pin connector used on the iPod (trademark of Apple Inc.) device, and/or a compatible It is a multi-pin (for example, 30-pin) connector. In some embodiments, the external port is the same as, or similar to, and/or compatible with an 8-pin connector (e.g., a Lightning connector) used on iPhone and iPod (trademark of Apple Inc.) devices. It is a flexible multi-pin (e.g. 8-pin) connector.

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

In some embodiments, the touch/movement module 130 includes one or more methods for determining whether an action has been performed by the user (e.g., determining whether the user has "clicked" on an icon). using a set of intensity thresholds. In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are determined by the physical hardware of device 100 rather than being determined by the activation threshold of a particular physical actuator. (can be adjusted without changing). For example, a trackpad or touchscreen display mouse "click" threshold can be set to any of a wide range of predetermined thresholds without changing the trackpad or touchscreen display hardware. Additionally, in some implementations, a user of the device may be given the ability to control multiple intensities at once (e.g., by adjusting individual intensity thresholds and/or using a system-level click "intensity" parameter). Software settings are provided for adjusting one or more of the set of intensity thresholds (by adjusting the threshold).

Touch/movement module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (eg, different movements, timing, and/or detected contact intensities). Gestures are therefore optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture may detect a finger down event, followed by a finger up (liftoff) event at the same location (or substantially the same location) as the finger down event (e.g., at the location of an icon). Including detecting. As another example, detecting a finger swipe gesture on a touch-sensitive surface may include detecting a finger down event, followed by one or more finger drag events, and then detecting a finger up (liftoff) event. including.

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

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

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

Text input module 134 is optionally a component of graphics module 132 and is used for various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other applications that require text input. ) provides a soft keyboard for entering text.

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

Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof.
● contacts module 137 (sometimes called address book or contact list);
●Telephone module 138,
●Video conference module 139,
- E-mail client module 140,
● Instant messaging (IM) module 141,
●Training support module 142,
- camera module 143 for still and/or video images;
●Image management module 144,
●Browser module 147,
●Calendar module 148,
- Weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets acquired by the user and user-created widgets 149-6. a widget module 149, optionally including one or more of
- a widget creation module 150 for creating a user created widget 149-6;
●Search module 151,
- a video and music playback module 152, optionally consisting of a video playback module and a music playback module;
●Memo module 153,
● Map module 154 and/or ● Online video module 155.

Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital These include copyright management, voice recognition, and voice reproduction.

Contacts module 137, along with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, optionally includes an application of contacts module 137 in memory 102 or memory 370. is used to manage an address book or contact list (stored in internal state 192), including adding name(s) to the address book, removing name(s) from the address book, etc. ); associate telephone number(s), email address(es), physical address(es), or other information with a name; associate an image with a name; associate an image with a name; providing a telephone number or email address to initiate and/or facilitate communication, such as by telephone 138, video conference 139, email 140, or IM 141.

Telephone module 138, along with 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 134, generates a series of characters corresponding to a telephone number. to access one or more phone numbers in address book 137, modify the phone number entered, dial the corresponding phone number, conduct a conversation, and connect when the conversation is complete. Optionally used to hang up or end a call. As mentioned above, wireless communications optionally use any of a number of communication standards, protocols, and technologies.

RF circuit 108, audio circuit 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and In conjunction with telephony module 138, video conferencing module 139 includes executable instructions for initiating, conducting, and terminating a video conference between a user and one or more other participants according to the user's instructions. .

In conjunction 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 composes an email in response to user instructions. , including executable instructions for sending, receiving, and managing. Together with the image management module 144, the email client module 140 greatly facilitates creating and sending emails with still or video images taken with the camera module 143.

In conjunction with the RF circuit 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 inputs a series of characters corresponding to an instant message and Modify entered characters (e.g. using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephone-based instant messaging, or XMPP, SIMPLE, for Internet-based instant messaging) or using IMPS), receive instant messages, and view received instant messages. In some embodiments, instant messages sent and/or received may include graphics, photos, audio files, video files, and and/or other attachments, optionally. As used herein, "instant messaging" refers to telephone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS). message).

In conjunction with the 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 music playback module 146, the training support module 142 provides training calibrate the sensors used to create (e.g., regarding time, distance, and/or calorie consumption goals), communicate with training sensors (sport devices), receive training sensor data, and monitor training. Contains executable instructions for selecting and playing music for training, displaying, storing, and transmitting training data.

In conjunction with touch screen 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 can capture still images or video ( including video streams) and storing them in memory 102, modifying characteristics of still images or videos, or deleting still images or videos from memory 102.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 arranges and modifies still images and/or video (e.g., , edit), otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store.

In conjunction with the RF circuitry 108, the touch screen 112, the display system controller 156, the contact module 130, the graphics module 132, and the text input module 134, the browser module 147 displays web pages or portions thereof, and links to the web pages. includes executable instructions for browsing the Internet according to a user's instructions, including searching for, linking to, receiving, and displaying attached attachments and other files;

In conjunction with the RF circuitry 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, the calendar module 148 operates according to user instructions. , including executable instructions for creating, displaying, modifying, and storing calendars and data associated with calendars (e.g., calendar items, to-do lists, etc.).

Widget module 149, along 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, includes a mini applications (e.g., weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or mini-applications created by users (e.g., user-created widget 149-6). In some embodiments, the widget includes Hypertext Markup Language (HTML) files, Cascading Style Sheets (CSS) files, and JavaScript files. In some embodiments, widgets include XML (Extensible Markup Language) files and JavaScript files (eg, Yahoo!® widgets).

Widget creation module 150, along with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, creates widgets (e.g., optionally used by the user to turn a location into a widget).

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

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

Along with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 provides executable instructions for creating and managing notes, to-do lists, etc. according to user instructions. including.

Along with the 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, the map module 154 provides the map and receive, display, modify, and store data associated with (e.g., driving directions, data about stores and other points of interest at or near a particular location, and other location-based data); Optionally used for.

In conjunction with 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 client module 140, and browser module 147, online video Module 155 allows the user to use H. access, browse, receive (e.g., by streaming and/or download), and play (e.g., on a touch screen or connected via external port 124) online video in one or more file formats, such as 264. (on an external display), sends an email with a link to a particular online video, and contains instructions that allow you to manage it in another way. 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 includes a set of executable instructions for performing one or more of the functions described above and methods described in this application (e.g., computer-implemented methods and methods described herein). other information processing methods). These modules (i.e., instruction sets) need not be implemented as separate software programs, procedures, or modules; therefore, various subsets of these modules may optionally be implemented in various embodiments. be combined or rearranged. In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Additionally, memory 102 optionally stores additional modules and data structures not mentioned above.

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

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

FIG. 1B is a block diagram illustrating example components for event processing, according to some embodiments. In some embodiments, memory 102 (in FIG. 1A) or 370 (FIG. 3) stores event sorter 170 (e.g., in operating system 126) and corresponding applications 136-1 (e.g., applications 137-151, as described above). 155, and any one of 380 to 390).

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

In some embodiments, application internal state 192 includes additional information, such as resume information used when application 136-1 resumes execution, information that is being displayed or ready for display by application 136-1. a queue of states to enable the user to return to a previous state or view of the application 136-1, and a queue of states to redo/undo previously taken actions by the user; Contains one or more of the matrices.

Event monitor 171 receives event information from peripheral interface 118. Event information includes information about sub-events (eg, a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripheral interface 118 transmits information received from I/O subsystem 106 or from sensors such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (via audio circuitry 110). do. The information that peripheral 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 peripheral interface 118 at predetermined intervals. In response, peripheral device interface 118 sends event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (eg, exceeding a predetermined noise threshold and/or receiving input for more than a predetermined amount of time).

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

Hit view determination module 172 provides software procedures for determining where within one or more views a sub-event occurs when touch-sensitive display 112 displays more than one view. do. A view consists of controls and other elements that a 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 are performed. Implemented. The application view (of the corresponding application) in which the touch is detected optionally corresponds to a programmatic level within the programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is optionally referred to as the hit view, and the set of events that are recognized as appropriate input are, at least in part, the first to initiate a touch-based gesture. Optionally, the determination is made based on the hit view of the touch.

Hit view determination module 172 receives information related to touch-based gesture sub-events. If the application has multiple views organized as a hierarchy, 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 first sub-event (ie, the first sub-event in a sequence of sub-events forming an 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 for which it was identified as the hit view.

Active event recognizer determination module 173 determines which views in the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only hit views should receive a particular sequence of sub-events. In other embodiments, the active event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively involved views. , determine that a particular sequence of sub-events should be received. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, views higher up in the hierarchy are still considered actively participating views. maintained.

Event dispatcher module 174 distributes 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 delivers event information to the event recognizers determined by the active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information read by each 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 yet other embodiments, event sorter 170 is a standalone module or is part of another module stored in memory 102, such as touch/movement module 130.

In some embodiments, the application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each including instructions for handling touch events that occur within each view of the application's user interface. include. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple event recognizers 180. In other embodiments, one or more of the event recognizers 180 may be implemented as a user interface kit (not shown) or a higher level object from which the application 136-1 inherits methods and other attributes. , is part of a separate module. In some embodiments, each event handler 190 includes one or more of a data updater 176 , an object updater 177 , a GUI updater 178 , and/or event data 179 received from event sorter 170 . Event handler 190 optionally utilizes 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 corresponding event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included within the corresponding application view 191.

Each event recognition unit 180 receives event information (for example, event data 179) from the event sorter 170 and identifies an event from the event information. The event recognition section 180 includes an event reception section 182 and an event comparison section 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 receiving unit 182 receives event information from the event sorter 170. The event information includes, for example, information on sub-events such as a touch or a movement of a touch. 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 a touch movement, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes a current orientation of the device ( (also referred to as device pose).

The event comparison unit 184 compares the event information with a predetermined event or sub-event definition, and based on the comparison, determines the event or sub-event, or determines or updates the state of the event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definitions 186 include definitions of events (eg, a predetermined sequence of sub-events), such as event 1 (187-1), event 2 (187-2), and so on. In some embodiments, sub-events within event 187 include, for example, start touch, end touch, move touch, stop touch, and multiple touches. In one embodiment, the definition for event 1 (187-1) is a double tap on a display object. A double tap may include, for example, a first touch for a given step on a displayed object (touch start), a first lift-off for a given step (touch end), a first touch for a given step on a displayed object. a second touch (touch start), and a second lift-off (touch end) for a given stage. In another embodiment, the definition of event 2 (187-2) is a drag on the displayed object. Dragging includes, for example, touching (or contacting) a predetermined step on a displayed object, moving the touch across the touch-sensitive display 112, and lifting off the touch. In some embodiments, an 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 a corresponding user interface object. In some embodiments, event comparator 184 performs a hit test to determine the user interface object associated with the sub-event. For example, in an application view where three user interface objects are displayed on the touch-sensitive display 112, when a touch is detected on the touch-sensitive display 112, the event comparator 184 determines which of the three user interface objects was touched. Perform a hit test to determine whether it is associated with (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the results of the hit test to determine which event handler 190 needs to be activated. For example, the event comparison unit 184 selects an event handler associated with an object that triggers a sub-event and a hit test.

In some embodiments, the definition for each event 187 also includes a delay effect that delays delivery of event information until it is determined whether the sequence of sub-events corresponds to the event recognizer's event type. .

If the respective event recognizer 180 determines that the series of sub-events does not match any of the events in the event definition 186, the respective event recognizer 180 determines an event impossible state, an event failed state, or Enters the event end state and thereafter ignores subsequent sub-events of the gesture based on this touch. In this situation, other event recognizers, if present, that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

In some embodiments, each event recognizer 180 includes configurable attributes, flags, etc. that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. and/or metadata 183 having a list. In some embodiments, metadata 183 includes configurable attributes, flags, and/or lists that indicate how event recognizers interact or are enabled to interact with each other. include. In some embodiments, metadata 183 includes a list indicating whether configurable attributes, flags, and/or subevents are distributed to various levels within a view hierarchy or a program hierarchy.

In some embodiments, the corresponding event recognizer 180 activates the event handler 190 associated with the event when one or more particular sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to an event handler 190. Activating an event handler 190 is different from sending (and deferring sending) a sub-event to each hit view. In some embodiments, the event recognizer 180 throws a flag associated with the recognized event, and the event handler 190 associated with the flag catches the flag and performs a predetermined 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 views that are actively involved. An event handler associated with a series of sub-events or actively participating views receives the event information and performs a predetermined process.

In some embodiments, data updater 176 creates and updates data used by application 136-1. For example, data updater 176 updates phone numbers used by contact module 137 or stores video files used by video player module 145. In some embodiments, object updater 177 creates and updates objects used by application 136-1. For example, object updater 176 creates a new user interface object or updates the position 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 the touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are contained within a single module of each application 136-1 or application view 191. In other embodiments, they are included within two or more software modules.

The foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user input for operating multifunction device 100 using input devices, all of which are touch sensitive. It will be appreciated that it does not begin on screen. For example, mouse movements and mouse button presses, contact movements such as tapping, dragging, scrolling on a touchpad, pen stylus input, optionally in conjunction with single or multiple keyboard presses or holds; Device movements, verbal commands, detected eye movements, biometric inputs, and/or any combination thereof are optionally utilized as inputs corresponding to sub-events defining the event to be recognized. .

FIG. 2 is a diagram illustrating a portable multifunction device 100 with a touch screen 112, according to some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment, as well as other embodiments described below, the user may, for example, use one or more fingers 202 (not drawn to scale) or one or more stylus 203 (not drawn to scale). (not drawn to scale) allows one or more of the graphics to be selected by performing gestures on the graphics. In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture includes one or more taps, one or more swipes (from left to right, right to left, up, and/or down), and/or contact with device 100. rolling of the finger (from right to left, left to right, upward, and/or downward). In some implementations or situations, accidental contact with a graphic does not select that graphic. For example, if the gesture corresponding to selection is a tap, a swipe gesture that swipes over an application icon optionally does not select the corresponding application.

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

In one embodiment, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for powering the device on/off and locking the device, a volume control button(s) 208, a subscriber identity module. (SIM) card slot 210 , headset jack 212 , and docking/charging external port 124 . The push button 206 turns on and off power on the device by pressing the button down and holding the button down for a predetermined time interval, and by pressing the button down and holding the button down for a predetermined time interval. is optionally used to lock the device and/or unlock the device or initiate an unlocking process by releasing the button. In an alternative embodiment, device 100 also accepts verbal input via microphone 113 regarding activation or deactivation of some features. Device 100 also includes one or more touch intensity sensors 165 to detect the intensity of a touch on touch screen 112 and/or one or more touch intensity sensors 165 to generate a tactile output to a user of device 100. A tactile output generator 167 is also optionally included.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface, according to some embodiments. Device 300 may not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia playback device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (such as a household computer). or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more processors for interconnecting these components. Includes a communication bus 320. Communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communications between system components. Device 300 includes an input/output (I/O) interface 330 with a display 340, typically a touch screen display (eg, touch screen display 112). I/O interface 330 also includes a keyboard and/or mouse (or other pointing device) 350 and touch pad 355 (e.g., as described above with reference to FIG. 1A) for producing tactile output on device 300. A tactile output generator 357 (similar to tactile output generator(s) 167), a sensor 359 (e.g., a light sensor, an acceleration sensor, a proximity sensor, a touch sensitive sensor, and/or as described above with reference to FIG. 1A) 165) is also optionally included. Memory 370 includes high speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access semiconductor memory device, and optionally one or more magnetic disk storage devices, optical disk storage devices, flash memory. device, or other non-volatile semiconductor storage device. Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to those stored in memory 102 of portable multifunction device 100 (FIG. 1A), or a subset thereof. remember. Furthermore, memory 370 optionally stores additional programs, modules, and data structures that are not present within memory 102 of portable multifunction device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a presentation module 382, a word processing module 384, a website creation module 386, a disk authoring module 388, and/or a spreadsheet module 390; On the other hand, memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

Each of the elements of FIG. 3 identified above are optionally stored in one or more of the aforementioned memory devices. Each of the modules identified above corresponds to a set of instructions for performing the functions described above. The identified modules or programs (i.e., instruction sets) described above need not be implemented as separate software programs, procedures, or modules; therefore, 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 identified modules and data structures described above. Additionally, memory 370 optionally stores additional modules and data structures not described above.

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

FIG. 4A illustrates an example user interface for a menu of applications on portable multifunction device 100, according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof.
● signal strength indicator(s) 402 for wireless communication(s) such as cellular signals and Wi-Fi signals;
●Time 404,
●Bluetooth indicator 405,
●Battery status indicator 406,
- a tray 408 with icons for frequently used applications, such as:
o Icon 416 for the telephone module 138, labeled "Phone", optionally including an indicator 414 of the number of missed calls or voice mail messages;
o an icon 418 for the email client module 140 labeled "Mail", optionally including an indicator 410 of the number of unread emails;
o Icon 420 for the browser module 147, labeled "Browser"; o Icon 420 for the video and music playback module 152, also referred to as the iPod (trademark of Apple Inc.) module 152, labeled "iPod" icon 422, and icons for other applications such as:
o icon 424 for the IM module 141, labeled "Text";
o icon 426 for calendar module 148, labeled "Calendar";
o an icon 428 for the image management module 144, labeled "Photos";
o icon 430 for camera module 143, labeled "camera";
o icon 432 for online video module 155, labeled "online video";
o Icon 434 for the stock widget 149-2, labeled "Stocks";
o Icon 436 for map module 154, labeled "Map";
o Icon 438 for the weather widget 149-1, labeled "Weather";
o icon 440 for the alarm clock widget 149-4, labeled "clock";
o icon 442 for the training support module 142, labeled "Training Support";
o Icon 444 for the notes module 153, labeled "Notes," and o Icon 446 for a settings application or module that provides access to settings regarding the device 100 and its various applications 136.

Note that the icon labels shown in FIG. 4A are merely exemplary. For example, icon 422 for video and music playback module 152 is labeled "Music" or "Music Player." Other labels are optionally used for various application icons. In some embodiments, the label for the corresponding application icon includes the name of the application that corresponds to the corresponding application icon. In some embodiments, the label for a particular application icon is different from the name of the application that corresponds to that particular application icon.

FIG. 4B shows an example screen on a device (e.g., device 300 of FIG. 3) that includes a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3) separate from a display 450 (e.g., touchscreen display 112). A typical user interface is shown. Device 300 also includes one or more touch intensity sensors (e.g., one or more of sensors 357) for detecting the intensity of a touch on touch-sensitive surface 451 and/or a tactile sensor for a user of device 300. Includes one or more tactile output generators 359 for generating output.

Although some of the examples below are described with reference to input on the touch screen display 112 (if the touch-sensitive surface and display are combined), in some embodiments the device , detects input on a touch-sensitive surface separate from the display, as shown in FIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) has a major axis (e.g., 452 in FIG. 4B) that corresponds to a major axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). have According to these embodiments, the device may be connected to the touch-sensitive surface 451 at locations corresponding to corresponding locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). A touch (eg, 460 and 462 in FIG. 4B) is detected. Thus, when the touch-sensitive surface is separate from the display, user inputs (e.g., contacts 460 and 462 and their movements) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) ) is used by the device to operate the user interface on the multifunction device's display (eg, 450 in FIG. 4B). It should be understood that similar methods are optionally used with respect to other user interfaces described herein.

Furthermore, although the following description is primarily described with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), in some embodiments, such finger inputs It should be understood that one or more of them may be replaced with input from another input device (eg, mouse-based input or stylus input). For example, a swipe gesture is optionally replaced with a mouse click (e.g., instead of a contact), followed by cursor movement along a swipe path (e.g., instead of a contact movement). As another example, the tap gesture is optionally replaced with a mouse click while the cursor is placed at the location of the tap gesture (e.g., instead of detecting the contact and then stopping detecting the contact). . Similarly, it will be appreciated that when multiple user inputs are detected simultaneously, multiple computer mice are optionally used simultaneously, or mouse and finger contacts are optionally used simultaneously. sea bream.
User interface and related processes

Attention is directed to embodiments of user interfaces (“UI”) and related processing that can be implemented on electronic devices with displays and touch-sensitive surfaces, such as device 300 or portable multifunction device 100.

5A-5R illustrate example user interfaces for providing access to various functionality, including navigation and search functionality, according to some embodiments. The user interfaces of these figures are used to illustrate the processes described below, including the processes of FIGS. 6A-6D.

FIG. 5A shows a user interface 503 displayed on touch screen 112 of portable multifunction device 100 (sometimes referred to herein as "device 100"). User interface 503 includes a plurality of user interface objects (herein referred to as "affordances" or "selectable objects"), including an application icon 501 and a tray 408 that optionally includes one or more selectable user interface objects. (sometimes referred to as "user interface objects"). FIG. 5A illustrates a contact and touch screen 112 in which the device navigates from a first page to a second page of a multi-page application launch interface (eg, as shown in FIGS. 5B-5D) accordingly. in response to an input 502 including a touch movement to the left starting away from the edge and the device displaying a search interface including a search input field (e.g., as shown in FIGS. 5E-5G); the top edge of the touch screen 112 in which an input 504 includes a touch and a downward movement of the touch, and in response the device optionally displays a notification center interface (e.g., as shown in FIGS. 5J-5L); an input 506 including a touch and a downward movement on the touch screen 112, in response to which the device optionally displays a multitasking interface (e.g., as shown in FIGS. 5M-5O). At the bottom of the touch screen 112, an input 508 including a touch at the right edge and a movement to the left, and in response the device optionally displays a settings interface (e.g., as shown in FIGS. 5P-5R). Further shown is an input 510 that includes contact and upward movement.

5B-5D illustrate an example of navigating from a first page to a second page of a multi-page application launch interface. FIG. 5B shows the detection of user interface 503 (eg, page 1) and input 502. Input 502 includes a touch and a movement of the touch to the left. FIG. 5C shows input 502 at location 502-b and the corresponding transition between user interface 503 (eg, page 1) and user interface 505 (eg, page 2). FIG. 5D shows a user interface 505 (e.g., page 2) with a plurality of different application icons 501 (e.g., application icons 501-17 through 501-29) (e.g., when the device is moved away from the edge of touch screen 112). switching to the next page of the multi-page application launch interface in response to detecting a horizontal swipe gesture starting at

5E-5G illustrate an example of displaying a search interface that includes a search input field. FIG. 5E shows the detection of user interface 503 and input 504. Input 504 includes touch and downward movement. FIG. 5F shows input 504 at location 504-b and the corresponding transition between user interface 503 and search interface 507, which includes search field 514. FIG. 5G shows a search interface 507 that includes a search field 514 and a keyboard 516 (e.g., the device starts off the top edge of the touch screen 112 and the first page of the multi-page application launch interface is on the display). Display the search interface in response to a downward swipe gesture detected while displayed in the search interface.

5H-5I illustrate another example of displaying a search interface that includes a search input field. FIG. 5H shows the detection of user interface 505 and input 518. Input 518 includes touching (away from the top edge of touch screen 112) and downward movement. FIG. 5I shows a search interface 509 that includes a search field 514 and a keyboard 516 (e.g., the device starts off the top edge of the touch screen 112 and the second page of the multi-page application launch interface is on the display). Display the search interface in response to a downward swipe gesture detected while displayed in the search interface. Thus, in some embodiments, documents, applications, and other content stored on the device 100 are searched in response to detecting a downward swipe gesture that begins away from the top edge of the touch screen 112. A search interface for searching is directly accessible on any of a number of different pages within the multi-page application launch interface.

5J-5L illustrate embodiments of displaying a notification center interface. FIG. 5J shows the detection of user interface 503 and input 506. Input 506 includes a touch detected at the top edge of touch screen 112 and a downward movement of the touch. FIG. 5K shows input 506 at location 506-b and the corresponding transition between user interface 503 and notification interface 511 including event content 520 and completion affordance 522. FIG. 5L shows a notification interface 511 that includes event content 520, email content 524, weather forecast content 526, and completion affordances 522 (e.g., the device performs a downward swipe gesture starting at the top of the touch screen 112). (Display Notification Center in response to detections).

5M-5O illustrate an example of displaying a multitasking interface. FIG. 5M shows user interface 503 and detection of input 508. Input 508 includes a touch detected at the right edge of touch screen 112 and a movement of the touch to the left. FIG. 5N shows input 508 and multitasking interface 513 at location 508-b, which when activated cause the device to display a browser application (e.g., in full-screen mode of operation). , including a representation of a web browser application 528 and a browser application icon 420. FIG. 5O shows input 508 and multitasking interface 515 at location 508-c, which continues to display representations of web browser application 528 and browser application icon 420, and in addition shows that if either is active including displaying a representation of an email application 530 and an email application icon 418 that causes the device to display the email application (eg, in a full-screen mode of operation) when activated. Accordingly, in some embodiments, the device activates the multitasking interface in response to detecting a horizontal (e.g., left or right) swipe gesture that begins at a vertical edge of the touch screen 112. indicate. In some embodiments, a row of application icons (eg, icons 420 and 418) is configured to slide horizontally on the display in response to a horizontal swipe input on the row of application icons. In some embodiments, the rows of application representations (eg, representations 528 and 530) are configured to slide horizontally on the display in response to horizontal swipe inputs on the rows of application icons.

In some embodiments, the reduced representation 531 of the page of the multi-page application launch interface detects a tap gesture at a location on the touch screen 112 that corresponds to the reduced representation 531 of the page of the multi-page application launch interface (e.g., If activated (accordingly), the device ceases displaying the multitasking interface and redisplays the corresponding page in the multipage application launch interface (eg, FIG. 5M).

5P-5R illustrate an example of displaying a configuration interface. FIG. 5P shows the detection of user interface 503 and input 510. Input 510 includes a touch detected at the bottom edge of touch screen 112 and a movement of the touch in an upward direction. FIG. 5Q shows input 510 at location 510-b and the corresponding transition between user interface 503 and settings interface 517 (eg, a control center interface) that includes device icon 534 and brightness slider 536. FIG. 5R shows a settings interface 517 that includes a device icon 534, a brightness slider 536, music controls 538, and an application icon 540 (e.g., when the device detects an upward swipe gesture starting at the bottom edge of the touch screen 112). display the configuration interface, if applicable).

6A-6D are flowcharts illustrating a method 600 of providing access to various functionality including navigation and search functionality, according to some embodiments. Method 600 is performed on an electronic device (eg, device 300 of FIG. 3 or portable multifunction device 100 of FIG. 1A) that includes a display and a touch-sensitive surface. In some embodiments, the display is a touch screen display (eg, touch screen 112) and the touch sensitive surface is on the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations in method 600 are optionally combined and/or the order of some operations is optionally changed.

As described below, method 600 provides an intuitive method for providing direct access to multiple features from a multi-page application launch interface. The method reduces the cognitive burden on users when using navigation and search functions, creating a more efficient human-machine interface. For battery-operated electronic devices, users are able to navigate and search faster and more efficiently, thereby conserving power and increasing the time between charging batteries.

The electronic device with a display and a touch-sensitive surface displays a first page of a multi-page application launch interface including multiple (separately displayed) pages of application icons for launching an application; The page includes a first plurality of application icons (602). In some embodiments, the touch-sensitive surfaces described herein are part of a touch screen display. In some embodiments, the touch-sensitive surfaces described herein are sub-regions of a larger touch-sensitive surface, and the "edges" of the touch-sensitive surface described below are Corresponds to the edge of the sub-region of the sensing surface. For example, the device includes a larger touch-sensitive surface that matches the display of the device and also extends onto the bezel of the device, and a "touch-sensitive surface" as described herein refers to a touch-sensitive surface of the touch-sensitive surface. The edges are also sub-regions of a larger touch-sensitive device that coincide with the display, so that they correspond to the edges of the display (sometimes referred to as a touch screen display). In some embodiments, one or more pages of the application launch interface include, in addition to an application icon that launches a corresponding application when activated, one or more pages for controlling various features of the device. Contains bookmark icons, widgets, folder icons and/or other controls. For example, FIG. 5A shows that device 100 displays user interface 503 (e.g., page 1 of the three-page application launch interface), and FIG. 5D shows device 100 displaying user interface 505 (e.g., page 1 of the three-page application launch interface). Indicates that page 2) of the application startup interface will be displayed.

The device includes detecting a first input (e.g., a finger gesture) on the touch-sensitive surface, detecting a first contact on the touch-sensitive surface, and detecting movement of the first contact. Contains (604). For example, FIG. 5A shows device 100 detecting inputs 502, 504, 506, 508, and 510, each input including a touch and a movement of the touch on touch screen 112.

In response to detecting a first input on the touch-sensitive surface (606), the device detects that the first contact causes a predetermined amount (606) in a first predetermined direction (e.g., right to left) on the touch-sensitive surface. the first input of the multi-page application launch interface in accordance with a determination that the first input satisfies the display criteria for the next page, including criteria that are met when the page is moved by more than 10, 20, 30, 50, or 100 pixels). replacing the display of the first page with a second page of the multi-page application launch interface that includes a second plurality of application icons that are different (or distinct) from the first plurality of application icons; For example, FIGS. 5B-5D illustrate device 100 detecting input 502 on touch screen 112 and replacing user interface 503 (e.g., page 1) with user interface 505 (e.g., page 2). show. FIG. 5D shows a plurality of application icons 501 (e.g., application icons 501-17 to 501) that are different from the plurality of application icons 501 (e.g., application icons 501-1 to 501-16) included in the user interface 503 (FIG. 5B). -29) is further shown.

In some embodiments, in response to detecting the first input (606), a criterion is determined that is met when the first input originates at a first end (e.g., at the top) of the touch-sensitive surface. The device displays (610) a notification interface that includes a recently received notification in accordance with a determination that the first input satisfies display criteria for a notification interface, including a notification interface. In some embodiments, the notification interface datum is within a predetermined distance (e.g., 0.1-1.0 mm) or a predetermined number of pixels (e.g., 1-20 pixels) from the first edge of the touch-sensitive surface. ) that is met when the first input begins at a location proximate the first end of the touch-sensitive surface. For example, FIG. 5J shows the device 100 detecting an input 506 that includes a touch on the top edge of the touch screen 112 followed by a downward movement of the touch. 5K-5L illustrate that device 100 replaces the display of user interface 503 (eg, page 1) with the display of notification interface 511. FIG. 5L further illustrates notification interface 511 including email content 524 (eg, providing notification of recently received emails) and event content 520 (eg, providing notification of next occurring events).

In some embodiments, in response to detecting (606) the first input, the first input originated at a second end of the touch-sensitive surface that is different from the first end of the touch-sensitive surface. In accordance with a determination that the first input meets the display criteria of the multitasking interface, including criteria that are met when the first contact is first detected, the device may display multiple open applications. A multitasking interface including the representation is displayed (612). In some embodiments, the display criteria of the multitasking interface is within a predetermined distance (e.g., 0.1-1.0 mm) or a predetermined number of pixels (e.g., 1.0 mm) from the second edge of the touch-sensitive surface. 20 pixels) that is met when the first input begins at a location proximate to the second edge of the touch-sensitive surface. In some embodiments, a multitasking interface may be used to switch between open applications and/or close open applications. In some embodiments, the multitasking interface provides a reduced representation of the corresponding page of the multi-page application launch interface (e.g., multiple ) at one end of the row of open application representations. For example, FIG. 5M shows device 100 detecting input 508, which includes detecting a touch on the right edge of touch screen 112 and subsequent movement of the touch on touch screen 112 to the right. 5N-5O illustrate that device 100 replaces the display of user interface 503 (e.g., page 1) with the display of multitasking interface 513 of FIG. 5N and the display of multitasking interface 515 of FIG. 5O. . FIG. 5O further shows multitasking interface 515 including multiple open applications (eg, browser window 528 and email window 530).

In response to detecting a first input on the touch-sensitive surface (606), the device causes the first contact to move a predetermined amount (e.g., downward) in a second predetermined direction perpendicular to the first direction (606). for entering search criteria in accordance with a determination that the first input satisfies display criteria of the search interface, including criteria that are met when moved by more than 10, 20, 30, 50, or 100 pixels); A search interface including a search input field is displayed (614). For example, FIG. 5E shows that the device 100 generates an input 504 that includes detecting a touch on the touch screen 112 and a subsequent movement of the touch in a downward direction (e.g., perpendicular to the movement of the input 502 shown in FIG. 5B). Indicates that it is detected. 5F-5G show that device 100 at least partially replaces a display of user interface 503 (e.g., page 1) with a display of search interface 507 that includes a search field 514 (e.g., to display search field 514). (slide the wallpaper and application icons 501 downward). In some embodiments, the search field is pulled from "below" a device status bar that includes the current time as well as battery status and other device status information. 5H-5I show similar embodiments. 5H-5I, device 100 detects input 518 and at least partially replaces the display of user interface 505 (eg, page 2) with the display of search interface 509.

In some embodiments, displaying the search interface includes displaying a keyboard for entering text within the search input field (616). In some embodiments, both a keyboard and a search input field are displayed in response to detecting the first input. In some embodiments, a keyboard is displayed in response to detecting selection/activation (eg, using a tap gesture) of a search input field. For example, FIG. 5G shows device 100 displaying search interface 507 that includes keyboard 516.

In some embodiments, displaying the search interface includes translating the set of application icons on the first page in a second predetermined direction away from a corresponding edge of the display; displaying the input field between a corresponding edge (eg, top edge) of the display and the application icon (618). For example, FIGS. 5E-5G show device 100 transitioning from user interface 503 to search interface 507, which includes translating application icons 501 downward and displaying search field 514 above them. shows.

In some embodiments, displaying the search interface includes ceasing displaying at least a subset of the application icons on the first page (620). In some embodiments, all application icons are faded out, covered, or otherwise removed from the display. In some embodiments, some application icons are covered by the keyboard or other portions of the search interface while other application icons continue to appear on the display at the same time as the search interface. For example, FIGS. 5E-5G illustrate device 100 transitioning from user interface 503 to search interface 507, which includes ceasing to display application icons 501-13 through 501-16 in FIG. 5G.

In some embodiments, in response to detecting the first input (606), the device selects one of the application icons on the first page of the multi-page user interface while displaying the search interface. The above display is maintained (622). For example, FIGS. 5E-5G show device 100 transitioning from user interface 503 to search interface 507 and maintaining display of application icons 501-1 through 501-12 in search interface 507.

In some embodiments, the multi-page application launch interface includes a fixed icon area (e.g., an application dock) containing multiple application icons, and a fixed icon area (e.g., the same fixed icon area containing the same icon therein). is displayed simultaneously with each page of application icons across multiple pages (624). In some embodiments, displaying the search interface in response to detecting the first input may include ceasing displaying the fixed icon area (e.g., changing the search interface so that the search input field appears on the display). the application dock in the second direction so that the application dock disappears from the display when the application dock is slid in the second direction. For example, FIGS. 5E-5G show device 100 transitioning from user interface 503 to search interface 507. 5E shows device 100 displaying user interface 503 that includes tray 408 (e.g., an application dock), and FIG. 5G shows device 100 displaying user interface 507 and displaying tray 408. Indicates that the In some embodiments, the tray 408 is covered when the keyboard is displayed (eg, slid upward from the bottom of the touch screen 112). In some embodiments, while the search field 514 slides downwards to appear on the touch screen 112 (e.g., from below a device status bar that includes the current time and battery status), the tray 408 slides downwards to appear on the touch screen 112. It slides and disappears from the touch screen 112.

In some embodiments, while displaying (626) the search input field, the device receives (626) text input (e.g., text corresponding to a multiple character keypress action or a cut-and-paste action) within the search input field. 628), retrieve search results corresponding to the text input (630), and display one or more of the retrieved search results on a display (632). In some embodiments, the search results are search results corresponding to applications and content stored on the device. In some embodiments, the search results are search results that correspond to content stored remotely from the device (eg, a web page or media stream that can be streamed to the device). In some embodiments, search results are automatically obtained in response to receiving text input. In some embodiments, upon detecting selection of a search execution affordance displayed within a search user interface (e.g., a "Search" button on a keyboard used to enter text input within a search field). Accordingly, search results are obtained. In some embodiments, in response to detecting the selection of the respective search result, the device displays content corresponding to the respective search result (e.g., the device displays the content corresponding to the selected application or the selected search). display a user interface for the content corresponding to the result).

In some embodiments, in response to detecting the first input (606), the first input is a touch-sensitive device that is different from the first end of the touch-sensitive surface and the second end of the touch-sensitive surface. the device according to a determination that the first input satisfies display criteria of the settings interface, including criteria that are met when starting at the third end of the surface (e.g., the first contact is first detected); , displays (634) a settings interface that includes controls for changing multiple device settings. In some embodiments, the display criteria of the settings interface is within a predetermined distance (e.g., 0.1-1.0 mm) or a predetermined number of pixels (e.g., 1-20 mm) from the third edge of the touch-sensitive surface. and a criterion that is met when the first input begins at a location proximate to the third edge of the touch-sensitive surface, such as within a third edge of the touch-sensitive surface. In some embodiments, a settings interface may be used to change commonly used device settings such as screen brightness, volume, aircraft mode, and turning on/off wireless communications. For example, FIG. 5P shows device 100 detecting an input 510 that includes a contact on the bottom edge of touch screen 112 and subsequent upward movement of the contact on touch screen 112. 5Q-5R illustrate that device 100 at least partially replaces the display of user interface 503 (eg, page 1) with the display of settings interface 517 (eg, control center interface). FIG. 5R further shows a settings interface 517 that includes multiple controls (eg, brightness slider 536, music control 538, and device icon 534) for changing device settings.

In some embodiments, the display criteria of the search interface is such that the first input begins (e.g., the second touch first) away from the first edge (e.g., the top) of the touch-sensitive surface. 636). For example, the search interface display criteria may include a first criterion that is met when the contact moves more than a predetermined amount in a first direction, and a first criterion that is met when the contact moves more than a predetermined amount in a first direction; and a second criterion that is satisfied when the condition is met. In some embodiments, the distance from the first end is more than a predetermined distance (e.g., 0.1-1.0 mm) or a predetermined number of pixels (e.g., 1-1.0 mm) from the first end. When the first input begins at a location more than 20 pixels away (e.g., a touch on the first input is first detected), the first input leaves the first edge " ” is determined to have started at the location. Some embodiments include a criterion that is met when a first input begins (e.g., a first contact is first detected) at a first end (e.g., top) of the touch-sensitive surface. , the device displays a notification interface including recently received notifications (e.g., instant messages, emails, social network messages, application state updates, etc.) in accordance with a determination that the first input satisfies display criteria for the notification interface. . In some embodiments, the display criteria of the notification interface is within a predetermined distance (e.g., 0.1-1.0 mm) or a predetermined number of pixels (e.g., 1-20 mm) from the first edge of the touch-sensitive surface. the first input begins at a location proximate to the first edge of the touch-sensitive surface, such as within a first edge of the touch-sensitive surface; For example, FIG. 5J includes device 100 detecting input 506 starting at the top edge of touchscreen 112. 5K-5L show that the device 100 replaces the display of the user interface 503 with the notification interface 511 as a result. In a targeted example, FIG. 5E shows that device 100 detects input 504 that begins at a location away from the top edge of touch screen 112. 5F-5G show that, as a result, device 100 replaces the display of user interface 503 with search interface 507.

In some embodiments, the device detects a second input (e.g., a finger gesture) on the touch-sensitive surface while displaying a corresponding page of the multi-page application launch interface, and the second contact detecting (different from the first touch) and exceeding a predetermined amount (e.g., 10, 20, 30, 50, or 100 pixels) of the second touch in a second direction (e.g., downward); and detecting movement (638).

In some embodiments, in response to detecting (640) the second input on the touch-sensitive surface, the first end (e.g., the top) of the touch-sensitive surface is the device according to a determination that the second input satisfies display criteria of the search interface, including criteria that are met when the second input begins (e.g., the second contact is first detected) at a location displays a search interface (642). In some embodiments, the distance from the first end is more than a predetermined distance (e.g., 0.1-1.0 mm) or a predetermined number of pixels (e.g., 1-1.0 mm) from the first end. When the first input begins at a location more than 20 pixels away (e.g., a touch on the first input is first detected), the first input leaves the first edge " ” is determined to have started at the location.

In some embodiments, in response to detecting (640) a second input on the touch-sensitive surface, the second input is initiated at the first end (e.g., the top) of the touch-sensitive surface ( In accordance with a determination that the second input satisfies the display criteria of the notification interface, including the criteria met when the first contact is first detected), the device displays a recently received notification (e.g., an instant message, A notification interface is displayed (644) including emails, social network messages, application status updates, etc. In some embodiments, the display criteria of the notification interface is within a predetermined distance (e.g., 0.1-1.0 mm) or a predetermined number of pixels (e.g., 1-20 mm) from the first edge of the touch-sensitive surface. and a criterion that is met when the second input begins at a location proximate to the first edge of the touch-sensitive surface, such as within (pixel). For example, in response to detecting a first input (e.g., movement of contact 502 in FIG. 5B that satisfies the next page display criteria), the device may apply a multi-page application, as shown in FIGS. 5B-5D. The first page of the launch user interface is replaced with a second page of the multi-page application launch user interface, and the device, after detecting the first input, detects the second input (e.g., from the edge of the touch screen 112). 5H-5I), the device displays a search input interface, as shown in FIGS. 5H-5I.

It is understood that the particular order described for the operations in FIGS. 6A-6D is merely an example and that the described order is not intended to indicate that the operations are the only order in which the operations may be performed. I want to be Those skilled in the art will recognize various ways to reorder the operations described herein.

According to some embodiments, FIG. 7 depicts a functional block diagram of an electronic device 700 configured in accordance with the principles of various described embodiments. Functional blocks of the device are optionally implemented in hardware, software, or a combination of hardware and software to carry out the principles of the various described embodiments. Those skilled in the art will appreciate that the functional blocks illustrated in FIG. 7 may optionally be combined or separated into sub-blocks to implement the principles of the various embodiments described. Accordingly, the description herein optionally supports any possible combinations or divisions or further definitions of the functional blocks described herein.

As shown in FIG. 7, the electronic device 700 includes a display unit 701 configured to display a first page of a multi-page application launch interface that includes multiple pages of application icons for launching an application. , the first page includes a first plurality of application icons. Electronic device 700 also includes a touch-sensitive surface unit 703 configured to receive user gestures, and a processing unit 702 coupled to display unit 701 and touch-sensitive surface unit 703. In some embodiments, processing unit 702 includes a detection unit 704, a replacement unit 706, a display enabling unit 708, a receiving unit 710, and an acquisition unit 712.

The processing unit 702 is configured to detect a first input on the touch-sensitive surface unit (e.g., using detection unit 704), and includes detecting a first contact and detecting a first input on the touch-sensitive surface unit. and detecting movement of the first contact. Processing unit 702 is responsive to detecting a first input on the touch-sensitive surface unit to determine whether the first contact is satisfied when the first contact moves more than a predetermined amount in a first predetermined direction on the touch-sensitive surface. displaying a first page of a multi-page application launch interface in accordance with a determination that the first input satisfies display criteria for a next page, including criteria for displaying a second plurality of applications that are different from the first plurality of application icons; replacing (e.g., using replacement unit 706) a display of a second page of the multi-page application launch interface containing an icon, and the first contact is in a second predetermined direction perpendicular to the first direction; displaying a search interface that includes a search input field for entering search criteria in accordance with a determination that the first input satisfies display criteria for the search interface, including criteria that are met when moved by more than a predetermined amount; For example, using display enabling unit 708).

In some embodiments, in response to detecting the first input, display criteria for the notification interface include criteria that are met when the first input originates at the first end of the touch-sensitive surface unit. Processing unit 702 is further configured to enable display (eg, using display enabling unit 708) of a notification interface that includes recently received notifications in accordance with the determination that the first input satisfies .

In some embodiments, in response to detecting the first input, when the first input originates at a second end of the touch-sensitive surface unit that is different from the first end of the touch-sensitive surface unit. displaying a multitasking interface that includes a representation of a plurality of open applications (e.g., display enabling unit 708 Processing unit 702 is further configured to enable (using)

In some embodiments, in response to detecting the first input, the first input is different from the first end of the touch-sensitive surface unit and the second end of the touch-sensitive surface unit. a display of a settings interface including controls for changing a plurality of device settings in accordance with a determination that the first input satisfies display criteria of the settings interface, including criteria that are met when initiated at a third end of the unit; Processing unit 702 is further configured to enable (eg, using display enabling unit 708).

In some embodiments, the search interface display criteria includes an additional criterion that is met when the first input begins at a location remote from the first end of the touch-sensitive surface unit. In some embodiments, the most recent input is determined in accordance with a determination that the first input satisfies display criteria of the notification interface, including criteria that are met when the first input originates at the first end of the touch-sensitive surface unit. Processing unit 702 is further configured to enable display (eg, using display enabling unit 708) of a notification interface including the received notification.

In some embodiments, the second input is configured to detect (e.g., using detection unit 704) on the touch-sensitive surface unit while enabling display of a corresponding page of the multi-page application launch interface. The processing unit 702 is further configured to include detecting the second touch and detecting movement of the second touch in a second direction by more than a predetermined amount. In some embodiments, in response to detecting the second input on the touch-sensitive surface unit, the second input is satisfied when the second input originates at a location remote from the first end of the touch-sensitive surface unit. enabling display of the search interface (e.g., using display enablement unit 708) and determining that the second input satisfies display criteria of the search interface, including criteria to be touched; displaying a notification interface containing recently received notifications in accordance with a determination that the second input satisfies display criteria for the notification interface, including criteria met when initiated at the first end of the sensing surface unit (e.g., The processing unit 702 is further configured to enable display (using a display enabling unit 708).

In some embodiments, enabling display of a search interface (e.g., using display enabling unit 708) may include displaying a keyboard for entering text within the search input field. including.

In some embodiments, enabling the display of the search interface (e.g., using the display enabling unit 708) includes displaying the set of application icons of the first page from the corresponding end of the display unit. translating away in a second predetermined direction and enabling display of a search input field between a corresponding edge of the display unit and the application icon.

In some embodiments, enabling display of the search interface (e.g., using display enabling unit 708) includes ceasing to display at least a subset of the application icons on the first page. including.

In some embodiments, displaying the search interface is enabled (e.g., using display enabling unit 708) in response to detecting the first input (e.g., using detection unit 704). The processing unit 702 is further configured to maintain display (e.g., using display enabling unit 718) of one or more of the application icons of the first page of the multi-page user interface while displaying the first page of the multi-page user interface. Ru.

In some embodiments, the multi-page application launch interface includes a fixed icon area that includes a plurality of application icons, the fixed icon area is displayed simultaneously with each page of application icons across multiple pages, and the fixed icon area is displayed simultaneously with each page of application icons across multiple pages; Enabling display of the search interface (eg, using display enabling unit 708) in response to detecting the search interface includes ceasing displaying the fixed icon region.

In some embodiments, while enabling display of the search input field, text input into the search input field is received (e.g., using receiving unit 710) and search results corresponding to the text input ( e.g., using the retrieval unit 712) and enable display of the retrieved search results on one or more display units (e.g., using the display enablement unit 708); A processing unit 702 is further configured.

Operations in the information processing method described above may be performed on one or more functional modules within an information processing device, such as a general-purpose processor (e.g., as described above in connection with FIGS. 1A and 3) or an application-specific chip. is optionally implemented by running the .

The operations described above with reference to FIGS. 6A-6D are optionally performed by the components shown in FIG. 1A, FIG. 1B, or FIG. 7. For example, display operations 602 and 614, detect operation 604, and replace operation 608 are optionally performed by event sorter 170, event recognizer 180, and event handler 190. An event monitor 171 within event sorter 170 detects contacts on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. The corresponding event recognizer 180 of the application 136-1 queries the event information against the corresponding event definition 186 and determines that a first contact (or rotation of the device) at a first location on the touch-sensitive surface Determine whether it corresponds to a predetermined event or sub-event, such as selection of an object on a user interface or rotation of a device from one orientation to another. When a corresponding predetermined event or sub-event is detected, the event recognizer 180 activates the event handler 1100 associated with the detection of the event or sub-event. Event handler 190 optionally uses or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses a corresponding GUI updater 178 to update what is displayed by the application. Similarly, it will be clear to those skilled in the art how other processes may be implemented based on the components shown in FIGS. 1A-1B.

The foregoing description has been described with reference to specific embodiments for purposes of explanation. However, the above illustrative discussion is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The principles of the invention and its practical application are explained in the best manner, and thus enable others skilled in the art to utilize the invention and its various embodiments with various modifications suitable to the particular applications contemplated. These embodiments have been selected and described to enable use in the format.

Claims (15)

In electronic devices that include touch-sensitive displays,
displaying a first user interface on the touch sensitive display;
detecting a swipe gesture while displaying the first user interface;
In response to the detection of the swipe gesture,
in accordance with a determination that the swipe gesture satisfies a first criterion that includes a criterion that is met when the swipe gesture is initiated at a first end of the touch-sensitive display and moved away from the first end; , displaying a reduced representation of the first user interface and displaying a reduced representation of a second user interface that was not displayed immediately before detecting the swipe gesture; reducing the size of the reduced representation of the first user interface as the user moves away from an edge of the first user interface;
while displaying both a reduced representation of the first user interface and a reduced representation of the second user interface;
detecting a tap gesture on the touch-sensitive display at a location corresponding to the second user interface;
in response to detecting a tap gesture on the touch-sensitive display at a location corresponding to the second user interface, ceasing display of the first user interface, displaying a representation of the second user interface;
method including. Displaying a scaled-down representation of the first user interface and displaying a scaled-down representation of the second user interface comprises: as the swipe gesture moves away from the first end; 2. The method of claim 1, comprising moving the reduced representation of a user interface and the reduced representation of the second user interface. 3. A method according to claim 1 or 2 , wherein the second user interface is a user interface for an open application. In response to the detection of the swipe gesture,
In accordance with the determination that the swipe gesture satisfies the first criterion, while displaying the reduced representation of the first user interface and the reduced representation of the second user interface, the swipe gesture 4. A method according to any preceding claim, comprising displaying a reduced representation of the third user interface that was not displayed immediately before being detected. 5. A method according to any preceding claim, wherein the first user interface is a home screen with a plurality of application icons. 6. A method according to any preceding claim, wherein the first user interface is a multi-page application launch interface comprising multiple pages of application icons for launching different applications. detecting a second swipe gesture while displaying the first user interface;
In response to detecting the second swipe gesture,
the second swipe gesture in accordance with a determination that the second swipe gesture satisfies second criteria, including a criterion that is met when the second swipe gesture is initiated away from a first edge of the touch-sensitive display; displaying a first page of the multi-page application launch interface that includes a first plurality of application icons; 7. The method of claim 6 , comprising: replacing the display of the second page of the application launch interface. detecting a second swipe gesture while displaying the first user interface;
In response to detecting the second swipe gesture,
in accordance with a determination that the second swipe gesture satisfies search interface display criteria, including criteria that are met when the second swipe gesture is initiated in an area of the touch-sensitive display that does not correspond to the first edge; , replacing at least a portion of the display of the first user interface with a display of a search interface that includes a search input field for inputting search terms . Method described. the first user interface is a multi-page application launch interface including multiple pages of application icons;
the first criterion includes a criterion that is met when the swipe gesture moves in a first predetermined direction on the touch-sensitive display;
the search interface display criteria include criteria that are met when the second swipe gesture moves on the touch-sensitive display in a second predetermined direction different from the first predetermined direction;
Displaying the search interface includes:
translating a set of application icons on a first page of the multi-page application launch interface in the second predetermined direction away from one discrete edge of the touch-sensitive display;
displaying the search input field between the discrete edge of the touch-sensitive display and the set of application icons;
9. The method of claim 8 , comprising: 10. The method of claim 8 or 9 , wherein displaying the search interface comprises ceasing display of at least a subset of application icons on a first page of a multi-page application launch interface. The method further comprises maintaining display of the one or more application icons on the first page of the multi-page application launch interface while displaying the search interface in response to detection of the second swipe gesture. The method according to item 10 . The multi-page application launch interface includes a fixed icon area including a plurality of application icons, the fixed icon area being displayed with a respective page in the plurality of pages of application icons;
10. The method of claim 9 , wherein displaying the search interface in response to detecting the second swipe gesture includes ceasing display of the fixed icon region. detecting a second swipe gesture while displaying the first user interface;
In response to detecting the second swipe gesture,
Criteria that the second swipe gesture satisfies if the second swipe gesture is initiated adjacent a second end of the touch-sensitive display that is different from the first end of the touch-sensitive display. displaying a settings interface including controls for modifying a plurality of device settings according to a determination that the settings interface display criteria are met;
7. A method according to any one of claims 1 to 6 , comprising: An electronic device,
a touch-sensitive display;
one or more processors;
memory and
one or more programs, the one or more programs being stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising: 14. An electronic device comprising instructions for performing the method according to any one of Claims 13 to 14. 14. A computer program comprising instructions, said instructions, when executed by an electronic device having a touch-sensitive display, causing said electronic device to perform a method according to any one of claims 1 to 13 . computer program.

Images