The present disclosure relate generally to user interfaces of electronic devices, and more specifically to techniques for sharing a user's location.
Text messaging is a common form of communication. Recently, text messaging has expanded to include additional functionality, including the ability to share location information between participants in a message conversation. Some methods for sharing location information can be, however, difficult and/or inefficient.
In some instances, many steps are required to share location, and these steps generally take the user away from the message transcript. In some instances, participants may want to share locations for a prolonged period of time. In such instances, the user repeats the steps to share location information each time a location update is desired, detracting from the user's messaging experience. Moreover, inefficiency, particularly on battery-powered mobile devices, may waste energy and increase the need for recharging.
Accordingly, there is a need for electronic devices with faster, more efficient methods and interfaces for sharing message participants' location information. Such methods and interfaces optionally complement or replace other methods for sharing location information. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.
In some embodiments, a method for sharing location information during a message conversation includes: at an electronic device comprising a touch-sensitive surface and a display: displaying, on the display, a message region; displaying, in the message region, messages sent between a first participant and a second participant in a message conversation; detecting a location-sharing request from the first participant to share first participant location information with the second participant; in response to detecting the location-sharing request from the first participant: enabling the second participant to obtain the first participant location information during a predetermined location-sharing time period, wherein the predetermined location-sharing time period is scheduled to end at a first time; detecting interaction by one of the first participant and the second participant with the message conversation during the predetermined location-sharing time period; and in response to detecting interaction by one of the first participant and the second participant with the message conversation during the predetermined location-sharing time period: extending the predetermined location-sharing time period to end at a second time that is after the first time.
In some embodiments, a method for sharing location information during a message conversation includes: at an electronic device comprising a touch-sensitive surface and a display: displaying, on the display, a message region; displaying, in the message region, messages sent between a first participant and a second participant in a message conversation; receiving a first location-sharing notification that first participant location information is being shared with the second participant for a predetermined location-sharing time period, wherein the predetermined location-sharing time period is scheduled to end at a first time; sending a message to the first participant; and receiving a second location-sharing notification that first participant location information is being shared with the second participant for an extended location-sharing time period, wherein the extended location-sharing time period is scheduled to end at a second time that is after the first time.
In some embodiments, a method for sharing location information during a message conversation includes: at an electronic device comprising a touch-sensitive surface and a display: displaying, on the display, a message region; displaying, at a first position in the message region, a bottom portion of a message transcript of messages sent between a first participant and a second participant; detecting contact on a location corresponding to the message transcript; detecting movement of the contact across the touch-sensitive surface and toward a top portion of the message region; and in response to detecting movement of the contact across the touch-sensitive surface and toward a top portion of the message region: displaying the bottom portion of the message transcript at a second position in the message region above the first position; and displaying a location-sharing affordance at the first position.
In some embodiments, a method for sharing location information during a message conversation includes: at an electronic device comprising a touch-sensitive surface and a display: displaying, on the display, a message region; displaying, in the message region, a message transcript of messages sent between a first participant and a second participant; displaying, at a first position in the message transcript, a shared-location affordance; while displaying the shared-location affordance at the first position, detecting a request to scroll the message transcript; in response to detecting the request to scroll the message transcript: determining whether the request to scroll the message transcript comprises a request to scroll the shared-location affordance beyond the message region; in accordance with a determination that the request to scroll the message transcript comprises a request to scroll the shared-location affordance beyond the message region: discontinuing display of the shared location in the message transcript; and displaying a location-sharing status bar outside the message region; and in accordance with a determination that the request to scroll the message transcript does not comprise a request to scroll the shared-location affordance beyond the message region: displaying the shared-location affordance at a second location in the message transcript.
In some embodiments, a method for sharing location information during a message conversation includes: at an electronic device comprising a touch-sensitive surface and a display: displaying, on the display, a message region; displaying, in the message region, a message transcript of messages sent between a first participant and a second participant; displaying a shared-location affordance in the message region, wherein the shared-location affordance is displayed below and adjacent to the message transcript, and wherein the shared-location affordance comprises a representation of a location of the first participant.
In some embodiments, a method for sharing location information during a message conversation includes: at an electronic device comprising a touch-sensitive surface and a display: displaying, on the display, a message region for displaying a message transcript of messages sent between a first participant and a second participant in a message conversation; displaying a location-sharing affordance; detecting a selection of the location-sharing affordance, wherein detecting a selection of the location-sharing affordance by the first participant consists of detecting a single contact by the first participant; and in response to detecting a selection of the location-sharing affordance: enabling the second participant to obtain the first participant location information; and displaying a modified location-sharing affordance.
In some embodiments, a non-transitory computer-readable storage medium has stored therein instructions which when executed by an electronic device with a display, causes the device to perform any of the methods described above. In some embodiments, an electronic device includes: a display and means for performing any of the methods described above. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a display, includes means for performing any of the methods described above.
In some embodiments, a multifunction device includes one or more processors; memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: displaying a message region; displaying, in the message region, messages sent between a first participant and a second participant in a message conversation; detecting a location-sharing request from the first participant to share first participant location information with the second participant; in response to detecting the location-sharing request from the first participant: enabling the second participant to obtain the first participant location information during a predetermined location-sharing time period, wherein the predetermined location-sharing time period is scheduled to end at a first time; detecting interaction by one of the first participant and the second participant with the message conversation during the predetermined location-sharing time period; and in response to detecting interaction by one of the first participant and the second participant with the message conversation during the predetermined location-sharing time period: extending the predetermined location-sharing time period to end at a second time that is after the first time.
In some embodiments, a multifunction device includes one or more processors; memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: displaying a message region; displaying, in the message region, messages sent between a first participant and a second participant in a message conversation; receiving a first location-sharing notification that first participant location information is being shared with the second participant for a predetermined location-sharing time period, wherein the predetermined location-sharing time period is scheduled to end at a first time; sending a message to the first participant; and receiving a second location-sharing notification that first participant location information is being shared with the second participant for an extended location-sharing time period, wherein the extended location-sharing time period is scheduled to end at a second time that is after the first time.
In some embodiments, a multifunction device includes one or more processors; memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: displaying a message region; displaying, in the message region, messages sent between a first participant and a second participant in a message conversation; receiving a first location-sharing notification that first participant location information is being shared with the second participant for a predetermined location-sharing time period, wherein the predetermined location-sharing time period is scheduled to end at a first time; sending a message to the first participant; and receiving a second location-sharing notification that first participant location information is being shared with the second participant for an extended location-sharing time period, wherein the extended location-sharing time period is scheduled to end at a second time that is after the first time.
In some embodiments, a multifunction device includes one or more processors; memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: displaying a message region; displaying, at a first position in the message region, a bottom portion of a message transcript of messages sent between a first participant and a second participant; detecting contact on a location corresponding to the message transcript; detecting movement of the contact across the touch-sensitive surface and toward a top portion of the message region; and in response to detecting movement of the contact across the touch-sensitive surface and toward a top portion of the message region: displaying the bottom portion of the message transcript at a second position in the message region above the first position; and displaying a location-sharing affordance at the first position.
In some embodiments, a multifunction device includes one or more processors; memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: displaying a message region; displaying, in the message region, a message transcript of messages sent between a first participant and a second participant; displaying, at a first position in the message transcript, a shared-location affordance; while displaying the shared-location affordance at the first position, detecting a request to scroll the message transcript; in response to detecting the request to scroll the message transcript: determining whether the request to scroll the message transcript comprises a request to scroll the shared-location affordance beyond the message region; in accordance with a determination that the request to scroll the message transcript comprises a request to scroll the shared-location affordance beyond the message region: discontinuing display of the shared location in the message transcript; and displaying a location-sharing status bar outside the message region; and in accordance with a determination that the request to scroll the message transcript does not comprise a request to scroll the shared-location affordance beyond the message region: displaying the shared-location affordance at a second location in the message transcript.
In some embodiments, a multifunction device includes one or more processors; memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: displaying, on the display, a message region for displaying a message transcript of messages sent between a first participant and a second participant in a message conversation; displaying a location-sharing affordance; detecting a selection of the location-sharing affordance, wherein detecting a selection of the location-sharing affordance by the first participant consists of detecting a single contact by the first participant; and in response to detecting a selection of the location-sharing affordance: enabling the second participant to obtain the first participant location information; and displaying a modified location-sharing affordance.
Thus, electronic devices are provided for easy location sharing in message conversation, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. The methods and interfaces provided may complement or replace conventional methods and interfaces for location sharing.
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
There is a need for electronic devices with faster, more efficient methods and interfaces for sharing location information of participants in a message conversation. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.
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” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a 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 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.
Peripherals interface 118 are optionally 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 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The 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 is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch 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 optionally disengages a lock of touch screen 112 or optionally begins 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) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. 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 optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds 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 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally 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, California
A touch-sensitive display in some embodiments of touch screen 112 is, optionally, 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 is 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 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes 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 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch 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 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes 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 is 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 optionally adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display is optionally 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 is, optionally, 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 module 138 for use in location-based dialing; to camera module 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, 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 are, optionally, 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 module 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 are, optionally, 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 optionally uses any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch 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 optionally 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 are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch 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 are, optionally, 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 are, optionally, 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 are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, 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 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 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 optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (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 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 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 optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first 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 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 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In some embodiments, 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 are, optionally, implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples that 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.
Exemplary techniques for detecting and processing touch intensity are 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, published as WIPO Publication No. WO/2013/169849, 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, published as WIPO Publication No. WO/2014/105276, 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 permit device 500 to be worn by a user.
Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes 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 is, optionally, operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 optionally includes one or more non-transitory computer-readable storage mediums, 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 below, including processes 700, 900, 1200, 1500, 1800, and 2000 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, 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 optionally includes 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 optionally receives 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 is, optionally, 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 is, optionally, 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 is, optionally, 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.
Attention is now directed toward embodiments of message user interfaces for sharing location information of participants in a message conversation.
Exemplary user interfaces and processes for sharing location information between message conversation participants are disclosed in U.S. application Ser. No. 14/503,376, filed Sep. 30, 2014 and titled “Message User Interfaces for Capture and Transmittal of Media and Location Content”, the contents of which are hereby incorporated by reference in their entirety.
A scheduled end 614 of the predetermined location-sharing time period is included below the map. In some embodiments, the predetermined location-sharing time period is displayed elsewhere, such as in banner 604 for example. In the embodiment of
A shared-location affordance 616 is displayed to indicate that first participant location information is currently shared with the second participant. As used herein, a location-sharing affordance can be understood to include a user-interactive graphical user interface object that permits a user to share location information by interacting with the object. As used herein, a shared-location affordance can be understood to include a user-interactive graphical user interface object that permits a user to stop sharing location information by interacting with the object.
In the embodiment of
In some embodiments, a map view (e.g., map 612) is provided to indicate location information is currently shared. In the embodiment of
In some embodiments, the text associated with the indication of location sharing is displayed adjacent to a map within a bounded message region. In other embodiments, the text is not contained within a bounded message region. The text is optionally displayed below the most recent message received from the participant sharing the location information and aligned to that message, for example. In some embodiments, the text is displayed such that it is horizontally centered within the transcript and vertically positioned between messages in the conversation.
When one of the first participant and the second participant interact with the message conversation during the predetermined location-sharing time period, the predetermined location-sharing time period is optionally extended to end at a second time that is after the first time.
Advantageously, this allows users to continue sharing location during a single conversation but ends location sharing after the conversation has ended to preserve privacy without requiring a user to explicitly indicate that the conversation has ended. At the same time, in embodiments in which a participant's location is updated periodically, users receive up-to-date location information for one or more participants, which may be preferable to static location information. This also improves the user's experience when the user is not required to remember to stop sharing indefinitely-shared location information when first participant information is no longer necessary for the second participant. The user is also not required to repeatedly share one-off location information when first participant information is necessary for the second participant. This reduces battery usage as users are not required to repeatedly access and select location-sharing via the user interface.
In some embodiments, the predetermined location-sharing time period is extended only when one of the participants adds content to the conversation (e.g., by sending a new message). In some embodiments, the extended time period is shorter than the predetermined location-sharing time period. In the examples displayed in
In some embodiments, the location-sharing time period is further extended after one of the first and second participant interacts with the message conversation during the already extended location-sharing time period.
The process of further extending the location-sharing time period is optionally repeated any number of times. This optionally allows users to continue sharing location during a single conversation but ends location sharing after the conversation has ended to preserve privacy without requiring a user to explicitly indicate that the conversation has ended.
Advantageously, this allows users to continue sharing location during a single conversation but ends location sharing after the conversation has ended to preserve privacy without requiring a user to explicitly indicate that the conversation has ended. This also improves the user's experience when the user is not required to remember to stop sharing indefinitely-shared location information when first participant information is no longer necessary for the second participant. The user is also not required to repeatedly share one-off location information when first participant information is necessary for the second participant. This reduces battery usage as users are not required to repeatedly access and select location-sharing via the user interface.
In some embodiments, device 600 determines whether or not to extend the location-sharing time period based on whether the interaction occurred after the location-sharing time period has ended.
In the embodiment of
In some embodiments, device 600 determines that the predetermined location-sharing time period has ended and, in response to the determination, displays an indication in the message conversation that the location of the first participant is not being shared with the second participant. In some embodiments, the indication includes a greyed out map (such as 628) or an empty caret (such as 632). In some embodiments, if an indication of a user's location was displayed in a message transcript when the user shared their location, redisplaying the portion of the transcript that includes the indication of the user's location still shows the previously displayed indication but its appearance is modified so as to indicate that the location information in the indication is stale (e.g., because the location-sharing time period had expired without being extended).
In some embodiments, a depiction, on device 600, of an ended location-sharing time period is provided at the moment the time period ends. In some embodiments, a depiction, on device 600, of an ended location-sharing time period is provided at the moment of the next interaction by one of the first participant and the second participant with the message conversation.
In some embodiments, interacting with the message conversation includes a participant viewing at least a portion of the message conversation and/or a participant adding a message to the message conversation. In some embodiments, a location-sharing time period is extended when an outside communication between the first and second participants is detected. Such outside communications optionally include a phone call or video call or other form of direct communication between the two participants outside of the message conversation.
In some embodiments, second participant location information is automatically shared when the first participant requests to share information.
In some embodiments, a location-sharing instruction is transmitted to an external device, wherein the location-sharing instruction permits the external device to share first participant location information with the second participant. For example, where an application tracks the first participant's location (e.g., Maps, location sharing applications, etc.), a server associated with that application is instructed to provide the first participant's location information. In some embodiments, the first participant location information is transmitted to an external device, such as a personal electronic device of the second participant.
In some embodiments, first participant location information is a location of device 600. In some embodiments, the first participant has multiple devices and first participant location information is the device that is determined to be most representative of the first participant's location. In such an embodiment, device 600 determines whether device 600 is representative of the first participant's location. If device 600 determines that it is representative of the first participant's location, a location of the device is transmitted. If device 600 determines that it is not representative of the first participant's location, a location of the device is not transmitted.
In some embodiments, location-sharing is extended only when a message interaction occurs within a window at the end of current location-sharing time period. For example, only interactions within the last fifteen minutes of a two-hour location-sharing time period extend the location-sharing time period. An interaction within the two-hour location-sharing time period but before the last fifteen minutes does not extend the location-sharing time period.
In some embodiments, a buffer time is provided after the location-sharing time period for extending location sharing. For example, if device 600 detects interaction with the message conversation after first participant location information sharing has stopped and device 600 determines that less than a buffer time period has elapsed since the time first participant location information sharing was stopped, device 600 re-enables the second participant to obtain the first participant location information. In some embodiments, device 600 re-enables only when the location-sharing time period expired and not when the first participant actively ends location-sharing (see, e.g.,
In some embodiments, a message conversation includes a third participant. Upon receiving a request from the first participant to share location information with the third participant, device 600 enables both the second and third participants to obtain first participant location information during a predetermined location-sharing time period. In some embodiments, the location-sharing request to share the first participant's location with the third participant is the same as the location-sharing request to share the first participant's location with the second participant (e.g., a single location-sharing request to share location in the message conversation causes the first participant's location to be shared with multiple other participants in the conversation or, optionally, all other participants in the conversation).
As described below, process 700 provides an intuitive way for sharing location information. The method reduces the cognitive burden on a user for sharing location information, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to share location information faster and more efficiently conserves power and increases the time between battery charges.
At block 702, the device displays, on the display, a message region (e.g., message region 602 in
Advantageously, this allows users to continue sharing location during a single conversation but ends location sharing after the conversation has ended to preserve privacy without requiring a user to explicitly indicate that the conversation has ended. This also improves the user's experience when the user is not required to remember to stop sharing indefinitely-shared location information when first participant information is no longer necessary for the second participant. The user is also not required to repeatedly share one-off location information when first participant information is necessary for the second participant. This reduces battery usage as users are not required to repeatedly access and select location-sharing via the user interface.
Turning to
In some embodiments, detecting interaction by one of the first participant and the second participant with the message conversation comprises detecting at least one criteria selected from the group consisting of: the first participant viewing at least a portion of the message conversation (e.g., viewing message region 602), the second participant viewing at least a portion of the message conversation, the first participant adding a message to the message conversation (e.g., adding message 622), and the second participant adding a message to the message conversation (e.g., adding message 618).
In some embodiments, the device displays an indication (e.g., modifying a visual attribute of a caret 616, an information bar 614, a map 612, or any other indication described herein) in the message conversation that the location of the first participant is being shared with the second participant. In some embodiments, when the location-sharing time period ends (e.g., without being extended), the device ceases to display the indication. In some embodiments, the indication is a map view (e.g., map view 614 in
In some embodiments, the indication is a shared-location affordance (e.g., shared location affordance 616 in
In some embodiments, the extended time period is shorter than the predetermined location-sharing time period. In some embodiments, the predetermined location-sharing time period is two hours and each extension is 15 minutes. In some embodiments, different location-sharing time periods and different extensions are used.
In some embodiments, a location-sharing instruction is received from an external device, wherein the location-sharing instruction permits the external device to share first participant location information with the second participant. For example, where an application tracks the first participant's location (e.g., Maps, location sharing applications, etc.), a server associated with that application is instructed to provide the first participant's location information. In some embodiments, the first participant location information is received from an external device, such as a mobile phone of the first participant. In some embodiments, first participant location information is a location of a device of the first participant.
Note that details of the processes described above with respect to process 700 (e.g.,
When the first participant requests to share location information (
Map 812 is displayed in the message transcript between two messages; in some embodiments, the map view is displayed above the transcript, in the banner for example, or below the transcript above a keyboard. In some embodiments, the map view is displayed behind an image (photo, avatar, etc.) of the participant currently sharing information. In some embodiments, the location of a message participant is updated over time (e.g., as the user moves around) and the device displays an updated map view as the participant's location information changes. In some embodiments, an indication of location sharing includes a location-sharing status, a current address of the first participant, a travel time between the first participant and the second participant, a distance between the first participant and the second participant, and a time when location sharing ends.
In some embodiments, the scheduled end of the predetermined location-sharing time period could also be displayed on device 800.
When one of the first participant and the second participant interact with the message conversation during the predetermined location-sharing time period, the predetermined location-sharing time period is extended to end at a second time that is after the first time. For example, if a message is sent from device 800 to device 600, the predetermined location-sharing time period is extended to end at a second time. Device 800 receives a second location-sharing notification that first participant location information is being shared for an extended location-sharing time period.
In some embodiments, the predetermined location-sharing time period is extended only when one of the participants adds content to the conversation (e.g., by sending a new message). In some embodiments, the extended time period is shorter than the predetermined location-sharing time period.
In some embodiments, the location-sharing time period is further extended after the second participant interacts with the message conversation during the already extended location-sharing time period. In response, a notification of the second participant's interaction is sent from device 800 to device 600. After sending this notification, device 800 receives a notification that the extended location-sharing time period is further extended.
The process of further extending the location-sharing time period is optionally repeated any number of times. This optionally allows users to continue sharing location during a single conversation but ends location sharing after the conversation has ended to preserve privacy without requiring a user to explicitly indicate that the conversation has ended. In some embodiments, if the second participant interacts with the message conversation after the extended predetermined location-sharing time period has ended, the predetermined location-sharing time period is not extended. Advantageously, this allows users to continue sharing location during a single conversation but ends location sharing after the conversation has ended to preserve privacy without requiring a user to explicitly indicate that the conversation has ended. This also improves the user's experience when the user is not required to remember to stop sharing indefinitely-shared location information when first participant information is no longer necessary for the second participant. The user is also not required to repeatedly share one-off location information when first participant information is necessary for the second participant. This reduces battery usage as users are not required to repeatedly access and select location-sharing via the user interface.
In some embodiments, an ended location-sharing time period is depicted by shading a map, displaying text, and/or displaying a symbol. In such embodiments, device 800 determines that the predetermined location-sharing time period has ended and, in response to the determination, displays an indication in the message conversation that the location of the first participant is not being shared with the second participant. In some embodiments, if an indication of a user's location was displayed in a message transcript when the user shared their location, redisplaying the portion of the transcript that includes the indication of the user's location would still show the previously displayed indication but it's appearance would be modified so as to indicate that the location information in the indication is stale (e.g., because the location-sharing time period had expired without being extended).
In some embodiments, a depiction, on device 800, of an ended location-sharing time period is provided at the moment the time period ends. In some embodiments, a depiction, on device 800, of an ended location-sharing time period is provided at the moment of the next interaction by one of the first participant and the second participant with the message conversation.
In some embodiments, a location-sharing instruction is received from an external device, wherein the location-sharing instruction permits the external device to share first participant location information with the second participant. For example, where an application tracks the first participant's location (e.g., Maps, location sharing applications, etc.), a server associated with that application is instructed to provide the first participant's location information. In some embodiments, the first participant location information is received from an external device, such as a mobile phone of the first participant. In some embodiments, first participant location information is a location of a device of the first participant.
As described below, process 900 provides an intuitive way for sharing location information. The method reduces the cognitive burden on a user for sharing location information, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to share location information faster and more efficiently conserves power and increases the time between battery charges.
At block 902, the device displays, on the display, a message region (e.g., message region 802 in
Advantageously, this allows users to continue sharing location during a single conversation but ends location sharing after the conversation has ended to preserve privacy without requiring a user to explicitly indicate that the conversation has ended. This also improves the user's experience when the user is not required to remember to stop sharing indefinitely-shared location information when first participant information is no longer necessary for the second participant. The user is also not required to repeatedly share one-off location information when first participant information is necessary for the second participant. This reduces battery usage as users are not required to repeatedly access and select location-sharing via the user interface.
In some embodiments, process 900 includes: detecting interaction by the second participant with the message conversation during the extended location-sharing time period and, in response to detecting interaction by the second participant with the message conversation during the extended location-sharing time period, sending a notification to the first participant; and, after sending the notification to the first participant, receiving a notification that extended location-sharing time period is further extended to end at a third time that is after the second time.
In some embodiments, process 900 includes detecting interaction by the second participant with the message conversation after the extended location-sharing time period and, in response to detecting interaction by the second participant with the message conversation after the extended location-sharing time period, forgoing sending a notification to the first participant.
In some embodiments, process 900 includes detecting interaction by the second participant with the message conversation comprises detecting at least one criteria selected from the group consisting of: the first participant viewing at least a portion of the message conversation, the second participant viewing at least a portion of the message conversation (e.g., viewing message region 802), the first participant adding a message to the message conversation, and the second participant adding a message to the message conversation.
In some embodiments, process 900 includes displaying an indication (e.g., map view 812 and text 814 in
In some embodiments, process 900 includes receiving updated first participant location information and updating the map view with the updated first participant location information. In some embodiments, the indication comprises one or more of a location-sharing status, the first time, the second time, a current address of the first participant (e.g., address “Palo Alto” in information bar 814 in
In some embodiments, process 900 includes determining that the predetermined location-sharing time period has ended and, in accordance with a determination that the predetermined location-sharing time period has ended, displaying an indication in the message conversation that the location of the first participant is not being shared with the second participant.
In some embodiments, the extended predetermined location-sharing time period is shorter than the predetermined location-sharing time period.
In some embodiments, process 900 includes, further in response to receiving the first location-sharing notification, sharing second participant location information with the first participant.
In some embodiments, process 900 includes, further in response to receiving the first location-sharing notification, displaying a request (e.g., request 816 in
In some embodiments, process 900 includes receiving the first location-sharing notification comprises receiving first participant location information from an external device. In some embodiments, receiving the first location-sharing notification comprises receiving the first participant location information from an electronic device of the first participant.
In some embodiments, first participant location information comprises a location of the electronic device of the first participant.
Note that details of the processes described above with respect to process 900 (e.g.,
In accordance with some embodiments,
As shown in
The processing unit 1006 is configured to: enable display (e.g., with display enabling unit 1028), on display unit 1002, of a message region; enable display (e.g., with display enabling unit 1028), in the message region, of messages sent between a first participant and a second participant in a message conversation; detect (e.g., with detecting unit 1008) a location-sharing request from the first participant to share first participant location information with the second participant; in response to detecting the location-sharing request from the first participant: enable (e.g., with enabling unit 1012) the second participant to obtain the first participant location information during a predetermined location-sharing time period, wherein the predetermined location-sharing time period is scheduled to end at a first time; detect (e.g., with detecting unit 1008) interaction by one of the first participant and the second participant with the message conversation during the predetermined location-sharing time period; and in response to detecting interaction by one of the first participant and the second participant with the message conversation during the predetermined location-sharing time period: extend (e.g., with extending unit 1014) the predetermined location-sharing time period to end at a second time that is after the first time.
In some embodiments, the processing unit is further configured to: detect (e.g., with detecting unit 1008) interaction by one of the first participant and the second participant with the message conversation during the extended location-sharing time period; and in response to detecting interaction by one of the first participant and the second participant with the message conversation during the extended location-sharing time period: further extend (e.g., with extending unit 1014) the predetermined location-sharing time period to end at a third time that is after the second time.
In some embodiments, the processing unit is further configured to: detect (e.g., with detecting unit 1008) interaction by one of the first participant and the second participant with the message conversation after the extended predetermined location-sharing time period; and in response to detecting interaction by one of the first participant and the second participant with the message conversation after the extended predetermined location-sharing time period: forgo further extending (e.g., with extending unit 1014) the predetermined location-sharing time period.
In some embodiments, an interaction by one of the first participant and the second participant with the message conversation comprises at least one criteria selected from the group consisting of: the first participant viewing at least a portion of the message conversation, the second participant viewing at least a portion of the message conversation, the first participant adding a message to the message conversation, and the second participant adding a message to the message conversation.
In some embodiments, the processing unit is further configured to: detect (e.g., with detecting unit 1008) a communication between the first and second participant outside of the message conversation during the predetermined location-sharing time period; and in response to detecting a communication between the first and second participant outside of the message conversation during the predetermined location-sharing time period: extend (e.g., with extending unit 1014) the predetermined location-sharing time period.
In some embodiments, the processing unit is further configured to: enable display (e.g., with display enabling unit 1028), on the display unit 1002, of an indication in the message conversation that the location of the first participant is being shared with the second participant. In some embodiments, the indication comprises a map-view. In some embodiments, the map-view is displayed behind an image of the first participant. In some embodiments, the map-view is displayed between two messages of the message conversation.
In some embodiments, the processing unit is further configured to update (e.g., with updating unit 1022) the map view when the first participant location information changes.
In some embodiments, the indication comprises one or more of a location-sharing status, the first time, the second time, a current address of the first participant, a travel time between the first participant and the second participant, and a distance between the first participant and the second participant. In some embodiments, the indication is a shared-location affordance, and the processing unit is further configured to: detect (e.g., with detecting unit 1008) a selection of the shared-location affordance by the first participant; and in response to detecting the selection of the shared-location affordance by the first participant: end (e.g., with ending unit 1016) the predetermined location-sharing time period.
In some embodiments, the processing unit is further configured to: determine (e.g., with determining unit 1010) that the predetermined location-sharing time period has ended; and in accordance with a determination that the predetermined location-sharing time period has ended: enable display (e.g., with display enabling unit 1028), on the display unit 1002, of an indication in the message conversation that the location of the first participant is not being shared with the second participant.
In some embodiments, extending the predetermined location-sharing time period to end at a second time that is after the first time comprises extending the predetermined location-sharing time period for an amount of time that is shorter than the predetermined location-sharing time period.
In some embodiments, the processing unit is further configured to: further in response to detecting the location-sharing request from the first participant: receive (e.g., with receiving unit 1018) second participant location information; and enable display (e.g., with enabling unit 1028), on the display unit 1002, of the second participant location information.
In some embodiments, the processing unit is further configured to: further in response to detecting the location-sharing request from the first participant: transmit (e.g., with transmitting unit 1020) a request for second participant location information.
In some embodiments, enablement of the second participant to obtain the first participant location information during a predetermined location-sharing time period comprises transmission of a location-sharing instruction to an external device, and the location-sharing instruction permits the external device to share first participant location information with the second participant.
In some embodiments, enabling the second participant to obtain the first participant location information during a predetermined location-sharing time period comprises enabling the transmission of the first participant location information to an external device.
In some embodiments, the first participant location information comprises a location of the electronic device.
In some embodiments, the processing unit is further configured to: determine (e.g., with determining unit 1010) whether the electronic device is representative of the first participant's location; in accordance with a determination that the electronic device is representative of the first participant's location: transmit (e.g., with transmitting unit 1020) a location of the electronic device; and in accordance with a determination that the electronic device is not representative of the first participant's location: forgo transmitting (e.g., with transmitting unit 1020) a location of the electronic device.
In some embodiments, the processing unit is further configured to: after the second time: cease to enable (e.g., with enabling unit 1012) the second participant to obtain the first participant location information; and detect (e.g., with detecting unit 1008) interaction by one of the first participant and the second participant with the message conversation; and in response to detecting interaction by one of the first participant and the second participant with the message conversation after the second time: in accordance with a determination that less than a buffer time period has elapsed since the second time, re-enable (e.g., with enabling unit 1012) the second participant to obtain the first participant location information; and in accordance with a determination that more than the buffer time period has elapsed since the second time, enable (e.g., with enabling unit 1012) display, on the display unit 1002, of the message conversation without re-enabling the second participant to obtain the first participant location information.
In some embodiments, the processing unit is further configured to: enable display (e.g., with display enabling unit 1028), in the message region, of messages sent between the first participant, the second participant, and a third participant in the message conversation; detect (e.g., with detecting unit 1008) a location-sharing request from the first participant to share first participant location information with the third participant; and in response to detecting the location-sharing request from the first participant to share first participant location information with the third participant: enable (e.g., with enabling unit 1012) the second and third participants to obtain the first participant location information during a second predetermined location-sharing time period.
The processing unit 1006 is configured to: enable display (e.g., with display enabling unit 1028), on the display unit 1002, of a message region; enable display (e.g., with display enabling unit 1028), in the message region, messages sent between a first participant and a second participant in a message conversation; receive (e.g., with receiving unit 1018) a first location-sharing notification that first participant location information is being shared with the second participant for a predetermined location-sharing time period, wherein the predetermined location-sharing time period is scheduled to end at a first time; send (e.g., with sending unit 1026) a message to the first participant; and receive (e.g., with receiving unit 1018) a second location-sharing notification that first participant location information is being shared with the second participant for an extended location-sharing time period, wherein the extended location-sharing time period is scheduled to end at a second time that is after the first time.
In some embodiments, the processing unit is further configured to: detect (e.g., with detecting unit 1008) interaction by the second participant with the message conversation during the extended location-sharing time period; and in response to detecting interaction by the second participant with the message conversation during the extended location-sharing time period: send (e.g., with sending unit 1026) a notification to the first participant; and after sending the notification to the first participant, receive (e.g., with receiving unit 1018) a notification that extended location-sharing time period is further extended to end at a third time that is after the second time.
In some embodiments, the processing unit is further configured to: detect (e.g., with detecting unit 1008) interaction by the second participant with the message conversation after the extended location-sharing time period; and in response to detecting interaction by the second participant with the message conversation after the extended location-sharing time period: forgo sending (e.g., with sending unit 1026) a notification to the first participant.
In some embodiments, detecting interaction by the second participant with the message conversation comprises detecting at least one criteria selected from the group consisting of: the first participant viewing at least a portion of the message conversation, the second participant viewing at least a portion of the message conversation, the first participant adding a message to the message conversation, and the second participant adding a message to the message conversation.
In some embodiments, the processing unit is further configured to: enable display (e.g., with display enabling unit 1028), on the display unit 1002, of an indication in the message conversation that the location of the first participant is being shared with the second participant.
In some embodiments, the indication comprises a map-view. In some embodiments, the map-view is displayed behind an image of the first participant. In some embodiments, the map-view is displayed between two messages of the message conversation.
In some embodiments, the processing unit is further configured to: receive (e.g., with receiving unit 1018) updated first participant location information; and update (e.g., with updating unit 1022) the map view with the updated first participant location information.
In some embodiments, the indication comprises one or more of a location-sharing status, the first time, the second time, a current address of the first participant, a travel time between the first participant and the second participant, and a distance between the first participant and the second participant.
In some embodiments, the processing unit is further configured to: determine (e.g., with detecting unit 1010) that the predetermined location-sharing time period has ended; and in accordance with a determination that the predetermined location-sharing time period has ended: enable display (e.g., with display enabling unit 1028), on the display unit 1002, of an indication in the message conversation that the location of the first participant is not being shared with the second participant.
In some embodiments, the extended predetermined location-sharing time period is shorter than the predetermined location-sharing time period.
In some embodiments, the processing unit is further configured to: further in response to receiving the first location-sharing notification: share (e.g., with sharing unit 1024) second participant location information with the first participant.
In some embodiments, the processing unit is further configured to: further in response to receiving the first location-sharing notification: enable display (e.g., with display enabling unit 1028), on the display unit 1002, of a request to share second participant location information with the first participant.
In some embodiments, receiving the first location-sharing notification comprises receiving first participant location information from an external device.
In some embodiments, receiving the first location-sharing notification comprises receiving the first participant location information from an electronic device of the first participant.
In some embodiments, first participant location information comprises a location of the electronic device of the first participant.
The operations described above with reference to
Advantageously, this improves the user's experience because the user can quickly access location-sharing. This reduces battery usage as users are not required to make multiple selections on the user interface in order to activate location sharing.
In like manner to other embodiments disclosed herein, in response to detecting interaction by one of the first participant and the second participant with the message conversation during the predetermined location-sharing time period, device 1100 will extend the predetermined location-sharing time period (see description of
As illustrated in
In some embodiments, shared-location affordance 1120 is continuously displayed while location information is shared. For example, while displaying shared-location affordance 1120, device 1100 detects an event that will cause a change in appearance of the transcript (e.g., with the receipt of a new message or a scrolling operation that will scroll the message conversation downward). In response to detecting the event, device 1100 determines whether location-sharing is enabled. If location-sharing is enabled, device 1100 changes the appearance of the transcript in accordance with the event and maintains the display of shared-location affordance 1120. If location-sharing is not enabled, device 1100 changes the appearance of the transcript in accordance with the event and ceases the display of shared-location affordance 1120.
In some embodiments, location-sharing affordance 1112 is no longer displayed after a user interacts with it (e.g.,
In some embodiments, device 1100 determines whether the movement of the contact (
As described below, process 1200 provides an intuitive way for sharing location information. The method reduces the cognitive burden on a user for sharing location information, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to share location information faster and more efficiently conserves power and increases the time between battery charges.
At block 1202, the device displays, on the display, a message region (e.g., message region 1102 in
Advantageously, this improves the user's experience because the user can quickly access location-sharing. This reduces battery usage as users are not required to make multiple selections on the user interface in order to activate location sharing.
Note that details of the processes described above with respect to process 1200 (e.g.,
In accordance with some embodiments,
As shown in
The processing unit 1306 is configured to: enable display (e.g., with display enabling unit 1320), on the display unit 1302, of a message region; enable display (e.g., with display enabling unit 1320), at a first position in the message region, of a bottom portion of a message transcript of messages sent between a first participant and a second participant; detect (e.g., with detecting unit 1308) contact on a location corresponding to the message transcript; detect (e.g., with detecting unit 1308) movement of the contact across the touch-sensitive surface and toward a top portion of the message region; and in response to detecting movement of the contact across the touch-sensitive surface and toward a top portion of the message region: enable display (e.g., with display enabling unit 1320), on the display unit 1302, of the bottom portion of the message transcript at a second position in the message region above the first position; and enable display (e.g., with display enabling unit 1320), on the display unit 1302, of a location-sharing affordance at the first position.
In some embodiments, the processing unit is further configured to: enable display (e.g., with display enabling unit 1320), on the display unit 1302, of a keyboard below the message region; and while displaying the location-sharing affordance at the first position, receive a new message for display in the message region; and in response to receiving the new message: enable display (e.g., with display enabling unit 1320), on the display unit 1302, of the new message in the message region; and cease display the location-sharing affordance.
In some embodiments, the processing unit is further configured to: detect (e.g., with detecting unit 1308) a selection of the location-sharing affordance; in response to detecting a selection of the location-sharing affordance: enable (e.g., with enabling unit 1314) the second participant to obtain the first participant location information during a predetermined location-sharing time period, wherein the predetermined location-sharing time period is scheduled to end at a first time.
In some embodiments, the processing unit is further configured to: detect (e.g., with detecting unit 1308) interaction by one of the first participant and the second participant with the message conversation during the predetermined location-sharing time period; and in response to detecting interaction by one of the first participant and the second participant with the message conversation during the predetermined location-sharing time period: extend (e.g., with extending unit 1316) the predetermined location-sharing time period to end at a second time that is after the first time.
In some embodiments, the processing unit is further configured to: while displaying the location-sharing affordance, detect (e.g., with detecting unit 1308) an event that will cause a change in appearance of the transcript; in response to detecting the event: in accordance with a determination that the location-sharing is enabled: change (e.g., with changing unit 1318) the appearance of the transcript in accordance with the event; and maintain display (e.g., with display unit 1302) of the location-sharing affordance; and in accordance with a determination that the location-sharing is disabled: change (e.g., with changing unit 1318) the appearance of the transcript in accordance with the event; and cease to display the location-sharing affordance.
In some embodiments, the processing unit is further configured to: receive (e.g., with receiving unit 1312) a new message in the message conversation; and in response to receiving the new message: enable (e.g., enabling unit 1314) display, on the display unit 1302, of a representation of the new message at the bottom portion of the transcript; and discontinue display of the location-sharing affordance.
In some embodiments, the processing unit is further configured to: detect (e.g., with detecting unit 1308) interaction with the location-sharing affordance; and in response to detecting interaction with the location-sharing affordance: discontinue display (e.g., with display unit 1302) of the location-sharing affordance.
In some embodiments, the processing unit is further configured to: determine (e.g., with detecting unit 1008) whether the movement of the contact across the touch-sensitive surface meets predefined criteria; in accordance with a determination that the movement meets the predetermined criteria: enable (e.g., enabling unit 1314) display, on the display unit 1302, of the location-sharing affordance for a predetermined time; and discontinue display (e.g., with display unit 1302) of the location-sharing affordance after the predetermined time lapses; and in accordance with a determination that the movement does not meet the predetermined criteria: enable display (e.g., with display enabling unit 1320), on the display unit 1302, of the location-sharing affordance.
In some embodiments, the movement comprises a release of the contact and wherein the predetermined criteria comprises a predetermined velocity of the movement at release.
The operations described above with reference to
Advantageously, this allows an indication of location sharing to remain on the user interface, while continuing a message conversation. Optionally, the user is reminded of location sharing, even as new messages in the message conversation cause the transcript to scroll out of view. Further, the user can receive updates on the location of the other participant or the travel time to the other participant, for example, even as new messages are continuously added to the transcript.
In some embodiments, discontinuing displaying the shared-location affordance 1410 and displaying the location-sharing status bar 1412 includes displaying an animated transition of the shared-location affordance 1410 turning into the location-sharing status bar 1412.
In some embodiments, discontinuing displaying the location-sharing status bar 1412 and displaying the shared-location affordance 1410 includes displaying an animated transition of the location-sharing status bar 1412 turning into the shared-location affordance 1410.
In some embodiments, a location-sharing status bar includes an indication of a distance between the first participant and the second participant. In some embodiments, a location-sharing status bar includes an indication of a travel time between the first participant and the second participant. In some embodiments, a location-sharing status bar alternates from the indication of a distance between the first participant and the second participant to the indication of the travel time between the first participant and the second participant. In some embodiments, the travel time between the first participant and the second participant is determined by the distance between the first participant and the second participant and a mode of transport. In some embodiments, the location-sharing status bar includes a representation of at least one of a period of time until location sharing will end and a time of day until location sharing will end. In some embodiments, the location-sharing status bar includes one of a current location of the first participant and a map view depicting the current location of the first participant.
In some embodiments, selection of the location-sharing status bar results in launching a map view (e.g., a map displayed in a location sharing application) with a representation of a location of the first participant and the second participant.
In some embodiments, selection of a map view affordance results in display of an enlarged map view. In some embodiments, the map view affordance indicates that multiple message conversation participants are sharing their respective locations (for example, text stating multiple view locations are available). In such embodiments, in response to detecting a section of the map view affordance, device 1400 displays a map view comprising representations of the multiple message conversation participants.
Advantageously, this allows an indication of location sharing to remain on the user interface, while continuing a message conversation. Optionally, the user is reminded of location sharing, even as new messages in the message conversation cause the transcript to scroll out of view. Further, the user can receive updates on the location of the other participant or the travel time to the other participant, for example, even as new messages are continuously added to the transcript. Further, by including the map view in the banner 1404, space in the message transcript 1402 is not occupied by information related to location sharing. This feature may improve the user's experience by allowing more messages in the message conversation to be displayed in the message transcript 1402.
In some embodiments, text of the banner (such as the time and name of the message participant in
As described below, process 1500 provides an intuitive way for sharing location information. The method reduces the cognitive burden on a user for sharing location information, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to share location information faster and more efficiently conserves power and increases the time between battery charges.
At block 1502, the device displays, on the display, a message region (e.g., message region 1402 in
Advantageously, this allows an indication of location sharing to remain on the user interface, while continuing a message conversation. Optionally, the user is reminded of location sharing, even as new messages in the message conversation cause the transcript to scroll out of view. Further, the user can receive updates on the location of the other participant or the travel time to the other participant, for example, even as new messages are continuously added to the transcript.
In some embodiments, the location-sharing status bar comprises an indication of a distance between the first participant and the second participant. In some embodiments, the location-sharing status bar comprises an indication of a travel time between the first participant and the second participant (e.g., “20 mins away” in location-sharing status bar 1412 in
In some embodiments, the location-sharing status bar comprises a representation of at least one of a period of time until location sharing will end and a time of day until location sharing will end. In some embodiments, the location-sharing status bar comprises one selected from the group consisting of a current location of the first participant and a map view depicting the current location of the first participant.
In some embodiments, displaying a location-sharing status bar outside of the message region comprises displaying the location-sharing status bar above and adjacent to the message region.
Note that details of the processes described above with respect to process 1500 (e.g.,
In accordance with some embodiments,
As shown in
The processing unit 1606 is configured to: enable display (e.g., with display enabling unit 1616), on the display unit 1602, of a message region; enable display (e.g., with display enabling unit 1616), in the message region, of a message transcript of messages sent between a first participant and a second participant; enable (e.g., with enabling unit 1614) display(e.g., with display unit 1302), at a first position in the message transcript, of a shared-location affordance; while displaying the shared-location affordance at the first position, detect (e.g., with detecting unit 1608) a request to scroll the message transcript; in response to detecting the request to scroll the message transcript: determine (e.g., with determining unit 1610) whether the request to scroll the message transcript comprises a request to scroll the shared-location affordance beyond the message region; in accordance with a determination that the request to scroll the message transcript comprises a request to scroll the shared-location affordance beyond the message region: discontinue display (e.g., with display unit 1602) of the shared location in the message transcript; and enable display (e.g., with display enabling unit 1616), on the display unit 1602, of a location-sharing status bar outside the message region; and in accordance with a determination that the request to scroll the message transcript does not comprise a request to scroll the shared-location affordance beyond the message region: enable display (e.g., with display enabling unit 1616), on the display unit, of the shared-location affordance at a second location in the message transcript.
In some embodiments, the processing unit is further configured to: while displaying a location-sharing status bar outside the message region, detect (e.g., with detecting unit 1608) a second request to scroll the message transcript; in response to detecting the second request to scroll the message transcript: determine (e.g., with determining unit 1610) whether the second request to scroll the message transcript comprises a request to display the shared-location affordance in the message region; in accordance with a determination that the second request to scroll the message transcript comprises a request to display the shared-location affordance in the message region: discontinue display (e.g., with display unit 1602) of the location-sharing status bar outside the message region; enable display (e.g., with display enabling unit 1616), on the display unit, of the shared-location affordance in the message transcript; and in accordance with a determination that the second request to scroll the message transcript does not comprise a request to display the shared-location affordance in the message region: forgo display (e.g., with display unit 1602) of the shared-location affordance in the message transcript.
In some embodiments, the location-sharing status bar comprises an indication of a distance between the first participant and the second participant.
In some embodiments, the location-sharing status bar comprises an indication of a travel time between the first participant and the second participant.
In some embodiments, the location-sharing status bar alternates from the indication of a distance between the first participant and the second participant to the indication of the travel time between the first participant and the second participant.
In some embodiments, the travel time between the first participant and the second participant is determined by the distance between the first participant and the second participant and a mode of transport.
In some embodiments, the location-sharing status bar is selectable, and wherein the processing unit is further configured to: detect (e.g., with detecting unit 1608) a selection of the location-sharing status bar; and in response to detecting a selection of the location-sharing status bar: launch (e.g., with launching unit 1612) a map view, wherein the map view comprises a representation of a location of the first participant and a location of the second participant.
In some embodiments, the location-sharing status bar comprises a representation of at least one of a period of time until location sharing will end and a time of day until location sharing will end.
In some embodiments, the location-sharing status bar comprises one selected from the group consisting of a current location of the first participant and a map view depicting the current location of the first participant.
In some embodiments, the processing unit is further configured to: enable display (e.g., with display enabling unit 1616), on the display unit, of a map view affordance; detect (e.g., with detecting unit 1608) a selection of the map view affordance; and in response to detecting a selection of the map view affordance: enable display (e.g., with display enabling unit 1616), on the display unit, of a map view comprising a representation of a location of the first participant.
In some embodiments, the map view affordance indicates that multiple message conversation participants are sharing their respective locations, and wherein the processing unit is further configured to: further in response to detecting a selection of the map view affordance: enable display (e.g., with display enabling unit 1616), on the display unit, of a map view comprising representations of respective locations of the multiple message conversation participants.
In some embodiments, enabling display of a location-sharing status bar outside of the message region comprises enabling display of the location-sharing status bar above and adjacent to the message region.
The operations described above with reference to
In some embodiments, device 1700 displays a representation of the first participant's updated location in the shared-location affordance as the first participant's location changes. In some embodiments, displaying the representation of the updated location includes shifting the map while maintaining the representation of the first participant in the same location on the display.
In some embodiments, the selection is a predefined gesture, such as a single tap gesture, a double tap gesture, or a press and hold gesture (for example, a contact that is detected for more than a threshold amount of time). In some embodiments, if device 1700 determines that the characteristic of the gesture do not meet a predefined threshold, device 1700 forgoes enlarging the map view.
In some embodiments, device 1700 enlarges the map view with animation, such as a page curl or fade in. In some embodiments, enlarging the map view includes gradually enlarging the map view as a parameter associated with the gesture changes (for example, as a duration or intensity of the contact increases, the animation speed increases).
In some embodiments, a second map view is displayed if both participants are simultaneously sharing their locations (see
In some embodiments, selection of a location-sharing affordance consists of a single contact. In response to the selection, device 1700 enables the second participant to obtain the first participant location information and displays a modified location-sharing affordance. (See, e.g.,
In some embodiments, the second participant receives updated first participant location information as the first participant's location changes. In some embodiments, displaying a modified location-sharing affordance comprises replacing the location-sharing affordance with the modified location-sharing affordance. In some embodiments, a message compose field includes the modified location-sharing affordance. For example, the modified location-sharing affordance is displayed within a text entry field that is configured for entering text for draft messages. In some embodiments, tapping in the message compose field at a location that is away from the modified location-sharing affordance causes a cursor to be displayed in the message compose field (and, if a keyboard is not displayed, optionally, causes a soft keyboard to be displayed for entering text into the message compose field at the location of the cursor), while tapping in the message compose field at a location that corresponds to the location-sharing affordance toggles on/off location sharing. In some embodiments, the modified location-sharing affordance is discontinued after detection of a message composition.
In some embodiments, the most recent message 1708 sent by the first participant is centered in the message transcript 1702. The tail of the most recent message 1708 is pointed toward the rounded corner of the shared-location affordance.
In some embodiments, the displayed map region is not scrolled with the message transcript; it remains stationary in the message region as new messages are displayed. In this manner, participants can continue to view shared location information over the course of a message conversation, as the transcript continues to be scrolled.
As described below, process 1800 provides an intuitive way for sharing location information. The method reduces the cognitive burden on a user for sharing location information, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to share location information faster and more efficiently conserves power and increases the time between battery charges.
At block 1802, the device displays, on the display, a message region (e.g., message region 1702 in
In some embodiments, the shared location affordance comprises a map view (e.g., map view 1710 in
In some embodiments, the device displays the representation of the first participant on the map view at a position that corresponds to a location of the first participant.
In some embodiments, the shared location affordance comprises a representation of the first participant, such as an avatar or a captured image.
Note that details of the processes described above with respect to process 1800 (e.g.,
In accordance with some embodiments,
As shown in
The processing unit 1906 is configured to: enable display (e.g., with display enabling unit 1918), on the display unit, of a message region; enable display (e.g., with display enabling unit 1918), in the message region, of a message transcript of messages sent between a first participant and a second participant; and enable display (e.g., with display unit 1902), on the display unit, of a shared-location affordance in the message region, wherein the shared-location affordance is displayed below and adjacent to the message transcript, and wherein the shared-location affordance comprises a representation of a location of the first participant.
In some embodiments, the shared-location affordance comprises a map view.
In some embodiments, the processing unit is further configured to: detect (e.g., with detecting unit 1908) a predefined gesture on the touch-sensitive surface at a position that corresponds to the shared-location affordance; in response to detecting the predefined gesture, enlarge (e.g., with enlarging unit 1912) the map view.
In some embodiments, enlarging the map view comprises gradually enlarging the map view as a parameter associated with the gesture changes.
In some embodiments, the processing unit is further configured to: enable (e.g., with enabling unit 1914) display, on the display unit, of the representation of the first participant on the map view at a position that corresponds to a location of the first participant.
In some embodiments, the processing unit is further configured to: enable (e.g., with enabling unit 1914) display, on the display unit, of a second map view in the message transcript; and enable display, on the display unit, of a representation of the second participant at a position on the second map view that corresponds to a location of the second participant.
In some embodiments, the processing unit is further configured to: receive (e.g., with receiving unit 1916) an updated location of the first participant; and in response to receiving the updated location of the first participant: enable (e.g., with enabling unit 1914) display, on the display unit, of a representation of the updated location of the first participant in the shared-location affordance associated with the first participant.
In some embodiments, the processing unit is further configured to: receive (e.g., with receiving unit 1916) a new message sent between the first and second participant in the message conversation; and in response to receiving the new message: enable (e.g., with enabling unit 1914) display, on the display unit, of a representation of the new message at the bottom of the transcript; and continue enabling display of the shared-location affordance at the same location.
In some embodiments, the shared-location affordance comprises a representation of the first participant.
The operations described above with reference to
As described below, process 2000 provides an intuitive way for sharing location information. The method reduces the cognitive burden on a user for sharing location information, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to share location information faster and more efficiently conserves power and increases the time between battery charges.
At block 2002, the device displays, on the display, a message region (e.g., message region 602 in
Advantageously, this single contact improves the user experience by minimizing the number of selections necessary to share location. In some embodiments, the device enables the second participant to obtain the first participant location information without adding a new message to the message transcript.
In some embodiments, enabling the second participant to obtain the first participant location information is performed without adding a new message to the message transcript.
In some embodiments, displaying a modified location-sharing affordance comprises replacing the location-sharing affordance with the modified location-sharing affordance.
In some embodiments, the device displays a message compose field that includes a modified location-sharing affordance. For example, the modified location-sharing affordance is displayed within a text entry field that is configured for entering text for draft messages. In some embodiments, tapping in the message compose field at a location that is away from the modified location-sharing affordance causes a cursor to be displayed in the message compose field (and, if a keyboard is not displayed, optionally, causes a soft keyboard to be displayed for entering text into the message compose field at the location of the cursor), while tapping in the message compose field at a location that corresponds to the location-sharing affordance toggles on/off location sharing. In some embodiments, the modified location-sharing affordance is discontinued after detection of a message composition.
In some embodiments, the modified location-sharing affordance is a toggle.
Note that details of the processes described above with respect to process 2000 (e.g.,
In accordance with some embodiments,
As shown in
The processing unit 2106 is configured to: enable display (e.g., with enabling unit 2116), on the display unit 2102, of a message region for displaying a message transcript of messages sent between a first participant and a second participant in a message conversation; enable display (e.g., with enabling unit 2116), on the display unit 2102, of a location-sharing affordance; detect (e.g., with enabling unit 2108) a selection of the location-sharing affordance, wherein detecting a selection of the location-sharing affordance by the first participant consists of detecting a single contact by the first participant; and in response to detecting a selection of the location-sharing affordance: enable (e.g., with enabling unit 2112) the second participant to obtain the first participant location information; and enable display, on the display unit, of a modified location-sharing affordance.
In some embodiments, enabling the second participant to obtain the first participant location information is performed without adding a new message to the message transcript.
In some embodiments, the processing unit is further configured to: receive (e.g., with receiving unit 2114) an updated location of the first participant; and in response to receiving an updated location of the first participant: enable (e.g., with enabling unit 2112) the second participant to obtain the updated location of the first participant.
In some embodiments, enabling display of a modified location-sharing affordance comprises enabling replacement of the location-sharing affordance with the modified location-sharing affordance.
In some embodiments, the processing unit is further configured to: enable display (e.g., with enabling unit 2116), on the display unit, of a message compose field, wherein the message compose field comprises the modified location-sharing affordance.
In some embodiments, the processing unit is further configured to: detect (e.g., with detecting unit 2108) a message composition; and in response to detecting a message composition: discontinue display of the modified location-sharing affordance.
In some embodiments, the modified location-sharing affordance is a toggle.
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 drawings, 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 claims.
As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the delivery to users of invitational content or any other content that may be of interest to them. The present disclosure contemplates that in some instances, this gathered data optionally includes personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information.
The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure.
The present disclosure further contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. For example, personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection should occur only after receiving the informed consent of the users. Additionally, such entities would take any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices.
Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of advertisement delivery services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services. In another example, users can select not to provide location information for targeted content delivery services. In yet another example, users can select to not provide precise location information, but permit the transfer of location zone information.
Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content delivery services, or publically available information.
This application is a continuation of U.S. patent application Ser. No. 16/454,884, entitled “EASY LOCATION SHARING”, filed Jun. 27, 2019, which in turn is a continuation of U.S. patent application Ser. No. 15/985,570, now U.S. Pat. No. 10,341,826, entitled “EASY LOCATION SHARING”, filed May 21, 2018, which in turn is a continuation of U.S. patent application Ser. No. 15/876,673, now U.S. Pat. No. 9,998,888, entitled “EASY LOCATION SHARING”, filed Jan. 22, 2018, which in turn is a continuation of U.S. patent application Ser. No. 15/142,661, now U.S. Pat. No. 10,003,938, entitled “EASY LOCATION SHARING”, filed Apr. 29, 2016, which in turn claims priority to U.S. Provisional Application No. 62/205,562, entitled “EASY LOCATION SHARING”, filed Aug. 14, 2015. The contents of each of these applications are hereby incorporated by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
5475653 | Yamada et al. | Dec 1995 | A |
5801700 | Ferguson | Sep 1998 | A |
6002402 | Schacher | Dec 1999 | A |
6014429 | Laporta et al. | Jan 2000 | A |
6191807 | Hamada et al. | Feb 2001 | B1 |
6323846 | Westerman et al. | Nov 2001 | B1 |
6362842 | Tahara et al. | Mar 2002 | B1 |
6570557 | Westerman et al. | May 2003 | B1 |
6629793 | Miller | Oct 2003 | B1 |
6677932 | Westerman | Jan 2004 | B1 |
6721784 | Leonard et al. | Apr 2004 | B1 |
6809724 | Shiraishi et al. | Oct 2004 | B1 |
6987991 | Nelson | Jan 2006 | B2 |
6990452 | Ostermann et al. | Jan 2006 | B1 |
7149893 | Leonard et al. | Dec 2006 | B1 |
7167731 | Nelson | Jan 2007 | B2 |
7197122 | Vuori | Mar 2007 | B2 |
7365736 | Marvit et al. | Apr 2008 | B2 |
7419469 | Vacca et al. | Sep 2008 | B2 |
7593749 | Vallström et al. | Sep 2009 | B2 |
7614008 | Ording | Nov 2009 | B2 |
7633076 | Huppi et al. | Dec 2009 | B2 |
7653883 | Hotelling et al. | Jan 2010 | B2 |
7657849 | Chaudhri et al. | Feb 2010 | B2 |
7663607 | Hotelling et al. | Feb 2010 | B2 |
7669135 | Cunningham et al. | Feb 2010 | B2 |
7789225 | Whiteis | Sep 2010 | B2 |
7797390 | Hagale et al. | Sep 2010 | B2 |
7834861 | Lee | Nov 2010 | B2 |
7844914 | Andre et al. | Nov 2010 | B2 |
7908219 | Abanami et al. | Mar 2011 | B2 |
7957762 | Herz et al. | Jun 2011 | B2 |
8006002 | Kalayjian et al. | Aug 2011 | B2 |
8074172 | Kocienda et al. | Dec 2011 | B2 |
8121586 | Araradian et al. | Feb 2012 | B2 |
8150930 | Satterfield et al. | Apr 2012 | B2 |
8180382 | Graefen | May 2012 | B1 |
8232973 | Kocienda et al. | Jul 2012 | B2 |
8239784 | Hotelling et al. | Aug 2012 | B2 |
8255810 | Moore et al. | Aug 2012 | B2 |
8255830 | Ording et al. | Aug 2012 | B2 |
8279180 | Hotelling et al. | Oct 2012 | B2 |
8285258 | Schultz et al. | Oct 2012 | B2 |
8290478 | Shim et al. | Oct 2012 | B2 |
8381135 | Hotelling et al. | Feb 2013 | B2 |
8456297 | Van Os | Jun 2013 | B2 |
8479122 | Hotelling et al. | Jul 2013 | B2 |
8488752 | Wiesen | Jul 2013 | B1 |
8543927 | Mckinley et al. | Sep 2013 | B1 |
8566403 | Pascal et al. | Oct 2013 | B2 |
8572493 | Qureshi | Oct 2013 | B2 |
8648799 | Llyod et al. | Feb 2014 | B1 |
8811951 | Faaborg et al. | Aug 2014 | B1 |
8848932 | Poulsen et al. | Sep 2014 | B2 |
8893023 | Perry et al. | Nov 2014 | B2 |
8922485 | Lloyd | Dec 2014 | B1 |
8996639 | Faaborg et al. | Mar 2015 | B1 |
9100944 | Sauhta et al. | Aug 2015 | B2 |
9143907 | Caldwell et al. | Sep 2015 | B1 |
9185062 | Yang et al. | Nov 2015 | B1 |
9191988 | Newham | Nov 2015 | B2 |
9207835 | Yang et al. | Dec 2015 | B1 |
9213754 | Zhang et al. | Dec 2015 | B1 |
9317870 | Tew et al. | Apr 2016 | B2 |
9338242 | Suchland et al. | May 2016 | B1 |
9400489 | Kim et al. | Jul 2016 | B2 |
9477208 | Park et al. | Oct 2016 | B2 |
9483529 | Pasoi et al. | Nov 2016 | B1 |
9575591 | Yang et al. | Feb 2017 | B2 |
9578160 | Kim et al. | Feb 2017 | B2 |
9740399 | Paek et al. | Aug 2017 | B2 |
9904906 | Kim et al. | Feb 2018 | B2 |
9906928 | Kim et al. | Feb 2018 | B2 |
9998888 | Chang et al. | Jun 2018 | B1 |
10003938 | Chang et al. | Jun 2018 | B2 |
10013601 | Ebersman et al. | Jul 2018 | B2 |
10019136 | Ozog | Jul 2018 | B1 |
10051103 | Gordon et al. | Aug 2018 | B1 |
10083213 | Podgorny et al. | Sep 2018 | B1 |
10341826 | Chang et al. | Jul 2019 | B2 |
10416844 | Yang et al. | Sep 2019 | B2 |
10445425 | Jon et al. | Oct 2019 | B2 |
11194467 | Zhu et al. | Dec 2021 | B2 |
11327649 | Spivak et al. | May 2022 | B1 |
20020015024 | Westerman et al. | Feb 2002 | A1 |
20020037715 | Mauney et al. | Mar 2002 | A1 |
20020057284 | Dalby et al. | May 2002 | A1 |
20020115478 | Fujisawa et al. | Aug 2002 | A1 |
20020120869 | Engstrom | Aug 2002 | A1 |
20020126135 | Ball et al. | Sep 2002 | A1 |
20020167488 | Hinckley et al. | Nov 2002 | A1 |
20030003897 | Hyon | Jan 2003 | A1 |
20030081506 | Karhu et al. | May 2003 | A1 |
20030177067 | Cowell et al. | Sep 2003 | A1 |
20030229722 | Beyda | Dec 2003 | A1 |
20040070511 | Kim | Apr 2004 | A1 |
20040078752 | Johnson | Apr 2004 | A1 |
20040225502 | Bear et al. | Nov 2004 | A1 |
20050081150 | Beardow et al. | Apr 2005 | A1 |
20050138552 | Venolia | Jun 2005 | A1 |
20050156873 | Walter et al. | Jul 2005 | A1 |
20050190059 | Wehrenberg | Sep 2005 | A1 |
20050191159 | Benko | Sep 2005 | A1 |
20050198128 | Anderson et al. | Sep 2005 | A1 |
20050256712 | Yamada et al. | Nov 2005 | A1 |
20050266884 | Marriott et al. | Dec 2005 | A1 |
20050268237 | Crane et al. | Dec 2005 | A1 |
20050289173 | Vacca et al. | Dec 2005 | A1 |
20060005156 | Korpipä et al. | Jan 2006 | A1 |
20060017692 | Wehrenberg et al. | Jan 2006 | A1 |
20060019639 | Adams et al. | Jan 2006 | A1 |
20060019649 | Feinleib et al. | Jan 2006 | A1 |
20060026245 | Cunningham et al. | Feb 2006 | A1 |
20060026536 | Hotelling et al. | Feb 2006 | A1 |
20060033724 | Chaudhri et al. | Feb 2006 | A1 |
20060044283 | Eri et al. | Mar 2006 | A1 |
20060053386 | Kuhl et al. | Mar 2006 | A1 |
20060161629 | Cohen et al. | Jul 2006 | A1 |
20060179114 | Deeds | Aug 2006 | A1 |
20060195787 | Topiwala et al. | Aug 2006 | A1 |
20060197753 | Hotelling | Sep 2006 | A1 |
20070002077 | Gopalakrishnan et al. | Jan 2007 | A1 |
20070004461 | Bathina et al. | Jan 2007 | A1 |
20070036300 | Brown et al. | Feb 2007 | A1 |
20070037605 | Logan et al. | Feb 2007 | A1 |
20070073823 | Cohen | Mar 2007 | A1 |
20070085157 | Fadell et al. | Apr 2007 | A1 |
20070117549 | Arnos | May 2007 | A1 |
20070150834 | Muller et al. | Jun 2007 | A1 |
20070150836 | Deggelmann et al. | Jun 2007 | A1 |
20070150842 | Chaudhri et al. | Jun 2007 | A1 |
20070173233 | Vander Veen et al. | Jul 2007 | A1 |
20070216659 | Amineh | Sep 2007 | A1 |
20070236475 | Wherry | Oct 2007 | A1 |
20070271340 | Goodman et al. | Nov 2007 | A1 |
20080014989 | Sandegard et al. | Jan 2008 | A1 |
20080052945 | Matas et al. | Mar 2008 | A1 |
20080055264 | Anzures et al. | Mar 2008 | A1 |
20080057926 | Forstall et al. | Mar 2008 | A1 |
20080070593 | Altman et al. | Mar 2008 | A1 |
20080079589 | Blackadar | Apr 2008 | A1 |
20080094370 | Ording et al. | Apr 2008 | A1 |
20080122796 | Jobs et al. | May 2008 | A1 |
20080133479 | Zelevinsky et al. | Jun 2008 | A1 |
20080146289 | Korneluk et al. | Jun 2008 | A1 |
20080165136 | Christie et al. | Jul 2008 | A1 |
20080168144 | Lee | Jul 2008 | A1 |
20080168366 | Kocienda et al. | Jul 2008 | A1 |
20080216022 | Lorch et al. | Sep 2008 | A1 |
20080228386 | Geelen et al. | Sep 2008 | A1 |
20080320391 | Lemay et al. | Dec 2008 | A1 |
20090003552 | Goldman et al. | Jan 2009 | A1 |
20090003620 | Mckillop et al. | Jan 2009 | A1 |
20090005011 | Christie et al. | Jan 2009 | A1 |
20090037536 | Braam | Feb 2009 | A1 |
20090049502 | Levien et al. | Feb 2009 | A1 |
20090051648 | Shamaie et al. | Feb 2009 | A1 |
20090051649 | Rondel | Feb 2009 | A1 |
20090055383 | Zalewski | Feb 2009 | A1 |
20090055494 | Fukumoto et al. | Feb 2009 | A1 |
20090085881 | Keam | Apr 2009 | A1 |
20090088204 | Culbert et al. | Apr 2009 | A1 |
20090106695 | Perry et al. | Apr 2009 | A1 |
20090113315 | Fisher et al. | Apr 2009 | A1 |
20090164219 | Yeung et al. | Jun 2009 | A1 |
20090172599 | Nezu | Jul 2009 | A1 |
20090175425 | Lee | Jul 2009 | A1 |
20090177981 | Christie et al. | Jul 2009 | A1 |
20090181726 | Vargas et al. | Jul 2009 | A1 |
20090187842 | Collins et al. | Jul 2009 | A1 |
20090209293 | Louch | Aug 2009 | A1 |
20090248751 | Myman et al. | Oct 2009 | A1 |
20090254840 | Churchill et al. | Oct 2009 | A1 |
20090265643 | Jachner et al. | Oct 2009 | A1 |
20090284471 | Longe et al. | Nov 2009 | A1 |
20090298444 | Shigeta | Dec 2009 | A1 |
20090306969 | Goud et al. | Dec 2009 | A1 |
20090313582 | Rupsingh et al. | Dec 2009 | A1 |
20100058231 | Duarte et al. | Mar 2010 | A1 |
20100088616 | Park et al. | Apr 2010 | A1 |
20100094809 | Consul et al. | Apr 2010 | A1 |
20100121636 | Burke et al. | May 2010 | A1 |
20100123724 | Moore et al. | May 2010 | A1 |
20100124906 | Hautala | May 2010 | A1 |
20100125785 | Moore et al. | May 2010 | A1 |
20100162138 | Pascal et al. | Jun 2010 | A1 |
20100177048 | Semenets et al. | Jul 2010 | A1 |
20100179991 | Lorch et al. | Jul 2010 | A1 |
20100199228 | Latta et al. | Aug 2010 | A1 |
20100235746 | Anzures et al. | Sep 2010 | A1 |
20100251158 | Geppert et al. | Sep 2010 | A1 |
20100279663 | Wang et al. | Nov 2010 | A1 |
20100281409 | Rainisto et al. | Nov 2010 | A1 |
20100287249 | Yigang et al. | Nov 2010 | A1 |
20100299601 | Kaplan et al. | Nov 2010 | A1 |
20100306185 | Smith et al. | Dec 2010 | A1 |
20100309149 | Blumenberg et al. | Dec 2010 | A1 |
20100325194 | Williamson et al. | Dec 2010 | A1 |
20100332518 | Song et al. | Dec 2010 | A1 |
20110003587 | Belz et al. | Jan 2011 | A1 |
20110009109 | Hyon | Jan 2011 | A1 |
20110012919 | Tai et al. | Jan 2011 | A1 |
20110054830 | Logan | Mar 2011 | A1 |
20110059769 | Brunolli | Mar 2011 | A1 |
20110080356 | Kang et al. | Apr 2011 | A1 |
20110087747 | Hirst et al. | Apr 2011 | A1 |
20110092190 | Willey et al. | Apr 2011 | A1 |
20110151418 | Delespaul et al. | Jun 2011 | A1 |
20110157046 | Lee et al. | Jun 2011 | A1 |
20110164058 | Lemay | Jul 2011 | A1 |
20110167383 | Schuller et al. | Jul 2011 | A1 |
20110183650 | Mckee | Jul 2011 | A1 |
20110201387 | Paek et al. | Aug 2011 | A1 |
20110221685 | Lee et al. | Sep 2011 | A1 |
20110254684 | Antoci et al. | Oct 2011 | A1 |
20110265041 | Ganetakos et al. | Oct 2011 | A1 |
20110276901 | Zambetti et al. | Nov 2011 | A1 |
20110279323 | Hung et al. | Nov 2011 | A1 |
20110294525 | Jonsson | Dec 2011 | A1 |
20110304648 | Kim et al. | Dec 2011 | A1 |
20110306393 | Goldman et al. | Dec 2011 | A1 |
20110316769 | Boettcher et al. | Dec 2011 | A1 |
20120008526 | Borghei et al. | Jan 2012 | A1 |
20120022872 | Gruber et al. | Jan 2012 | A1 |
20120038546 | Cromer et al. | Feb 2012 | A1 |
20120054655 | Kang et al. | Mar 2012 | A1 |
20120060077 | Mate et al. | Mar 2012 | A1 |
20120060089 | Heo et al. | Mar 2012 | A1 |
20120102437 | Worley et al. | Apr 2012 | A1 |
20120105358 | Momeyer et al. | May 2012 | A1 |
20120108215 | Kameli et al. | May 2012 | A1 |
20120117507 | Tseng et al. | May 2012 | A1 |
20120131458 | Hayes et al. | May 2012 | A1 |
20120136855 | Ni et al. | May 2012 | A1 |
20120143361 | Kurabayashi et al. | Jun 2012 | A1 |
20120149405 | Bhat | Jun 2012 | A1 |
20120150970 | Peterson et al. | Jun 2012 | A1 |
20120157114 | Alameh et al. | Jun 2012 | A1 |
20120158511 | Lucero et al. | Jun 2012 | A1 |
20120172088 | Kirch et al. | Jul 2012 | A1 |
20120185547 | Hugg et al. | Jul 2012 | A1 |
20120218177 | Pang et al. | Aug 2012 | A1 |
20120233571 | Wever et al. | Sep 2012 | A1 |
20120239949 | Kalyanasundaram et al. | Sep 2012 | A1 |
20120254324 | Majeti et al. | Oct 2012 | A1 |
20120254325 | Majeti et al. | Oct 2012 | A1 |
20120302256 | Pai et al. | Nov 2012 | A1 |
20120304084 | Kim et al. | Nov 2012 | A1 |
20120306770 | Moore et al. | Dec 2012 | A1 |
20120311032 | Murphy et al. | Dec 2012 | A1 |
20120313847 | Boda et al. | Dec 2012 | A1 |
20130007665 | Chaudhri et al. | Jan 2013 | A1 |
20130026293 | Schneider et al. | Jan 2013 | A1 |
20130053007 | Cosman et al. | Feb 2013 | A1 |
20130054634 | Chakraborty et al. | Feb 2013 | A1 |
20130063364 | Moore | Mar 2013 | A1 |
20130065566 | Gisby et al. | Mar 2013 | A1 |
20130067027 | Song et al. | Mar 2013 | A1 |
20130091298 | Ozzie et al. | Apr 2013 | A1 |
20130091443 | Park et al. | Apr 2013 | A1 |
20130093833 | Al-asaaed et al. | Apr 2013 | A1 |
20130120106 | Cauwels et al. | May 2013 | A1 |
20130159919 | Leydon | Jun 2013 | A1 |
20130159941 | Langlois et al. | Jun 2013 | A1 |
20130204897 | Mcdougall | Aug 2013 | A1 |
20130205210 | Jeon et al. | Aug 2013 | A1 |
20130212470 | Karunamuni et al. | Aug 2013 | A1 |
20130222230 | Choi et al. | Aug 2013 | A1 |
20130222236 | GÄrdenfors et al. | Aug 2013 | A1 |
20130234924 | Janefalkar et al. | Sep 2013 | A1 |
20130243924 | Bhandari et al. | Sep 2013 | A1 |
20130244633 | Jacobs et al. | Sep 2013 | A1 |
20130246329 | Pasquero et al. | Sep 2013 | A1 |
20130254714 | Shin et al. | Sep 2013 | A1 |
20130259247 | Kim | Oct 2013 | A1 |
20130262298 | Morley et al. | Oct 2013 | A1 |
20130275923 | Griffin et al. | Oct 2013 | A1 |
20130275924 | Weinberg et al. | Oct 2013 | A1 |
20130282844 | Logan et al. | Oct 2013 | A1 |
20130300645 | Fedorov | Nov 2013 | A1 |
20130301482 | Katis et al. | Nov 2013 | A1 |
20130310089 | Gianoukos et al. | Nov 2013 | A1 |
20130322634 | Bennett et al. | Dec 2013 | A1 |
20130325970 | Roberts et al. | Dec 2013 | A1 |
20130346882 | Shiplacoff et al. | Dec 2013 | A1 |
20130347018 | Limp et al. | Dec 2013 | A1 |
20140012927 | Gertzfield et al. | Jan 2014 | A1 |
20140025737 | Kruglick | Jan 2014 | A1 |
20140032682 | Prado et al. | Jan 2014 | A1 |
20140055552 | Song et al. | Feb 2014 | A1 |
20140059448 | Lee | Feb 2014 | A1 |
20140066105 | Bridge | Mar 2014 | A1 |
20140073256 | Newham et al. | Mar 2014 | A1 |
20140082501 | Bae et al. | Mar 2014 | A1 |
20140085487 | Park et al. | Mar 2014 | A1 |
20140136989 | Choi | May 2014 | A1 |
20140136990 | Gonnen et al. | May 2014 | A1 |
20140156262 | Yuen et al. | Jun 2014 | A1 |
20140163954 | Joshi et al. | Jun 2014 | A1 |
20140181183 | Yamamoto et al. | Jun 2014 | A1 |
20140181205 | Sherrets et al. | Jun 2014 | A1 |
20140222933 | Stovicek et al. | Aug 2014 | A1 |
20140240122 | Roberts et al. | Aug 2014 | A1 |
20140282211 | Ady et al. | Sep 2014 | A1 |
20140294167 | Kim et al. | Oct 2014 | A1 |
20140337438 | Govande et al. | Nov 2014 | A1 |
20140344711 | Hallerstrom Sjostedt et al. | Nov 2014 | A1 |
20140354527 | Chen et al. | Dec 2014 | A1 |
20140365944 | Moore et al. | Dec 2014 | A1 |
20150007049 | Langlois | Jan 2015 | A1 |
20150040029 | Koum et al. | Feb 2015 | A1 |
20150042852 | Lee et al. | Feb 2015 | A1 |
20150046828 | Desai et al. | Feb 2015 | A1 |
20150052212 | Flam | Feb 2015 | A1 |
20150058720 | Smadja et al. | Feb 2015 | A1 |
20150089660 | Song et al. | Mar 2015 | A1 |
20150100537 | Grieves et al. | Apr 2015 | A1 |
20150102992 | Klement et al. | Apr 2015 | A1 |
20150113435 | Phillips | Apr 2015 | A1 |
20150169893 | Desai | Jun 2015 | A1 |
20150172393 | Oplinger | Jun 2015 | A1 |
20150172584 | Park et al. | Jun 2015 | A1 |
20150180980 | Welinder et al. | Jun 2015 | A1 |
20150185849 | Ramsay et al. | Jul 2015 | A1 |
20150185995 | Shoemaker et al. | Jul 2015 | A1 |
20150188861 | Esplin et al. | Jul 2015 | A1 |
20150188869 | Smilak et al. | Jul 2015 | A1 |
20150201062 | Shih et al. | Jul 2015 | A1 |
20150220774 | Ebersman et al. | Aug 2015 | A1 |
20150222586 | Ebersman et al. | Aug 2015 | A1 |
20150227782 | Salvador et al. | Aug 2015 | A1 |
20150242114 | Hirabayashi et al. | Aug 2015 | A1 |
20150248389 | Kahn et al. | Sep 2015 | A1 |
20150256491 | Eatough et al. | Sep 2015 | A1 |
20150264303 | Chastney et al. | Sep 2015 | A1 |
20150269432 | Motoi | Sep 2015 | A1 |
20150271120 | Langholz | Sep 2015 | A1 |
20150286387 | Gu et al. | Oct 2015 | A1 |
20150286391 | Jacobs et al. | Oct 2015 | A1 |
20150312184 | Langholz et al. | Oct 2015 | A1 |
20150312185 | Langholz et al. | Oct 2015 | A1 |
20150326510 | Tomlinson et al. | Nov 2015 | A1 |
20150331881 | Myles | Nov 2015 | A1 |
20150347007 | Jong et al. | Dec 2015 | A1 |
20150347985 | Gross et al. | Dec 2015 | A1 |
20150350141 | Yang et al. | Dec 2015 | A1 |
20150370455 | Van Os et al. | Dec 2015 | A1 |
20160026730 | Hasan | Jan 2016 | A1 |
20160036996 | Midholt et al. | Feb 2016 | A1 |
20160041597 | Graham et al. | Feb 2016 | A1 |
20160041966 | Pasquero et al. | Feb 2016 | A1 |
20160044269 | Kang | Feb 2016 | A1 |
20160054841 | Yang et al. | Feb 2016 | A1 |
20160062540 | Yang et al. | Mar 2016 | A1 |
20160062589 | Wan et al. | Mar 2016 | A1 |
20160065707 | Yang et al. | Mar 2016 | A1 |
20160065708 | Yang et al. | Mar 2016 | A1 |
20160066277 | Yang et al. | Mar 2016 | A1 |
20160073034 | Mukherjee et al. | Mar 2016 | A1 |
20160073223 | Woolsey | Mar 2016 | A1 |
20160080552 | Keating et al. | Mar 2016 | A1 |
20160088146 | Ying et al. | Mar 2016 | A1 |
20160088335 | Zucchetta | Mar 2016 | A1 |
20160092431 | Motoi | Mar 2016 | A1 |
20160098186 | Sugiura | Apr 2016 | A1 |
20160132232 | Baba et al. | May 2016 | A1 |
20160165032 | Chang | Jun 2016 | A1 |
20160165600 | Choi et al. | Jun 2016 | A1 |
20160182410 | Janakiraman et al. | Jun 2016 | A1 |
20160202889 | Shin et al. | Jul 2016 | A1 |
20160224540 | Stewart et al. | Aug 2016 | A1 |
20160239724 | Arfvidsson et al. | Aug 2016 | A1 |
20160261790 | Lee et al. | Sep 2016 | A1 |
20160274756 | Sakaguchi | Sep 2016 | A1 |
20160277885 | Shan et al. | Sep 2016 | A1 |
20160294958 | Zhang | Oct 2016 | A1 |
20160295384 | Shan et al. | Oct 2016 | A1 |
20160299526 | Inagaki et al. | Oct 2016 | A1 |
20160320931 | Kovacs et al. | Nov 2016 | A1 |
20160337301 | Rollins et al. | Nov 2016 | A1 |
20160342141 | Koumaiha et al. | Nov 2016 | A1 |
20160359771 | Sridhar | Dec 2016 | A1 |
20170026430 | Beckhardt et al. | Jan 2017 | A1 |
20170041549 | Kim et al. | Feb 2017 | A1 |
20170048686 | Chang et al. | Feb 2017 | A1 |
20170063753 | Probasco et al. | Mar 2017 | A1 |
20170068439 | Mohseni | Mar 2017 | A1 |
20170075878 | Jon et al. | Mar 2017 | A1 |
20170083189 | Yang et al. | Mar 2017 | A1 |
20170083202 | Yang et al. | Mar 2017 | A1 |
20170093780 | Lieb et al. | Mar 2017 | A1 |
20170147197 | Yang et al. | May 2017 | A1 |
20170153795 | Yang et al. | Jun 2017 | A1 |
20170220212 | Yang et al. | Aug 2017 | A1 |
20170339264 | Steel et al. | Nov 2017 | A1 |
20170344257 | Gnedin et al. | Nov 2017 | A1 |
20170359302 | Van Os et al. | Dec 2017 | A1 |
20180034765 | Keszler et al. | Feb 2018 | A1 |
20180039406 | Kong et al. | Feb 2018 | A1 |
20180047189 | Diverdi et al. | Feb 2018 | A1 |
20180063324 | Van Meter, II | Mar 2018 | A1 |
20180121074 | Peron et al. | May 2018 | A1 |
20180143761 | Choi et al. | May 2018 | A1 |
20180146349 | Chang et al. | May 2018 | A1 |
20180239520 | Hinckley et al. | Aug 2018 | A1 |
20180270627 | Chang et al. | Sep 2018 | A1 |
20180309801 | Rathod | Oct 2018 | A1 |
20180329586 | Sundstrom et al. | Nov 2018 | A1 |
20180329622 | Missig et al. | Nov 2018 | A1 |
20180329672 | Sadak et al. | Nov 2018 | A1 |
20180349020 | Jon et al. | Dec 2018 | A1 |
20190187889 | Moon et al. | Jun 2019 | A1 |
20190265844 | Burkert et al. | Aug 2019 | A1 |
20190303423 | Thimbleby | Oct 2019 | A1 |
20190320301 | Chang et al. | Oct 2019 | A1 |
20190339822 | Devine et al. | Nov 2019 | A1 |
20200089374 | Hill et al. | Mar 2020 | A1 |
20200089402 | Kakani et al. | Mar 2020 | A1 |
20200110798 | Jon et al. | Apr 2020 | A1 |
20200118325 | Sasikumar et al. | Apr 2020 | A1 |
20200211250 | Sasikumar et al. | Jul 2020 | A1 |
20200348807 | Garcia et al. | Nov 2020 | A1 |
20200379638 | Zhu et al. | Dec 2020 | A1 |
20200380208 | Garcia, III et al. | Dec 2020 | A1 |
20200408521 | Lyons et al. | Dec 2020 | A1 |
20210034860 | Bednarowicz et al. | Feb 2021 | A1 |
20210149549 | Ubillos et al. | May 2021 | A1 |
20210150121 | Thimbleby | May 2021 | A1 |
20210342535 | Garcia et al. | Nov 2021 | A1 |
20220057931 | Zhu et al. | Feb 2022 | A1 |
20220291793 | Zambetti et al. | Sep 2022 | A1 |
20230079965 | Garcia et al. | Mar 2023 | A1 |
20230152964 | Zhu et al. | May 2023 | A1 |
20230393705 | Krenn | Dec 2023 | A1 |
20240004521 | Devine et al. | Jan 2024 | A1 |
Number | Date | Country |
---|---|---|
2015100705 | Jun 2015 | AU |
2022201622 | Mar 2022 | AU |
101046721 | Oct 2007 | CN |
101129059 | Feb 2008 | CN |
101276255 | Oct 2008 | CN |
101374090 | Feb 2009 | CN |
101535940 | Sep 2009 | CN |
101853132 | Oct 2010 | CN |
201928419 | Aug 2011 | CN |
102215374 | Oct 2011 | CN |
102265586 | Nov 2011 | CN |
102414755 | Apr 2012 | CN |
102695302 | Sep 2012 | CN |
103119968 | May 2013 | CN |
103207674 | Jul 2013 | CN |
103309606 | Sep 2013 | CN |
103399703 | Nov 2013 | CN |
103440247 | Dec 2013 | CN |
103460651 | Dec 2013 | CN |
103473004 | Dec 2013 | CN |
103500079 | Jan 2014 | CN |
103581544 | Feb 2014 | CN |
103583031 | Feb 2014 | CN |
103685729 | Mar 2014 | CN |
103809905 | May 2014 | CN |
103959751 | Jul 2014 | CN |
104205785 | Dec 2014 | CN |
104471521 | Mar 2015 | CN |
104487927 | Apr 2015 | CN |
104487928 | Apr 2015 | CN |
104685470 | Jun 2015 | CN |
205263700 | May 2016 | CN |
105874447 | Aug 2016 | CN |
106415476 | Feb 2017 | CN |
106575149 | Apr 2017 | CN |
106843711 | Jun 2017 | CN |
107122049 | Sep 2017 | CN |
107710197 | Feb 2018 | CN |
109600456 | Apr 2019 | CN |
2172833 | Apr 2010 | EP |
2490432 | Aug 2012 | EP |
2574026 | Mar 2013 | EP |
2582120 | Apr 2013 | EP |
2610701 | Jul 2013 | EP |
2610701 | Apr 2014 | EP |
2849042 | Mar 2015 | EP |
2470585 | Dec 2010 | GB |
2550639 | Nov 2017 | GB |
11-98249 | Apr 1999 | JP |
2002-163217 | Jun 2002 | JP |
2002-366485 | Dec 2002 | JP |
2003-141050 | May 2003 | JP |
2006-72489 | Mar 2006 | JP |
2006-113637 | Apr 2006 | JP |
2006-129429 | May 2006 | JP |
2006-135667 | May 2006 | JP |
2008-526156 | Jul 2008 | JP |
2008-546069 | Dec 2008 | JP |
2010-503126 | Jan 2010 | JP |
2010-503332 | Jan 2010 | JP |
2011-65654 | Mar 2011 | JP |
2011-107823 | Jun 2011 | JP |
2012-508530 | Apr 2012 | JP |
2013-48389 | Mar 2013 | JP |
2013-542522 | Nov 2013 | JP |
10-2004-0089329 | Oct 2004 | KR |
2008030972 | Mar 2008 | WO |
2009071112 | Jun 2009 | WO |
2010054373 | May 2010 | WO |
2010059306 | May 2010 | WO |
2011011224 | Jan 2011 | WO |
2011127457 | Oct 2011 | WO |
2012128824 | Sep 2012 | WO |
2012166277 | Dec 2012 | WO |
2012170446 | Dec 2012 | WO |
2013021385 | Feb 2013 | WO |
2013048880 | Apr 2013 | WO |
2013093558 | Jun 2013 | WO |
2013169854 | Nov 2013 | WO |
2013169870 | Nov 2013 | WO |
2013169875 | Nov 2013 | WO |
2013169877 | Nov 2013 | WO |
2014105276 | Jul 2014 | WO |
2014197340 | Dec 2014 | WO |
2015038684 | Mar 2015 | WO |
2015087084 | Jun 2015 | WO |
2015120358 | Aug 2015 | WO |
2015183755 | Dec 2015 | WO |
2017027632 | Feb 2017 | WO |
2017192881 | Nov 2017 | WO |
2018009404 | Jan 2018 | WO |
Entry |
---|
Office Action received for Australian Patent Application No. 2022200514, mailed on Feb. 15, 2023, 2 pages. |
Decision on Appeal received for U.S. Appl. No. 16/145,033, mailed on Apr. 4, 2023, 9 pages. |
Decision to Refuse received for European Patent Application No. 22209306.4, mailed on Mar. 20, 2023, 2 pages. |
Intention to Grant received for European Patent Application No. 20197945.7, mailed on Mar. 28, 2023, 9 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/989,086, mailed on Apr. 12, 2023, 21 pages. |
Notice of Allowance received for Chinese Patent Application No. 202111644466.1, mailed on Mar. 30, 2023, 2 pages (1 page of English Translation and 1 page of Official Copy). |
Office Action received for European Patent Application No. 20723742.1, mailed on Jan. 2, 2023, 10 pages. |
Office Action received for Japanese Patent Application No. 2021-166451, mailed on Jan. 5, 2023, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
Communication of the Board of Appeal received for European Patent Application No. 15728307.8, mailed on Sep. 14, 2022, 9 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/519,229, mailed on Oct. 4, 2022, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 16/936,164, mailed on Sep. 21, 2022, 9 pages. |
Decision of Board of Appeal received for European Patent Application No. 15728307.8, mailed on Dec. 8, 2022, 17 pages. |
Minutes of the Oral Proceedings received for European Patent Application No. 15729286.3, mailed on Dec. 6, 2022, 5 pages. |
Communication of the Board of Appeal received for European Patent Application No. 15729286.3, mailed on Oct. 6, 2022, 8 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/936,164, mailed on Oct. 13, 2022, 3 pages. |
Office Action received for European Patent Application No. 16807953.1, mailed on Oct. 7, 2022, 6 pages. |
Office Action received for Australian Patent Application No. 2022200514, mailed on Jan. 17, 2023, 3 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/936,164, mailed on Aug. 23, 2022, 5 pages. |
Examiner's Answer to Appeal Brief received for U.S. Appl. No. 16/145,033, mailed on Aug. 4, 2022, 10 pages. |
Extended European Search Report received for European Patent Application No. 22152524.9, mailed on May 2, 2022, 10 pages. |
Final Office Action received for U.S. Appl. No. 16/936,164, mailed on Jul. 6, 2022, 21 pages. |
Notice of Acceptance received for Australian Patent Application No. 2021202815, mailed on Jun. 16, 2022, 3 pages. |
Techniqued, “How to Sent Voice Messages in WhatsApp”, Published on YouTube.com, Available at: https://www.youtube.com/watch?v=mkJqYO984v0, Aug. 12, 2013, 1 page. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/936,164, mailed on Oct. 28, 2022, 3 pages. |
Minutes of Oral Proceedings received for European Patent Application No. 15728307.8, mailed on Nov. 11, 2022, 4 pages. |
Notice of Allowance received for U.S. Appl. No. 17/519,229, mailed on Nov. 10, 2022, 9 pages. |
“How to use popular SNS confidence (wechat) in China 2 _ voice message, press together, shake function etc.”, Available at: <http://seechina365.com/2014/04/05/wechat02/>, Apr. 5, 2014, 27 pages. |
“WhatsApp” users over 400 million people! I tried to investigate the most used messaging application in the world, Available at “http://www.appps.jp/2128786/”, Jan. 24, 2014, 10 pages. |
Advisory Action received for U.S. Appl. No. 14/846,574, mailed on Jul. 31, 2020, 8 pages. |
Advisory Action received for U.S. Appl. No. 16/145,033, mailed on Nov. 2, 2021, 5 pages. |
Advisory Action received for U.S. Appl. No. 16/454,884, mailed on Jan. 1, 2021, 6 pages. |
Applicant initiated interview summary received for U.S. Appl. No. 15/488,093, mailed on Jan. 14, 2020, 4 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 14/846,574, mailed on Feb. 3, 2020, 6 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 14/846,574, mailed on Jan. 14, 2021, 5 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 14/846,574, mailed on Jul. 21, 2020, 7 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/145,033, mailed on Apr. 30, 2021, 4 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/145,033, mailed on Jun. 29, 2020, 5 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/145,033, mailed on Nov. 24, 2020, 4 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/145,033, mailed on Oct. 7, 2021, 4 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/454,884, mailed on Dec. 4, 2020, 4 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/454,884, mailed on Jun. 2, 2020, 3 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/601,064, mailed on Dec. 14, 2020, 5 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/736,711, mailed on Oct. 16, 2020, 3 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/936,164, mailed on Mar. 22, 2022, 4 pages. |
Board Decision received for Chinese Patent Application No. 201580029071.7, mailed on Jul. 13, 2021, 2 pages. |
Brief Communication Regarding Oral Proceedings received for European Patent Application No. 17167629.9, mailed on Nov. 12, 2020, 2 pages. |
Brief Communication Regarding Oral Proceedings received for European Patent Application No. 19724963.4, mailed on Jun. 22, 2021, 2 pages. |
Certificate of Examination received for Australian Patent Application No. 2019100490, mailed on Oct. 16, 2019, 2 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 14/928,865, mailed on Aug. 5, 2019, 2 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 14/928,865, mailed on May 16, 2019, 2 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 15/366,763, mailed on Jan. 2, 2020, 5 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 15/366,890, mailed on Feb. 12, 2020, 2 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 15/488,093, mailed on Jun. 15, 2020, 2 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 15/488,093, mailed on Jun. 30, 2020, 2 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/736,711, mailed on Jun. 17, 2021, 6 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/736,711, mailed on May 17, 2021, 6 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 17/373,272, mailed on Apr. 26, 2022, 5 pages. |
Decision on Appeal received for U.S. Appl. No. 14/503,355, mailed on Aug. 25, 2020, 10 pages. |
Decision on Appeal received for U.S. Appl. No. 16/454,884, mailed on Feb. 16, 2022, 12 pages. |
Decision to Grant received for Danish Patent Application No. PA201870385, mailed on Mar. 26, 2020, 2 pages. |
Decision to Grant received for European Patent Application No. 16844879.3, mailed on Sep. 24, 2020, 2 pages. |
Decision to Grant received for European Patent Application No. 19724963.4, mailed on Feb. 3, 2022, 2 pages. |
Decision to Refuse received for European Patent Application No. 15728307.8, mailed on Dec. 18, 2019, 14 pages. |
Decision to Refuse received for European Patent Application No. 15729286.3, mailed on Dec. 18, 2019, 13 pages. |
Decision to Refuse received for European Patent Application No. 17167629.9, mailed on Nov. 24, 2020, 2 pages. |
Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/503,355, mailed on Apr. 17, 2020, 17 pages. |
Examiner's Answer to Appeal Brief received for U.S. Appl. No. 16/454,884, mailed on Sep. 17, 2021, 33 pages. |
Extended European Search Report received for European Patent Application No. 16844879.3, mailed on Mar. 1, 2019, 6 pages. |
Extended European Search Report Received for European Patent Application No. 17167629.9, mailed on Jun. 2, 2017, 7 pages. |
Extended European Search Report received for European Patent Application No. 20197945.7, mailed on Feb. 9, 2021, 8 pages. |
Extended European Search Report received for European Patent Application No. 16807953.1, mailed on Dec. 4, 2018, 7 Pages. |
Final Office Action received for U.S. Appl. No. 14/503,355, mailed on May 20, 2019, 27 pages. |
Final Office Action received for U.S. Appl. No. 14/503,355, mailed on Sep. 8, 2017, 25 pages. |
Final Office Action received for U.S. Appl. No. 14/817,572, mailed on Mar. 23, 2017, 14 pages. |
Final Office Action received for U.S. Appl. No. 14/838,235, mailed on Jun. 15, 2016, 18 pages. |
Final Office Action received for U.S. Appl. No. 14/841,623, mailed on Sep. 5, 2017, 16 pages. |
Final Office Action received for U.S. Appl. No. 14/846,574, mailed on Jun. 4, 2020, 25 pages. |
Final Office Action received for U.S. Appl. No. 14/846,574, mailed on May 10, 2019, 36 pages. |
Final Office Action received for U.S. Appl. No. 14/928,865, mailed on Dec. 5, 2018, 15 pages. |
Final Office Action received for U.S. Appl. No. 15/188,081, mailed on Dec. 13, 2018, 10 pages. |
Final Office Action received for U.S. Appl. No. 16/145,033, mailed on Jul. 6, 2021, 113 pages. |
Final Office Action received for U.S. Appl. No. 16/145,033, mailed on Sep. 22, 2020, 49 pages. |
Final Office Action received for U.S. Appl. No. 16/454,884, mailed on Sep. 11, 2020, 28 pages. |
Final Office Action received for U.S. Appl. No. 16/601,064, mailed on Mar. 8, 2021, 8 pages. |
Final Office Action received for U.S. Appl. No. 16/736,711, mailed on Dec. 10, 2020, 11 pages. |
How to Move Mail to Different Folders in Gmail, Available online at <https://web.archive.org/web/20140731230338/http://www.wikihow.com/Move-Mail-to-Different-Folders-in-Gmail>, Jul. 31, 2014, pp. 1-4. |
Intention to Grant received for Danish Patent Application No. PA201570550, mailed on Dec. 22, 2016, 2 pages. |
Intention to Grant received for Danish Patent Application No. PA201870385, mailed on Jan. 24, 2020, 2 pages. |
Intention to Grant received for European Patent Application No. 16844879.3, mailed on May 11, 2020, 8 pages. |
Intention to Grant received for European Patent Application No. 19724963.4, mailed on Sep. 20, 2021, 7 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/032305, mailed on Dec. 15, 2016, 8 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/043487, mailed on Feb. 16, 2017, 13 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/044083, mailed on Mar. 16, 2017, 24 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/025418, mailed on Dec. 21, 2017, 16 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/046828, mailed on Mar. 1, 2018, 19 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/048044, mailed on Mar. 22, 2018, 8 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/024790, mailed on Nov. 19, 2020, 11 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/028215, mailed on Dec. 16, 2021, 13 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/046787, mailed on Mar. 16, 2017, 19 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/025418, mailed on Jul. 1, 2016, 20 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/046828, mailed on Dec. 15, 2016, 22 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/048044, mailed on Oct. 31, 2016, 9 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/024790, mailed on Sep. 11, 2019, 18 pages. |
International Search Report and written Opinion received for PCT Patent Application No. PCT/US2020/028215, mailed on Aug. 10, 2020, 18 pages. |
Invitation to Pay Additional Fee received for PCT Patent Application No. PCT/US2019/024790, mailed on Jul. 18, 2019, 10 pages. |
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/044083, mailed on Nov. 4, 2015, 11 pages. |
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2016/046828, mailed on Sep. 23, 2016, 2 pages. |
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/028215, mailed on Jun. 19, 2020, 11 pages. |
Minutes of Oral Proceedings received for European Patent Application No. 15728307.8, mailed on Dec. 13, 2019, 4 pages. |
Minutes of Oral Proceedings received for European Patent Application No. 15729286.3, mailed on Dec. 13, 2019, 4 pages. |
Minutes of the Oral Proceedings received for European Patent Application No. 19724963.4, mailed on Sep. 3, 2021, 6 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/817,572, mailed on Sep. 12, 2016, 9 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/503,355, mailed on Dec. 30, 2016, 23 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/503,355, mailed on Sep. 4, 2018, 25 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/841,608, mailed on Apr. 12, 2017, 9 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/841,614, mailed on Jul. 27, 2017, 13 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/841,623, mailed on Feb. 2, 2017, 17 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/846,574, mailed on Nov. 29, 2017, 27 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/846,574, mailed on Sep. 24, 2020, 29 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/846,574, mailed on Sep. 30, 2019, 29 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/928,865, mailed on Mar. 27, 2018, 15 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/142,661, mailed on Jan. 25, 2017, 29 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/188,081, mailed on Jun. 8, 2017, 17 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/188,081, mailed on Mar. 30, 2018, 21 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/366,763, mailed on Mar. 8, 2019, 14 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/366,890, mailed on May 8, 2019, 16 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/431,435, mailed on Jun. 8, 2017, 13 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/488,093, mailed on Oct. 4, 2019, 18 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/985,570, mailed on Aug. 16, 2018, 23 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/145,033, mailed on Feb. 9, 2021, 55 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/145,033, mailed on Mar. 4, 2020, 50 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/454,884, mailed on Jan. 14, 2020, 41 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/601,064, mailed on Oct. 7, 2020, 13 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/736,711, mailed on Jun. 11, 2020, 10 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/936,164, mailed on Jan. 18, 2022, 18 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/846,574, mailed on Jun. 22, 2017, 21 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/846,574, mailed on Sep. 20, 2018, 61 pages. |
Notice of Acceptance received for Australian Patent Application No. 2015267259, mailed on Jan. 30, 2018, 3 pages. |
Notice of Acceptance received for Australian Patent Application No. 2015267260, mailed on Jan. 30, 2018, 3 pages. |
Notice of Acceptance received for Australian Patent Application No. 2018203215, mailed on Nov. 20, 2019, 3 pages. |
Notice of Acceptance received for Australian Patent Application No. 2019266054, mailed on Nov. 25, 2021, 3 pages. |
Notice of Acceptance received for Australian Patent Application No. 2020201575, mailed on Mar. 15, 2021, 3 pages. |
Notice of Allowance received for Chinese Patent Application No. 201510290133.1, mailed on Jan. 9, 2019, 2 pages. |
Notice of Allowance received for Chinese Patent Application No. 201510291012.9, mailed on Jan. 9, 2019, 2 pages. |
Notice of Allowance received for Chinese Patent Application No. 201520669842.6, mailed on May 18, 2016, 4 pages. |
Notice of Allowance received for Chinese Patent Application No. 201580029071.7, mailed on Aug. 19, 2021, 5 pages. |
Notice of Allowance received for Chinese Patent Application No. 201620830403.3, mailed on Sep. 8, 2017, 2 pages. |
Notice of Allowance received for Chinese Patent Application No. 201680031609.2, mailed on Mar. 18, 2021, 2 pages. |
Notice of Allowance received for Chinese Patent Application No. 201680049868.8, mailed on Feb. 9, 2021, 4 pages. |
Notice of Allowance received for Chinese Patent Application No. 201710267617.3, mailed on May 8, 2021, 2 pages. |
Notice of Allowance received for Chinese Patent Application No. 201811136445.7, mailed on Aug. 11, 2021, 2 pages. |
Notice of Allowance received for Danish Patent Application No. PA201570550, mailed on Mar. 20, 2017, 2 pages. |
Notice of Allowance received for Japanese Patent Application No. 2017-514992, mailed on Feb. 15, 2019, 4 pages. |
Notice of Allowance received for Japanese Patent Application No. 2017-514993, mailed on Jan. 12, 2018, 4 pages. |
Notice of Allowance received for Japanese Patent Application No. 2018-018497, mailed on Jun. 21, 2019, 4 pages. |
Notice of Allowance received for Japanese Patent Application No. 2019-050138, mailed on Jun. 15, 2020, 5 pages. |
Notice of Allowance received for Japanese Patent Application No. 2020-118723, mailed on Oct. 16, 2020, 4 pages. |
Notice of Allowance received for Japanese Patent Application No. 2020-187397, mailed on Sep. 10, 2021, 4 pages. |
Notice of Allowance received for Taiwanese Patent Application No. 104128519, mailed on Nov. 20, 2017, 5 pages. |
Notice of Allowance received for U.S. Appl. No. 14/841,608, mailed on Nov. 14, 2017, 5 pages. |
Notice of Allowance received for U.S. Appl. No. 14/817,572, mailed on Nov. 30, 2017, 26 pages. |
Notice of Allowance received for U.S. Appl. No. 14/838,235, mailed on Dec. 29, 2016, 4 pages. |
Notice of Allowance received for U.S. Appl. No. 14/838,235, mailed on Oct. 4, 2016, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 14/846,574, mailed on Feb. 9, 2021, 12 pages. |
Notice of Allowance received for U.S. Appl. No. 14/928,865, mailed on Apr. 3, 2019, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 14/928,865, mailed on Jul. 22, 2019, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 15/142,661, mailed on Feb. 15, 2018, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 15/142,661, mailed on Oct. 4, 2017, 22 pages. |
Notice of Allowance received for U.S. Appl. No. 15/188,081, mailed on Jun. 26, 2019, 8 pages. |
Notice of Allowance received for U.S. Appl. No. 15/188,081, mailed on Mar. 20, 2019, 6 pages. |
Notice of Allowance received for U.S. Appl. No. 15/366,763, mailed on Oct. 8, 2019, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 15/366,890, mailed on Nov. 14, 2019, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 15/488,093, mailed on Apr. 22, 2020, 8 pages. |
Notice of Allowance received for U.S. Appl. No. 15/876,673, mailed on May 4, 2018, 27 pages. |
Notice of Allowance received for U.S. Appl. No. 15/985,570, mailed on Mar. 13, 2019, 22 pages. |
Notice of Allowance received for U.S. Appl. No. 16/454,884, mailed on May 18, 2022, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 16/601,064, mailed on May 17, 2021, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 16/736,711, mailed on Apr. 21, 2021, 8 pages. |
Notice of Allowance received for U.S. Appl. No. 16/736,711, mailed on Jun. 8, 2021, 8 pages. |
Notice of Allowance received for U.S. Appl. No. 16/814,770, mailed on Jun. 1, 2021, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 16/814,770, mailed on Sep. 17, 2021, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 17/373,272, mailed on Feb. 9, 2022, 10 pages. |
Office Action received for Australian Patent Application No. 2015267259, mailed on Jun. 2, 2017, 2 pages. |
Office Action received for Australian Patent Application No. 2015267260, mailed on Jun. 2, 2017, 2 pages. |
Office Action received for Australian Patent Application No. 2016102028, mailed on Feb. 13, 2017, 4 pages. |
Office Action received for Australian Patent Application No. 2016102029, mailed on Feb. 22, 2017, 4 pages. |
Office Action received for Australian Patent Application No. 2017100197, mailed on Apr. 28, 2017, 4 pages. |
Office Action received for Australian Patent Application No. 2017100198, mailed on Apr. 20, 2017, 4 pages. |
Office Action received for Australian Patent Application No. 2017100760, mailed on Aug. 10, 2017, 4 pages. |
Office Action received for Australian Patent Application No. 2018203215, mailed on Mar. 29, 2019, 3 pages. |
Office Action received for Australian Patent Application No. 2019100490, mailed on Jul. 26, 2019, 4 pages. |
Office Action received for Australian Patent Application No. 2019266054, mailed on Aug. 23, 2021, 4 pages. |
Office Action received for Australian Patent Application No. 2019266054, mailed on Jun. 29, 2021, 3 pages. |
Office Action received for Australian Patent Application No. 2020201575, mailed on Dec. 22, 2020, 3 pages. |
Office Action received for Australian Patent Application No. 2021202815, mailed on Apr. 11, 2022, 2 pages. |
Office Action received for Australian Patent Application No. 2015312369, mailed on Mar. 29, 2017, 3 pages. |
Office Action received for Chinese Patent Application No. 201510290133.1, mailed on Feb. 9, 2018, 10 pages. |
Office Action Received for Chinese Patent Application No. 201510291012.9, mailed on Feb. 8, 2018, 10 pages. |
Office Action received for Chinese Patent Application No. 201580029071.7, mailed on Apr. 2, 2021, 19 pages. |
Office Action received for Chinese Patent Application No. 201580029071.7, mailed on Apr. 9, 2020, 33 pages. |
Office Action received for Chinese Patent Application No. 201580029071.7, mailed on Jul. 2, 2019, 29 pages. |
Office Action received for Chinese Patent Application No. 201580029071.7, mailed on Oct. 29, 2020, 20 pages. |
Office Action received for Chinese Patent Application No. 201620393549.6, mailed on Aug. 18, 2016, 2 pages. |
Office Action received for Chinese Patent Application No. 201620393549.6, mailed on Jan. 13, 2017, 2 pages. |
Office Action received for Chinese Patent Application No. 201620393748.7, mailed on Aug. 18, 2016, 2 pages. |
Office Action received for Chinese Patent Application No. 201620393748.7, mailed on Jan. 13, 2017, 2 pages. |
Office Action Received for Chinese Patent Application No. 201620830403.3, mailed on Jun. 7, 2017, 2 pages. |
Office Action Received for Chinese Patent Application No. 201620830403.3, mailed on Mar. 7, 2017, 3 pages. |
Office Action received for Chinese Patent Application No. 201680031609.2, mailed on Aug. 20, 2020, 6 pages. |
Office Action received for Chinese Patent Application No. 201680031609.2, mailed on Jan. 15, 2020, 20 pages. |
Office Action received for Chinese Patent Application No. 201680049868.8, mailed on May 25, 2020, 30 pages. |
Office Action received for Chinese Patent Application No. 201680049868.8, mailed on Oct. 20, 2020, 8 pages. |
Office Action received for Chinese Patent Application No. 201710267617.3, mailed on Apr. 17, 2020, 23 pages. |
Office Action received for Chinese Patent Application No. 201710267617.3, mailed on Jul. 10, 2019, 18 pages. |
Office Action received for Chinese Patent Application No. 201710267617.3, mailed on Nov. 2, 2020, 6 pages. |
Office Action received for Chinese Patent Application No. 201811136445.7, mailed on Apr. 14, 2021, 7 pages. |
Office Action received for Chinese Patent Application No. 201811136445.7, mailed on Oct. 28, 2020, 17 pages. |
Office Action received for Danish Patent Application No. PA201570550, mailed on Oct. 19, 2016, 3 pages. |
Office Action received for Danish Patent Application No. PA201770089, mailed on Apr. 25, 2017, 10 pages. |
Office Action received for Danish Patent Application No. PA201770126, mailed on Oct. 18, 2017, 3 pages. |
Office Action received for Danish Patent Application No. PA201870385, mailed on Aug. 23, 2019, 3 pages. |
Office Action received for European Patent Application No. 15729286.3, mailed on Feb. 7, 2018, 7 pages. |
Office Action received for European Patent Application No. 15728307.8, mailed on Feb. 8, 2018, 7 pages. |
Office Action received for European Patent Application No. 16807953.1, mailed on Apr. 7, 2021, 4 pages. |
Office Action received for European Patent Application No. 16807953.1, mailed on Sep. 10, 2020, 4 pages. |
Office Action received for European Patent Application No. 17167629.9, mailed on Jan. 25, 2019, 7 pages. |
Office Action received for European Patent Application No. 19724963.4, mailed on Jul. 28, 2020, 6 pages. |
Office Action received for German Patent Application No. 212015000194.6, mailed on Mar. 16, 2017, 2 pages. |
Office Action received for Japanese Patent Application No. 2017-510297, mailed on Jul. 10, 2017, 10 pages. |
Office Action received for Japanese Patent Application No. 2017-514992, mailed on Apr. 6, 2018, 11 pages. |
Office Action received for Japanese Patent Application No. 2018-018497, mailed on Dec. 10, 2018, 8 pages. |
Office Action received for Japanese Patent Application No. 2019-050138, mailed on Jan. 27, 2020, 9 pages. |
Office Action received for Japanese Patent Application No. 2020-187397, mailed on Mar. 12, 2021, 8 pages. |
Office Action received for Korean Patent Application No. 10-2017-7005628, mailed on May 10, 2017, 12 pages. |
Office Action received for Taiwanese Patent Application No. 104128519, mailed on Mar. 29, 2017, 16 pages. |
Office Action received for Taiwanese Patent Application No. 104128704, mailed on Jul. 31, 2017, 7 pages. |
Office Action received for Taiwanese Patent Application No. 104128704, mailed on Nov. 2, 2016, 12 pages. |
Record of Oral Hearing received for U.S. Appl. No. 16/454,884, mailed on Feb. 14, 2022, 13 pages. |
Result of Consultation received for European Patent Application No. 15728307.8, mailed on Nov. 21, 2019, 7 pages. |
Result of Consultation received for European Patent Application No. 15729286.3, mailed on Nov. 21, 2019, 6 pages. |
Result of Consultation received for European Patent Application No. 16807953.1, mailed on Sep. 24, 2020, 3 pages. |
Result of Consultation received for European Patent Application No. 17167629.9, mailed on Nov. 10, 2020, 3 pages. |
Result of Consultation received for European Patent Application No. 19724963.4, mailed on Jul. 8, 2021, 3 pages. |
Result of Consultation received for European Patent Application No. 19724963.4, mailed on May 31, 2021, 3 pages. |
Samsung User Manual, SM-R380_UM_EU_Eng_D13_140411.pdf, Apr. 2014, 78 pages. |
Search Report and Opinion received for Danish Patent Application No. PA201870385, mailed on Nov. 16, 2018, 10 pages. |
Search Report and Opinion received for Netherlands Patent Application No. 2015354, completed on Jun. 22, 2017, 24 pages. |
Search Report received for Danish Patent Application No. PA201770125, mailed on May 5, 2017, 10 pages. |
Search Report received for Danish Patent Application No. PA201770126, mailed on Apr. 26, 2017, 8 pages. |
Summons to Attend Oral Proceedings received for European Patent Application No. 15728307.8, mailed on Jun. 28, 2019, 10 pages. |
Summons to Attend Oral Proceedings received for European Patent Application No. 15728307.8, mailed on Mar. 7, 2022, 4 pages. |
Summons to Attend Oral Proceedings received for European Patent Application No. 15729286.3, mailed on Jun. 27, 2019, 9 pages. |
Summons to Attend Oral Proceedings received for European Patent Application No. 15729286.3, mailed on Mar. 10, 2022, 3 pages. |
Summons to Attend Oral Proceedings received for European Patent Application No. 17167629.9, mailed on Jun. 3, 2020, 11 pages. |
Summons to Attend Oral Proceedings received for European Patent Application No. 19724963.4, mailed on Dec. 23, 2020, 8 pages. |
Supplemental Notice of Allowance received for U.S. Appl. No. 14/846,574, mailed on Apr. 15, 2021, 3 pages. |
Supplemental Notice of Allowance received for U.S. Appl. No. 14/846,574, mailed on Apr. 30, 2021, 3 pages. |
“WeChat Wiki”, available on: <http://web.archive.org/web/20130514131044/http://wechat.wikia.com/wiki/WeChat_Wiki>, May 14, 2013, 12 pages. |
Notice of Allowance received for U.S. Appl. No. 12/789,440, mailed on Jan. 14, 2013, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 12/789,440, mailed on Jun. 26, 2012, 9 pages. |
Supplemental Notice of Allowance received for U.S. Appl. No. 12/789,440, mailed on Apr. 23, 2013, 2 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/503,376, mailed on Dec. 22, 2014, 21 pages. |
Notice of Allowance received for U.S. Appl. No. 14/503,376, mailed on Jul. 29, 2015, 13 pages. |
Notice of Allowance received for U.S. Appl. No. 14/503,376, mailed on Sep. 2, 2015, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 14/503,376, mailed on Sep. 24, 2015, 5 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/503,386, mailed on Jan. 7, 2015, 19 pages. |
Notice of Allowance received for U.S. Appl. No. 14/503,386, mailed on Jul. 30, 2015, 12 pages. |
Notice of Allowance received for U.S. Appl. No. 14/503,386, mailed on Sep. 24, 2015, 5 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/838,235, mailed on Jan. 5, 2016, 3 pages. |
Office Action received for Australian Patent Application No. 2015100711, issued on Jul. 27, 2015, 7 pages. |
Office Action Received for Australian Patent Application No. 2015100711, mailed on Nov. 19, 2015, 6 pages. |
Office Action received for Australian Patent Application No. 2015101188, issued on Apr. 14, 2016, 3 pages. |
Notice of Allowance received for Chinese Patent Application No. 201520365358.4, mailed on Nov. 20, 2015, 4 pages. |
Office Action received for Chinese Patent Application No. 201520365358.4, mailed on Aug. 11, 2015, 4 pages. |
Notice of Allowance received for Chinese Patent Application No. 201520365843.1, issued on Feb. 15, 2016, 5 pages. |
Office Action received for Chinese Patent Application No. 201520365843.1, mailed on Aug. 25, 2015, 4 pages. |
Office Action Received for Chinese Patent Application No. 201520365843.1, mailed on Nov. 16, 2015, 3 pages. |
Office Action received for Chinese Patent Application No. 201520669842.6, mailed on Dec. 4, 2015, 7 pages. |
Airize, “Notification & Control Center Problem Issue Solution”, Available online at: “https://www.youtube.com/watch?v=K0zCueYlaTA”, Dec. 6, 2013, 1 page. |
Ambrogi Robert, “Send Secure, Self-Destructing Messages with Wickr”, Lawsites Blog, Available online at: https://www.lawsitesblog.com/2013/11/send-secure-self-destructing-messages-wickr.html, Nov. 5, 2013, 3 pages. |
Basu Saikat, “MS Outlook Tip: How to Automatically Organize Incoming Emails”, Available online at <http://www.makeuseof.com/tag/ms-outlook-productivity-tip-how-to-move-emails-to-individual-folders-automatically/>, Sep. 27, 2009, pp. 1-6. |
CNET download.com, “WeChat for Android”, Available at: <http://download.cnet.com/WeChat/3000-2150_4-75739423.html>, Jan. 7, 2013, 6 pages. |
digitalstreetsa.com, “Why WeChat might kill Whatsapp's future . . . ”, Available at <http://digitalstreetsa.com/why-wechatmight-kill-whatsapps-future/>, Jul. 3, 2013, 10 pages. |
Filipowicz Luke, “How to use the QuickType keyboard in iOS 8”, available online at <https://www.imore.com/comment/568232>, Oct. 11, 2014, pp. 1-17. |
Grothaus Michael, “WhatsApp Introduces Major New Audio Features”, Engadget, Available at <http://www.engadget.com/2013/08/07/whatsapp-introduces-major-new-audio-features/>, Aug. 7, 2013, 4 pages. |
Hazra et al., “Sentiment Learning Using Twitter Ideograms”, 8th Annual Industrial Automation and Electromechanical Engineering Conference, 2017, pp. 115-120. |
Ikeda Masaru, “beGLOBAL SEOUL 2015 Startup Battle: Talkey”, YouTube Publisher, Online Available at: https://www.youtube.com/watch?v=4Wkp7sAAldg, May 14, 2015, 1 page. |
Inews and Tech, “How To Use The QuickType Keyboard In IOS 8”, Available online at: http://www.inewsandtech.com/how-to-use-the-quicktype-keyboard-in-ios-8/, Sep. 17, 2014, 6 pages. |
“Quick Type Keyboard on iOS 8 Makes Typing Easier”, Online available at: <https://www.youtube.com/watch?v=0CldLR4fhVU>, Jun. 3, 2014, 3 pages. |
Iosvlog Daily, “iOS 7 Notification Center Complete Walkthrough”, Available online at: “https://www.youtube.com/watch?v=gATXt-o42LA”, Jun. 10, 2013, 1 page. |
Iphone, “User Guide for iOS 7.1 Software”, Mar. 2014, 162 pages. |
Komninos et al., “Text Input on a Smart Watch”, IEEE, 2014, pp. 50-58. |
Leonard Jonathano, “How to: dismiss banner notifications or toast notifications on ios7”, Available online at: “https://www.youtube.com/watch?v=vSjHnBFIW_M”, Dec. 17, 2013, 1 page. |
Lewis Jeffery, “iOS Notification Banner Pull Down to Notification Center in iOS 7 Beta 5”, Available online at: “https://www.youtube.com/watch?v=nP0s6ETPxDg”, Aug. 6, 2013, 1 page. |
Mobile How To, “How To Send A Picture Message/MMS—Samsung Galaxy Note 3”, Online Available at: https://www.youtube.com/watch?v=-3d0z8-KeDw, Published on Nov. 3, 2013, 1 page. |
Norman Don, “Affordances and Design”, Jng.org, Available at <http://jnd.org/dn.mss/affordances_and.html>, Jan. 14, 2006, 5 pages. |
Olson Parmy, “Delete By Default: Why More Snapchat-Like Messaging Is On Its Way”, Forbes.com, Available Online at https://www.forbes.com/sites/parmyolson/2013/11/22/delete-by-default-why-more-snapchat-like-messaging-is-on-its-way, Nov. 22, 2013, 6 pages. |
Office Action received for Danish Patent Application No. PA201570550, mailed on Dec. 7, 2015, 6 pages. |
Office Action received for Danish Patent Application No. PA201570550, mailed on Jan. 19, 2016, 2 pages. |
You can use LINE perfectly if you just read this!!, How to use & set up LINE, LINE convenience book for 50 million people, Japan, EI Publishing Co., Ltd., Mar. 10, 2014, pp. 16-55. |
Patterson Ben, “iOS 7 tip: Alerts, banners, and badgesâwhats the difference?”; Available online at: “https://web.archive.org/web/20140128072440/http://heresthethingblog.com/2014/01/22/ios-7-tip-whats-difference-alert/”, Jan. 22, 2014, 5 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/032305, mailed on Sep. 10, 2015, 10 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/032309, mailed on Dec. 15, 2016, 8 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/032309, mailed on Sep. 2, 2015, 10 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/043487, mailed on Jan. 29, 2016, 19 pages. |
Invitation to Pay Additional Fees and Partial Search Report received for PCT Patent Application No. PCT/US2015/043487, mailed on Nov. 9, 2015, 4 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/044083, mailed on Feb. 4, 2016, 33 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/046787, mailed on Apr. 1, 2016, 26 pages. |
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/046787, mailed on Dec. 15, 2015, 8 pages. |
Ritchie Rene, “QuickType keyboard in iOS 8: Explained”, Retrieved via URL: https://www.imore.com/quicktype-keyboards-ios-8-explained, Jun. 21, 2014, pp. 1-19. |
S. Rohan, “WeChat Review—Communication Application with Screenshots”, Absolute Blogger, Available at <http://www.absoluteblogger.com/2012/10/wechat-review-communication-application.html>, Oct. 19, 2010, 5 pages. |
Samsung, “Samsung Gear 2 User manual”, Online Available <https://data2.manualslib.com/pdf3/76/7550/754923-samsung/gear_2.pdf?7eb313a9f65b1566bcf9ff58661c6b3a&take=binary>, XP055464984, retrieved on Apr. 5, 2018, Apr. 9, 2014, pp. 1-97. |
Samsung, “SM-G900F User Manual”, English (EU). Rev.1.0, Mar. 2014, 249 pages. |
“User Manual”, Available online at: <http://www.manualslib.com/download/754923/Samsung-Gear-2.html>, 2014, pp. 1-97. |
Softonic, “Beginners Guide to WhatsApp”, Retrieved from the Internet: https://www.youtube.com/watch?v=1YN36kYDgrk, Apr. 29, 2013, 2 pages. |
Tomic et al., “Emoticons”, FIP—Journal of Finance and Law, vol. 1, No. 1, 2013, pp. 35-42. |
WeChat Philippines, “WeChat TVC—Hold To Talk”, available at <https://www.youtube.com/watch?v=E_UxteOWVSo>, May 11, 2013, 1 page. |
Yundanfengqingdeqing, “A light cloud and light breeze; How to upload multiple pictures on Sina Weibo”, Baidu Experience, Available Online at: <https://jingyan.baidu.com/article/6181c3e074ad0d152ff15353.html>, Jan. 13, 2014, 12 pages. |
Office Action received for Chinese Patent Application No. 202111644466.1, mailed on Nov. 2, 2022, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
Office Action received for European Patent Application No. 20197945.7, mailed on Nov. 18, 2022, 5 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 17/989,086, mailed on Aug. 7, 2023, 2 pages. |
Decision to Grant received for European Patent Application No. 20197945.7, mailed on Jul. 20, 2023, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 18/153,922, mailed on Jul. 26, 2023, 9 pages. |
Summons to Attend Oral Proceedings received for European Patent Application No. 20723742.1, mailed on Jul. 21, 2023, 12 pages. |
Notice of Acceptance received for Australian Patent Application No. 2022200514, mailed on Apr. 17, 2023, 3 pages. |
Notice of Allowance received for U.S. Appl. No. 16/145,033, mailed on May 3, 2023, 5 pages. |
Record of Oral Hearing received for U.S. Appl. No. 16/145,033, mailed on Apr. 19, 2023, 16 pages. |
Notice of Allowance received for U.S. Appl. No. 16/145,033, mailed on Aug. 17, 2023, 8 pages. |
Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20723742.1, mailed on Nov. 15, 2023, 10 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 18/153,922, mailed on Nov. 3, 2023, 3 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/145,033, mailed on Jun. 23, 2023, 3 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 17/989,086, mailed on Jun. 22, 2023, 2 pages. |
Notice of Allowance received for Japanese Patent Application No. 2021-166451, mailed on Jun. 5, 2023, 4 pages (1 pages of English Translation and 3 pages of Official Copy). |
Notice of Allowance received for U.S. Appl. No. 17/989,086, mailed on Jun. 9, 2023, 8 pages. |
Office Action received for Chinese Patent Application No. 202080040442.2, mailed on Apr. 29, 2023, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/153,922, mailed on May 12, 2023, 2 pages. |
Non-Final Office Action received for U.S. Appl. No. 18/153,922, mailed on May 10, 2023, 7 pages. |
Intention to Grant received for European Patent Application No. 16807953.1, mailed on Jan. 24, 2024, 9 pages. |
Non-Final Office Action received for U.S. Appl. No. 18/237,341, mailed on Feb. 14, 2024, 13 pages. |
Notice of Allowance received for Chinese Patent Application No. 202080040442.2, mailed on Dec. 9, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
Office Action received for European Patent Application No. 22152524.9, mailed on Dec. 5, 2023, 8 pages. |
Decision to Refuse received for European Patent Application No. 20723742.1, mailed on Jan. 5, 2024, 21 pages. |
Minutes of the Oral Proceedings received for European Patent Application No. 20723742.1, mailed on Jan. 4, 2024, 8 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/237,341, mailed on Mar. 22, 2024, 4 pages. |
Caitlin McGarry, “Mail in iOS 9: Three huge changes that make email less awful”, Online Available at: https://www.macworld.com/article/225975/mail-in-iOS-9-three-huge-changes-that-will-make-email-less-awful.html, Sep. 16, 2015, 6 pages. |
Decision to Grant received for European Patent Application No. 16807953.1, mailed on May 31, 2024, 2 pages. |
Extended European Search Report received for European Patent Application No. 24161066.6, mailed on Jun. 14, 2024, 10 pages. |
Final Office Action received for U.S. Appl. No. 18/237,341, mailed on Apr. 23, 2024, 15 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/031984, mailed on Mar. 13, 2024, 21 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/031984, mailed on May 21, 2024, 21 pages. |
Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2023/031984, mailed on Jan. 9, 2024, 16 pages. |
Office Action received for Chinese Patent Application No. 202110366820.2, mailed on Apr. 12, 2024, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
Office Action received for Chinese Patent Application No. 202110744146.7, mailed on Apr. 1, 2024, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
Office Action received for Chinese Patent Application No. 202110744381.4, mailed on Mar. 25, 2024, 17 pages (6 pages of English Translation and 11 pages of Official Copy). |
Office Action received for Chinese Patent Application No. 202111244490.6, mailed on Apr. 3, 2024, 20 pages (11 pages of English Translation and 9 pages of Official Copy). |
Office Action received for European Patent Application No. 22152524.9, mailed on Jun. 25, 2024, 7 pages. |
Number | Date | Country | |
---|---|---|---|
20220386085 A1 | Dec 2022 | US |
Number | Date | Country | |
---|---|---|---|
62205562 | Aug 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16454884 | Jun 2019 | US |
Child | 17885807 | US | |
Parent | 15985570 | May 2018 | US |
Child | 16454884 | US | |
Parent | 15876673 | Jan 2018 | US |
Child | 15985570 | US | |
Parent | 15142661 | Apr 2016 | US |
Child | 15876673 | US |