Patent Grant
11861159
This relates generally to electronic devices, including but not limited to electronic devices that provide different operating modes with context-based functionality.
The use of portable electronic devices has increased significantly in recent years. Example portable electronic devices include smart watches, mobile phones, tablets, and laptops.
As portable devices become more integrated into a user's daily activities, the number of functions with which a user regularly interacts grows. One way to manage the growing number of regularly used applications, content, and device settings is to have different operating modes for the device (e.g., a work mode, a home mode, a driving mode, and/or a workout mode) that group together regularly used functions/applications in a tailored user interface for a given mode. However, conventional methods for selecting and interacting with different device modes are tedious and inefficient. In addition, selecting and interacting with different device modes takes longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, there is a need for portable electronic devices with faster, more efficient methods and interfaces for selecting and interacting with different device modes. Such methods and interfaces optionally complement or replace conventional methods for selecting and interacting with different device modes. Such methods and interfaces reduce the number, extent, and/or nature of the inputs from a user and produce a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.
The above deficiencies and other problems associated with user interfaces for portable electronic devices are reduced or eliminated by the disclosed devices. 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 has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and/or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions optionally include image editing, drawing, presenting, word processing, website creating, disk authoring, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music playing, and/or digital video playing. Executable instructions for performing these functions are, optionally, included in a non-transitory computer readable storage medium or other computer program product configured for execution by one or more processors.
In accordance with some embodiments, a method is performed at an electronic device with a display. The method includes: displaying a first mode of a plurality of modes of the device, wherein: the plurality of modes of the device includes the first mode and a second mode; the first mode of the device is active when a first set of time and/or device location criteria are met; and the second mode of the device is active when a second set of time and/or device location criteria, distinct from the first set of time and/or device location criteria, are met; and, while the first set of time and/or device location criteria are met: while the first mode of the device is active, detecting a first input that overrides the first mode of the device; in response to detecting the first input, activating the second mode of the device; after responding to the first input, while the second mode of the device is active, detecting a second input; in response to detecting the second input, performing an operation in the second mode of the device; and, after performing the operation in the second mode of the device, returning to the first mode of the device.
In accordance with some embodiments, a method is performed at an electronic device with a display. The method includes: concurrently displaying a plurality of mode affordances, wherein: the plurality of mode affordances includes a first mode affordance that, when activated, initiates a first mode of the mobile device; the plurality of mode affordances includes a second mode affordance that, when activated, initiates a second mode of the mobile device, distinct from the first mode of the mobile device; and the mobile device is configured to recommend activating a respective mode of the device in accordance with a determination that a respective set of time and/or device location criteria that correspond to the respective mode of the device are met; determining that a first set of time and/or device location criteria that correspond to the first mode of the device are met; in response to determining that the first set of time and/or device location criteria are met, displaying a visual indication that corresponds to a recommendation to activate the first mode of the device; while the first set of time and/or device location criteria are met and the visual indication that corresponds to the recommendation to activate the first mode of the device is displayed, detecting activation of a respective mode affordance in the plurality of concurrently displayed mode affordances; and, in response to detecting activation of the respective mode affordance in the plurality of concurrently displayed mode affordances: ceasing to display the plurality of mode affordances; and activating a mode of the device that corresponds to the respective mode affordance.
In accordance with some embodiments, an electronic device includes a display unit and a processing unit coupled with the display unit. The processing unit is configured to: enable display a first mode of a plurality of modes of the device, wherein: the plurality of modes of the device includes the first mode and a second mode; the first mode of the device is active when a first set of time and/or device location criteria are met; and the second mode of the device is active when a second set of time and/or device location criteria, distinct from the first set of time and/or device location criteria, are met; and, while the first set of time and/or device location criteria are met: while the first mode of the device is active, detect a first input that overrides the first mode of the device; in response to detecting the first input, activate the second mode of the device; after responding to the first input, while the second mode of the device is active, detect a second input; in response to detecting the second input, perform an operation in the second mode of the device; and, after performing the operation in the second mode of the device, return to the first mode of the device.
In accordance with some embodiments, an electronic device includes a display unit and a processing unit coupled with the display unit. The processing unit is configured to: concurrently enable display of a plurality of mode affordances, wherein: the plurality of mode affordances includes a first mode affordance that, when activated, initiates a first mode of the mobile device; the plurality of mode affordances includes a second mode affordance that, when activated, initiates a second mode of the mobile device, distinct from the first mode of the mobile device; and the mobile device is configured to recommend activating a respective mode of the device in accordance with a determination that a respective set of time and/or device location criteria that correspond to the respective mode of the device are met; determine that a first set of time and/or device location criteria that correspond to the first mode of the device are met; in response to determining that the first set of time and/or device location criteria are met, enable display of a visual indication that corresponds to a recommendation to activate the first mode of the device; while the first set of time and/or device location criteria are met and the visual indication that corresponds to the recommendation to activate the first mode of the device is displayed, detect activation of a respective mode affordance in the plurality of concurrently displayed mode affordances; and, in response to detecting activation of the respective mode affordance in the plurality of concurrently displayed mode affordances: cease to display the plurality of mode affordances; and activate a mode of the device that corresponds to the respective mode affordance.
In accordance with some embodiments, an electronic device includes a display, optionally a touch-sensitive surface, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, one or more processors, memory, and one or more programs; the one or more programs are stored in the memory and configured to be executed by the one or more processors and the one or more programs include instructions for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, a computer readable storage medium has stored therein instructions which when executed by an electronic device with a display, optionally a touch-sensitive surface, and optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, cause the device to perform or cause performance of the operations of any of the methods described herein. In accordance with some embodiments, a graphical user interface on an electronic device with a display, optionally a touch-sensitive surface, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, a memory, and one or more processors to execute one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described above, which are updated in response to inputs, as described in any of the methods described herein. In accordance with some embodiments, an electronic device includes: a display, optionally a touch-sensitive surface, and optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface; and means for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a display, optionally a touch-sensitive surface, and optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, includes means for performing or causing performance of the operations of any of the methods described herein.
Thus, electronic devices with displays, optionally touch-sensitive surfaces, and optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface are provided with faster, more efficient methods and interfaces for selecting and interacting with different device modes, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for selecting and interacting with different device modes.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
Many portable electronic devices have a large number of features including applications, controls, and content with which a user engages, as well as settings that impact the functionality of the electronic device. A user may typically use different device features depending on contextual factors such as the time of day and/or the user's location. For example, at home, a user may frequently use applications related to entertainment, media delivery, and home automation, while these applications are less frequently accessed when the user is at work. Applications related to appointment scheduling and communication may play a larger role in device usage while the user is at work, as compared with other contexts. Within a particular communications application, such as a messaging application, a user may wish to view messages from contacts the user associates with a particular setting only when the user is present within that setting. The user may prefer for a device to always establish a connection to a particular network or network type in some contexts, and to connect to that network or network type only on an opt-in basis in other contexts. Device modes are a way to tie device features such as applications, controls, content, and settings to particular contexts (e.g., work, home, driving, or workout). A mobile device may use information such as time and device location to determine a device mode and apply and/or display a particular set of features that are desirable in that device mode. This streamlines access to device features, thereby reducing or eliminating the time spent by a user navigating user interfaces to locate desired features.
Here, improved ways to select device modes and interact with device modes are described.
In some embodiments, the device displays a plurality of mode icons (e.g., on a lock screen or wake screen), and visually highlights the mode icon that corresponds to the mode automatically recommended by the device (e.g., based on time and/or device location criteria), which helps the user to select the proper mode. The user then selects the recommended mode icon or another mode icon to activate the corresponding mode.
In some embodiments, while in a first device mode, the device detects an input that overrides the first mode and activates a second mode. The device performs an operation while in the second mode in response to another input, and then returns to the first mode. This method helps a user to interact with different modes. The user can easily leave a first mode, perform an operation in a second mode, and then return to the first mode.
Below,
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill 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.
It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact, unless the context clearly indicates otherwise.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Example embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch-screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch-screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a note taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user. Using tactile outputs to provide haptic feedback to a user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU(s) 120 and the peripherals interface 118, is, optionally, controlled by memory controller 122.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU(s) 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.
In some embodiments, peripherals interface 118, CPU(s) 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication optionally uses any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSDPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110 speaker 111 and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch-sensitive display system 112 and other input or control devices 116, with peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled with any (or none) of the following: a keyboard, infrared port, USB port, stylus, and/or a pointer device such as a mouse. The one or more buttons (e.g., 208,
Touch-sensitive display system 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch-sensitive display system 112. Touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term “affordance” refers to a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to inputs directed toward the graphical user interface object). Examples of user-interactive graphical user interface objects include, without limitation, a button, slider, icon, selectable menu item, switch, hyperlink, or other user interface control.
Touch-sensitive display system 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic/tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch-sensitive display system 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch-sensitive display system 112. In an example embodiment, a point of contact between touch-sensitive display system 112 and the user corresponds to a finger of the user or a stylus.
Touch-sensitive display system 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch-sensitive display system 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch-sensitive display system 112. In an example embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, California.
Touch-sensitive display system 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen video resolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally makes contact with touch-sensitive display system 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch-sensitive display system 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 163.
Device 100 optionally also includes one or more accelerometers 167, gyroscopes 168, and/or magnetometers 169 (e.g., as part of an inertial measurement unit (IMU)) for obtaining information concerning the position (e.g., attitude) of the device.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, position module (or set of instructions) 131, graphics module (or set of instructions) 132, haptic feedback module (or set of instructions) 133, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 stores device/global internal state 157, as shown in
Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California In some embodiments, the external port is a Lightning connector that is the same as, or similar to and/or compatible with the Lightning connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California.
Contact/motion module 130 optionally detects contact with touch-sensitive display system 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes software components for performing various operations related to detection of contact (e.g., by a finger or by a stylus), such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts or stylus contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts and/or stylus contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event. Similarly, tap, swipe, drag, and other gestures are optionally detected for a stylus by detecting a particular contact pattern for the stylus.
In some embodiments, detecting a finger tap gesture depends on the length of time between detecting the finger-down event and the finger-up event, but is independent of the intensity of the finger contact between detecting the finger-down event and the finger-up event. In some embodiments, a tap gesture is detected in accordance with a determination that the length of time between the finger-down event and the finger-up event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4 or 0.5 seconds), independent of whether the intensity of the finger contact during the tap meets a given intensity threshold (greater than a nominal contact-detection intensity threshold), such as a light press or deep press intensity threshold. Thus, a finger tap gesture can satisfy particular input criteria that do not require that the characteristic intensity of a contact satisfy a given intensity threshold in order for the particular input criteria to be met. For clarity, the finger contact in a tap gesture typically needs to satisfy a nominal contact-detection intensity threshold, below which the contact is not detected, in order for the finger-down event to be detected. A similar analysis applies to detecting a tap gesture by a stylus or other contact. In cases where the device is capable of detecting a finger or stylus contact hovering over a touch sensitive surface, the nominal contact-detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch sensitive surface.
The same concepts apply in an analogous manner to other types of gestures. For example, a swipe gesture, a pinch gesture, a depinch gesture, and/or a long press gesture are optionally detected based on the satisfaction of criteria that are either independent of intensities of contacts included in the gesture, or do not require that contact(s) that perform the gesture reach intensity thresholds in order to be recognized. For example, a swipe gesture is detected based on an amount of movement of one or more contacts; a pinch gesture is detected based on movement of two or more contacts towards each other; a depinch gesture is detected based on movement of two or more contacts away from each other; and a long press gesture is detected based on a duration of the contact on the touch-sensitive surface with less than a threshold amount of movement. As such, the statement that particular gesture recognition criteria do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met means that the particular gesture recognition criteria are capable of being satisfied if the contact(s) in the gesture do not reach the respective intensity threshold, and are also capable of being satisfied in circumstances where one or more of the contacts in the gesture do reach or exceed the respective intensity threshold. In some embodiments, a tap gesture is detected based on a determination that the finger-down and finger-up event are detected within a predefined time period, without regard to whether the contact is above or below the respective intensity threshold during the predefined time period, and a swipe gesture is detected based on a determination that the contact movement is greater than a predefined magnitude, even if the contact is above the respective intensity threshold at the end of the contact movement. Even in implementations where detection of a gesture is influenced by the intensity of contacts performing the gesture (e.g., the device detects a long press more quickly when the intensity of the contact is above an intensity threshold or delays detection of a tap input when the intensity of the contact is higher), the detection of those gestures does not require that the contacts reach a particular intensity threshold so long as the criteria for recognizing the gesture can be met in circumstances where the contact does not reach the particular intensity threshold (e.g., even if the amount of time that it takes to recognize the gesture changes).
Contact intensity thresholds, duration thresholds, and movement thresholds are, in some circumstances, combined in a variety of different combinations in order to create heuristics for distinguishing two or more different gestures directed to the same input element or region so that multiple different interactions with the same input element are enabled to provide a richer set of user interactions and responses. The statement that a particular set of gesture recognition criteria do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met does not preclude the concurrent evaluation of other intensity-dependent gesture recognition criteria to identify other gestures that do have a criteria that is met when a gesture includes a contact with an intensity above the respective intensity threshold. For example, in some circumstances, first gesture recognition criteria for a first gesture—which do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the first gesture recognition criteria to be met—are in competition with second gesture recognition criteria for a second gesture—which are dependent on the contact(s) reaching the respective intensity threshold. In such competitions, the gesture is, optionally, not recognized as meeting the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are met first. For example, if a contact reaches the respective intensity threshold before the contact moves by a predefined amount of movement, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves by the predefined amount of movement before the contact reaches the respective intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such circumstances, the first gesture recognition criteria for the first gesture still do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the first gesture recognition criteria to be met because if the contact stayed below the respective intensity threshold until an end of the gesture (e.g., a swipe gesture with a contact that does not increase to an intensity above the respective intensity threshold), the gesture would have been recognized by the first gesture recognition criteria as a swipe gesture. As such, particular gesture recognition criteria that do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met will (A) in some circumstances ignore the intensity of the contact with respect to the intensity threshold (e.g. for a tap gesture) and/or (B) in some circumstances still be dependent on the intensity of the contact with respect to the intensity threshold in the sense that the particular gesture recognition criteria (e.g., for a long press gesture) will fail if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognize an input as corresponding to an intensity-dependent gesture before the particular gesture recognition criteria recognize a gesture corresponding to the input (e.g., for a long press gesture that is competing with a deep press gesture for recognition).
Position module 131, in conjunction with accelerometers 167, gyroscopes 168, and/or magnetometers 169, optionally detects positional information concerning the device, such as the device's attitude (roll, pitch, and/or yaw) in a particular frame of reference. Position module 130 includes software components for performing various operations related to detecting the position of the device and detecting changes to the position of the device. In some embodiments, position module 131 uses information received from a stylus being used with the device to detect positional information concerning the stylus, such as detecting the positional state of the stylus relative to the device and detecting changes to the positional state of the stylus.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch-sensitive display system 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 163 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts module 137, e-mail module 140, IM module 141, reminder module 142, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone module 138 for use in location-based dialing, to camera module 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, voice replication, meeting information, location sharing, document reader (e.g., book reader), and/or accessory control (e.g., home accessory control).
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 includes executable instructions to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers and/or e-mail addresses to initiate and/or facilitate communications by telephone module 138, video conference module 139, e-mail module 140, or IM module 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110 speaker 111 microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols and technologies.
In conjunction with RF circuitry 108, audio circuitry 110 speaker 111 microphone 113, touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, Apple Push Notification Service (APNs) or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and GPS module 135, reminders module 142 includes executable instructions to set reminders.
In conjunction with touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, and/or delete a still image or video from memory 102.
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 includes executable instructions to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110 speaker 111 RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch-sensitive display system 112, or on an external display connected wirelessly or via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110 speaker 111 RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes executable instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen 112, or on an external display connected wirelessly or via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video.
Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display system 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display system 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 167, gyroscope(s) 168, magnetometer(s) 169, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
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 a sub-event has taken place within one or more views, when touch-sensitive display system 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (i.e., the first sub-event in the sequence of sub-events that form an event or potential event). Once the 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 view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver module 182.
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 stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, 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 the application internal state 192. Alternatively, one or more of the application views 191 includes one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170, and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include 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 corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event 187 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display system 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display system 112, when a touch is detected on touch-sensitive display system 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event 187 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module 145. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 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 a 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 included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input-devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 optionally also includes one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch-screen display.
In some embodiments, device 100 includes the touch-screen display, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In some embodiments, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch-sensitive display system 112 and/or one or more tactile output generators 163 for generating tactile outputs for a user of device 100.
Each of the above identified elements in
Attention is now directed towards embodiments of user interfaces (“UI”) that are, optionally, implemented on portable multifunction device 100.
It should be noted that the icon labels illustrated in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures, etc.), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse based input or a stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
As used herein, the term “focus selector” is an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector,” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact or a stylus contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average or a sum) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be readily accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
In some embodiments, contact/motion module 130 and/or 430 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch-screen display can be set to any of a large range of predefined thresholds values without changing the trackpad or touch-screen display hardware. Additionally, in some embodiments, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
As used in the specification and claims, the term “characteristic intensity” of a contact is a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second intensity threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more intensity thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective option or forgo performing the respective operation) rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact transitioning from a start location and reaching an end location (e.g., a drag gesture), at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location may be based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm may be applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The user interface figures described herein optionally include various intensity diagrams that show the current intensity of the contact on the touch-sensitive surface relative to one or more intensity thresholds (e.g., a contact detection intensity threshold IT0, a light press intensity threshold ITL, a deep press intensity threshold ITD (e.g., that is at least initially higher than IL), and/or one or more other intensity thresholds (e.g., an intensity threshold IH that is lower than IL)). This intensity diagram is typically not part of the displayed user interface, but is provided to aid in the interpretation of the figures. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold IT0 below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
In some embodiments, the response of the device to inputs detected by the device depends on criteria based on the contact intensity during the input. For example, for some “light press” inputs, the intensity of a contact exceeding a first intensity threshold during the input triggers a first response. In some embodiments, the response of the device to inputs detected by the device depends on criteria that include both the contact intensity during the input and time-based criteria. For example, for some “deep press” inputs, the intensity of a contact exceeding a second intensity threshold during the input, greater than the first intensity threshold for a light press, triggers a second response only if a delay time has elapsed between meeting the first intensity threshold and meeting the second intensity threshold. This delay time is typically less than 200 ms in duration (e.g., 40, 100, or 120 ms, depending on the magnitude of the second intensity threshold, with the delay time increasing as the second intensity threshold increases). This delay time helps to avoid accidental deep press inputs. As another example, for some “deep press” inputs, there is a reduced-sensitivity time period that occurs after the time at which the first intensity threshold is met. During the reduced-sensitivity time period, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep press inputs. For other deep press inputs, the response to detection of a deep press input does not depend on time-based criteria.
In some embodiments, one or more of the input intensity thresholds and/or the corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, application running, rate at which the intensity is applied, number of concurrent inputs, user history, environmental factors (e.g., ambient noise), focus selector position, and the like. Example factors are described in U.S. patent application Ser. Nos. 14/399,606 and 14/624,296, which are incorporated by reference herein in their entireties.
For example,
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold ITL to an intensity between the light press intensity threshold ITL and the deep press intensity threshold ITD is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold ITD to an intensity above the deep press intensity threshold ITD is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold IT0 to an intensity between the contact-detection intensity threshold IT0 and the light press intensity threshold ITL is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold IT0 to an intensity below the contact-detection intensity threshold IT0 is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments IT0 is zero. In some embodiments, IT0 is greater than zero. In some illustrations a shaded circle or oval is used to represent intensity of a contact on the touch-sensitive surface. In some illustrations, a circle or oval without shading is used represent a respective contact on the touch-sensitive surface without specifying the intensity of the respective contact.
In some embodiments, described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., the respective operation is performed on a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., the respective operation is performed on an “up stroke” of the respective press input).
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., the respective operation is performed on an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the description of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. As described above, in some embodiment, the triggering of these responses also depends on time-based criteria being met (e.g., a delay time has elapsed between a first intensity threshold being met and a second intensity threshold being met).
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on an electronic device with a display, such as portable multifunction device 100 or device 300.
In some embodiments, in response to receiving input to unlock and/or awaken the device (and/or in response to receiving other input that results in a lock screen being displayed), the device determines a mode of the device, such as a mode of the device that is currently active and/or a mode of the device that is recommended for activation. Determining a mode of the device includes, e.g., determining that time and/or device location criteria for the mode are met. For example, the device determines whether a current time (e.g., 2:40 PM) meets time criteria for the work mode. Time criteria for the work mode include, e.g., one or more time ranges indicating when the device user is typically at work, such as the time range 9:00 AM-1:30 and 2:30-6:00 PM. In accordance with a determination that the current time falls within the time range, the device determines that the work mode is a mode of the device that is recommended for activation. In some embodiments (e.g., when time and/or device location criteria for multiple modes are met), multiple modes are concurrently recommended.
In some embodiments, the device displays a visual indication that corresponds to a recommendation to activate a mode of the device. For example, an area corresponding to mode affordance 5004 is shaded to indicate that the work mode is the recommended mode for activation and/or to visually distinguish mode affordance 5004 from mode affordances 5002 and 5006. The text of mode affordance 5004 is bolded to indicate that the work mode is the recommended mode for activation and/or to visually distinguish text associated with mode affordance 5004 from text associated with mode affordances 5002 and 5006.
In some embodiments, the device displays information associated with a mode of the device that is recommended for activation. The information includes, e.g., one or more information items such as notifications (including, e.g., calendar appointment information, reminder information, e-mail information, telephone call information, message information, stock information, activity information, and/or navigation information, such as currently predicted drive time), content items, content item metadata, application data, and/or graphical items (e.g., icons) indicating a source of the information. The information includes, e.g., one or more information items having a highest priority among the information items of the mode (e.g., determined in accordance with automatic weighting or in accordance with user preference information). For example, information associated with a work mode includes calendar appointment notification 5010. In some embodiments, calendar appointment notification 5010 includes calendar icon 5012. In some embodiments, the information associated with the work mode is displayed at a location corresponding to mode affordance 5004, e.g., a location proximate to mode affordance 5004.
In some embodiments, to activate the recommended mode, a user provides input at a location corresponding to the recommended mode affordance. For example, recommended mode 5004 is activated in response to user input such as a gesture (e.g., a finger tap gesture) detected while a focus selector 5008 is at a location corresponding to the recommended mode affordance 5004.
In some embodiments, a mode interface (e.g., work mode interface 5014) includes information items in addition to a set of currently displayed information items. The additional information items are displayed, e.g., in response to user input (e.g., a vertical drag gesture to reveal information items below or above currently displayed information items and/or a horizontal drag gesture to reveal additional information items to the left or right of currently displayed information items).
In some embodiments, one or more information items of a mode interface are constrained to have a minimum area and/or minimum font size. Larger interface features are provided to improve safety when drive mode interface 5030 is active and/or when the device determines that it is located in a moving vehicle. For example, the font size of navigation instructions 5032, place information affordance 5036, and notification 5046 of drive mode interface 5030 is larger than font sizes used in other mode interfaces such as work mode interface 5014. The area of icons shown in drive mode interface 5030, such as reminders icon 5042, is larger than the area of icons shown in work mode interface 5014, such as reminders icon 5044. In some embodiments, one or more information items (and/or types of information items) are not shown (e.g., not permitted to be shown) when drive mode interface 5030 is active and/or when the device determines that it is located in a moving vehicle. For example, in some embodiments, mode settings affordance 5028 ceases to be shown when the device determines that a vehicle in which the device is located is moving.
In some embodiments, different mode interfaces are configured to display different information originating from the same application. For example, when a reminder application includes reminder 5022 and reminder 5046, reminder 5046 is displayed in drive mode interface 5030 but not in work mode interface 5014, and reminder 5022 is displayed in work mode interface 5014 but not in drive mode interface 5030. A further description of configuring a mode interface to display or to not display a category of reminders is provided below with reference to
In
In some embodiments, in response to user input such as a gesture (e.g., a tap gesture) detected while a focus selector 5078 is at a location of a mode settings affordance 5028, a mode settings interface 5080 is displayed.
In some embodiments, mode settings interface 5080 includes one or more affordances for adjusting network settings (e.g., affordances 5082, 5084, 5086 for enabling and disabling Wi-Fi, Cellular Data, and/or Bluetooth, respectively; affordance 5090 for removing a currently added Wi-Fi network, affordance 5092 for adding one or more Wi-Fi Networks, affordance 5094 for removing a currently added accessory that connects to the device via Bluetooth, and/or affordance 5096 for adding one or more accessories to connect to the device via Bluetooth).
In some embodiments, mode settings interface 5080 includes one or more affordances for adding, modifying, and/or removing application information items. For example, affordance 5098 corresponds to information items 5056, 5058, 5060 and/or 5062 for a video viewer application. In some embodiments, in response to a user input received while a focus selector is at a location corresponding to affordance 5098, information items 5056, 5058, 5060 and 5062 for a video viewer application are removed from home mode interface 5054.
In some embodiments, mode settings interface 5080 includes affordance 5100 that corresponds to home accessory control. For example, to remove a home accessory control region from home mode interface 5054, a user provides input at a location corresponding to affordance 5100. To remove individual controls 5064 or 5066 for controlling home accessory devices, user input is provided at a location corresponding to affordances 5112 or 5113, respectively. To add controls for home accessory devices, user input is provided at a location corresponding to affordance 5114.
Affordances 5102, 5104, 5106, and 5108 are usable to remove application icons 5068, 5070, 5072, and 5074, respectively from home mode interface 5054. For example, to remove weather application icon 5072 from home mode interface 5054, a user provides user input while a focus selector is at weather application removal affordance 5104. Affordance 5110 is usable to remove reminder notification area 5076 from home mode interface 5054. To remove reminders from home mode interface 5054, a user provides user input while a focus selector is at a location that corresponds to reminders removal affordance 5114.
In some embodiments, a mode is configurable to display communications and/or communication notifications from a filtered set of contacts. For example, a user may wish to avoid displaying e-mail from work contacts while the user is at home (e.g., when the home mode is active). In another example, a user wishes to avoid displaying message notifications from personal contacts while the user is at work (e.g., when the work mode is active). In some embodiments, mode settings interface 5080 includes one or more affordances 5116 for removing contacts (and/or groups of contacts) from which messages and/or message notifications are to be displayed while the home mode is active. In some embodiments, mode settings interface 5080 includes an affordance 5118 for adding contacts (and/or groups of contacts) from which messages and/or message notifications are to be displayed while the home mode is active. In some embodiments, application settings such as contact settings for e-mail, phone, calendar, and/or location sharing are configurable (e.g., in mode settings interface 5080) to limit information displayed in a mode to information associated with a limited set of contacts.
In some embodiments, a mode is configurable to display reminders and/or reminder notifications from a filtered set of reminders. For example, a set of reminders are stored in a “Work Reminders” group and a different set of reminders is stored in a “Home Reminders” group. In some embodiments, mode settings interface 5080 includes one or more affordances 5120 for removing a reminder group from which reminders and/or reminder notifications are to be displayed while the home mode is active. In some embodiments, mode settings interface 5080 includes an affordance 5122 for adding a reminder group from which reminders and/or reminder notifications are displayed while the home mode is active.
In some embodiments, mode settings interface 5080 includes one or more affordances 5124, 5126, 5128, 5130 for adding application information items (e.g., application icons, application notification areas, application notifications, and/or application widgets) to home mode interface 5054. For example, to add a view of data from a calendar application to home mode interface 5054 (e.g., similar to view 5016 of data from a calendar application shown in work mode interface 5014), a user provides user input while a focus selector is at a location corresponding to affordance 5124.
In some embodiments, mode settings interface 5080 includes settings affordances in addition to a set of currently displayed settings affordances. The additional settings affordances are displayed, e.g., in response to user input. For example, in some embodiments, in response to a vertical drag gesture, the device reveals settings affordances below or above currently displayed affordances (e.g., settings affordances for the same mode as the currently displayed mode affordances). In some embodiments, in response to a horizontal drag gesture, the device reveals settings affordances to the left or right of currently displayed settings (e.g., settings for different modes).
In some embodiments, mode settings interface 5080 includes an affordance 5146 corresponding to a “Done” option to apply changes (e.g., all changes made using affordances of mode settings interface 5080 since mode settings interface 5080 was displayed). In some embodiments, mode settings interface 5080 includes an affordance 5148 corresponding to a “Cancel” option to cancel changes (e.g., all changes made using affordances of mode settings interface 5080 since mode settings interface 5080 was displayed).
In some embodiments, a mode settings interface 5080 is used to perform an operation in a mode that is not the currently active mode. For example, a user may wish to wrap up a task stored in a work reminders group after the user returns home. While the user is still at work, and the work mode is active, the user can override the work mode to activate the home mode. While the home mode is activated (and the home mode interface 5054 is displayed), the user visits the mode settings interface 5080 and adds the work reminders group to the reminders notifications for the home mode. The device returns to the work mode. Later, when the user is at home and the home mode is active, the work reminder from the work reminders group is displayed in the home mode interface 5054.
A process for performing an operation in an override mode that is not the currently active mode is illustrated in the series of user interfaces of
In some embodiments, as indicated in the series of user interfaces of
In some embodiments, as indicated in the series of user interfaces of
In some embodiments, (e.g., when a user input meets information item movement criteria), a gesture is used to override a current mode, remove the information item from the current mode, activate an alternate mode, and/or add an information item to the alternate mode. In some embodiments, a user input meets information item movement criteria when the duration of a contact with touch screen 112 exceeds a threshold duration. In some embodiments, as explained below with reference to
As shown in
In
In some embodiments, a user input (e.g., received after a characteristic intensity of the detected contact is above an information item movement relocation threshold) is a gesture that moves contact/focus selector 5162 to the left. When the movement to the left exceeds a mode change threshold distance, the gesture overrides the work mode, activates the activity mode, and adds message notification 5020 to an activity mode interface (because the activity mode is the mode preceding the current mode, e.g., as indicated by the location of activity mode affordance 5002 to the left of work mode affordance 5004 in mode affordance chrome 5024). In some embodiments, a user input (e.g., received after a characteristic intensity of the detected contact is above an information item movement relocation threshold) is a gesture that moves contact/focus selector 5162 to the right. When the movement to the right exceeds a mode change threshold distance, the gesture overrides the work mode, activates the drive mode, and adds message notification 5020 to drive mode interface 5030 (because drive mode is the mode following the current mode, e.g., as indicated by the location of drive mode affordance 5006 to the right of work mode affordance 5004 in mode affordance chrome 5024).
In some embodiments, when message notification 5020 is added to another mode, such as an activity mode (e.g., an activity mode interface), a drive mode (e.g., drive mode interface 5030), or a home mode (e.g., home mode interface 5054), message notification 5020 is removed from the work mode (e.g., message notification 5020 is no longer displayed in work mode interface 5014).
As described below, the method 600 provides an intuitive way to interact with different device modes. The method reduces the number, extent, and/or nature of the inputs from a user when changing device modes, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to changing device modes faster and more efficiently conserves power and increases the time between battery charges.
The device (602) displays a first mode of a plurality of modes of the device. Examples of modes are provided below. In some embodiments, a mode is a mode of the entire device (e.g., the mode provides the primary interface for interacting with device features). In some embodiments, a mode is subsidiary to a primary interface for interacting with device features.
The plurality of modes of the device include (604) the first mode and a second mode. In some embodiments, a mode is a state of the device in which a set of operations that are relevant to, e.g., a place, time and/or an activity of the device or its user are performed, available, or otherwise made prominent on the device. For example, icons for applications relevant to a particular mode are displayed concurrently when the mode is active (e.g., application initiation icons 5068, 5070, 5072, and 5074 are displayed concurrently in home mode interface 5054 when the home mode of the device is active, as indicated in
Examples of modes, mode activation criteria, and mode features are described below in Table 1. Time criteria, location criteria, movement criteria, and transit criteria that correspond to the various modes described in Table 1 are explained below.
In some embodiments, time criteria are met when a current time (e.g., determined by the device) is within defined time parameters (e.g., a user input time range, a default time range, and/or an automatically determined time range) for a particular mode (e.g., a mode listed below in Table 1).
In some embodiments, location criteria are met when a current location of the device is within defined location parameters that correspond to a particular mode (e.g., a mode listed below in Table 1). The current location of a device is determined using, e.g., position data determined from GPS, a Wi-Fi network, a location beacon (e.g., iBeacon), and/or Bluetooth pairing (e.g., detecting availability of a Bluetooth connection with a Bluetooth transmitter in a known location, such as an automobile). For example, a device determines that a location criterion is satisfied in response to determining that a current location of the device is within (and/or within a predetermined distance from) a location such as a neighborhood, a city block, an address, a point location, a set of coordinates (e.g. latitude/longitude), and/or another defined boundary (such as a virtual boundary associated with a campus, a building, or a portion of a building). Location parameters are determined, e.g., in accordance with user input (a text and/or map pin entry indicating a location) and/or automatically (e.g., based on data stored by the device, such as a location of the device determined by the device during a typical time frame associated with the mode, data from communications, and/or data from calendar entries). In some embodiments, a device determines that a location criterion is satisfied in response to detecting a signal from a Wi-Fi network that corresponds to a particular mode (e.g., as indicated by a mode settings interface).
In some embodiments, travel criteria are met when a current location of the device does not match a previously defined location, matches a previously defined location for a mode that uses travel criteria, is in a geographic region that is different from the defined home and/or work location (e.g., a different city, state, and/or country), or is beyond a defined distance from a defined home and/or work location.
In some embodiments, movement criteria are met when output from one or more device sensors (e.g., the device accelerometer) indicates a velocity exceeding a predetermined threshold and/or indicates a velocity that falls within a predetermined velocity range. In some embodiments, determining whether device movement meets movement criteria includes determining, at a first time, a first location of the device; determining, at a second time, a second location of the device; determining a distance between the first location of the device and the second location of the device; and, based on a velocity determined from the distance between the first location and the second location divided by the difference between the first time and the second time, determining whether the first movement exceeds a velocity threshold and/or falls within a predetermined velocity range. For example, movement criteria include walking movement criteria (e.g., the velocity exceeds a movement threshold and/or the velocity falls within a range that corresponds to typical walking movement), running movement criteria (e.g., the velocity exceeds a movement threshold and/or the velocity falls within a range that corresponds to typical running movement), bicycling movement criteria (e.g., the velocity exceeds a movement threshold and/or the velocity falls within a range that corresponds to typical bicycling movement), and/or automobile/transit movement criteria (e.g., the velocity exceeds a movement threshold and/or falls within a range that corresponds to typical automobile movement and/or transit movement, such as bus, train, airplane, etc.).
The first mode of the device is active (and, in some embodiments, a first mode interface is displayed) when (606) a first set of time and/or device location criteria are met. For example, the first mode is a “work mode” and the first set of criteria are satisfied when a current time as determined by the device falls within a predefined (e.g., defined by the user) or predetermined (e.g., defined from data collected by the device) time range (e.g., work hours) for a user of the mobile device and/or GPS or other location data for the mobile device indicate that the mobile device is at a predefined or predetermined work location for the user.
For example, in
The second mode of the device is active (and, in some embodiments, a second mode interface is displayed) when (608) a second set of time and/or device location criteria, distinct from the first set of time and/or device location criteria, are met. For example, the second mode is a “home mode” and the second set of criteria are satisfied when a current time as determined by the device falls within predefined or predetermined time range for the home mode and/or GPS or other location data for the mobile device indicate that the mobile device is at a predefined or predetermined location for the home mode.
While the first set of time and/or device location criteria are met (610) (e.g., and the second set of time and/or device location criteria are not met), and while the first mode of the device is active (e.g., and information associated with a mode, such as a mode interface is displayed), the device detects (612) a first input that overrides the first mode of the device. In some embodiments, the first input is, e.g., a voice command or a gesture (e.g., a contact or other input received while a focus selector is at a location corresponding to a mode affordance, such as a “tap” gesture or mouse-click, and/or a user input that moves a focus selector across a display, such a movement of a contact across a touch-sensitive surface in a “swipe” gesture). In response to detecting the first input, the device activates (614) the second mode of the device. In some embodiments, the device displays information associated with a second mode of the device (e.g., a second mode interface) when the device activates the second mode of the device.
For example, in
After responding to the first input, while the second mode of the device is active (and, in some embodiments, while information associated with the second mode is displayed) the device detects (616) a second input, such as an input that corresponds to a request to perform an operation in the second mode of the device. In some embodiments, an input that corresponds to a request to perform an operation includes, e.g., a user input for displaying a mode settings interface 5080, a user input for modifying mode settings (e.g., modifications made using mode settings interface 5080), and/or a user input for applying modifications (e.g., user input received at a location corresponding to affordance 5146 for applying changes made using mode settings interface 5080). In some embodiments, an input that corresponds to a request to perform an operation is, e.g., a user input to move an object from a first mode to a second mode (e.g., as described with regard to
In response to detecting the second input, the device performs (618) an operation in the second mode of the device. For example, the device applies a change made using a mode settings interface 5080 (e.g., when user input is received at a location corresponding to affordance 5146, for applying changes made using mode settings interface 5080 to add a “Work Reminders” group to a reminder notifications area 5076 of home mode interface 5054, as described with regard to
Example operations in the second mode include:
After performing the operation in the second mode of the device, the device returns (620) to (and, in some embodiments, resumes display of) the first mode of the device. For example, after adding a “Work Reminders” group to a reminder notification area 5076 of home mode interface 5054, the device displays work mode interface 5014. In some embodiments, the device returns to the first mode automatically, such as after a predetermined period of time since detecting the second input and/or at a time when the device enters a sleep state. In some embodiments, the device returns to the first mode in response to the second input (e.g., a second input includes input received at affordance 5146 for applying changes made using mode settings interface 5080). For example, in some embodiments, in response to receiving input at affordance 5146 for applying changes made using mode settings interface 5080, the device displays work mode interface 5014 (e.g., rather than displaying home mode interface 5054 as modified by the second input). In some embodiments, the device returns to the first mode in response to a third input (e.g., a tap gesture received at work mode affordance 5004).
In some embodiments, performing the operation in the second mode of the device (e.g., while the first set of time and/or device location criteria are met and the second set of time and/or device location criteria are not met) includes adding (622) an affordance to the second mode of the device. An affordance is, e.g., an application initiation icon (e.g., an application icon 5068, 5070, 5072, 5074 as shown in
In some embodiments, after returning to the first mode of the device, the device determines (624) that the second set of time and/or device location criteria are met and, in response to determining that the second set of time and/or device location criteria are met, the device activates and displays the second mode of the device and the device displays the affordance in the second mode of the device.
For example, the device receives input to override a work mode and activate a home mode, and while the home mode is active, a work mode reminder 5022 is added to home mode interface 5054, as described with regard to
In some embodiments, overriding the first mode includes (626) ceasing to display the first mode of the device and displaying the second mode of the device. For example, overriding the first mode, as described with regard to
In some embodiments, second mode settings are implemented after the second mode has been displayed for a predetermined period of time (e.g., a predetermined period of time after the first input is received, after the second mode interface is displayed, and/or after the second input is received). For example, the user provides input to override the work mode with the home mode. After a predetermined period of time (e.g., during which the user does not provide subsequent input to return to the work mode), the device applies the home mode settings.
In some embodiments, a respective mode of the plurality of modes includes (628) one or more affordances. The one or more affordances includes an application affordance (e.g., application initiation icons 5068, 5070, 5072, 5074, as shown in
In some embodiments, performing the operation in the second mode of the device includes (630) modifying a setting for a parameter (e.g., a permission setting for an application and/or an access setting for a communication type, a contact, or a user; a privacy setting; or a network setting) in the second mode of the device. For example, mode interface 5080 as shown in
In some embodiments, after returning to the first mode of the device, the device determines (632) that the second set of time and/or device location criteria are met and, in response to determining that the second set of time and/or location criteria are met, the device initiates the second mode of the device and applies the setting to the parameter of the device.
For example, the device receives input to override a work mode and activate a home mode, as described with regard to
In some embodiments, overriding the first mode includes (634) applying the setting to the parameter of the device in the second mode. For example, network settings of the home mode indicate that Wi-Fi connectivity is enabled for the home mode. When the device overrides a work mode and activates the home mode (e.g., in response to receiving input to activate the home mode), the device enables Wi-Fi connectivity (e.g., if Wi-Fi connectivity is not already enabled).
In some embodiments, returning to the first mode of the device includes (636) automatically returning to the first mode of the device after a predetermined period of time. In some embodiments, returning to the first mode of the device includes automatically returning to the first mode of the device after the second mode of the device has been active for the predetermined period of time. In some embodiments, returning to the first mode of the device includes automatically returning to the first mode of the device after a predetermined period of time since a user input (e.g., the first user input or the second user input) was received by the device. In some embodiments, returning to the first mode of the device includes automatically returning to the first mode of the device after a predetermined period of time since a change was made to the second mode.
In some embodiments, while the second mode is active (and the first mode is overridden), the device detects (638) a third input (e.g., a voice command and/or a gesture); and, in response to detecting the third input, the device re-activates the first mode of the device. In some embodiments, re-activating the first mode of the device includes displaying a first mode interface (e.g., work mode interface 5014). For example, while the home mode is active and home mode interface 5054 is displayed (e.g., in response to a first input received to override a home mode, as described with regard to
In some embodiments, detecting the first input (that overrides the first mode of the device) includes (640) detecting a gesture at a location corresponding to a mode selection affordance. The gesture is, e.g., a tap gesture, a swipe gesture, a drag gesture, a contact that has a characteristic intensity above a threshold intensity level, and/or a combination of these. For example, a first input includes a tap gesture received while a contact/focus selector 5052 is at a location corresponding to home mode affordance 5026 to override a work mode and activate a home mode, as described with regard to
In some embodiments, the device includes a touch-sensitive surface 112 and one or more sensors for detecting intensities of contacts on the touch-sensitive surface. While a focus selector is at a location of a mode selection affordance, the device detects (642) an increase in a characteristic intensity of the contact on the touch-sensitive surface 112 above a mode display intensity threshold and, in response to detecting the increase in the characteristic intensity of the contact above the mode display intensity threshold, the device displays a plurality of mode affordances that correspond to at least a subset of the plurality of modes (e.g., as a scrollable list) of the device. For example, a contact with touch-sensitive surface 112 is detected while a focus selector 5152 is at a location of mode affordance chrome 5024, as indicated in
In some embodiments, detecting the first input (that overrides the first mode of the device) includes receiving a selection of a mode affordance that corresponds to the second mode (e.g., from mode selection interface 5158). For example, detecting the first input includes detecting a contact/focus selector 5160 at a location corresponding to home mode affordance 5026, as indicated at
In some embodiments, the mode selection is received when, after the increase in the characteristic intensity above the mode display intensity threshold is detected, a decrease in the characteristic intensity is detected, followed by a subsequent increase above the mode display intensity threshold. For example, detecting the first input includes detecting a subsequent increase in a characteristic intensity of the contact while focus selector 5160 is at a location corresponding to home mode affordance 5026.
In some embodiments, detecting the first input (that overrides the first mode of the device) includes detecting an increase in the characteristic intensity of the contact on the touch-sensitive surface above a mode selection intensity threshold (e.g., a light press intensity threshold ITL, as indicated by intensity meter 5156, or another intensity threshold) when a focus selector is at an indication of the second mode. For example, in response to detecting an increase in the characteristic intensity of the contact on the touch-sensitive surface above a mode selection intensity threshold when a focus selector 5152 is at a location of activity mode affordance 5002, an activity mode of the device is activated (and, in some embodiments, an activity mode interface is displayed).
In some embodiments (644), the first mode is a work mode (e.g., as indicated by work mode interface 5014) and the second mode is a home mode (e.g., as indicated by home mode interface 5054).
In some embodiments, the first set of time and/or device location criteria are met when (646) at least one of a work time criterion or a work location criterion is satisfied.
In some embodiments, a work time criterion is satisfied when a current time (e.g., determined by the device, e.g., according to a device clock) is within work time parameters. Work time parameters are, e.g., a user input time range (e.g., input via a calendar application), a default time range, and/or an automatically determined time range. A work time range is determined automatically, for example, based on a time range during which a user is typically at a work location (e.g., a work location indicated by the user or a location at which the device is located during a typical work time range). A time range during which a user is typically at a work location is determined, for example, based on data stored by the device, such as a location of the device determined (using GPS, Wi-Fi or other location information) during a typical work time frame, data from calendar entries, and/or data from communications.
In some embodiments, a work location criterion is satisfied when a current location of the device (e.g., a location indicated by positioning data such as positioning data determined from GPS, Wi-Fi network, location beacon (e.g., iBeacon), and/or Bluetooth pairing) is within work location parameters. For example, a device determines that a location criterion is satisfied in response to determining that a current location of the device is within (and/or within a predetermined distance from) a location such as a neighborhood, a city block, an address, a point location, and/or a set of coordinates (e.g. latitude/longitude). Location parameters are determined, e.g., in accordance with user input (a text and/or map pin entry indicating a location) and/or automatically (e.g., based on data stored by the device, such as a location of the device determined by the device during a typical work time frame, data from communications, and/or data from calendar entries). In some embodiments, a device determines that a work location criterion is satisfied in response to detecting a signal from a Wi-Fi network of the work mode (e.g., as indicated by a mode settings interface).
It should be understood that the particular order in which the operations in
The operations described above with reference to
As described below, the method 700 provides an intuitive way to recommend and activate a device mode from among a plurality of displayed mode affordances. The method reduces the number, extent, and/or nature of the inputs from a user when selecting and activating a mode, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to select and activate a mode faster and more efficiently conserves power and increases the time between battery charges.
The device concurrently displays (702) a plurality of mode affordances (e.g., user-activatable icons that correspond to respective modes of the mobile device, such as icons that display thumbnail images of the user interfaces for the respective modes of the mobile device). In some embodiments, the device concurrently displays the plurality of mode affordances on a lock screen. For example, as shown in
The plurality of mode affordances includes (704) a first mode affordance that, when activated, initiates a first mode of the mobile device. For example, work mode affordance 5004, when activated (e.g., in response to a user input received when a focus selector 5008 is at a location corresponding to work mode affordance 5004), initiates a work mode of the device and, in some embodiments, displays a work mode interface 5014, as described with regard to
The plurality of mode affordances includes (706) a second mode affordance that, when activated, initiates a second mode of the mobile device, distinct from the first mode of the mobile device. For example, drive mode affordance 5006, when activated (e.g., in response to a user input received when a focus selector 5008 is at a location corresponding to drive mode affordance 5006), initiates a drive mode of the device and, in some embodiments, displays a drive mode interface 5030, as described with regard to
The device is configured to recommend (708) activating a respective mode of the device in accordance with a determination that a respective set of time and/or device location criteria that correspond to the respective mode of the device are met. For example, in
In some embodiments, the device determines (710) that a first set of time and/or device location criteria that correspond to the first mode of the device are met. For example, the device determines that a first set of time and/or device location criteria that correspond to the work mode of the device are met, e.g., as described with regard to (646) above.
In response to determining that the first set of time and/or device location criteria are met, the device displays (712) a visual indication that corresponds to a recommendation to activate the first mode of the device. In some embodiments, the first mode of the device is recommended for activation by visually distinguishing the first mode affordance from the other mode affordances in the plurality of mode affordances (e.g., by highlighting the first mode affordance, enlarging the first mode affordance and/or altering displayed text of the first mode affordance). For example, in
While the first set of time and/or device location criteria are met and the visual indication that corresponds to the recommendation to activate the first mode of the device is displayed, the device detects (714) activation of a respective mode affordance in the plurality of concurrently displayed mode affordances. For example, the device detects activation of a work mode (e.g., the device detects a user input received when a focus selector 5008 is at a location corresponding to work mode affordance 5004), as described with regard to
In response to detecting activation of the respective mode affordance in the plurality of concurrently displayed mode affordances, the device (716) ceases to display the plurality of mode affordances and activates a mode of the device that corresponds to the respective mode affordance. For example, in response to detecting a user input received when a focus selector 5008 is at a location corresponding to work mode affordance 5004, the device ceases to display the plurality of mode affordances 5002, 5004, and 5006, as shown in
In some embodiments, displaying the visual indication that corresponds to the recommendation to activate the first mode of the device, in response to determining that the first set of time and/or device location criteria are met, occurs (718) while maintaining concurrent display of the plurality of mode affordances. For example, in
In some embodiments, in accordance with a determination that the respective mode is a vehicle operation mode, a displayed area of at least one affordance is increased (720) from a default area to a vehicle operation mode area that is larger than the default area. For example, in
In some embodiments, detecting activation of the respective mode affordance includes (722) detecting a gesture at a location of the respective mode affordance. The gesture is, e.g., a tap gesture, a swipe gesture, a drag gesture, a contact that has a characteristic intensity above a threshold intensity level, and/or a combination of these. For example, detecting activation of work mode affordance 5004 includes detecting a tap gesture received while a focus selector 5008 is at a location corresponding to work mode affordance 5004, as described with regard to
In some embodiments, the device includes (724) a microphone (e.g., microphone 113) and detecting activation of the respective mode affordance includes detecting a voice command that indicates the respective mode affordance. For example, a drive mode of the device is activated in response to a detected voice command (e.g., a voice command including a particular word or phrase, such as the word “drive” or the phrase “drive mode”).
In some embodiments, determining whether the first set of time and/or device location criteria are met includes (726) determining a current time at the device (e.g., according to a device clock) and determining whether the current time is within time parameters for the first mode. In accordance with a determination that the current time is within the time parameters for the first mode (e.g., the current time is within the block of time), the device determines that the first set of time and/or device location criteria are met. Time parameters for the first mode are, e.g., a user input block of time (e.g., input via a calendar application), a default block of time, and/or an automatically determined block of time. A block of time for a mode is determined automatically, for example, based on a time range during which a user is typically at a location associated with the mode (e.g., a location indicated by the user).
In some embodiments, determining whether the first set of time and/or device location criteria are met includes (728) determining a current location of the device (e.g., a location indicated by positioning data such as positioning data determined from data acquired by a GPS module and/or Wi-Fi component of the device), and determining whether the current location is within location parameters for the first mode. Determining whether the current location is within location parameters for the first mode, includes, e.g., determining whether the current location is within (or within a predetermined distance from) a designated location such as a neighborhood, a city block, an address, a point location (e.g., designated with a pin on a map), and/or a set of coordinates (e.g. latitude/longitude). In some embodiments, the location is determined automatically or in accordance with user input. In some embodiments, in accordance with a determination that the current location is within the location parameters for the first mode, the device determines that the first set of time and/or device location criteria are met. For example, the device detects a signal produced by Wi-Fi network 5090 (“Hal”) that is associated with a home mode, as indicated in
In some embodiments, determining whether the first set of time and/or device location criteria are met includes (730) determining whether device movement meets movement criteria. For example, in some embodiments, an “on-the-go” mode is activated in response to a determination that device movement meets movement criteria. In some embodiments, movement criteria are met when output from the device accelerometer indicates a velocity exceeding a predetermined threshold. In some embodiments, determining whether device movement meets movement criteria includes determining, at a first time, a first location of the device; determining, at a second time, a second location of the device; determining a distance between the first location of the device and the second location of the device; and, based on the distance between the first location and the second location, determining that the first set of time and/or device location criteria are met.
In some embodiments, one or more features of a mode are user-configured. In some embodiments, the device automatically adds features to (and/or removes features from) a mode, e.g., based on typical usage. For example, the device automatically adds an application icon to home mode interface 5054 for an application that is frequently used when time and/or location criteria for the home mode are met.
In some embodiments, data from modes (e.g., an amount of time during which the mode has been active) is exposed for use by applications of the device and/or an operating system of the device. In some embodiments, information identifying a current mode of the device is available and/or communicated to applications (e.g., third party applications) of the device. In some embodiments, mode interfaces are generated based on user data for the user of the device and/or data about usage of the device.)
It should be understood that the particular order in which the operations in
The operations described above with reference to
In accordance with some embodiments,
As shown in
In some embodiments, the processing unit 804 is configured to: enable display (e.g., with display enabling unit 806) a first mode of a plurality of modes of the device, wherein: the plurality of modes of the device includes the first mode and a second mode; the first mode of the device is active when a first set of time and/or device location criteria are met; and the second mode of the device is active when a second set of time and/or device location criteria, distinct from the first set of time and/or device location criteria, are met; and, while the first set of time and/or device location criteria are met: while the first mode of the device is active, detect (e.g., with detecting unit 808) a first input that overrides the first mode of the device; in response to detecting the first input, activate (e.g., with activating unit 810) the second mode of the device; after responding to the first input, while the second mode of the device is active, detect (e.g., with detecting unit 808) a second input; in response to detecting the second input, perform (e.g., with performing unit 812) an operation in the second mode of the device; and, after performing the operation in the second mode of the device, return (e.g., with returning unit 814) to the first mode of the device.
In some embodiments, performing the operation in the second mode of the device includes adding (e.g., with adding unit 816) an affordance to the second mode of the device.
In some embodiments, the processing unit 804 is configured to: after returning to the first mode of the device, determine (e.g., with determining unit 818) that the second set of time and/or device location criteria are met; and, in response to determining that the second set of time and/or device location criteria are met: activate (e.g., with activating unit 810) and enable display (e.g., with display enabling unit 806) of the second mode of the device; and enable display (e.g., with display enabling unit 806) of the affordance in the second mode of the device.
In some embodiments, overriding the first mode includes ceasing (e.g., with ceasing unit 820) to display the first mode of the device and enabling display of the second mode of the device.
In some embodiments, a respective mode of the plurality of modes includes one or more affordances, and the one or more affordances includes: an application affordance that, when activated, initiates (e.g., with initiating unit 822) an application; a media affordance, that, when activated, initiates (e.g., with initiating unit 822) playback of content; a control affordance, that, when activated, initiates (e.g., with initiating unit 822) a function; and/or an information affordance that displays information.
In some embodiments, performing the operation in the second mode of the device includes modifying (e.g., with modifying unit 824) a setting for a parameter in the second mode of the device.
In some embodiments, the processing unit 804 is configured to: after returning to the first mode of the device, determine (e.g., with determining unit 818) that that the second set of time and/or device location criteria are met; and in response to determining that the second set of time and/or location criteria are met: initiate (e.g., with initiating unit 822) the second mode of the device; and, apply (e.g., with applying unit 826) the setting to the parameter of the device.
In some embodiments, overriding the first mode includes applying (e.g., with applying unit 826) the setting to the parameter of the device in the second mode.
In some embodiments, returning to the first mode of the device includes automatically returning (e.g., with returning unit 814) to the first mode of the device after a predetermined period of time.
In some embodiments, the processing unit 804 is configured to: while the second mode is active, detect (e.g., with detecting unit 808) a third input; and, in response to detecting the third input, re-activate (e.g., with activating unit 810) the first mode of the device.
In some embodiments, detecting the first input includes detecting a gesture at a mode selection affordance.
In some embodiments, the electronic device 800 includes a touch-sensitive surface unit 828 (e.g., coupled with the processing unit 804) configured to receive contacts and one or more sensor units 830 (e.g., coupled with the processing unit 804) for detecting intensity of contacts on the touch-sensitive surface unit 828. The processing unit 804 is configured to: while a focus selector is at a location of a mode selection affordance, detecting (e.g., with detecting unit 808) an increase in a characteristic intensity of the contact on the touch-sensitive surface unit 828 above a mode display intensity threshold; and, in response to detecting the increase in the characteristic intensity of the contact above the mode display intensity threshold, enable display (e.g., with display enabling unit 806) of a plurality of mode affordances that correspond to at least a subset of the plurality of modes of the device; wherein detecting the first input includes receiving a selection of a mode affordance that corresponds to the second mode.
In some embodiments, the first mode is a work mode and the second mode is a home mode.
In some embodiments, the first set of time and/or device location criteria are met when at least one of a work time criterion or a work location criterion is satisfied, a work time criterion is satisfied when a current time is within work time parameters; and
In accordance with some embodiments,
As shown in
The processing unit 904 is configured to concurrently enable display (e.g., with display enabling unit 906) of a plurality of mode affordances, wherein the plurality of mode affordances includes a first mode affordance that, when activated, initiates a first mode of the mobile device; the plurality of mode affordances includes a second mode affordance that, when activated, initiates a second mode of the mobile device, distinct from the first mode of the mobile device; and the mobile device is configured to recommend activating a respective mode of the device in accordance with a determination that a respective set of time and/or device location criteria that correspond to the respective mode of the device are met; determine (e.g., with determining unit 908) that a first set of time and/or device location criteria that correspond to the first mode of the device are met; in response to determining that the first set of time and/or device location criteria are met, enable display (e.g., with display enabling unit 906) of a visual indication that corresponds to a recommendation to activate the first mode of the device; while the first set of time and/or device location criteria are met and the visual indication that corresponds to the recommendation to activate the first mode of the device is displayed, detect (e.g., with detecting unit 910) activation of a respective mode affordance in the plurality of concurrently displayed mode affordances; and, in response to detecting activation of the respective mode affordance in the plurality of concurrently displayed mode affordances: cease (e.g., with ceasing unit 912) to display the plurality of mode affordances; and activate (e.g., with activating unit 914) a mode of the device that corresponds to the respective mode affordance.
In some embodiments, enabling display of the visual indication that corresponds to the recommendation to activate the first mode of the device, in response to determining that the first set of time and/or device location criteria are met, occurs while maintaining concurrent display of the plurality of mode affordances.
In some embodiments, in accordance with a determination that the respective mode is a vehicle operation mode, a displayed area of at least one affordance is increased from a default area to a vehicle operation mode area that is larger than the default area.
In some embodiments, detecting activation of the respective mode affordance includes detecting a gesture at a location of the respective mode affordance.
In some embodiments, the electronic device 900 includes a microphone unit 916 (e.g., coupled with processing unit 904); and detecting activation of the respective mode affordance includes detecting a voice command that indicates the respective mode affordance.
In some embodiments, determining whether the first set of time and/or device location criteria are met includes: determining a current time at the device, and determining whether the current time is within time parameters for the first mode; and in accordance with a determination that the current time is within the time parameters for the first mode, determine (e.g., with determining unit 908) that the first set of time and/or device location criteria are met.
In some embodiments, determining whether the first set of time and/or device location criteria are met includes: determining a current location of the device, and determining whether the current location is within location parameters for the first mode; and in accordance with a determination that the current location is within the location parameters for the first mode, determine (e.g., with determining unit 908) that the first set of time and/or device location criteria are met.
In some embodiments, determining whether the first set of time and/or device location criteria are met includes determining whether device movement meets movement criteria.
The operations in the information processing methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best use the invention and various described embodiments with various modifications as are suited to the particular use contemplated.
This application is a continuation of U.S. application Ser. No. 17/112,883, filed Dec. 4, 2020, which is a continuation of U.S. application Ser. No. 16/730,921, filed Dec. 30, 2019, now U.S. Pat. No. 10,860,207, which is a continuation of U.S. application Ser. No. 15/707,757, filed Sep. 18, 2017, now U.S. Pat. No. 10,521,107, which claims priority to U.S. Provisional Application Ser. No. 62/399,394, filed Sep. 24, 2016, each of which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 8218403 | Scott et al. | Jul 2012 | B2 |
| 8477566 | Lazaridis et al. | Jul 2013 | B2 |
| 8553502 | Lazaridis et al. | Oct 2013 | B2 |
| 8768648 | Panther et al. | Jul 2014 | B2 |
| 9406103 | Gray et al. | Aug 2016 | B1 |
| 9461833 | Marra et al. | Oct 2016 | B1 |
| 9541986 | Rohrweck | Jan 2017 | B2 |
| 9590942 | Yeskel et al. | Mar 2017 | B1 |
| 9693311 | Cardozo et al. | Jun 2017 | B2 |
| 9808185 | Arnold et al. | Nov 2017 | B2 |
| 9847999 | Van Os et al. | Dec 2017 | B2 |
| 10055634 | Han et al. | Aug 2018 | B2 |
| 10114534 | Kasterstein et al. | Oct 2018 | B2 |
| 10198073 | Chaudhri et al. | Feb 2019 | B2 |
| 10228815 | Forstall et al. | Mar 2019 | B2 |
| 10261475 | Kahn et al. | Apr 2019 | B1 |
| 10296128 | Nold et al. | May 2019 | B1 |
| 10311745 | Arnold et al. | Jun 2019 | B2 |
| 10334054 | Van Os et al. | Jun 2019 | B2 |
| 10338773 | Murarka et al. | Jul 2019 | B2 |
| 10410035 | Han | Sep 2019 | B2 |
| 10521107 | van Os | Dec 2019 | B2 |
| 10860207 | van Os | Dec 2020 | B2 |
| 11137904 | Tyler | Oct 2021 | B1 |
| 11354034 | van Os | Jun 2022 | B2 |
| 20020078393 | Parker | Jun 2002 | A1 |
| 20030236935 | Amemiya et al. | Dec 2003 | A1 |
| 20050120306 | Klassen et al. | Jun 2005 | A1 |
| 20050154935 | Jin | Jul 2005 | A1 |
| 20050249023 | Bodlaender | Nov 2005 | A1 |
| 20060116178 | Vuong et al. | Jun 2006 | A1 |
| 20070150842 | Chaudhri et al. | Jun 2007 | A1 |
| 20070211877 | Martin et al. | Sep 2007 | A1 |
| 20070268784 | Xu | Nov 2007 | A1 |
| 20090143062 | Skinner et al. | Jun 2009 | A1 |
| 20090143114 | Vargas et al. | Jun 2009 | A1 |
| 20090284389 | Klassen et al. | Nov 2009 | A1 |
| 20090284482 | Chin | Nov 2009 | A1 |
| 20100295789 | Shin et al. | Nov 2010 | A1 |
| 20110119630 | Stroupe et al. | May 2011 | A1 |
| 20110231499 | Stovecek et al. | Sep 2011 | A1 |
| 20110283241 | Miller et al. | Nov 2011 | A1 |
| 20120112908 | Prykari et al. | May 2012 | A1 |
| 20120157165 | Kim et al. | Jun 2012 | A1 |
| 20120233563 | Chakra et al. | Sep 2012 | A1 |
| 20120252426 | Nagaoka et al. | Oct 2012 | A1 |
| 20120311466 | Kluttz et al. | Dec 2012 | A1 |
| 20130024799 | Fadell et al. | Jan 2013 | A1 |
| 20130029729 | Logan et al. | Jan 2013 | A1 |
| 20130100044 | Zhao et al. | Apr 2013 | A1 |
| 20130190032 | Li | Jul 2013 | A1 |
| 20130290757 | Barlow et al. | Oct 2013 | A1 |
| 20130332721 | Chaudhri et al. | Dec 2013 | A1 |
| 20130346408 | Duarte et al. | Dec 2013 | A1 |
| 20140055388 | Yook et al. | Feb 2014 | A1 |
| 20140068755 | King et al. | Mar 2014 | A1 |
| 20140106821 | Nakahara | Apr 2014 | A1 |
| 20140172996 | Deeter et al. | Jun 2014 | A1 |
| 20140232671 | Chaudhri | Aug 2014 | A1 |
| 20140245202 | Yoon et al. | Aug 2014 | A1 |
| 20140282174 | Dempski | Sep 2014 | A1 |
| 20140283142 | Shepherd et al. | Sep 2014 | A1 |
| 20140365919 | Shaw et al. | Dec 2014 | A1 |
| 20150067365 | Nakazima et al. | Mar 2015 | A1 |
| 20150094120 | Suh et al. | Apr 2015 | A1 |
| 20150186517 | Gilad et al. | Jul 2015 | A1 |
| 20150195789 | Yoon et al. | Jul 2015 | A1 |
| 20150253894 | McKenzie et al. | Sep 2015 | A1 |
| 20150261423 | Beaumont et al. | Sep 2015 | A1 |
| 20160005290 | Takahashi | Jan 2016 | A1 |
| 20160022202 | Peterson et al. | Jan 2016 | A1 |
| 20160034695 | Won et al. | Feb 2016 | A1 |
| 20160065708 | Yang et al. | Mar 2016 | A1 |
| 20160077724 | Lee et al. | Mar 2016 | A1 |
| 20160124579 | Tokutake | May 2016 | A1 |
| 20160154549 | Chaudhri et al. | Jun 2016 | A1 |
| 20160235359 | Cho et al. | Aug 2016 | A1 |
| 20160248865 | Dotan-Cohen et al. | Aug 2016 | A1 |
| 20160255188 | Chaudhri et al. | Sep 2016 | A1 |
| 20160292994 | Grimme et al. | Oct 2016 | A1 |
| 20160337299 | Lane et al. | Nov 2016 | A1 |
| 20160357394 | Tae et al. | Dec 2016 | A1 |
| 20170011210 | Cheong et al. | Jan 2017 | A1 |
| 20170099602 | Joo et al. | Apr 2017 | A1 |
| 20170118162 | Ratiu et al. | Apr 2017 | A1 |
| 20170126609 | Sharifi et al. | May 2017 | A1 |
| 20170127009 | Friedrich | May 2017 | A1 |
| 20170127967 | Garcia Molina et al. | May 2017 | A1 |
| 20170185275 | Ziegler et al. | Jun 2017 | A1 |
| 20170189641 | Moturu et al. | Jul 2017 | A1 |
| 20170228114 | Brett et al. | Aug 2017 | A1 |
| 20170302609 | Vardhan et al. | Oct 2017 | A1 |
| 20170347946 | Arnold et al. | Dec 2017 | A1 |
| 20170347949 | Arnold et al. | Dec 2017 | A1 |
| 20170352287 | Arnold et al. | Dec 2017 | A1 |
| 20170357217 | Raymann et al. | Dec 2017 | A1 |
| 20170357419 | Raymann et al. | Dec 2017 | A1 |
| 20170357439 | Lemay et al. | Dec 2017 | A1 |
| 20180032220 | Anzures et al. | Feb 2018 | A1 |
| 20180074693 | Jones et al. | Mar 2018 | A1 |
| 20180088787 | Bereza et al. | Mar 2018 | A1 |
| 20180088795 | Van Os et al. | Mar 2018 | A1 |
| 20180088797 | Mcatee et al. | Mar 2018 | A1 |
| 20180101297 | Yang et al. | Apr 2018 | A1 |
| 20180109629 | Van Os et al. | Apr 2018 | A1 |
| 20180121409 | Karunamuni et al. | May 2018 | A1 |
| 20180164973 | Kim et al. | Jun 2018 | A1 |
| 20180173928 | Han | Jun 2018 | A1 |
| 20180188925 | Na et al. | Jul 2018 | A1 |
| 20180188935 | Singh et al. | Jul 2018 | A1 |
| 20180225945 | Moravek et al. | Aug 2018 | A1 |
| 20180226055 | Raymann et al. | Aug 2018 | A1 |
| 20180227377 | Trivedi et al. | Aug 2018 | A1 |
| 20180267593 | Ramasamy et al. | Sep 2018 | A1 |
| 20180336530 | Johnson et al. | Nov 2018 | A1 |
| 20190097957 | Phanshikar et al. | Mar 2019 | A1 |
| 20190150854 | Chung et al. | May 2019 | A1 |
| 20190179493 | Goenka et al. | Jun 2019 | A1 |
| 20190213060 | Raymann et al. | Jul 2019 | A1 |
| 20190278901 | Lewis | Sep 2019 | A1 |
| 20190289079 | Van Os et al. | Sep 2019 | A1 |
| 20190318608 | Rao et al. | Oct 2019 | A1 |
| 20190342251 | Dascola et al. | Nov 2019 | A1 |
| 20190342252 | Dascola et al. | Nov 2019 | A1 |
| 20190342447 | Ko et al. | Nov 2019 | A1 |
| 20190361714 | Rothkopf | Nov 2019 | A1 |
| 20200012423 | Cinek et al. | Jan 2020 | A1 |
| 20200098300 | Verma et al. | Mar 2020 | A1 |
| 20200120201 | Siritzky | Apr 2020 | A1 |
| 20200133477 | Van Os et al. | Apr 2020 | A1 |
| 20200228616 | Nishikawa et al. | Jul 2020 | A1 |
| 20210051226 | Ko et al. | Feb 2021 | A1 |
| 20210060429 | Juenger et al. | Mar 2021 | A1 |
| 20210122469 | Wu | Apr 2021 | A1 |
| 20210173664 | Bai et al. | Jun 2021 | A1 |
| 20210216201 | Van Os et al. | Jul 2021 | A1 |
| 20210349617 | Crowley et al. | Nov 2021 | A1 |
| 20210349618 | Crowley et al. | Nov 2021 | A1 |
| 20210349619 | Crowley et al. | Nov 2021 | A1 |
| 20220365640 | Graham et al. | Nov 2022 | A1 |
| 20230035905 | Dascola et al. | Feb 2023 | A1 |
| 20230161470 | Crowley et al. | May 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 2019100493 | Jun 2019 | AU |
| 102841755 | Dec 2012 | CN |
| 103297939 | Sep 2013 | CN |
| 103514416 | Jan 2014 | CN |
| 106022062 | Oct 2016 | CN |
| 106250133 | Dec 2016 | CN |
| 106462358 | Feb 2017 | CN |
| 107491257 | Dec 2017 | CN |
| 107968885 | Apr 2018 | CN |
| 3 312 713 | Apr 2018 | EP |
| H10-106344 | Apr 1998 | JP |
| 2011-509541 | Mar 2011 | JP |
| 4860505 | Jan 2012 | JP |
| 2015-045902 | Mar 2015 | JP |
| 2015-188275 | Oct 2015 | JP |
| 2016-105630 | Jun 2016 | JP |
| 2017-126067 | Jul 2017 | JP |
| 2017-208112 | Nov 2017 | JP |
| 2018-185830 | Nov 2018 | JP |
| 2019-111181 | Jul 2019 | JP |
| WO 2013184530 | Dec 2013 | WO |
| WO 2016200584 | Dec 2016 | WO |
| WO 2017027526 | Feb 2017 | WO |
| WO 2017052043 | Mar 2017 | WO |
| WO 2018191972 | Oct 2018 | WO |
| WO 2019217020 | Nov 2019 | WO |
| Entry |
|---|
| Office Action, dated Jul. 13, 2020, received in U.S. Appl. No. 16/730,921, 7 pages. |
| Notice of Allowance, dated Jul. 29, 2020, received in U.S. Appl. No. 16/730,921, 8 pages. |
| Amadeo, “Twitter Post [online]”, https://twitter.com/ronamadeo/status/972152445848694789, Mar. 9, 2018, 2 pages. |
| Anonymous, “Create a Group of Notifications / Android Developers”, https://web.archive.org/20181028202552/https://devloper.android.com/training/notif-user/group, Oct. 27, 2018, 5 pages. |
| Apple, “iPhone User Guide for iOS 7.1 Software”, https://manuals.info.apple.com/en_US/iphone_ios7_user_guide.pdf, Mar. 10, 2014, 162 pages. |
| Apple, “Stay Focused While Driving with iPhone”, https://support.apple.com/guide/iphone/turn-on-do-not-disturb-while-driving-iphae754533b/ios#:˜:text=Send%20an%20auto%2Dreply%20text%20message%20that%20you're%20driving&text=Go%20to%20Settings%20%3E%20Do%20Not%20Disturb%20%3E%20Auto%2DReply%20To,re%20not%20in%20your%20Contacts, 2022, 2 pages. |
| Black, “Samsung Galaxy S7 Silent Alarm Fix”, https://www.youtube.com/watch?v=35LQtw7ucaw, Jan. 20, 2017, 4 pages. |
| Bohn, “Why Android Notifications Are Better Than the iPhone's”, https://www.youtube.com/watch?v=bHtkjHSB5Nw, Apr. 18, 2018, 10 pages. |
| CNET, “Android Lollipop Lock-Screen Notification Tips”, https://www.youtube.com/watch?v=LZTxHBOwzIU, Nov. 13, 2014, 3 pages. |
| Droid Life, “Android 5.0 Feature: Notification Access and Do Not Disturb”, https://www.youtube.com/watch?v=SY2kAqCqOko, Oct. 17, 2014, 2 pages. |
| Frick, “Automatically Turn On Theater Mode on Android Wear Watch When Sleep Tracking”, https://forum.urbandroid.org/t/automatically-turn-on-theater-mode-on-android-wear-watch-when-sleep-tracking/398, Mar. 6, 2018, 2 pages. |
| Google, “Limit Interruptions with Do Not Disturb on Android”, https://support.google.com/android/answer/9069335?hl=en#zippy=%2Cset-what-to-block, 2022, 2 pages. |
| Hill, “From Oreo to Jelly Bean, Here's How to Turn Off Notifications in Android”, https://web.archive.org/web/20180503062117/https://www.ditaltrends.com/android/how-to-turn-off-notifications-in-android, May 3, 2018, 10 pages. |
| Hill, Here's How to Use Do Not Disturb Mode in Android, https://web.archive.org/web/20180313165228/https://www.digitaltrends.com/mobile/do-not-disturb-mode-in-android, Mar. 13, 2018, 6 pages. |
| Hill, “How to Turn Off Notifications in Andoid”, http://web.archive.org/web/20180203023547/https://www.digitaltrends.com/android/how-to-turn-off-notifications-in-android, Dec. 28, 2017, 16 pages. |
| IPhoneHacksTV, How to Group Notifications by App in iOS 9 Notification Center—iPhone Hacks, https://www.youtube.com/watch?v=j9kEN1_1yh8, Sep. 16, 2015, 2 pages. |
| iPhoneTricks.org, “How to Snooze or Stop an iPhone Alarm Without Looking at the Display?”, https://www.iphonetricks.org/how-to-snooze-or-stop-an-iphone-alarm-without-looking-at-the-display, Nov. 29, 2016, 5 pages. |
| Isom, “How to Change iPhone Notification Settings”, https://www.youtube.com/watch?v=P2Z4dvieB5k, Mar. 16, 2017, 3 pages. |
| Jason, “New i0S 8 Features that Apple Didn't Have Time to Tell US About Today”, https://web.archive.org/web/20171018064601-features-hidden.html, Jun. 2, 2014, 7 pages. |
| Klein, “How Manage, Customize, and Block Notifications in Android Lollipop and Marshmellow”, http://web.archive.org/web/20171229125502/https:www.howtogeek.com/202404/how-to-tame-notifications-in-android-5.0, Sep. 29, 2016, 11 pages. |
| Lew, “Correctly Handling Bundled Android Notifications”, https://web.archive.org/web/20171210085025/https://blog.danlew.net/20171018064601/http://, Feb. 7, 2017, 5 pages. |
| MacRumors, “iOS 11: How to Use the Lock Screen and Notification Center”, https://www.youtube.com/watch?v=BQDyGNO9oGc, Sep. 19, 2017, 4 pages. |
| Mcfasa09, “Toggle Theater Mode on Wear 2.0”, https://www.reddit.com/r/AndroidWear/comments/64qitr/toggle_theater_mode_on_wear_20, Mar. 18, 2014, 3 pages. |
| Mediati, “Master Notifications in Android Lollipop with Notification Priority and Downtime”, https:/web.archive.org/web/20180503062117/https://www.digitaltrends.com/android/how-to-turn-off-notifications-in-android, Dec. 3, 2014, 7 pages. |
| Phandroid, “Do Not Disturb” mode will save you from notification hell, https://www.youtube.com/watch?v=R6A2As4VJpl, Jan. 16, 2017, 3 pages. |
| Raphael, “Oh, Oreo! 8 Things to Try When You Get Andoid 8.0”, https://web.archive.org/web/20171224100520/https://www.computerworld.com/article/32191126/android/oreo-android-8, Aug. 24, 2017, 10 pages. |
| Rosenbaun, “How to Keep your Apple Watch Quiet”, https://www.theverge.com/2019/10/24/20930506/how-to-apple-watch-do-not-disturb-iphone-quiet-mute-theater-mode, Oct. 24, 2019, 8 pages. |
| Samsung, “Samsung Goodnight Mode”, https:/www.samsung.com/us/support/answer/ANS00080310, 1995-2021, 2 pages. |
| Sony Xperia Z, “How to turn off alarm when it sounds”, https://www.youtube.com/watch?v=eerWJMN7e5s, May 14, 2015, 3 pages. |
| Summerson, ‘Android's Confusing “Do Not Disturb” Settings, Explained’, https://www.howtogeek.com/260225/androids-confusing-do-not-disturb-settings-explained, Jul. 3, 2017, 8 pages. |
| Tantsissa Holdings, “Autosleep Seep Rings”, http://autosleep.tantsissa.com/sleeprings, 2016-2010, 6 pages. |
| Tropical Tech, How to Set Up Do Not Disturb Mode Rules / Schedule in Android / 2018, http://www.youtube.com/watch?v=DLnGcpKHVyM, Sep. 4, 2017, 3 pages. |
| VikuBalupura, “[Android] Hands-On With Android P—Is This the Beginning of a New Design Language?”, http://en.miui.com/thread-1995365-1-1.html, Mar. 10, 2018, 11 pages. |
| Wallen, “How to Customize Androlid Oreo Notifications With Categories”, http://web.archive.org/web/20171017232141/https://www.techrepublic.com/article/how-to-customize-android-oreo-notifications-with-categories, Oct. 17, 2017, 14 pages. |
| Wayback Machine, “Nights Keeper”, http://nightskeeper.com/?page_id=15, 2013, 9 pages. |
| Whitwam, Android N Feature Spotlight: Do Not Disturb Automatic Rules Get Option toEnd DND on Next Alarm, https://www.androidpolice.com/2016/03/11/android-n-feature-spotlight-do-not-disturb-gets-option-to-end-automatically-on-next-alarm/, Mar. 11, 2016, 5 pages. |
| Whitwarm, “Android P Feature Spotlight: Android Will Offer to Hide Notifications From Apps You Frequently Dismiss”, https://www.androidpolice.com/2018/03/12/android-P-feature-spotlight-android-will-offer-hide-notifications-apps-frequently-dismiss, Mar. 12, 2018, 5 pages. |
| Woodpress, “Features—Lighting Launcher”, https://www.lightninglauncher.com/wordpress/features, 2021, 3 pages. |
| XDA Spotlight, “Lock Me Out”, https://www.xda-developers.com/curb-android-smartphone-addiction-lock-me-out, Apr. 16, 2018, 7 pages. |
| YouTube, “Notification Digest”, https://support.google.com/youtube/answer/9012820_at_00:38, Dec. 29, 2018, 1 page. |
| Notice of Allowance, dated Apr. 19, 2019, received in U.S. Appl. No. 15/707,757, 8 pages. |
| Notice of Allowance, dated Aug. 6, 2019, received in U.S. Appl. No. 15/707,757, 8 pages. |
| Office Action, dated Jan. 16, 2020, received in U.S. Appl. No. 16/142,599, 13 pages. |
| Notice of Allowance, dated Jul. 16, 2020, received in U.S. Appl. No. 16/142,599, 7 pages. |
| Notice of Allowance, dated Sep. 18, 2020, received in U.S. Appl. No. 16/142,599, 7 pages. |
| Office Action, dated Nov. 6, 2020, received in Chinese Patent Application No. 202010095124.8, which corresponds with U.S. Appl. No. 16/142,599, 11 pages. |
| Office Action, dated Jul. 7, 2021, received in Chinese Patent Application No. 202010095124.8, which corresponds with U.S. Appl. No. 16/142,599, 1 page. |
| Notice of Allowance, dated Aug. 9, 2021, received in Chinese Patent Application No. 202010095124.8, which corresponds with U.S. Appl. No. 16/142,599, 2 pages. |
| Patent, dated Oct. 29, 2021, received in Chinese Patent Application No. 202010095124.8, which corresponds with U.S. Appl. No. 16/142,599, 5 pages. |
| Office Action, dated Aug. 27, 2018, received in Danish Patent Application No. 201870333, which corresponds with U.S. Appl. No. 16/142,599, 9 pages. |
| Office Action, dated Nov. 12, 2018, received in Danish Patent Application No. 201870333, which corresponds with U.S. Appl. No. 16/142,599, 3 pages. |
| Office Action, dated May 14, 2019, received in Danish Patent Application No. 201870333, which corresponds with U.S. Appl. No. 16/142,599, 6 pages. |
| Office Action, dated Nov. 15, 2019, received in Danish Patent Application No. 201870333, 2 pages. |
| Intention to Grant, dated Dec. 19, 2019, received in Danish Patent Application No. 201870333, 2 pages. |
| Notice of Allowance, dated Apr. 2, 2020, received in Danish Patent Application No. 201870333, 4 pages. |
| Patent, dated May 15, 2020, received in Danish Patent Application No. 201870333, which corresponds with U.S. Appl. No. 16/142,599, 5 pages. |
| Office Action, dated Sep. 9, 2022, received in European Patent Application No. 1972341.6, which corresponds with U.S. Appl. No. 16/142,599, 8 Pages. |
| Office Action, dated Apr. 3, 2020, received in U.S. Appl. No. 16/145,068, 35 pages. |
| Final Office Action, dated Nov. 30, 2020, received in U.S. Appl. No. 16/145,068, 44 pages. |
| Office Action, dated Jul. 12, 2021, received in U.S. Appl. No. 16/145,068, 82 pages. |
| Notice of Allowance, dated Feb. 28, 2022, received in U.S. Appl. No. 16/145,068, 25 pages. |
| Notice of Allowance, dated Jul. 12, 2022, received in U.S. Appl. No. 16/145,068, 9 pages. |
| Office Action, dated Aug. 29, 2018, received in Danish Patent Application No. 201870334, which corresponds with U.S. Patent U.S. Appl. No. 16/145,068, 9 pages. |
| Office Action, dated Mar. 5, 2019, received in Danish Patent Application No. 201870334, which corresponds with U.S. Patent U.S. Appl. No. 16/145,068, 6 pages. |
| Office Action, dated Sep. 6, 2019, received in Danish Patent Application No. 201870334, which corresponds with U.S. Patent U.S. Appl. No. 16/145,068, 4 pages. |
| Office Action, dated Apr. 22, 2020, received in Danish Patent Application No. 201870334, which corresponds with U.S. Patent U.S. Appl. No. 16/145,068, 2 pages. |
| Office Action, dated Apr. 6, 2020, received in U.S. Appl. No. 16/145,074, 22 pages. |
| Final Office Action, dated Nov. 16, 2020, received in U.S. Appl. No. 16/145,074, 33 pages. |
| Office Action, dated Jun. 28, 2021, received in U.S. Appl. No. 16/145,074, 39 pages. |
| Notice of Allowance, dated Mar. 11, 2022, received in U.S. Appl. No. 16/145,074, 27 pages. |
| Notice of Allowance, dated Jul. 28, 2022, received in U.S. Appl. No. 16/145,074, 27 pages. |
| Office Action, dated Apr. 16, 2021, received in Australian Patent Application No. 2019265367, U.S. Appl. No. 16/145,074, 3 pages. |
| Notice of Allowance, dated Jan. 18, 2022, received in Australian Patent Application No. 2019265367, U.S. Appl. No. 16/145,074, 3 pages. |
| Certificate of Grant, dated May 19, 2022, received in Australian Patent Application No. 2019265367, U.S. Appl. No. 16/145,074, 3 pages. |
| Office Action, dated Jan. 24, 2022, received in Chinese Patent Application No. 201811165505.8, which corresponds with U.S. Appl. No. 16/145,074, 1 page. |
| Office Action, dated Oct. 19, 2022, received in Chinese Patent Application No. 201811165505.8, which corresponds with U.S. Appl. No. 16/145,074, 2 pages. |
| Notice of Allowance, dated Jan. 28, 2023, received in Chinese Patent Application No. 201811165505.8, which corresponds with U.S. Appl. No. 16/145,074, 2 pages. |
| Patent, dated Jun. 27, 2023, received in Chinese Patent Application No. 201811165505.8, which corresponds with U.S. Appl. No. 16/145,074, 5 pages. |
| Office Action, dated Aug. 31, 2018, received in Danish Patent Application No. 201870335, which corresponds with U.S. Appl. No. 16/145,074, 9 pages. |
| Innovation Patent, dated Jan. 31, 2022, received in Australian U.S. Appl. No. 16/948,374 (7740AU01), which corresponds with U.S. Appl. No. 16/948,374, 3 pages. |
| Office Action, dated Dec. 20, 2018, received in Danish Patent Application No. 201870335, which corresponds with U.S. Appl. No. 16/145,074, 4 pages. |
| Office Action, dated Aug. 28, 2019, received in Danish Patent Application No. 201870335, which corresponds with U.S. Appl. No. 16/145,074, 5 pages. |
| Office Action, dated Apr. 20, 2020, received in Danish Patent Application No. 201870335, which corresponds with U.S. Appl. No. 16/145,074, 4 pages. |
| Office Action, dated Dec. 10, 2021, received in Japanese Patent Application No. 2020-557940, which corresponds with U.S. Appl. No. 16/145,074, 2 pages. |
| Notice of Allowance, dated Aug. 8, 2022, received in Japanese Patent Application No. 2020-557940, which corresponds with U.S. Appl. No. 16/145,074, 1 page. |
| Patent, dated Sep. 9, 2022, received in Japanese Patent Application No. 2020-557940, which corresponds with U.S. Appl. No. 16/145,074, 3 pages. |
| Office Action, dated Nov. 30, 2021, received in Korean Patent Application No. 2020-7037439, which corresponds with U.S. Appl. No. 16/145,074, 3 pages. |
| Notice of Allowance, dated Jul. 28, 2022, received in Korean Patent Application No. 2020-7037439, which corresponds with U.S. Appl. No. 16/145,074, 3 pages. |
| Office Action, dated Aug. 12, 2021, received in U.S. Appl. No. 16/948,370, 35 pages. |
| Final Office Action, dated Apr. 5, 2022, received in U.S. Appl. No. 16/948,370, 44 pages. |
| Notice of Allowance, dated Sep. 7, 2022, received in U.S. Appl. No. 16/948,370, 12 pages. |
| Notice of Allowance, dated Jan. 17, 2023, received in U.S. Appl. No. 16/948,370, 13 pages. |
| Office Action, dated Jun. 25, 2021, received in Australian Patent Application No. 2020233622, which corresponds with U.S. Appl. No. 16/948,370, 8 pages. |
| Notice of Allowance, dated Feb. 22, 2022, received in Australian Patent Application No. 2020233622, which corresponds with U.S. Appl. No. 16/948,370, 3 pages. |
| Office Action, dated Dec. 18, 2020, received in Danish Patent Application No. 2020-70595, which corresponds with U.S. Appl. No. 16/948,370, 9 pages. |
| Office Action, dated Sep. 30, 2021, received in Danish Patent Application No. 2020-70595, which corresponds with U.S. Appl. No. 16/948,370, 5 pages. |
| Office Action, dated May 19, 2022, received in Danish Patent Application No. 2020-70595, which corresponds with U.S. Appl. No. 16/948,370, 2 pages. |
| Intention to Grant, dated Nov. 3, 2022, received in Danish Patent Application No. 2020-70595, which corresponds with U.S. Appl. No. 16/948,370, 2 pages. |
| Patent, dated Jun. 20, 2023, received in Danish Patent Application No. 2020-70595, which corresponds with U.S. Appl. No. 16/948,370, 8 pages. |
| Office Action, dated Dec. 2, 2021, received in Indian Patent Application No. 202014040025, which corresponds with U.S. Appl. No. 16/948,370, 8 pages. |
| Office Action, dated Mar. 4, 2022, received in Japanese Patent Application No. 2020-160012, which corresponds with U.S. Appl. No. 16/948,370, 2 pages. |
| Notice of Allowance, dated Jan. 6, 2023, received in Japanese Patent Application No. 2020-160012, which corresponds with U.S. Appl. No. 16/948,370, 2 pages. |
| Patent, dated Jan. 26, 2023, received in Japanese Patent Application No. 2020-160012, which corresponds with U.S. Appl. No. 16/948,370, 3 pages. |
| Office Action, dated Apr. 20, 2023, received in Korean Patent Application No. 2020-0123965, which corresponds with U.S. Appl. No. 16/948,370, 4 pages. |
| Office Action, dated Feb. 1, 2021, received in U.S. Appl. No. 16/948,374, 27 pages. |
| Final Office Action, dated Jun. 11, 2021, received in U.S. Appl. No. 16/948,374, 29 pages. |
| Office Action, dated Dec. 29, 2021, received in U.S. Appl. No. 16/948,374, 29 pages. |
| Final Office Action, dated May 6, 2022, received in U.S. Appl. No. 16/948,374, 27 pages. |
| Notice of Allowance, dated Sep. 28, 2022, received in U.S. Appl. No. 16/948,374, 13 pages. |
| Office Action, dated May 11, 2021, received in Australian Patent Application No. 2020239686, which corresponds with U.S. Appl. No. 16/948,374, 4 pages. |
| Notice of Allowance, dated Oct. 7, 2021, received in Australian Patent Application No. 2020239686, which corresponds with U.S. Appl. No. 16/948,374, 3 pages. |
| Patent, dated Feb. 10, 2022, received in Australian Patent Application No. 2020239686, which corresponds with U.S. Appl. No. 16/948,374, 3 pages. |
| Innovation Patent, dated Jun. 9, 2021, received in Australian Patent Application No. 2021102471, which corresponds with U.S. Appl. No. 16/948,374, 5 pages. |
| Office Action, dated Jul. 30, 2021, received in Australian Patent Application No. 2021102471, which corresponds with U.S. Appl. No. 16/948,374, 4 pages. |
| Innovation Patent, dated Jan. 31, 2022, received in Australian Patent Application No. 2021102471, which corresponds with U.S. Appl. No. 16/948,374, 3 pages. |
| Office Action, dated Dec. 21, 2020, received in Danish Patent Application No. 2020-70599, which corresponds with U.S. Appl. No. 16/948,374, 8 pages. |
| Office Action, dated Oct. 4, 2021, received in Danish Patent Application No. 2020-70599, which corresponds with U.S. Appl. No. 16/948,374, 2 pages. |
| Office Action, dated Jun. 2, 2022, received in Danish Patent Application No. 2020-70599, which corresponds with U.S. Appl. No. 16/948,374, 2 pages. |
| Office Action, dated Dec. 1, 2021, received in Indian Patent Application No. 202014040935, which corresponds with U.S. Appl. No. 16/948,374, 9 pages. |
| Office Action, dated Nov. 30, 2021, received in Japanese Patent Application No. 2020-160013, which corresponds with U.S. Appl. No. 16/948,374, 2 pages. |
| Notice of Allowance, dated Sep. 22, 2022, received in Japanese Patent Application No. 2020-160013, which corresponds with U.S. Appl. No. 16/948,374, 2 pages. |
| Patent, dated Oct. 21, 2022, received in Japanese Patent Application No. 2020-160013, which corresponds with U.S. Appl. No. 16/948,374, 2 pages. |
| Office Action, dated May 29, 2022, received in Korean Patent Application No. 2020-0123967, which corresponds with U.S. Appl. No. 16/948,374, 3 pages. |
| Notice of Allowance, dated Dec. 26, 2022, received in Korean Patent Application No. 2020-0123967, which corresponds with U.S. Appl. No. 16/948,374, 2 pages. |
| Patent, dated Mar. 24, 2023, received in Korean Patent Application No. 2020-0123967, which corresponds with U.S. Appl. No. 16/948,374, 5 pages. |
| Office Action, dated Jan. 8, 2021, received in U.S. Appl. No. 16/948,375, 19 pages. |
| Final Office Action, dated Mar. 9, 2021, received in U.S. Appl. No. 16/948,375, 19 pages. |
| Notice of Allowance, dated Jun. 24, 2021, received in U.S. Appl. No. 16/948,375, 6 pages. |
| Notice of Allowance, dated Oct. 26, 2021, received in U.S. Appl. No. 16/948,375, 5 pages. |
| Office Action, dated Apr. 13, 2021, received in Australian Patent Application No. 2020239689, which corresponds with U.S. Appl. No. 16/948,375, 8 pages. |
| Notice of Allowance, dated Oct. 5, 2021, received in Australian Patent Application No. 2020239689, which corresponds with U.S. Appl. No. 16/948,375, 3 pages. |
| Patent, dated Feb. 10, 2022, received in Australian Patent Application No. 2020239689, which corresponds with U.S. Appl. No. 16/948,375, 3 pages. |
| Office Action, dated Jan. 11, 2021, received in Danish Patent Application No. 2020-70629, which corresponds with U.S. Appl. No. 16/948,375, 10 pages. |
| Office Action, dated Sep. 15, 2022, received in Danish Patent Application No. 2020-70629, which corresponds with U.S. Appl. No. 16/948,375, 5 pages. |
| Office Action, dated Dec. 1, 2021, received in Indian Patent Application No. 202014040936, which corresponds with U.S. Appl. No. 16/948,375, 10 pages. |
| Office Action, dated Dec. 6, 2021, received in Japanese Patent Application No. 2020-160014, which corresponds with U.S. Appl. No. 16/948,375, 2 pages. |
| Notice of Allowance, dated Jul. 29, 2022, received in Japanese Patent Application No. 2020-160014, which corresponds with U.S. Appl. No. 16/948,375, 2 pages. |
| Patent, dated Aug. 30, 2022, received in Japanese Patent Application No. 2020-160014, which corresponds with U.S. Appl. No. 16/948,375, 4 pages. |
| Office Action, dated Apr. 22, 2022, received in U.S. Appl. No. 17/084,579, 10 pages. |
| Office Action, dated May 5, 2022, received in U.S. Appl. No. 17/084,579, 11 pages. |
| Final Office Action, dated Oct. 11, 2022, received in U.S. Appl. No. 17/084,579, 12 pages. |
| Office Action, dated Jul. 26, 2021, received in U.S. Appl. No. 17/112,883, 9 pages. |
| Notice of Allowance, dated Feb. 4, 2022, received in U.S. Appl. No. 17/112,883, 8 pages. |
| Office Action, dated Jul. 27, 2022, received in U.S. Appl. No. 17/483,751, 30 pages. |
| Final Office Action, dated Dec. 20, 2022, received in U.S. Appl. No. 17/483,751, 43 pages. |
| Office Action, dated Apr. 14, 2023, received in U.S. Appl. No. 17/483,751, 43 pages. |
| Notice of Allowance, dated Feb. 2, 2022, received in U.S. Appl. No. 17/483,757, 35 pages. |
| Notice of Allowance, dated Mar. 30, 2022, received in U.S. Appl. No. 17/483,757, 5 pages. |
| Office Action, dated May 18, 2023, received in Australian Patent Application No. 2022203663, which corresponds with U.S. Appl. No. 18/100,530, 3 pages. |
| Office Action, dated Nov. 21, 2022, received in Korean Patent Application No. 2022-7032607, which corresponds with U.S. Appl. No. 17/940,858, 5 pages. |
| Notice of Allowance, dated May 30, 2023, received in Korean Patent Application No. 2022-7032607, which corresponds with U.S. Appl. No. 17/940,858, 2 pages. |
| Invitation to Pay Additional Fees, dated Jun. 17, 2019, received in International Patent Application No. PCT/US2019/026353, which corresponds with U.S. Appl. No. 16/142,599, 19 pages. |
| International Search Report and Written Opinion, dated Aug. 7, 2019, received in International Patent Application No. PCT/US2019/026353, which corresponds with U.S. Appl. No. 16/142,599, 26 pages. |
| International Search Report and Written Opinion, dated May 28, 2019, received in International Patent Application No. PCT/US2019/026349, which corresponds with U.S. Appl. No. 16/145,068, 16 pages. |
| Invitation to Pay Additional Fees, dated Aug. 6, 2021, received in International Patent Application No. PCT/US2021/031131, which corresponds with U.S. Appl. No. 16/948,370, 5 pages. |
| International Search Report and Written Opinion, dated Nov. 2, 2022, received in International Patent Application No. PCT/US2022028806, which corresponds with U.S. Appl. No. 17/483,751, 20 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20220404963 A1 | Dec 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62399394 | Sep 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17112883 | Dec 2020 | US |
| Child | 17831384 | US | |
| Parent | 16730921 | Dec 2019 | US |
| Child | 17112883 | US | |
| Parent | 15707757 | Sep 2017 | US |
| Child | 16730921 | US |
