Patent Application
20190172016
The disclosed embodiments relate generally to user interfaces of portable electronic devices, and specifically to user interfaces for managing calendar information.
Consumers often store their calendars electronically. Those who own more than one electronic device may wish to access their electronic calendars from any device. Access to calendar information from portable electronic devices is particularly desirable for mobile users. As portable electronic devices become more portable—which will increase the desire for electronic information access—suitable user interfaces for managing calendar information will also become increasingly desirable.
In some embodiments, techniques for presenting calendar information comprises, at an electronic device with a touch-sensitive display: displaying, on the touch-sensitive display, an icon representing a calendar application; detecting user input; in response to a determination that the detected user input represents a touch on the displayed icon: launching the calendar application and transitioning from the display of the icon, through at least one intermediate user interface screen, to displaying a landing screen of the calendar application; and in response to a determination that the detected user input represents movement of the rotatable input mechanism: launching the calendar application and transitioning from the display of the icon directly to displaying the landing screen of the calendar application.
In some embodiments, techniques for presenting calendar information comprises, at an electronic device with a touch-sensitive display: displaying, on the touch-sensitive display, an affordance representing a calendar application; detecting user input; in response to detecting the user input: (a) in accordance with a determination that the detected user input is a touch on the displayed affordance: displaying a first text indicating at least two months in a year, then, replacing the display of the first text with a display of a second text indicating at least some days in one and only one month of the year, and then, replacing the display of the second text with a display of at least one affordance representing at least one calendar entry; (b) in accordance with a determination that the detected user input is a movement of the rotatable input mechanism: displaying at least one affordance representing at least one calendar entry.
In some embodiments, techniques for presenting calendar information comprises, at an electronic device with a touch-sensitive display: displaying, on the touch-sensitive display, an affordance representing a calendar application; detecting user input; in response to detecting the user input: (a) in accordance with a determination that the detected user input is a touch on the displayed affordance: displaying a first text indicating at least two months in a year, then, replacing the display of the first text with a display of a second text indicating at least some days in one and only one month of the year, and then, replacing the display of the second text with a display of at least one affordance representing at least one calendar entry; (b) in accordance with a determination that the detected user input is a movement of the rotatable input mechanism: displaying the first text indicating at least two months in a year.
In some embodiments, techniques for presenting calendar information comprises, at an electronic device with a touch-sensitive display: displaying an affordance representing a calendar entry in a calendar application; detecting a touch on the display, the touch having a characteristic intensity, the touch located at the displayed user interface object representing the calendar entry; determining whether the characteristic intensity of the touch is below a threshold intensity; in response to a determination that the characteristic intensity of the touch is below the threshold intensity, displaying a time and a location associated with the calendar entry; in response to a determination that the characteristic intensity of the touch is not below the threshold intensity, displaying, on the touch-sensitive display, a plurality of affordances representing functions of the calendar application.
In some embodiments, techniques for presenting calendar information comprises, at an electronic device with a touch-sensitive display: displaying, on the touch-sensitive display, a plurality of calendar entries, the plurality of calendar entries including a first calendar entry and a second calendar entry, the first calendar entry displayed above the second calendar entry; receiving user input representing user acceptance of the first calendar entry; and in response to receiving the user input, displaying the first calendar entry below the second calendar entry.
In some embodiments, techniques for presenting calendar information comprises, at an electronic device with a touch-sensitive display: displaying, on the touch-sensitive display, a first user interface screen having a plurality of calendar entries; receiving first data representing user acceptance of a first calendar entry of the plurality of calendar entries; in response to receiving the first data, removing the accepted first calendar entry from the first user interface screen; receiving second data representing a user input; and in response to receiving the second data, replacing the display of the first user interface screen with a display of a second user interface screen having a plurality of accepted calendar entries.
In some embodiments, techniques for presenting calendar information comprises, at an electronic device with a touch-sensitive display: displaying a user interface screen on the touch-sensitive display, wherein the displayed user interface screen includes a plurality of texts indicating a plurality of months in a year, wherein the texts of the plurality of texts are organized according to a layout having at least two rows and at least two columns, wherein the plurality of texts have an initial visual characteristic; detecting a user selection of a first text of the plurality of texts, the first text indicating a first month of the plurality of months; and in response to detecting the user selection, changing the visual characteristic of the plurality of texts except the first text indicating the first month.
In some embodiments, techniques for presenting calendar information comprises, at an electronic device with a touch-sensitive display: displaying a row of numerals, the numerals indicating days in a month; detecting user input; and in response to detecting the user input, translating all but one of the displayed numerals from its respective position in the row into a new position, wherein the displayed numerals, in their new positions, form a column of numerals.
In some embodiments, techniques for presenting calendar information comprises, at an electronic device with a touch-sensitive display: at an electronic device with a touch-sensitive display: displaying on the touch-sensitive display: text indicating hours in a day, at least one region representing a calendar entry scheduled during the indicated hours, and text inside the at least one region indicating a name of the calendar entry; detecting user input representing a zoom-in or zoom-out command; in accordance with a determination that the user input represents a zoom-in command: enlarging the at least one region, and displaying additional text inside the at least one region indicating details of the calendar entry.
In some embodiments, techniques for presenting calendar information comprises, at an electronic device with a touch-sensitive display: displaying, on the touch-sensitive display, an application affordance representing a calendar application; detecting a user selection of the application affordance; in response to detecting the user selection of the application affordance: launching the calendar application; displaying a first event affordance representing a first calendar entry, and displaying a second event affordance representing a second calendar entry, wherein the second calendar entry is longer in duration than the first calendar entry, but the size of the first event affordance is larger than the size of the second event affordance.
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.
The following description sets forth exemplary methods, parameters and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
User interfaces for efficient presentation and management of calendar information, particularly on portable electronic devices, are described. Below,
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
The 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.
The term “if” may be 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” may be 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. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. 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 may support a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk 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 “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a 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) 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 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).
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.
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 may include one or more computer-readable storage mediums. The computer-readable storage mediums may be tangible and non-transitory. Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 may control access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 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 120, and memory controller 122 may be implemented on a single chip, such as chip 104. In some other embodiments, they may be implemented on separate chips.
RF (radio frequency) circuitry 108 receives and 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 RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. 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 (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), 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 may be 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 screen 112 and other input control devices 116, to 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 control devices 116. The other input 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 to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button may disengage a lock of touch screen 112 or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) may turn power to device 100 on or off. The user may be able to customize a functionality of one or more of the buttons. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 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 screen 112. Touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 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 screen 112 and convert 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 screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 112 and display controller 156 may 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 screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.
A touch-sensitive display in some embodiments of touch screen 112 may be analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make contact with touch screen 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 primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device 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 may include 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 may be a touch-sensitive surface that is separate from touch screen 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 may include 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 may also include one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 may also include one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 may also include one or more accelerometers 168.
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, graphics module (or set of instructions) 132, 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 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
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 on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 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 various software components for performing various operations related to detection of contact, 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 to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 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 threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, 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).
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 (liftoff) 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 (liftoff) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 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) 167 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 may be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, 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 138 for use in location-based dialing; to camera 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 may include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 may be used 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 or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 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 may use any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference 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 screen 112, display controller 156, contact/motion 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 screen 112, display controller 156, contact/motion 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, 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 may include graphics, photos, audio files, video files and/or other attachments as are supported in an 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, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion 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, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact/motion 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 screen 112, display controller 156, contact/motion 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 screen 112, display controller 156, contact/motion 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 screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that may be 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 screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display controller 156, contact/motion 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 screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow 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 screen 112 or on an external, connected display 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 screen 112, display controller 156, contact/motion 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 screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 may be used 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 screen 112, display controller 156, contact/motion 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 instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display 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. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds 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 (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. For example, video player module may be combined with music player module into a single module (e.g., video and music player module 152,
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 may be 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 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 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) 168, 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 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, peripherals 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 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 may 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 may be called the hit view, and the set of events that are recognized as proper inputs may be 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 (e.g., 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 172, 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 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 may utilize or call data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more 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 may 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 may also include 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 liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (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 112, and liftoff 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 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a 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 may 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. 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 touchpads; 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 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In one embodiment, device 100 includes touch screen 112, 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, headset 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 an alternative embodiment, 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 screen 112 and/or one or more tactile output generators 167 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 that may be implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples which follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), 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 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.
Techniques for detecting and processing touch intensity may be found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms may permit device 500 to be worn by a user.
Input mechanism 508 may be a microphone, in some examples. Personal electronic device 500 can include various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can be a non-transitory computer-readable storage medium, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described above, including processes 2400-3300 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that may be displayed on the display screen of devices 100, 300, and/or 500 (
As used herein, the term “focus selector” refers to 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 “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on 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 threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation 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, 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 intensity of a contact on the touch-sensitive surface may be characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform 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 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.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a 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., 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., 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., 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 descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: 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, and/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 used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and/or 500) and is ready to be launched (e.g., become opened) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system.
As used herein, the term “open application” or “executing application” refers to a software application with retained state information (e.g., as part of device/global internal state 157 and/or application internal state 192). An open or executing application may be any one of the following types of applications:
an active application, which is currently displayed on a display screen of the device that the application is being used on;
a background application (or background processes), which is not currently displayed, but one or more processes for the application are being processed by one or more processors; and
a suspended or hibernated application, which is not running, but has state information that is stored in memory (volatile and non-volatile, respectively) and that can be used to resume execution of the application.
As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.
Attention is now directed to user interface screens that support a calendar application that is operable on portable electronic devices. In the discussion that follow, device 500 (
Exemplary calendar user interface screens are now discussed with reference to
Month screen 600 is interactive. For example, month screen 600 may be scrollable to reveal days that are not already displayed, if any. As another example, month screen 600 may zoom. A user may initiate these interactions through different input modalities. In some embodiments, scrolling may be invoked via a touch gesture (e.g., swipe or flick). In some embodiments, scrolling may be invoked via a physical input mechanism (e.g., rotation of a rotatable mechanism). In some embodiments, zooming may be invoked via one or more of these mechanisms.
Day screen 630 may indicate calendar entries of the day using regions 636 and 638. Calendar entries may be stored on electronic device 500, a companion device (e.g., a cellular phone), at a network-accessible location (e.g., in the “cloud”), or in some combination thereof. These regions are contiguous regions that are visually distinguishable from the background of day screen 630. In some examples, these regions may take on a geometric shape. As shown, region 636 and 638 are rectangular boxes. The edges of region 636 and 638 may indicate the start and end times of corresponding calendar entries. For example, region 636 represents an event scheduled from nine o'clock to half-past nine because its top edge is aligned with the hour marker indicating 9 o'clock. As another example, region 638 represents an event scheduled from ten o'clock to half-past eleven. Due to the correspondence between the edges of regions 636 and 638 with the start/end times of their corresponding calendar entries, the vertical heights of the regions are proportional to the durations of the respective calendar entries. This presentation of calendar entries imparts a grid-like appearance to day screen 230. Accordingly, day screen 630 may be referred to as the “grid” version of the day screen.
Day screen 630 also may have all-day entry indicator 639 indicating a calendared event that spans the day. In some examples, all-day entry indicator 639 is displayed above all other partial-day calendar entries to promote its visibility. Note that, to reduce its on-screen footprint, the vertical height of all-day entry indicator 639 may be shorter compared to regions 636 and 638, even though its (all-day) duration is longer than that of the events represented by regions 636 and 638.
Day screen 640 also may have affordances 648 and 649 indicating the source of the represented calendar entries. (As discussed above, it is possible for device 500 to have access to more than one calendar.) Calendar indicator 648 may indicate that “John's Birthday” resides in a first calendar such as a personal calendar, while calendar indicator 649 may indicate that “Meeting B” resides in a second calendar such as work calendar.
Attention is now directed to ways in which embodiments of the calendar application may, in response to user interaction, transition between the displays of the calendar screens described with respect to
As shown in
In flow 700, year screen 710 is the landing screen for the calendar application, meaning that, if user invoked the calendar application using touch contact 707, the calendar application would launch and settle into the display of year screen 710. Flow 700 presents calendar information to a user in a decreasing level of granularity, as the user is initially presented calendar information for the day, followed by the month, and followed by the year.
Attention is now directed to the defaulting behaviors of day screen 708, month screen 709, and year screen 710. In some embodiments, the display of day screen 708 in the above-described flows (
In some embodiments, the displays of day view 708 (
In some embodiments, device 500 supports both flows 700 and 740 such that it responds differently to input in the form of a selection (e.g., 707) of icon 702 versus input in the form of a rotational movement (e.g., 717), when screen 701 is displayed. Other combinations are possible. In some embodiments, device 500 supports flows 700 and 730 when screen 701 is displayed. In some embodiments, device supports flows 720 and 740 when screen 701 is displayed. In some embodiments, device 500 supports flows 720 and 730 when screen 701 is displayed. Other combinations are permutations in different embodiments. In some embodiments, device 500 permits user-designation of preferred flow(s).
Among other things, the above-described user interface flows beneficially improve the efficiency of man-machine interface between a user and device 500. For example, in the described embodiments, device 500 may present a user with multiple ways of winnowing and accessing specific calendar entries out of a greater set of calendar information. Consider flow 720 (
In addition, the availability of a rotatable input mechanism on device 500 further improves the speed of these man-machine interactions. For example, after seeing device 500 transition between different calendar screens (e.g., year, month, day) in flow 720 (
Attention is now directed to additional exemplary user interactions with the calendar application executing on device 500. These aspects are described with reference to
All-day calendar entry indicator 810 is responsive to user interaction. In some embodiments, having seen indicator 810, the user may select the indicator to reveal more information about the all-day event. In some embodiments, the selection is made with touch gesture such as a tap or a swipe (e.g., downward swipe 842) involving indicator 810. In response to the user selection, the calendar application may enlarge all-day event indicator 810 to reveal that today is “John's Birthday,” as indicated by text 844.
As used here, a swipe need not be perfectly aligned with one direction in order for the swipe to be considered as a swipe in that direction. That is, a downward swipe need not be perfectly straight nor vertical in the down direction. Instead, a swipe that is substantially in one direction may be considered to be a swipe in that direction. In some examples, a swipe that is within less than 45 degrees from an axis is may be considered to be substantially along that axis. In some examples, particularly those in which a screen is scrollable only along one axis, a swipe that has any detectable motion along that axis may be considered a swipe substantially along that axis.
A user may select (e.g., touch) the displayed regions 846-848 to display additional event details for the represented calendar entries. In some embodiments, a selection of any one of the regions 846-848 causes calendar entries screen 850 to be displayed. Calendar entries screen 850 has non-overlapping regions 852, 854, and 856 corresponding to regions 846, 847, and 848, respectively. Regions 852, 854, 856 are presented in a non-overlapping manner on screen 850 to facilitate user selection. A user may select any one of regions 852, 854, 856 to access detailed information for the represented calendar entry. The additional details may be displayed via calendar entry details screen 650 (
In some embodiments (not illustrated), it is possible for a user to bypass calendar entries screen 850 by precisely selecting one of regions 846-848 in day screen 840. For example, if device 500 detects user selection at a position that falls within a single displayed region (e.g., 847) and not another overlapping region (e.g., 846 or 848), device 500 displays details for the calendar entry represented by the single region (e.g., 847). The additional details may be displayed via calendar entry details screen 650 (
A user may select (e.g., touch) region 866 to display calendar entries screen 870. Calendar entries screen 870 has regions 872, 874, and 876 representing the multiple (in this case, three) calendar entries that had been coalesced into and were represented by region 866. From screen 870, a user may select any one of regions 872, 874, and 876 to access detailed information for the represented calendar entry. The additional details may be displayed via calendar entry details screen 650 (
Attention is now directed to techniques for accessing contextual user interfaces in embodiments of the calendar application. Device 500 may have a small form factor. Due to its size, device 500 may not lend itself to displaying large numbers of graphical user interface elements, as the inclusion of many elements could reduce the display area available for calendar content.
In some embodiments, the calendar application of device 500 may invoke different features based on the touch intensity of user input. This aspect is described with reference to
Options screen 920 may include affordances for invoking various options (or features) of the calendar application. For example, options screen 920 may include affordance 922 for displaying a day screen for the current day. Options screen 920 may include affordance 924 displaying a “calendar inbox” screen. (Exemplary calendar inbox screens are described below with reference to
Attention is now directed to calendar inbox screens that may be invoked using affordance 924 on options screen 920 (
Calendar inbox screens 950 and 952 may each include affordances 962 and 964 indicating the position of each screen among a plurality of screens. Affordances 962 and 964 may enlarge, darken, or otherwise change in visual appearance when the corresponding calendar inbox screen is displayed. An exemplary implementation of affordances 962 and 964 is paging dots.
Attention is now directed to configuration settings screens that may be invoked using affordance 926 on options screen 920 (
In some embodiments, device 500 may display calendar selection screen 980 in response to a touch on affordance 972. Calendar selection screen 980 may include a legend identifying visual representations used to represent different calendars, such as the use of circle 982 to represent calendar 984. Circle 982 may be affordance 670 (
Attention is now directed to the toggling of different on-screen presentations of calendar entries that may be invoked by affordance 928 on options screen 920 (
The calendar application may display options screens other than options screen 920 (
Attention is now directed to how the calendar application permits a user to respond (e.g., accept or decline) to an incoming calendar entry (e.g., an invitation). With reference to
In some embodiments, device 500 may display acceptance screen 1130 momentarily (e.g., for a predetermined time interval), and subsequently display calendar inbox screen 1140. In some embodiments, device 500 may display acceptance screen 1130 until a user input is received (e.g., a touch or swipe), at which time device 500 transitions to the display of calendar inbox screen 1140. While calendar inbox screens 1100 and 1140 are similar, note that region 1102 is displayed below divider 1142 in screen 1140. This positioning indicates that the user has responded to the incoming calendar entry represented by affordance 1102. In this way, other invitations (e.g., the invitation represented by region 1144) may be more prominently displayed to encourage user response.
Attention is now directed to the creation of new calendar entries using the calendar application. This aspect is described with respect to
Attention is now directed to features for contacting one or more persons associated with calendar entry, such as an event organizer. This aspect is described with respect to
Contact card screen 1320 also may include name 1322, phone number 1324, and e-mail 1326 for the event organizer. When a user selects phone number 1322, the calendar application may initiate a phone call to the indicated number. In some embodiments, the phone call may be initiated using a cellular communication unit of device 500. In some embodiments, the phone call may be initiated using a network communication unit of device 500, such as a voice-over-IP unit. In some embodiments, device 500 instructs a companion device, such as a cellular phone, to initiate the phone call using the companion device's cellular communication unit. In some embodiments, device 500 instructs a companion device, such as a networkable laptop computer, to initiate the phone call using the companion device's network communication unit. Upon initiating the phone call, device 500 displays call progress screen 1330. At the conclusion of the phone call, device 500 returns to event details screen 1310.
Contact card screen 1410 may include affordance 1412 for initiating a phone call to the event organizer. If a user selects affordance 1412, device 500 may display screen 1330 (
Contact card screen 1410 also may include affordance 1414 for initiating an e-mail to the event organizer. If a user selects affordance 1414, device 500 may permit a user to create an e-mail message using various modalities. In some embodiments, device 500 may display a soft keyboard for entering an e-mail message. In some embodiments, device 500 may permit a user to aurally dictate a message which is then included in a draft e-mail as text. In some embodiments, device 500 may permit a user to record a voice memo, which is then included in a draft e-mail as an audio attachment. In some embodiments, device 500 may permit a user to send emoji characters. In some embodiments, device 500 may present, for the user's selection, a list of predicted text that device 500 has determined to be possible and/or likely responses.
These predicted texts may include those described in U.S. Provisional Patent Application No. 62/005,958, “Canned Answers in Messages,” filed May 30, 2014, (the “Canned Answers Specification”) the content of which is hereby incorporated by reference. For instance, the Canned Answers Specification describes predicting a user's likely response to an incoming message and presenting those predicted responses as options for user selection. In some embodiments the predictions are based the content of an incoming message and/or the sender's identity. In some examples, responsive to an incoming message that contains a question mark, the system predicts and presents the canned answers “yes” and “no.” In some examples, responsive to an incoming message that contains two phrases separated by the word “or,” the system presents the word appearing before “or” and the word appearing after “or” as canned answers. In some examples, responsive to an incoming message from a sender identified as the user's wife (e.g., through the user's contact list), the system predicts and presents the phrase “I love you” as a canned response.
Contact card screen 1410 may also include affordance 1418 for sending a message to the event organizer. Device 500 may permit a user to create a message (e.g., SMS message) using one or more of the above-described input modalities.
Contact card screen 1410 also may include affordance 1416 for launching a map application that maps an address of the event organizer. If a user selects affordance 1416, device 500 may launch a maps application mapping the address of the event organizer. In some embodiments, the address is static, such as a work address from the organizer's business card. In some embodiments, the address is dynamic, such as updated locational information reported by a GPS-equipped device of the organizer's.
Attention is now directed to additional user interface transitions that may be displayed by the calendar application in response to user interaction.
While still selecting (e.g., touching) the touch-sensitive display of device 500, the user may drag (e.g., slide) his finger in a particular direction, for example, upwards. As shown, in response to the upward sliding finger, month 1704 (November)—which precedes month 1702 (December)—becomes visually emphasized, and month 1702 becomes visually de-emphasized. As the user continues to slide his finger upwards, month 1706 (October)—which precedes month 1704 (November)—becomes visually emphasized, and month 1702 becomes visually de-emphasized. When the user releases his selection (e.g., touch), all of the displayed months may return to their normal visual appearance, except month 1706 (October), which now has focus. In this way, a user can place focus on a particular month of the displayed year. While month 1706 has focus, a user may rotate the rotatable input mechanism of device 500 (as indicated by arrow 1708) to transition from year screen 1730 to month screen 1740, which shows the days of month 1706.
The translation between screen 1900 and screen 1930 involves on-screen translation of numerals (representing days) from their positions in row 1904 to their new positions in column 1932. This transition is illustrated by exemplary screens 1910 and 1920. In screen 1910, row 1904 is shown pivoting from its horizontal (row) orientation towards a vertical (column) orientation roughly about position 1912. While row 1904 pivots, numerals in other rows are translated off-screen. Screen 1920 illustrates further progression of this translation. As can be seen, in this stage of the transition, many numerals have been translated off-screen, leaving primarily the numerals of row 1904. As the transition of row 1904 into column 1932 completes, weekday identifiers are added adjacent the displayed numerals, as shown on week screen 1930.
Exemplary user interface screens illustrating progressive disclosure are now described. As shown in
As illustrated in
Turning to
Attention is now directed to other exemplary user interface screens for displaying calendar information for a particular day and a particular year.
In addition,
Attention is now directed to an exemplary transition between the day screen and the inbox screen of the calendar application in some embodiments. As shown in
While day screen 2200 is displayed, a user may contact (e.g., touch) the touch-sensitive display of device 500. Device 500 may determine or otherwise obtain a measurement of the intensity of the contact. If the intensity is above the threshold, the calendar application may cause device 500 to display options screen 2220. Options screen 2220 may be screens 992 (
While calendar inbox screen 2210 is displayed, a user may contact (e.g., touch) the touch-sensitive display of device 500. Device 500 may determine or otherwise obtain a measurement of the intensity of the contact. If the intensity is above the threshold, the calendar application may cause device 500 to display options screen 2230. Options screen 2220 may be screens 992 (
Attention is now directed to another exemplary landing screen 2310 for the calendar application, an example of which is shown in
Attention is now directed to exemplary processes for carrying out the user interface techniques described above.
In some embodiments, the transition at block 2408 involves the display of a year screen (e.g., screen 610;
When displaying the day screen, device 500 may display one or more affordances representing calendar entries scheduled for the day. The affordances may have the visual appearance of a geometric shape, such as a rectangle. More generally speaking, the affordances may be regions of the display that are distinguishable from the background of the calendar application. Optionally, when the landing screen is the day screen, device 500 may display calendar entries for the current day. Optionally, when the month screen is displayed, device 500 may display an indicator (e.g., numeral) indicating the current day towards the vertical center of the display.
The ability of the device to provide multiple navigational paths is beneficial in that it permits a user to invoke the most suitable device behavior for particular usage cases. The ability is also beneficial in battery operated devices in that short-cutting through intermediate user interface screens can reduce processor drain thereby conserving battery life.
Optionally, the displayed affordances may include an affordance for initiating a phone call to a contact that is associated with the calendar entry, such as an event organizer. Optionally, the displayed affordances may include an affordance for initiating an e-mail draft to the contact. The phone call and the e-mail draft may be initiated on device 500, or device 500 may instruct a companion device, such as a cellular phone or a laptop computer, to initiate the phone call and/or the e-mail draft.
Optionally, at block 2804, the device may detect a touch on the touch-sensitive display having a characteristic intensity, where the touch has a characteristic intensity. The device may determine whether the characteristic intensity is above a threshold intensity. The device may, in response to a determination that the characteristic intensity is above the threshold intensity, display an accept affordance for accepting the calendar entry and a decline affordance for declining the calendar entry. The device may detect a user selection of the accept affordance.
Optionally, at block 2804, the device may detect a user selection of the first calendar entry. In response to detecting the user selection of the first calendar entry, the device may: (i) display a time and location of the calendar entry; and (ii) display an accept affordance for accepting the calendar entry. Further, the device may detect a user selection of the accept affordance.
In some embodiments, processing unit 3408 is configured to detect a user input (e.g., detecting a touch gesture or other button input with the detecting unit 3410) on a graphical user interface object, and display relevant calendar information in accordance with the calendar instruction.
For example, in some embodiments, in response to a touch on a calendar, application icon, graphics processing unit 3412 will cause display unit 3402 to display a sequence of user interface screens (e.g., year screen, to month screen, to day screen). As another example, in some embodiments, in response to a movement of a rotatable input mechanism, graphics processing unit 3412 will cause display unit 3402 to displaying cycle through the display of individual user interface screens (e.g., year screen, month screen, day screen). Calendar management unit 3414 may identify relevant information to be displayed on each screen. In some embodiments, calendar management unit 3414 may progressively present an increasing amount of information to a user as the user focuses on a particular day's activities.
As yet another example, in some embodiments, input/output unit 3404 may be able to determine the intensities of touch contacts. In response to a high-intensity contact, graphics processing unit 3412 may cause display unit 3402 to present additional user interface features. For instance, a user may able to invoke graphical user interface affordances for accepting or declining calendar invitations using a high-intensity contact(s). A user may also be able to invoke graphical user interface affordances for contacting (e.g., e-mailing and/or calling) other members of a calendar entry, such as an event organizer associated with the calendar entry.
As still yet another example, in some embodiments, calendar management unit 3414 may maintain a list of calendar entries that a user has responded to and those that the user has not responded to. Calendar management unit 3414, in conjunction with graphics processing unit 3412, may cause display unit 3402 to present calendar entries that still require a user's response in one region of the user interface screen, and to present calendar entries that the user has already dealt with in another region.
As still yet another example, in some embodiments, graphics processing unit 3412 will cause display unit 3402 to visually emphasize and de-emphasized displayed days, months, and/or years. Calendar management unit 3414 may recognize a visually emphasized day/month/year as being information that is relevant to the user. For instance, a user may use one input modality (e.g., touch) to emphasize a particular month among displayed months, and use another input modality (e.g., movement of a rotatable input mechanism) to retrieve more information about the particular month.
In accordance with some embodiments,
As shown in
The processing unit 3506 is configured to enable display (e.g., with the display enabling unit 3508) of, on the display unit 3502, an icon representing a calendar application; detect (e.g., with the detecting unit 3510) user input; in response to a determination that the detected user input represents a touch on the displayed icon, launch (e.g., with the launching unit 3512) the calendar application and transition (e.g., with the transitioning unit 3514) from the display of the icon, through at least one intermediate user interface screen, to enable display of a landing screen of the calendar application; and in response to a determination that the detected user input represents movement of a rotatable input mechanism, launch (e.g., with the launching unit 3512) the calendar application and transitioning from the display of the icon directly to enable display of the landing screen of the calendar application.
In some embodiments, enabling display of the landing screen of the calendar application comprises enabling display of at least one calendar entry scheduled for the current day.
In some embodiments, transitioning through the at least one intermediate user interface screen comprises enabling display of an intermediate user interface screen having text representing at least some days of the current month.
In some embodiments, the user input is a first user input representing a first movement of the rotatable input mechanism, and the processing unit 3506 is further configured to detect (e.g., with the detecting unit 3510) a second user input representing a second movement of the rotatable movement mechanism; and in response to detecting the second user input, enable display (e.g., with the display enabling unit 3508) of text representing at least some days of the current month.
In some embodiments, the processing unit 3506 is further configured to enable display (e.g., with the display enabling unit 3508) of an indicator indicating the current day in the current month.
In some embodiments, enabling display of the icon representing the calendar application comprises enabling display of a plurality of other icons representing other software applications and enabling display of the icon representing the calendar application as the center-most icon on-screen among the displayed icons.
In some embodiments, enabling display of the text that represents the current day in the current month comprises enabling display of the text substantially centered on-screen in the vertical direction.
In some embodiments, the processing unit 3506 is further configured to detect (e.g., with the detecting unit 3510) user selection of a calendar entry of the at least one calendar entry scheduled for the current day, and in response to detecting user selection of the calendar entry, enable display (e.g., with the display enabling unit 3508) of a time and location of the selected calendar entry.
In some embodiments, the processing unit 3506 is further configured to detect (e.g., with the detecting unit 3510) a touch on the touch-sensitive surface unit 3504 while enabling display of the time and location of the selected calendar entry, the touch having a characteristic intensity; determine (e.g., with the determining unit 3516) whether the characteristic intensity of the touch is above a threshold intensity; and in response to a determination that the characteristic intensity of the touch is above the threshold intensity, enable display (e.g., with the display enabling unit 3508) of, on the display unit 3502, an affordance for accepting the calendar entry.
In some embodiments, the processing unit 3506 is further configured to, in response to a determination that the characteristic intensity of the touch is not above the threshold intensity, enable display (e.g., with the display enabling unit 3508) of additional information regarding the selected calendar entry.
In some embodiments, enabling display of at least one calendar entry scheduled for the current day comprises enabling display of at least one affordance representing the at least one calendar entries scheduled for the current day; detecting user input representing a zoom-in command; and in response to detecting the user input representing the zoom-in command, enlarging the at least one affordance, and enabling display of additional text inside the at least one affordance indicating details of at least one represented calendar entry.
In some embodiments, enabling display of at least one calendar entry scheduled for the current day comprises enabling display of an affordance representing at least two calendar entries scheduled for the current day; detecting user input on the displayed affordance; and in response to detecting the user input on the displayed affordance, enabling display of at least two affordances representing the at least two calendar entries.
In some embodiments, enabling display of additional text comprises enabling display of calendar entry information selected from the group consisting of calendar entry time, location, and organizer.
In some embodiments, the affordance representing the calendar application is a contiguous region visually distinguishable from a background of the calendar application.
The operations described above with reference to
In accordance with some embodiments,
As shown in
The processing unit 3606 is configured to enable display (e.g., with the display enabling unit 3608) of, on the display unit 3602, an affordance representing a calendar application; detect (e.g., with the detecting unit 3610) user input; in response to detecting the user input, (a) in accordance with a determination that the detected user input is a touch on the displayed affordance: enable display (e.g., with the display enabling unit 3608) of a first text indicating at least two months in a year, then, replace (e.g., with the replacing unit 3612) the display of the first text with a display of a second text indicating at least some days in one and only one month of the year, and then, replace (e.g., with the replacing unit 3612) the display of the second text with a display of at least one affordance representing at least one calendar entry; and (b) in accordance with a determination that the detected user input is a movement of a rotatable input mechanism: enable display (e.g., with the display enabling unit 3608) of at least one affordance representing at least one calendar entry.
In some embodiments, the movement of the rotatable input mechanism is a first movement of the rotatable input mechanism, the processing unit 3606 further configured to detect (e.g., with the detecting unit 3610) a second movement of the rotatable input mechanism; and in response to detecting the second movement, replace (e.g., with the replacing unit 3612) the display of the at least one affordance representing the at least one calendar entry with a display of the second text indicating the at least some days in the one and only one month of the year.
In some embodiments, the processing unit 3606 is further configured to detect (e.g., with the detecting unit 3610) a third movement of the rotatable input mechanism; and in response to detecting the third movement, replace (e.g., with the replacing unit 3612) the display of the second text with a display of the first text indicating the at least two months in the year.
In some embodiments, replacing the display of the first text with the second text occurs automatically after the first text is displayed for a predetermined amount of time.
In some embodiments, replacing the display of the second text with the at least one affordance representing at least one calendar entry occurs automatically after the second text is displayed for the predetermined amount of time.
In some embodiments, the at least one calendar entry is scheduled for the current day.
In some embodiments, the first text indicating the at least two months comprises text indicating the names of the at least two months including the current month and a plurality of numerals indicating at least some days of the current month, where the text and the plurality of numerals associated with the current month are displayed such that, as a unit, they span the vertical center of the display unit 3602.
In some embodiments, the second text indicating the at least some days in the one and only month comprises a plurality of numerals indicating at least some days of the current month, including the current day, where the display of the numeral indicating the current day spans the vertical center of the display unit 3602.
In some embodiments, the at least one affordance representing the at least one calendar entry is a contiguous region visually distinguishable from a background of the calendar application.
In some embodiments, (a) and (b) are both performed.
The operations described above with reference to
In accordance with some embodiments,
As shown in
The processing unit 3706 is configured to enable display (e.g., with the display enabling unit 3708) of, on the display unit 3702, an affordance representing a calendar application; detect (e.g., with the detecting unit 3710) user input; in response to detecting the user input, (a) in accordance with a determination that the detected user input is a touch on the displayed affordance: enable display (e.g., with the display enabling unit 3708) of a first text indicating at least two months in a year, then, replace (e.g., with the replacing unit 3712) the display of the first text with a display of a second text indicating at least some days in one and only one month of the year, and then, replace (e.g., with the replacing unit 3712) the display of the second text with a display of at least one affordance representing at least one calendar entry; and (b) in accordance with a determination that the detected user input is a movement of a rotatable input mechanism, enable display (e.g., with the display enabling unit 3708) of the first text indicating at least two months in a year.
In some embodiments, the movement of the rotatable input mechanism is a first movement of the rotatable input mechanism, the processing unit 3706 further configured to detect (e.g., with the detecting unit 3710) a second movement of the rotatable input mechanism; and in response to detecting the second movement, replace (e.g., with the replacing unit 3712) the display of the first text with a display of the second text indicating the at least some days in the one and only one month of the year.
In some embodiments, the processing unit 3706 is further configured to detect (e.g., with the detecting unit 3710) a third movement of the rotatable input mechanism; and in response to detecting the third movement, replace (e.g., with the replacing unit 3712) the display of the second text with a display of the at least one user interface object representing the at least one calendar entry.
In some embodiments, replacing the display of the first text with the second text occurs automatically after the first text is displayed for a predetermined amount of time.
In some embodiments, replacing the display of the second text with the at least one user interface object representing at least one calendar entry occurs automatically after the second text is displayed for the predetermined amount of time.
In some embodiments, the at least one calendar entry is scheduled for the current day.
In some embodiments, the first text indicating the at least two months comprises text indicating the names of the at least two months including the current month, and a plurality of numerals indicating at least some days of the current month, where the text and the plurality of numerals associated with the current month are displayed such that, as a unit, they span the vertical center of the display unit 3702.
In some embodiments, the second text indicating the at least some days in the one and only month comprises a plurality of numerals indicating at least some days of the current month, including the current day, where the display of the numeral indicating the current day spans the vertical center of the display unit 3702.
In some embodiments, the at least one affordance representing the at least one calendar entry is a contiguous region visually distinguishable from a background of the calendar application.
In some embodiments, (a) and (b) are both performed.
The operations described above with reference to
In accordance with some embodiments,
As shown in
The processing unit 3806 is configured to enable display (e.g., with the display enabling unit 3808) of an affordance representing a calendar entry in a calendar application; detect (e.g., with the detecting unit 3810) a touch on the display, the touch having a characteristic intensity, the touch located at the displayed user interface object representing the calendar entry; determine (e.g., with the determining unit 3812) whether the characteristic intensity of the touch is below a threshold intensity; in response to a determination that the characteristic intensity of the touch is below the threshold intensity, enable display (e.g., with the display enabling unit 3808) of a time and a location associated with the calendar entry; and in response to a determination that the characteristic intensity of the touch is not below the threshold intensity, enable display (e.g., with the display enabling unit 3808) of, on the display unit 3802, a plurality of affordances representing functions of the calendar application.
In some embodiments, the processing unit 3806 is further configured to, in response to a determination that the characteristic intensity of the first touch is not below the threshold intensity, enable display (e.g., with the display enabling unit 3808) of, on the display unit 3802, an affordance for creating a calendar entry.
In some embodiments, enabling display of the plurality of affordances representing functions of the calendar application comprises enabling display of an affordance that, when selected, sends an instruction to another electronic device instructing the other electronic device to display a calendar entry.
In some embodiments, enabling display of the plurality of affordances representing functions of the calendar application comprises displaying an affordance that, when selected, displays a phone number associated with a calendar entry.
In some embodiments, the processing unit 3806 is further configured to detect (e.g., with the detecting unit 3810) user selection of the affordance for enable display of the phone number; and in response to detecting the user selection, send (e.g., with the sending unit 3814) an instruction to another electronic device instructing the other electronic device to initiate a phone call to the phone number.
In some embodiments, the processing unit 3806 is further configured to detect (e.g., with the detecting unit 3810) user selection of the affordance for enable display of the phone number, and, in response to detecting the user selection, initiate (e.g., with the initiating unit 3816) a phone call to the phone number.
In some embodiments, the phone number is associated with an organizer of the calendar entry.
In some embodiments, enabling display of the plurality of affordances representing functions of the calendar application comprises enabling display of an affordance that, when selected, displays an e-mail address associated with a calendar entry.
In some embodiments, the processing unit 3806 is further configured to detect (e.g., with the detecting unit 3810) user selection of the affordance for enable display of the e-mail address and in response to detecting the user selection, send (e.g., with the sending unit 3814) an instruction to another electronic device instructing the other electronic device to create an e-mail draft, the e-mail draft listing the displayed email address as a recipient.
In some embodiments, the processing unit 3806 is further configured to detect (e.g., with the detecting unit 3810) user selection of the affordance for enable display of the e-mail address and, in response to detecting the user selection, create (e.g., with the creating unit 3818) an e-mail draft, the e-mail draft listing the displayed email address as a recipient.
In some embodiments, the e-mail address is associated with an organizer of the calendar entry.
In some embodiments, the other device is a cellular phone.
The operations described above with reference to
In accordance with some embodiments,
As shown in
The processing unit 3906 is configured to enable display (e.g., with the display enabling unit 3908) of, on the display unit 3902, a plurality of calendar entries, the plurality of calendar entries including a first calendar entry and a second calendar entry, the first calendar entry displayed above the second calendar entry; receive (e.g., with the receiving unit 3910) user input representing user acceptance of the first calendar entry; and in response to receiving the user input, enable display (e.g., with the display enabling unit 3908) of the first calendar entry below the second calendar entry.
In some embodiments, receiving user input representing user acceptance of the first calendar entry comprises detecting a touch on the touch-sensitive surface unit 3904 having a characteristic intensity, the touch having a characteristic intensity; determining whether the characteristic intensity is above a threshold intensity; and in response to a determination that the characteristic intensity is above the threshold intensity, enabling display of an accept affordance for accepting the calendar entry and an decline affordance for declining the calendar entry; and detecting a user selection of the accept affordance.
In some embodiments, the processing unit 3906 is further configured to, in response to a determination that the characteristic intensity is not above the threshold intensity, enable display (e.g., with the display enabling unit 3908) of a time and location of the calendar entry.
In some embodiments, receiving user input representing user acceptance of the first calendar entry comprises detecting a user selection of the first calendar entry; in response to detecting the user selection of the first calendar entry, enabling display of a time and location of the calendar entry and enabling display of an accept affordance for accepting the calendar entry; and detecting a user selection of the accept affordance.
In some embodiments, the processing unit 3906 is further configured to in response to detecting the user selection of the accept affordance, enable display (e.g., with the display enabling unit 3908) of a visual indication indicating acceptance of the calendar entry.
In some embodiments, the visual indication comprises a message confirming acceptance of the calendar entry.
In some embodiments, enabling display of the plurality of calendar entries comprises enable display of calendar entries scheduled for different days.
The operations described above with reference to
In accordance with some embodiments,
As shown in
The processing unit 4006 is configured to enable display (e.g., with the display enabling unit 4008) of, on the display unit 4002, a first user interface screen having a plurality of calendar entries; receive (e.g., with the receiving unit 4010) first data representing user acceptance of a first calendar entry of the plurality of calendar entries; in response to receiving the first data, enable removal (e.g., with the removal enabling unit 4012) of the accepted first calendar entry from the first user interface screen; receive (e.g., with the receiving unit 4010) second data representing a user input; and in response to receiving the second data, replace (e.g., with the replacing unit 4014) the display of the first user interface screen with a display of a second user interface screen having a plurality of accepted calendar entries.
In some embodiments, the user input is a movement of a rotatable input mechanism of the electronic device.
In some embodiments, the user input is a swipe on the touch-sensitive surface unit 4004 in a substantially horizontal direction.
In some embodiments, receiving first data representing user acceptance of the first calendar entry comprises detecting a touch on the touch-sensitive surface unit 4004, the touch having a characteristic intensity; determining whether the characteristic intensity is above a threshold intensity; in response to a determination that the characteristic intensity is above the threshold intensity, enabling display of an accept affordance for accepting the calendar entry and an decline affordance for declining the calendar entry; and detecting a user selection of the accept affordance.
In some embodiments, the processing unit 4006 is further configured to, in response to a determination that the characteristic intensity is not above the threshold intensity, enable display (e.g., with the display enabling unit 4008) of a time and location of the calendar entry.
In some embodiments, receiving first data representing user acceptance of the first calendar entry comprises detecting a user selection of the first calendar entry; in response to detecting the user selection, enabling display of a time and location of the calendar entry and an accept affordance for accepting the calendar entry; and receiving a user selection of the accept affordance.
In some embodiments, the first and second user interface screens each include an affordance indicating the currently displayed user interface screen and a position of the displayed user interface screen within a sequence of the user interface screens.
The operations described above with reference to
In accordance with some embodiments,
As shown in
The processing unit 4106 is configured to enable display (e.g., with the display enabling unit 4108) of a user interface screen on the display unit 4102, where the displayed user interface screen includes a plurality of texts indicating a plurality of months in a year, the texts of the plurality of texts are organized according to a layout having at least two rows and at least two columns, and the plurality of texts have an initial visual characteristic; detect (e.g., with the detecting unit 4110) a user selection of a first text of the plurality of texts, the first text indicating a first month of the plurality of months; and in response to detecting the user selection, enable change (e.g., with the change enabling unit 4112) of the visual characteristic of the plurality of texts except the first text indicating the first month.
In some embodiments, the processing unit 4106 is further configured to detect (e.g., with the detecting unit 4110) a movement of the user selection of the first text, and in response to detecting the movement: enable change (e.g., with the change enabling unit 4112) of the visual characteristic of the first text indicating the first month and enable return (e.g., with the return enabling unit 4114) of the visual characteristic of a second text indicating a second month of the plurality of months to its initial visual characteristic.
In some embodiments, the first text and the second text represent consecutive months in the year.
In some embodiments, the user selection is a touch on the touch-sensitive surface unit 4104 at a position of the displayed first text.
In some embodiments, the movement is a swipe of the touch.
In some embodiments, the movement is a substantially vertical movement.
In some embodiments, the processing unit 4106 is further configured to detect (e.g., with the detecting unit 4110) a release of the user selection of the first text and in response to detecting the release, enable designation (e.g., with the designation enabling unit 4116) the second text indicating the second month as having focus.
In some embodiments, the processing unit 4106 is further configured to, in response to detecting the release, enable return (e.g., with the return enabling unit 4114) of the visual characteristic of the plurality of texts to the initial visual characteristic, except the second text.
In some embodiments, the change in visual characteristic comprises the visual effect of dimming.
In some embodiments, the change in visual characteristic comprises the visual effect of greying.
In some embodiments, the change in visual characteristic comprises increasing translucency.
In some embodiments, the change in visual characteristic comprises the visual effect of darkening.
The operations described above with reference to
In accordance with some embodiments,
As shown in
The processing unit 4206 is configured to enable display (e.g., with the display enabling unit 4208) of a row of numerals, the numerals indicating days in a month; detect user input; and in response to detecting the user input, enable translation (e.g., with the translation enabling unit 4210) of all but one of the displayed numerals from its respective position in the row into a new position, where the displayed numerals, in their new positions, form a column of numerals.
In some embodiments, the numerals displayed in the new position represent days in one week of the month.
In some embodiments, a numeral of the numerals is associated with a day of a week, the processing unit 4206 further configured to, after the translating, label (e.g., with the labeling unit 4212) the numeral with text identifying a day of the week.
In some embodiments, the processing unit 4206 is further configured to enable translation (e.g., with the translation enabling unit 4210) of the one remaining numeral from its position in the row of numerals to a position in the column of numerals.
In some embodiments, the user input is a movement of a rotatable input mechanism of the electronic device.
In some embodiments, enabling translation comprises enabling translation at least one displayed numeral visibly on the display unit 4202.
In some embodiments, the row of numerals is a first row of numerals, the processing unit 4306 further configured to enable display (e.g., with the display enabling unit 4208) of a second row of numerals representing additional days in the month; in response to detecting the user input, enable translation of (e.g., with the translation enabling unit 4210) the second row of numerals towards one or more edges of the display unit 4202; and cease (e.g., with the ceasing unit 4214) to enable display of the second row of numerals.
The operations described above with reference to
In accordance with some embodiments,
As shown in
The processing unit 4306 is configured to enable display (e.g., with the display enabling unit 4308) of on the display unit 4302: text indicating hours in a day, at least one region representing a calendar entry scheduled during the indicated hours, and text inside the at least one region indicating a name of the calendar entry; detect (e.g., with the detecting unit 4310) user input representing a zoom-in or zoom-out command; in accordance with a determination that the user input represents a zoom-in command: enable enlargement of (e.g., with the enlargement enabling unit 4312) the at least one region, and enable display (e.g., with the display enabling unit 4308) of additional text inside the at least one region indicating details of the calendar entry.
In some embodiments, enabling display of additional text comprises enabling display of one or more calendar entry information selected from the group consisting of calendar entry time, location, and organizer.
In some embodiments, the size of the enlarged at least one region is proportional to the duration of the calendar entry
In some embodiments, detecting user input comprises receiving data representing movement of a rotatable input mechanism of the electronic device.
In some embodiments, detecting user input comprises receiving data representing a de-pinching or pinching gesture on the touch-sensitive surface unit 4304.
In some embodiments, the processing unit 4306 is further configured to, in accordance with a determination that the user input represents a zoom-out command, enable removal (e.g., with the removal enabling unit 4314) of the display of the text indicating days of the month and the user interface object.
In some embodiments, the processing unit 4306 is further configured to, in accordance with a determination that the user input represents a zoom-out command: enable reduction (e.g., with the reduction enabling unit 4316) of the size of the at least one region representing a calendar entry.
In some embodiments, the processing unit 4306 is further configured to, in accordance with a determination that the user input represents a zoom-out command, enable display (e.g., with the display enabling unit 4308) of a count of calendar entries within a time interval.
In some embodiments, the time interval is a month or a year.
The operations described above with reference to
In accordance with some embodiments,
As shown in
The processing unit 4406 is configured to enable display (e.g., with the display enabling unit 4408) of, on the display unit 4402, an application affordance representing a calendar application; detect (e.g., with the detecting unit 4410) a user selection of the application affordance; and in response to detecting the user selection of the application affordance: launch (e.g., with the launching unit 4412) the calendar application, enable display (e.g., with the display enabling unit 4408) of a first event affordance representing a first calendar entry, and enable display (e.g., with the display enabling unit 4408) of a second event affordance representing a second calendar entry, where the second calendar entry is longer in duration than the first calendar entry, but the size of the first event affordance is larger than the size of the second event affordance.
In some embodiments, the second calendar entry is an all-day calendar entry.
In some embodiments, the processing unit 4406 is further configured to detect (e.g., with the detecting unit 4410) user selection of the second event affordance and, in response to detecting the user selection of the second event affordance, enable enlargement (e.g., with the enlargement enabling unit 4414) of the second affordance.
In some embodiments, the enlarged second affordance includes text representing the name of the second calendar entry.
In some embodiments, only one of the first affordance and the second affordance includes text representing a name of the first calendar entry.
In some embodiments, the second event affordance representing the all-day calendar entry is displayed on top of all other displayed affordances representing calendar entries.
In some embodiments, detecting user selection of the second event affordance comprises detecting a touch on the touch-sensitive surface unit 4404 at a position of the displayed second event affordance.
In some embodiments, wherein detecting user selection of the second event affordance comprises detecting a touch on the touch-sensitive surface unit 4404 at a position of the displayed second event affordance and a movement of the touch.
In some embodiments, detecting user selection of the second event affordance comprises detecting a touch on the touch-sensitive surface unit 4404 at a position of the displayed second event affordance and a movement of the touch above a threshold distance.
The operations described above with reference 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 techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
Although the disclosure and examples have been fully described with reference to the accompanying figures, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the appended claims.
This application is the continuation of U.S. application Ser. No. 14/752,776, “REDUCED SIZE USER INTERFACE,” filed Jun. 26, 2015, which claims the benefit of priority of U.S. Provisional Application Ser. No. 62/129,848, “Reduced Size User Interface,” filed Mar. 8, 2015; U.S. Provisional Application Ser. No. 62/047,611, “Reduced Size User Interface,” filed Sep. 8, 2014; and U.S. Provisional Application Ser. No. 62/018,529, “Reduced Size User Interface,” filed Jun. 27, 2014. The content of these applications is hereby incorporated by reference in its entirety for all purposes. This application relates to the following applications: International Patent Application Serial No. PCT/US2013/040061, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013; International Patent Application Serial No. PCT/US2013/069483, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013; and U.S. Patent Application No. 62/005,958, “Canned Answers in Messages,” filed May 30, 2014. The content of these applications is hereby incorporated by reference in its entirety for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| 62018529 | Jun 2014 | US | |
| 62047611 | Sep 2014 | US | |
| 62129848 | Mar 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14752776 | Jun 2015 | US |
| Child | 16265938 | US |
