Patent Grant
12131417
This relates generally to electronic devices that display images of a physical environment, including but not limited to electronic devices that display an annotation at a spatial location in an image that corresponds to a spatial location in a physical environment captured in an image.
The development of computer systems for augmented media has increased significantly in recent years. Examples of augmented media include augmented reality environments that include at least some virtual elements that replace or augment the physical world and augmented stored media that include at least some virtual elements that replace or augment stored media, such as image and video content. Input devices, such as touch-sensitive surfaces, for computer systems and other electronic computing devices are used to augment media. Example touch-sensitive surfaces include touchpads, touch-sensitive remote controls, and touch-screen displays. Such surfaces are used to manipulate user interfaces and objects therein on a display. Example user interface objects include digital images, video, text, icons, and control elements such as buttons and other graphics.
But methods and interfaces for augmenting media are cumbersome, inefficient, and limited. For example, augmentations such as user-input annotations that have a fixed spatial position relative to a portion of physical environment may be difficult for a user to locate when a current camera view of the user's device does not correspond to the portion of the physical environment. Searching for an augmentation creates a significant cognitive burden on a user, and detracts from the experience with the augmented media. Additionally, providing augmentation input for stored media (e.g., a previously captured video) is time intensive when augmentation input must be provided separately for various portions of the stored media. In addition, these methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, there is a need for computer systems with improved methods and interfaces for augmenting media data. Such methods and interfaces optionally complement or replace conventional methods for augmenting media data. Such methods and interfaces reduce the number, extent, and/or nature of the inputs from a user and produce a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.
The above deficiencies and other problems associated with interfaces for augmenting media data with virtual objects and/or annotation input are reduced or eliminated by the disclosed computer systems. In some embodiments, the computer system includes a desktop computer. In some embodiments, the computer system is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the computer system includes a personal electronic device (e.g., a wearable electronic device, such as a watch). In some embodiments, the computer system has (and/or is in communication with) a touchpad. In some embodiments, the computer system has (and/or is in communication with) a touch-sensitive display (also known as a “touch screen” or “touch-screen display”). In some embodiments, the computer system has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI in part through stylus and/or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions optionally include game playing, image editing, drawing, presenting, word processing, spreadsheet making, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music playing, note taking, and/or digital video playing. Executable instructions for performing these functions are, optionally, included in a non-transitory computer readable storage medium or other computer program product configured for execution by one or more processors.
In accordance with some embodiments, a method is performed at a computer system having a display generation component, one or more input devices, and one or more cameras. The method includes displaying, via the display generation component, a first user interface region that includes a representation of a field of view of the one or more cameras that is updated with changes in the field of view of the one or more cameras over time. The method further includes, while displaying the first user interface region including the representation of the field of view of the one or more cameras, receiving, via the one or more input devices, a first request to add an annotation to the displayed representation of the field of view of the one or more cameras. The method further includes, in response to the first request to add an annotation to the displayed representation of the field of view of the one or more cameras: replacing display of the representation of the field of view of the one or more cameras in the first user interface region with a still image of the field of view of the one or more cameras captured at a time corresponding to the receiving of the first request to add the annotation. The method further includes, while displaying the still image in the first user interface region, receiving, via the one or more input devices, a first annotation on a first portion of the still image, wherein the first portion of the still image corresponds to a first portion of a physical environment captured in the still image. The method further includes, while displaying the first annotation on the first portion of the still image in the first user interface region, receiving, via the one or more input devices, a first request to re-display the representation of the field of view of the one or more cameras in the first user interface region. The method further includes, in response to receiving the first request to re-display the representation of the field of view of the one or more cameras in the first user interface region: replacing display of the still image with the representation of the field of view of the one or more cameras in the first user interface region. The method further includes, in accordance with a determination that the first portion of the physical environment captured in the still image is currently outside of the field of view of the one or more cameras, displaying, concurrently with the representation of the field of view of the one or more cameras, an indication of a current spatial relationship of the one or more cameras relative to the first portion of the physical environment captured in the still image; and in accordance with a determination that the first portion of the physical environment captured in the still image is currently within the field of view of the one or more cameras, forgoing display of the indication.
In accordance with some embodiments, a method is performed at a computer system having a display generation component and one or more input devices. The method includes displaying, via the display generation component, a user interface that includes a video playback region. The method further includes, while displaying playback of a first portion of a video in the video playback region, receiving, via the one or more input devices, a request to add an annotation to the video playback. The method further includes, in response to receiving the request to add the annotation: pausing playback of the video at a first position in the video; and displaying a still image that corresponds to the first, paused position of the video. The method further includes, while displaying the still image, receiving, via the one or more input devices, an annotation on a first portion of a physical environment captured in the still image. The method further includes, after receiving the annotation, displaying, in the video playback region, a second portion of the video that corresponds to a second position in the video, distinct from the first position in the video, wherein the first portion of the physical environment is captured in the second portion of the video and the annotation is displayed in the second portion of the video.
In accordance with some embodiments, a method is performed at a computer system having a display generation component and one or more input devices. The method includes displaying, via the display generation component, a first previously captured media object including one or more first images, wherein the first previously captured media object was recorded and stored with first depth data corresponding to a first physical environment captured in each of the one or more first images. The method further includes, while displaying the first previously captured media object, receiving a first user request, via the one or more input devices, to add a first virtual object to the first previously captured media object. The method further includes, in response to the first user request to add the first virtual object to the first previously captured media object, displaying the first virtual object over at least a portion of a respective image in the first previously captured media object, wherein the first virtual object is displayed with at least a first position or orientation that is determined using the first depth data that corresponds to the respective image in the first previously captured media object.
In accordance with some embodiments, a method is performed at a computer system having a display generation component, a first set of one or more input devices, and a first set of one or more cameras. The method includes sending a request to a remote device to initiate a shared annotation session with a second device that includes a second display generation component, a second set of one or more input devices, and a second set of one or more cameras. The method further includes, in response to sending the request to initiate the shared annotation session with the second device, receiving an indication of acceptance of the request to initiate the shared annotation session. The method further includes, in response to receiving the indication of acceptance of the request to initiate the shared annotation session, displaying, via the first display generation component, a first prompt to move the first device toward the second device. The method further includes, after displaying the first prompt, in accordance with a determination that connection criteria for the first device and the second device are met, displaying a representation of a field of view of the first set of cameras in the shared annotation session with the second device, wherein: the connection criteria require that at least a portion of the field of view of the first device and a portion of a field of view of the second device correspond to a same portion of physical environment surrounding the first and second devices. The method further includes displaying, during the shared annotation session, one or more first virtual annotations corresponding to annotation input directed to a respective location in the physical environment by the first device is displayed via the first display generation component and one or more second virtual annotations corresponding to annotation input directed to the respective location in the physical environment by the second device is displayed via the first display generation component, provided that the respective location is included in the field of view of the first set of cameras.
In accordance with some embodiments, an electronic device includes a display generation component, optionally one or more input devices, optionally one or more touch-sensitive surfaces, optionally one or more cameras, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally one or more audio output generators, optionally one or more device orientation sensors, optionally one or more tactile output generators, optionally one or more attitude sensors for detecting changes in attitude, one or more processors, and memory storing one or more programs; the one or more programs are configured to be executed by the one or more processors and the one or more programs include instructions for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, a computer readable storage medium has stored therein instructions, which, when executed by an electronic device with a display generation component, optionally one or more input devices, optionally one or more touch-sensitive surfaces, optionally one or more cameras, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally one or more audio output generators, optionally one or more device orientation sensors, optionally one or more tactile output generators, and optionally one or more attitude sensors, cause the device to perform or cause performance of the operations of any of the methods described herein. In accordance with some embodiments, a graphical user interface on an electronic device with a display generation component, optionally one or more input devices, optionally one or more touch-sensitive surfaces, optionally one or more cameras, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally one or more audio output generators, optionally one or more device orientation sensors, optionally one or more tactile output generators, and optionally one or more attitude sensors, a memory, and one or more processors to execute one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described herein, which are updated in response to inputs, as described in any of the methods described herein. In accordance with some embodiments, an electronic device includes: a display generation component, optionally one or more input devices, optionally one or more touch-sensitive surfaces, optionally one or more cameras, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally one or more audio output generators, optionally one or more device orientation sensors, optionally one or more tactile output generators, and optionally one or more attitude sensors for detecting changes in attitude; and means for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a display generation component, optionally one or more input devices, optionally one or more touch-sensitive surfaces, optionally one or more cameras, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally one or more audio output generators, optionally one or more device orientation sensors, optionally one or more tactile output generators, and optionally one or more attitude sensors for detecting changes in attitude includes means for performing or causing performance of the operations of any of the methods described herein.
Thus, electronic devices with display generation components, optionally one or more input devices, optionally one or more touch-sensitive surfaces, optionally one or more cameras, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally one or more audio output generators, optionally one or more device orientation sensors, optionally one or more tactile output generators, and optionally one or more attitude sensors, are provided with improved methods and interfaces for displaying virtual objects in a variety of contexts, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for displaying virtual objects in a variety of contexts.
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.
Conventional methods of augmenting media often require multiple separate inputs (e.g., individual annotation of multiple frames and/or placement of augmentations relative to objects in media) to achieve an intended outcome (e.g., annotating a portion of a stored video or a live video feed and/or displaying virtual objects at positions that correspond to surfaces of physical objects in stored media). The embodiments herein provide an intuitive way for a user to augment media such as stored content, still images, and/or live video captured by one or more cameras of a device (e.g., by using depth data stored and/or captured in conjunction with image data to place augmentations and to maintain a fixed spatial relationship between augmentations and portions of a physical environment in a field of view of a camera).
The systems, methods, and GUIs described herein improve user interface interactions for augmenting media in multiple ways. For example, they make it easier to: relocalize an annotation, annotate a video, add virtual objects to previously captured media, and initiate a shared annotation session.
Below,
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact, unless the context clearly indicates otherwise.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Example embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch-screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch-screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a note taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU(s) 120 and the peripherals interface 118, is, optionally, controlled by memory controller 122.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU(s) 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.
In some embodiments, peripherals interface 118, CPU(s) 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication optionally uses any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VOIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch-sensitive display system 112 and other input or control devices 116, with peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled with any (or none) of the following: a keyboard, infrared port, USB port, stylus, and/or a pointer device such as a mouse. The one or more buttons (e.g., 208,
Touch-sensitive display system 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch-sensitive display system 112. Touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term “affordance” refers to a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to inputs directed toward the graphical user interface object). Examples of user-interactive graphical user interface objects include, without limitation, a button, slider, icon, selectable menu item, switch, hyperlink, or other user interface control.
Touch-sensitive display system 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch-sensitive display system 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch-sensitive display system 112. In some embodiments, a point of contact between touch-sensitive display system 112 and the user corresponds to a finger of the user or a stylus.
Touch-sensitive display system 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch-sensitive display system 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch-sensitive display system 112. In some embodiments, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, California.
Touch-sensitive display system 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen video resolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally makes contact with touch-sensitive display system 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch-sensitive display system 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 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, haptic feedback module (or set of instructions) 133, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 stores device/global internal state 157, as shown in
Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. In some embodiments, the external port is a Lightning connector that is the same as, or similar to and/or compatible with the Lightning connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California.
Contact/motion module 130 optionally detects contact with touch-sensitive display system 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact (e.g., by a finger or by a stylus), such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts or stylus contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event. Similarly, tap, swipe, drag, and other gestures are optionally detected for a stylus by detecting a particular contact pattern for the stylus.
In some embodiments, detecting a finger tap gesture depends on the length of time between detecting the finger-down event and the finger-up event, but is independent of the intensity of the finger contact between detecting the finger-down event and the finger-up event. In some embodiments, a tap gesture is detected in accordance with a determination that the length of time between the finger-down event and the finger-up event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4 or 0.5 seconds), independent of whether the intensity of the finger contact during the tap meets a given intensity threshold (greater than a nominal contact-detection intensity threshold), such as a light press or deep press intensity threshold. Thus, a finger tap gesture can satisfy particular input criteria that do not require that the characteristic intensity of a contact satisfy a given intensity threshold in order for the particular input criteria to be met. For clarity, the finger contact in a tap gesture typically needs to satisfy a nominal contact-detection intensity threshold, below which the contact is not detected, in order for the finger-down event to be detected. A similar analysis applies to detecting a tap gesture by a stylus or other contact. In cases where the device is capable of detecting a finger or stylus contact hovering over a touch sensitive surface, the nominal contact-detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch sensitive surface.
The same concepts apply in an analogous manner to other types of gestures. For example, a swipe gesture, a pinch gesture, a depinch gesture, and/or a long press gesture are optionally detected based on the satisfaction of criteria that are either independent of intensities of contacts included in the gesture, or do not require that contact(s) that perform the gesture reach intensity thresholds in order to be recognized. For example, a swipe gesture is detected based on an amount of movement of one or more contacts; a pinch gesture is detected based on movement of two or more contacts towards each other; a depinch gesture is detected based on movement of two or more contacts away from each other; and a long press gesture is detected based on a duration of the contact on the touch-sensitive surface with less than a threshold amount of movement. As such, the statement that particular gesture recognition criteria do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met means that the particular gesture recognition criteria are capable of being satisfied if the contact(s) in the gesture do not reach the respective intensity threshold, and are also capable of being satisfied in circumstances where one or more of the contacts in the gesture do reach or exceed the respective intensity threshold. In some embodiments, a tap gesture is detected based on a determination that the finger-down and finger-up event are detected within a predefined time period, without regard to whether the contact is above or below the respective intensity threshold during the predefined time period, and a swipe gesture is detected based on a determination that the contact movement is greater than a predefined magnitude, even if the contact is above the respective intensity threshold at the end of the contact movement. Even in implementations where detection of a gesture is influenced by the intensity of contacts performing the gesture (e.g., the device detects a long press more quickly when the intensity of the contact is above an intensity threshold or delays detection of a tap input when the intensity of the contact is higher), the detection of those gestures does not require that the contacts reach a particular intensity threshold so long as the criteria for recognizing the gesture can be met in circumstances where the contact does not reach the particular intensity threshold (e.g., even if the amount of time that it takes to recognize the gesture changes).
Contact intensity thresholds, duration thresholds, and movement thresholds are, in some circumstances, combined in a variety of different combinations in order to create heuristics for distinguishing two or more different gestures directed to the same input element or region so that multiple different interactions with the same input element are enabled to provide a richer set of user interactions and responses. The statement that a particular set of gesture recognition criteria do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met does not preclude the concurrent evaluation of other intensity-dependent gesture recognition criteria to identify other gestures that do have criteria that are met when a gesture includes a contact with an intensity above the respective intensity threshold. For example, in some circumstances, first gesture recognition criteria for a first gesture—which do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the first gesture recognition criteria to be met—are in competition with second gesture recognition criteria for a second gesture—which are dependent on the contact(s) reaching the respective intensity threshold. In such competitions, the gesture is, optionally, not recognized as meeting the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are met first. For example, if a contact reaches the respective intensity threshold before the contact moves by a predefined amount of movement, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves by the predefined amount of movement before the contact reaches the respective intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such circumstances, the first gesture recognition criteria for the first gesture still do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the first gesture recognition criteria to be met because if the contact stayed below the respective intensity threshold until an end of the gesture (e.g., a swipe gesture with a contact that does not increase to an intensity above the respective intensity threshold), the gesture would have been recognized by the first gesture recognition criteria as a swipe gesture. As such, particular gesture recognition criteria that do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met will (A) in some circumstances ignore the intensity of the contact with respect to the intensity threshold (e.g. for a tap gesture) and/or (B) in some circumstances still be dependent on the intensity of the contact with respect to the intensity threshold in the sense that the particular gesture recognition criteria (e.g., for a long press gesture) will fail if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognize an input as corresponding to an intensity-dependent gesture before the particular gesture recognition criteria recognize a gesture corresponding to the input (e.g., for a long press gesture that is competing with a deep press gesture for recognition).
Graphics module 132 includes various known software components for rendering and displaying graphics on touch-sensitive display system 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions (e.g., instructions used by haptic feedback controller 161) to produce tactile outputs using tactile output generator(s) 167 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 138 for use in location-based dialing, to camera 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 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-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 includes executable instructions to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers and/or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, Apple Push Notification Service (APNs) or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and video and music player module 152, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (in sports devices and smart watches); 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-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, and/or delete a still image or video from memory 102.
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 includes executable instructions to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch-sensitive display system 112, or on an external display connected wirelessly or via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes executable instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen 112, or on an external display connected wirelessly or via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video.
Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display system 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display system 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 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 system 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views, when touch-sensitive display system 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (i.e., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver module 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 includes one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170, and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event 187 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display system 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display system 112, when a touch is detected on touch-sensitive display system 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event 187 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video and music player module 152. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input-devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
In some embodiments, the tactile output module includes haptic feedback module 133. In some embodiments, haptic feedback module 133 aggregates and combines tactile outputs for user interface feedback from software applications on the electronic device (e.g., feedback that is responsive to user inputs that correspond to displayed user interfaces and alerts and other notifications that indicate the performance of operations or occurrence of events in user interfaces of the electronic device). Haptic feedback module 133 includes one or more of: waveform module 123 (for providing waveforms used for generating tactile outputs), mixer 125 (for mixing waveforms, such as waveforms in different channels), compressor 127 (for reducing or compressing a dynamic range of the waveforms), low-pass filter 129 (for filtering out high frequency signal components in the waveforms), and thermal controller 131 (for adjusting the waveforms in accordance with thermal conditions). In some embodiments, haptic feedback module 133 is included in haptic feedback controller 161 (
In some embodiments, haptic feedback module 133 also includes trigger module 121 (e.g., a software application, operating system, or other software module that determines a tactile output is to be generated and initiates the process for generating the corresponding tactile output). In some embodiments, trigger module 121 generates trigger signals for initiating generation of waveforms (e.g., by waveform module 123). For example, trigger module 121 generates trigger signals based on preset timing criteria. In some embodiments, trigger module 121 receives trigger signals from outside haptic feedback module 133 (e.g., in some embodiments, haptic feedback module 133 receives trigger signals from hardware input processing module 146 located outside haptic feedback module 133) and relays the trigger signals to other components within haptic feedback module 133 (e.g., waveform module 123) or software applications that trigger operations (e.g., with trigger module 121) based on activation of a user interface element (e.g., an application icon or an affordance within an application) or a hardware input device (e.g., a home button or an intensity-sensitive input surface, such as an intensity-sensitive touch screen). In some embodiments, trigger module 121 also receives tactile feedback generation instructions (e.g., from haptic feedback module 133,
Waveform module 123 receives trigger signals (e.g., from trigger module 121) as an input, and in response to receiving trigger signals, provides waveforms for generation of one or more tactile outputs (e.g., waveforms selected from a predefined set of waveforms designated for use by waveform module 123, such as the waveforms described in greater detail below with reference to
Mixer 125 receives waveforms (e.g., from waveform module 123) as an input, and mixes together the waveforms. For example, when mixer 125 receives two or more waveforms (e.g., a first waveform in a first channel and a second waveform that at least partially overlaps with the first waveform in a second channel) mixer 125 outputs a combined waveform that corresponds to a sum of the two or more waveforms. In some embodiments, mixer 125 also modifies one or more waveforms of the two or more waveforms to emphasize particular waveform(s) over the rest of the two or more waveforms (e.g., by increasing a scale of the particular waveform(s) and/or decreasing a scale of the rest of the waveforms). In some circumstances, mixer 125 selects one or more waveforms to remove from the combined waveform (e.g., the waveform from the oldest source is dropped when there are waveforms from more than three sources that have been requested to be output concurrently by tactile output generator 167).
Compressor 127 receives waveforms (e.g., a combined waveform from mixer 125) as an input, and modifies the waveforms. In some embodiments, compressor 127 reduces the waveforms (e.g., in accordance with physical specifications of tactile output generators 167 (
Low-pass filter 129 receives waveforms (e.g., compressed waveforms from compressor 127) as an input, and filters (e.g., smooths) the waveforms (e.g., removes or reduces high frequency signal components in the waveforms). For example, in some instances, compressor 127 includes, in compressed waveforms, extraneous signals (e.g., high frequency signal components) that interfere with the generation of tactile outputs and/or exceed performance specifications of tactile output generator 167 when the tactile outputs are generated in accordance with the compressed waveforms. Low-pass filter 129 reduces or removes such extraneous signals in the waveforms.
Thermal controller 131 receives waveforms (e.g., filtered waveforms from low-pass filter 129) as an input, and adjusts the waveforms in accordance with thermal conditions of device 100 (e.g., based on internal temperatures detected within device 100, such as the temperature of haptic feedback controller 161, and/or external temperatures detected by device 100). For example, in some cases, the output of haptic feedback controller 161 varies depending on the temperature (e.g. haptic feedback controller 161, in response to receiving same waveforms, generates a first tactile output when haptic feedback controller 161 is at a first temperature and generates a second tactile output when haptic feedback controller 161 is at a second temperature that is distinct from the first temperature). For example, the magnitude (or the amplitude) of the tactile outputs may vary depending on the temperature. To reduce the effect of the temperature variations, the waveforms are modified (e.g., an amplitude of the waveforms is increased or decreased based on the temperature).
In some embodiments, haptic feedback module 133 (e.g., trigger module 121) is coupled to hardware input processing module 146. In some embodiments, other input controller(s) 160 in
In some embodiments, the tactile output module includes haptic feedback controller 161 (e.g., haptic feedback controller 161 in
In some embodiments, as shown in
In some embodiments, the tactile output module includes amplifier 163. In some embodiments, amplifier 163 receives waveforms (e.g., from haptic feedback controller 161) and amplifies the waveforms prior to sending the amplified waveforms to tactile output generator 167 (e.g., any of tactile output generators 167 (
In some embodiments, the tactile output module includes sensor 169, which is coupled to tactile output generator 167. Sensor 169 detects states or state changes (e.g., mechanical position, physical displacement, and/or movement) of tactile output generator 167 or one or more components of tactile output generator 167 (e.g., one or more moving parts, such as a membrane, used to generate tactile outputs). In some embodiments, sensor 169 is a magnetic field sensor (e.g., a Hall effect sensor) or other displacement and/or movement sensor. In some embodiments, sensor 169 provides information (e.g., a position, a displacement, and/or a movement of one or more parts in tactile output generator 167) to haptic feedback controller 161 and, in accordance with the information provided by sensor 169 about the state of tactile output generator 167, haptic feedback controller 161 adjusts the waveforms output from haptic feedback controller 161 (e.g., waveforms sent to tactile output generator 167, optionally via amplifier 163).
Device 100 optionally also includes one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch-screen display.
In some embodiments, device 100 includes the touch-screen display, menu button 204 (sometimes called home button 204), push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In some embodiments, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensities of contacts on touch-sensitive display system 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 (“UI”) that are, optionally, implemented on portable multifunction device 100.
Signal strength indicator(s) for wireless communication(s), such as cellular and Wi-Fi signals;
It should be noted that the icon labels illustrated in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures, etc.), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse based input or a stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
As used herein, the term “focus selector” 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 “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact or a stylus contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average or a sum) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be readily accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
In some embodiments, contact/motion module 130 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 adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch-screen display can be set to any of a large range of predefined thresholds values without changing the trackpad or touch-screen display hardware. Additionally, in some 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).
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, a value produced by low-pass filtering the intensity of the contact over a predefined period or starting at a predefined time, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first intensity threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second intensity threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more intensity thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective option or forgo performing the respective operation) rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact transitioning from a start location and reaching an end location (e.g., a drag gesture), at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location may be based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm may be applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The user interface figures described herein optionally include various intensity diagrams that show the current intensity of the contact on the touch-sensitive surface relative to one or more intensity thresholds (e.g., a contact detection intensity threshold IT0, a light press intensity threshold ITL, a deep press intensity threshold ITD (e.g., that is at least initially higher than ITL), and/or one or more other intensity thresholds (e.g., an intensity threshold ITH that is lower than ITL)). This intensity diagram is typically not part of the displayed user interface, but is provided to aid in the interpretation of the figures. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold IT0 below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
In some embodiments, the response of the device to inputs detected by the device depends on criteria based on the contact intensity during the input. For example, for some “light press” inputs, the intensity of a contact exceeding a first intensity threshold during the input triggers a first response. In some embodiments, the response of the device to inputs detected by the device depends on criteria that include both the contact intensity during the input and time-based criteria. For example, for some “deep press” inputs, the intensity of a contact exceeding a second intensity threshold during the input, greater than the first intensity threshold for a light press, triggers a second response only if a delay time has elapsed between meeting the first intensity threshold and meeting the second intensity threshold. This delay time is typically less than 200 ms (milliseconds) in duration (e.g., 40, 100, or 120 ms, depending on the magnitude of the second intensity threshold, with the delay time increasing as the second intensity threshold increases). This delay time helps to avoid accidental recognition of deep press inputs. As another example, for some “deep press” inputs, there is a reduced-sensitivity time period that occurs after the time at which the first intensity threshold is met. During the reduced-sensitivity time period, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep press inputs. For other deep press inputs, the response to detection of a deep press input does not depend on time-based criteria.
In some embodiments, one or more of the input intensity thresholds and/or the corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, application running, rate at which the intensity is applied, number of concurrent inputs, user history, environmental factors (e.g., ambient noise), focus selector position, and the like. Example factors are described in U.S. patent application Ser. Nos. 14/399,606 and 14/624,296, which are incorporated by reference herein in their entireties.
For example,
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold ITL to an intensity between the light press intensity threshold ITL and the deep press intensity threshold ITD is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold ITD to an intensity above the deep press intensity threshold ITD is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold IT0 to an intensity between the contact-detection intensity threshold IT0 and the light press intensity threshold ITL is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold IT0 to an intensity below the contact-detection intensity threshold IT0 is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments IT0 is zero. In some embodiments, IT0 is greater than zero. In some illustrations a shaded circle or oval is used to represent intensity of a contact on the touch-sensitive surface. In some illustrations, a circle or oval without shading is used represent a respective contact on the touch-sensitive surface without specifying the intensity of the respective contact.
In some embodiments, described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., the respective operation is performed on a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., the respective operation is performed on an “up stroke” of the respective press input).
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., the respective operation is performed on an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the description of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. As described above, in some embodiments, the triggering of these responses also depends on time-based criteria being met (e.g., a delay time has elapsed between a first intensity threshold being met and a second intensity threshold being met).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user. Using tactile outputs to provide haptic feedback to a user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
User Interfaces and Associated Processes
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on an electronic device, such as portable multifunction device 100 or device 300, with a display, a touch-sensitive surface, (optionally) one or more tactile output generators for generating tactile outputs, and (optionally) one or more sensors to detect intensities of contacts with the touch-sensitive surface.
From
In
From
From
In
From
From
From
In
From
In
From
From
From
In
From
From
From
From
From
From
In
In
In
In
In
In
In
In
In
In
In
In
In
In
In
In
In
In
In
In
In
In
In
In
In
In
In
In some embodiments, displayed virtual confetti objects fade from display and/or cease to be displayed (e.g., when an amount of time that has passed since a virtual confetti object was displayed increases above a threshold time).
In
In
In
In
From
In
In 7BE, contact 7142 has lifted off of touch screen display 112. Virtual measurement object 7148 and measurement value indicator 7148 remain displayed. In
In
In
In
In
In
In
In
In some embodiments, one or more annotations (e.g., 8050-1, 8050-2, 8056-1, and/or 8056-2) have a fixed spatial relationship relative to a portion of physical environment 8000 (e.g., such that movement of device cameras relative to physical environment 8000 changes the displayed position of the annotation). In
In
From
Game application user interfaces 8063-1 and 8063-2 display basketball hoops 8074 and 8076, respectively. By providing input in the respective game application user interfaces, the users launch virtual basketball objects into the displayed representation of the field of view of the respective device cameras in an effort to make baskets in the respective basketball hoops. In some embodiments, the respective basketball hoops are fixed to the spatial positions of the respective devices such that the respective users may move the devices in an effort to create a challenge for the opponent. Game application user interfaces 8063-1 and 8063-2 also display game data regions 8078 and 8080, respectively. Game data displayed in the game data regions include, for example, a tally of points scored by successful baskets and a distance between devices 100-1 and 100-2 (e.g., to use as a basis for assigning a score to a given shot).
In
The device displays (902), via the display generation component, a first user interface region (e.g., user interface 5003) that includes a representation of a field of view of the one or more cameras that is updated with changes in the field of view of the one or more cameras over time (e.g., the representation of the field of view is continuously updated (e.g., with a preset frame rate such as 24, 48, or 60 fps, etc.) in accordance with changes occurring in the physical environment around the cameras and in accordance with movement of the cameras relative to the physical environment). For example, as shown in
While displaying the first user interface region including the representation of the field of view of the one or more cameras, the device receives (904), via the one or more input devices, a first request to add an annotation (e.g., text or figures produced and/or positioned by movement of a contact (e.g., contact by a finger or stylus) on a touch-sensitive surface) to the displayed representation of the field of view of the one or more cameras (e.g., the first request is an input by a contact that is detected in the first user interface region on a touch-screen display, (e.g., at a location that corresponds to a control to initiate annotation or at a location in the first user interface region (e.g., a location at which the annotation is to be initiated))). For example, a request to add an annotation is an input by a stylus 5012 (e.g., an input to initiate an annotation, as described with regard to
In response to the first request to add an annotation to the displayed representation of the field of view of the one or more cameras (e.g., including in response to detecting touch-down or movement of a finger contact or stylus on the touch-sensitive surface at a location corresponding to a portion of the physical environment captured within the representation of the field of view of the cameras, or a user interface object (e.g., a button for activating an AR annotation mode)), the device replaces (906) display of the representation of the field of view of the one or more cameras in the first user interface region with a still image of the field of view of the one or more cameras captured at a time corresponding to the receiving of the first request to add the annotation (e.g., pausing the live feed of the field of view of the one or more cameras (e.g., display a still image of the current field of view, while the field of view continues to change with device movement); and displaying, in the first user interface region, a still image that corresponds to the paused live feed of the field of view of the one or more cameras. For example, in response to an input by a stylus 5012 (e.g., as described with regard to
While displaying the still image in the first user interface region, the device receives (908), via the one or more input devices, a first annotation (e.g., a drawing input) on a first portion of the still image, wherein the first portion of the still image corresponds to a first portion of a physical environment captured in the still image. For example, annotation 5018 is received on a portion of a still image (e.g., a portion that includes representation 5002b of a physical mug 5002a) that corresponds to a portion of a physical environment captured in the still image (e.g., a portion of physical environment 5000 that includes physical mug 5002a) as described with regard to
While displaying the first annotation on the first portion of the still image in the first user interface region (e.g., after having received the first annotation on the first portion of the still image), the device receives (910), via the one or more input devices, a first request to re-display the representation of the field of view of the one or more cameras in the first user interface region. For example, the request to re-display the representation of the field of view of the one or more cameras in the first user interface region is an input by stylus 5012 at control 5004 for toggling between a still image mode and a video mode, as described with regard to
In response to receiving the first request to re-display the representation of the field of view of the one or more cameras in the first user interface region (e.g., including in response to detecting absence of the contact on the touch-sensitive surface for a threshold amount of time (e.g., drawing session is deemed terminated), or detecting a tap on a user interface object (e.g., a button for de-activating the AR annotation mode)) the device (910) replaces display of the still image with the representation of the field of view of the one or more cameras in the first user interface region (e.g., the representation of the field of view is continuously updated with a preset frame rate (e.g., 24, 48, or 60 fps, etc.) in accordance with changes occurring in the physical environment around the cameras and in accordance with movement of the cameras relative to the physical environment). For example, in response to the input by stylus 5012 at control 5004, as described with regard to
In some embodiments, displaying (912) the indication of the current spatial relationship of the one or more camera relative to the first portion of the physical environment captured in the still image includes: displaying an indicator in proximity to an edge of the representation of the field of view of the one or more cameras and moving the indicator along the edge in accordance with movement of the one or more cameras relative to the physical environment. For example, as described with regard to
In some embodiments, while displaying the indication of the current spatial relationship of the one or more cameras relative to the first portion of the physical environment captured in the still image, the deice detects (914) first movement of the one or more cameras (e.g., as part of the computing system). In response to detecting the first movement of the one or more cameras, the device updates the representation of the field of view of the one or more cameras in accordance with changes in the field of view of the one or more cameras caused by the first movement. In accordance with a determination that the first portion of the physical environment captured in the still image (e.g., a portion of the physical environment that includes an object relative to which the first annotation was received) is currently outside of the field of view of the one or more cameras, the device updates the indication of the current spatial relationship of the one or more cameras (e.g., as part of the computing system) relative to the first portion of the physical environment captured in the still image in accordance with the first movement of the one or more cameras (e.g., moving a visual indication such as a dot or other shape along an edge of the representation of the field of view in accordance with the first movement of the cameras). In accordance with a determination that the first portion of the physical environment captured in the still image (e.g., a portion of the physical environment that includes an object relative to which the first annotation was received) is currently within the field of view of the one or more cameras, the device ceases to display the indication. For example, as the camera of device 100 moves, while a portion of the physical environment captured in the still image is outside the field of view of the cameras (e.g., mug 5002a is outside the field of view of the cameras, as described with regard to
In some embodiments, in response to receiving the first request to re-display the representation of the field of view of the one or more cameras in the first user interface region (916): in accordance with the determination that the first portion of the physical environment captured in the still image (e.g., a portion of the physical environment that includes an object relative to which the first annotation was received) is currently within the field of view of the one or more cameras, the device displays the first annotation at the first portion of the physical environment captured within the representation of the field of view of the one or more cameras. For example, as described with regard to
In some embodiments, the first annotation is displayed as (918) a two-dimensional object (e.g., annotation 5018) on a first depth plane in the first portion of the physical environment captured within the representation of the field of view of the one or more cameras. In some embodiments, the first depth plane is detected in accordance with detection of a physical object (e.g., physical mug 5002a) or object feature at the first depth plane in the first portion of the physical environment. Displaying an annotation on a depth plane in the portion of the physical environment in the field of view of the one or more cameras provides improved visual feedback to the user (e.g., indicating that the annotation has a fixed spatial relationship to the physical environment). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing a user to imbue objects in the physical world with additional information contained in an annotation), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first annotation (e.g., annotation 5018) is displayed (920) at a location in space in the first portion of the physical environment captured within the representation of the field of view of the one or more cameras. In some embodiments, the first annotation floats in space detached from any physical object detected in the first portion of the physical environment. Displaying an annotation at a location in space in the portion of the physical environment captured in the still image provides improved visual feedback to the user (e.g., indicating that the annotation has a fixed spatial relationship to the physical environment). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing a user to imbue objects in the physical world with additional information contained in an annotation), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first annotation (e.g., annotation 5018) is displayed (922) at a location on a physical object (e.g., physical mug 5002a) detected in the first portion of the physical environment captured within the representation of the field of view of the one or more cameras. In some embodiments, the first annotation is attached to a physical object (or a feature of the physical object) detected in the first portion of the physical environment. Displaying an annotation of a portion of the physical environment at a location on a physical object detected in the portion of the physical environment captured in the still image provides improved visual feedback to the user (e.g., indicating that the annotation has a fixed spatial relationship to the physical environment). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing a user to imbue objects in the physical world with additional information contained in an annotation), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, in response to receiving the first request to re-display the representation of the field of view of the one or more cameras in the first user interface region (924): in accordance with the determination that the first portion of the physical environment captured in the still image (e.g., a portion of the physical environment that includes an object relative to which the first annotation was received) is not currently within the field of view of the one or more cameras, the device displays a visual representation of the first annotation (e.g., a drawing input) drawn on the first portion of the still image, concurrently with the representation of the field of view of the one or more cameras in the first user interface region (e.g., a reduced scale representation of the still image with the first annotation is displayed adjacent to the location on the edge of the representation of the field of view that is closest to the first portion of the physical space currently represented in the field of view of the cameras). For example, in response to the request to re-display the representation of the field of view of the one or more cameras in the first user interface region (e.g., an input by stylus 5012 at control 5004 for toggling between a still image mode and a video mode, as described with regard to
In some embodiments, the first annotation shown in the representation of the field of view has (926) a first viewing perspective that is based on the current spatial relationship of the one or more cameras (e.g., as part of the computing system) relative to the first portion of the physical environment captured in the still image, and is different from a second viewing perspective of the first annotation shown on the still image (e.g., the perspective of the first annotation shown in the reduced scale representation of the still image that is displayed adjacent to the representation of the field of view). In some embodiments, an animated transition is displayed showing the reduced scale representation of the still image being transformed to the representation of the current field of view. Displaying the annotation with a different viewing perspective from the viewing perspective shown in the still image provides improved visual feedback to the user (e.g., indicating that the annotation is fixed to a portion of the physical environment captured in the still image).
In some embodiments, in response to receiving the first request to re-display the representation of the field of view of the one or more cameras in the first user interface region (928): in accordance with the determination that the first portion of the physical environment captured in the still image (e.g., a portion of the physical environment that includes an object relative to which the first annotation was received) is currently outside of the field of view of the one or more cameras, displaying a visual representation of the first annotation (e.g., a drawing input) drawn on the first portion of the still image, concurrently with the representation of the field of view of the one or more cameras in the first user interface region (e.g., a reduced scale representation of the still image with the first annotation is displayed adjacent to the location on the edge of the representation of the field of view that is closest to the first portion of the physical space currently represented in the field of view of the cameras), wherein the visual representation of the first annotation drawn on the first portion of the still image (e.g., reduced scale representation 5020) is transformed into the indication (e.g., indication 5022) of the current spatial relationship of the one or more cameras (e.g., as part of the computing system) relative to the first portion of the physical environment captured in the still image (e.g., as described with regard to
In some embodiments, while displaying the first user interface region that includes the representation of the field of view of the one or more cameras, and prior to detecting the first request to add an annotation to the displayed representation of the field of view, the device displays (930) an indication (e.g., indication 5022) of a current spatial relationship of the one or more cameras (e.g., as part of the computing system) relative to a second portion of the physical environment to which a previously received, second annotation previously was added (e.g., displaying a visual indication such as a dot or other shape on an edge of the displayed field of view of the cameras and at a location on the edge that are closest to the second portion of the physical environment on which the second annotation was made, or displaying a simplified map of the physical environment concurrently with the representation of the field of view of the cameras and marking the relative locations of the second portion of the physical environment and the device on the map). In some embodiments, the second annotation was added to the second portion of the physical environment shown in the representation of the field of view of the one or more cameras in the same manner that the first annotation is added to the first portion of the physical environment shown in the representation of the field of view of the cameras. Displaying an indication of a current special relationship of the camera(s) relative to a second portion of the physical environment to which a previously received annotation was added provides improved visual feedback to the user (e.g., indicating that movement of the cameras is needed to view the previously received annotation relative to the portion of the physical environment that was captured in the still image). For example, indication 5022 is displayed prior to detecting a request to add annotation 5028 as described with regard to
In some embodiments, after receiving the first request to re-display the representation of the field of view of the one or more cameras in the first user interface region: in accordance with a determination that both the first portion of the physical environment and the second portion of the physical environment are outside of the field of view of the one or more cameras, the device concurrently displays (932) the indication of the current spatial relationship of the one or more cameras relative to the first portion of the physical environment and the indication of the current spatial relationship of the one or more cameras relative to the second portion of the physical environment. For example, when multiple annotations (e.g., annotation 5018 and 5036) have been added to different portions of the physical environment, the indicators (e.g., indicators 5018 and 5040,
In some embodiments, while concurrently displaying the indication of the current spatial relationship of the one or more cameras relative to the first portion of the physical environment and the indication of the current spatial relationship of the one or more cameras relative to the second portion of the physical environment, the device detects (934) second movement of the one or more cameras relative to the physical environment; and in response to detecting the second movement of the one or more cameras relative to the physical environment: in accordance with a determination that both the first portion of the physical environment and the second portion of the physical environment are outside of the field of view of the one or more cameras, the device respectively updates the indications of the current spatial relationships of the one or more cameras relative to the first and second portions of the physical environment (e.g., moving the visual indicators in different directions and/or with different speeds along the edge of the representation of the field of view), in accordance with the second movement of the one or more cameras relative to the physical environment. For example, respective visual indicators corresponding to different annotations directed to different portions of the physical environment are displayed at different locations on the edge of the representation of the field of view of the cameras, and with the movement of the device, the respective visual indicators are moved in different directions and with different speeds in accordance with the changes in the current spatial relationships of their respective annotations relative to the device (e.g., indicators 5018 and 5040 move in accordance with movement of device 100, as described with regard to 5AA-5AD). The visual indicators may move together or apart, and/or move with different speeds, depending on the actual spatial relationships between the different portions of the physical environment that are marked with different annotations. Updating the indications of the current spatial relationships of the camera(s) relative to the first and second portions of the physical environment in accordance with movement of the camera(s) provides improved visual feedback to the user (e.g., indicating whether movement of the camera(s) is bringing the camera(s) closer to or further away from portions of the physical environment that correspond to an annotated portions of the still image). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing a user to quickly and precisely locate the portion of the physical environment that corresponds to the previously annotated portion of the still image), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the indication of the current spatial relationship of the one or more cameras relative to the first portion of the physical environment and the indication of the current spatial relationship of the one or more cameras relative to the second portion of the physical environment are displayed (936) in accordance with a determination that the first portion and second portion of the physical environment are within a predefined range of the one or more cameras. In some embodiments, the user interface provides a method for selecting a subset of annotations from all annotations that have been added to various portions of the physical environment, and only the indications corresponding to the selected subset of annotations are displayed with the representation of the field of view of the cameras. Displaying the indications relative to the first portion of the physical environment and relative to the second portion of the physical environment in accordance with a determination that the first portion and second portion of the physical environment are within a predefined range of the one or more cameras provides improved visual feedback to the user (e.g., by reducing clutter of the user interface with indicators when the first and second portion are outside of the predefined range). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing a user to quickly and precisely locate the portion of the physical environment that corresponds to the previously annotated portion of the still image), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
It should be understood that the particular order in which the operations in
The device displays (1002), via the display generation component, a user interface that includes a video playback region. For example, device 100 displays, via touchscreen display 112, a user interface 6000 that includes video playback region 6002, as described with regard to
While displaying playback of a first portion of a video in the video playback region, the device receives (1004), via the one or more input devices, a request to add an annotation to the video playback (e.g., the request is an input by a contact that is detected in a video playback user interface on a touch-screen display, (e.g., at a location that corresponds to a control to initiate annotation or at a location in the video playback region (e.g., a location at which the annotation is to be initiated))). For example, a request to add an annotation to the video playback is an input by contact 6024 is detected at a location that corresponds to markup control 6010.
In response to receiving the request to add the annotation, the device (1006): pauses playback of the video at a first position in the video (e.g., identifying the current frame of the video (e.g., the paused position) and stops playback of the video at the current frame).
The device displays (1008) a still image (e.g., a frame of the video) that corresponds to the first, paused position of the video (e.g., displaying the current frame of the video that was shown at the time when the request was received). For example, as described with regard to
While displaying the still image (e.g., in the video playback region), the device receives (1008), via the one or more input devices, an annotation (e.g., a drawing input by a contact) on a first portion of a physical environment captured in the still image. For example, as described with regard to
After receiving the annotation, the device displays (1010), in the video playback region, a second portion of the video (e.g., during continued playback of the video or while input is received (e.g., on the timeline) to scrub through the video forward or backward) that corresponds to a second position in the video, distinct from the first position in the video (e.g., before or after the paused position in the video), wherein the first portion of the physical environment is captured in the second portion of the video and the annotation is displayed in the second portion of the video. For example, after annotation 6030 is received as described with regard to
In some embodiments, the video was captured (1012) by a camera during relative movement of the camera and the physical environment (e.g., during the video capturing, movement data of the camera and depth data of the physical environment are concurrently captured and stored with the image data captured at the same time) and a third portion of the video was captured between the first portion and the second portion of the video, and does not include the first portion of the physical environment, during the relative movement of the camera and the physical environment. In some embodiments, the annotation (e.g., annotation 6030) received on the still image (e.g., as indicated in
In some embodiments, the device displays (1014) a timeline (e.g., a scrub bar with a position indicator to indicate the position of the currently displayed frame, a scrollable sequence of reduced-scale images of sample frames from consecutive segments of the video with a stationary marker for the currently displayed frame) of the video (e.g., concurrently with display of the video (e.g., during playback of the video, and/or while the video is paused)), wherein displaying the second portion of the video is performed in response to a user input scrubbing through the timeline of the video to the second position in the video (e.g., a user input dragging the position indicator along a scrub bar, or a user input scrolling the sequence of reduced-scale images of sample frames past the stationary marker for currently displayed frame). For example, an input by contact 6038 is received at a location that corresponds to timeline 6004, which includes a sequence of sample frames (e.g., sample frame 6006, as described with regard to
In some embodiments, displaying the second portion of the video is performed as a result of (1016) rewinding of the video from the first position to the second position (e.g., the second position precedes the first position on the timeline of the video). For example, an input by contact 6038 is received for rewinding the video displayed in video playback region 6002, as described with regard to
In some embodiments, displaying the second portion of the video is performed as a result of (1018) fast-forwarding of the video from the first position to the second position (e.g., the second portion succeeds the first portion on the timeline of the video and the playback speed is faster than the normal playback speed). Displaying an annotation in a portion of video that is distinct from a portion of video to which the annotation was applied in response to a fast-forwarding input without requiring further user input enhances the operability of a device (e.g., by allowing the user to access the annotation displayed in a second portion of the video using an existing scrubbing control without requiring a separate control or input). Performing an operation without requiring further user input makes the user-device interface more efficient, which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, displaying the second portion of the video is performed as a result of (1020) normal playback of the video from the first position to the second position (e.g., the second portion succeeds the first portion on the timeline of the video and the playback speed is faster than the normal playback speed). In some embodiments, when the user finishes providing the annotation on the still image, the user exits the annotation mode by selecting a “done” button displayed with the still image (e.g., as described with regard to
In some embodiments, the device displays (1022), via the display generation component, a listing of media content objects, including the video (e.g., displaying a representation of the video in the media library). The device receives an input selecting the video from the listing of media content objects, and, in response to receiving the input selecting the video, displays a user interface object (e.g., a “mark-up” button for adding annotation) with the display of the video in the video playback region, wherein the user interface object is configured to receive a request to add an annotation to the video during playback of the video (e.g., a tap input to activate the button to add annotation). Displaying a user interface object, configured to receive a request to add an annotation to the video during playback of the video provides improved feedback (e.g., indicating an option, during playback of a video, to add an annotation to a portion of that video). In some embodiments, the mark-up button is displayed provides improved feedback (e.g., along with other playback controls) when a touch-input is detected on the video playback region during video playback, and when the mark-up button is activated, the currently displayed frame is shown in a mark-up enabled state, ready to receive drawing annotation directly on the image of the currently displayed frame. Providing enhanced feedback enhances the operability of a device (e.g., by allowing the user to access the annotation displayed in a second portion of the video using an existing scrubbing control without requiring a separate control or input). Performing an operation without requiring further user input makes the user-device interface more efficient, which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
It should be understood that the particular order in which the operations in
The device displays (1102), via the display generation component, a first previously captured media object including one or more first images (e.g., a still photo, a live photo, or a video including a sequence of image frames), wherein the first previously captured media object was recorded and stored with first depth data corresponding to a first physical environment captured in each of the one or more first images (e.g., first depth data generated by one or more depth sensors (e.g., an emitter/detector system, such as infrared, sonar, and/or lidar, and/or an image analysis system (e.g., video segment analysis and/or stereo image/video analysis)) of the device, e.g., at a time that corresponds to a time during which the first media object was captured by one or more cameras). For example, as described with regard to
While displaying the first previously captured media object (e.g., displaying a still image, displaying a representative image of a live photo, displaying a frame of the video during playback of the video, or displaying a frame of the video when the video is in a paused or stopped state), the device receives (1104) a first user request, via the one or more input devices, to add a first virtual object (e.g., falling balls, confetti, text, a spotlight, emoji, paint, measurement graphic) to the first previously captured media object. For example, a request to add a virtual object to a previously captured media object is a tap input received on touch screen display 112 for adding a virtual object to a previously captured image, as described with regard to
In response to the first user request to add the first virtual object to the first previously captured media object, the device displays (1106) the first virtual object over at least a portion of a respective image in the first previously captured media object, wherein the first virtual object is displayed with at least a first position or orientation (or movement path) that is determined using the first depth data that corresponds to the respective image in the first previously captured media object. For example, as described with regard to
In some embodiments, displaying the first virtual object over at least a portion of a respective image in the first previously captured media object includes (1108): after the first virtual object is placed on a respective one of the one or more first images, displaying first movement of the first virtual object relative to a first physical surface captured in the first previously captured media object, wherein the first movement of the first virtual object is constrained by a first simulated surface corresponding to the first physical surface that is determined based on the depth data and a simulated direction of gravity (e.g., the simulated direction of gravity is optionally determined based on the direction of gravity recorded with the depth data at the time the first images were captured, or is the same as the actual direction of gravity relative to the current orientation of the device displaying the respective image). For example, as described with regard to
In some embodiments, displaying the first virtual object over at least a portion of a respective image in the first previously captured media object includes (1110): after the first virtual object is placed on a respective one of the one or more first images, displaying a change in shape of the first virtual object in accordance with a first physical surface captured in the first previously captured media object, wherein the change in shape of the first virtual object is constrained by a first simulated surface corresponding to the first physical surface that is determined based on the first depth data. For example, as described with regard to
In some embodiments, while displaying the first virtual object over at least a portion of a respective image in the first previously captured media object, the device detects (1112) a second user request to switch from displaying the first previously captured media object to displaying a second previously captured media object (e.g., a horizontal swipe input on the first virtual object to show a previous or next item in a horizontally arranged list of media objects, a vertical swipe on the first virtual object to show a previous or next item in a vertically arranged list of media objects, or a tap on a forward or backward button for switching to the next or previous media object), wherein the second previously captured media object includes one or more second images, and the second previously captured media object was recorded and stored with second depth data corresponding to a second physical environment captured in each of the one or more second images (e.g., second depth data generated by one or more depth sensors (e.g., an emitter/detector system, such as infrared, sonar, and/or lidar, and/or an image analysis system (e.g., video segment analysis and/or stereo image/video analysis)) of the device, e.g., at a time that corresponds to a time during which the second media object was captured by one or more cameras). For example, as described with regard to
In some embodiments, the first user request is (1114) a request to add multiple instances of a first type of virtual objects (e.g., virtual ball objects 7034 and 7044 as described with regard to
In some embodiments, the first previously captured media object and the second previously captured media object (1116) are two distinct still images (e.g., a first previously captured image as shown in media object display region 7002 of
In some embodiments, the first previously captured media object is a video including a sequence of consecutive image frames (e.g., as described with regard to
In some embodiments, displaying the first previously captured media object includes (1120) playing the video in accordance with a first timeline that includes at least one of looping, fast forward, or reversal of the sequence of consecutive image frames; and displaying the first virtual object over at least a portion of a respective image in the first previously captured media object includes: during playback of the video in accordance with the first timeline, displaying changes in position or orientation (or movement path) of the first virtual object in accordance with a forward timeline (e.g., prior positions and orientations of the virtual object in each previously displayed image frame influences the position and orientation of the currently displayed image frame) that is associated with an actual order of the sequence of image frames (e.g., including looping from the end to the beginning of the video, switching frames at an uneven rate during the video playback, playing the video backwards from a later frame to an earlier frame, etc.) displayed during the playback of the video. In other words, the timeline of the movement of the virtual object in the displayed image frames is independent of the timeline according to which the media object is played back. Displaying changes in position or orientation of a virtual object in accordance with a timeline associated with an order of a sequence of image frames, without requiring further input (e.g., without requiring the user to provide input indicating the change in position of a virtual object in each frame of the video) enhances the operability of the device. Performing an operation without requiring further user input makes the user-device interface more efficient, which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, displaying the first virtual object over at least a portion of a respective image in the first previously captured media object includes (1122): while the first virtual object is placed on a respective one of the one or more first images, displaying a shadow of the first virtual object in accordance with a first physical surface captured in the first previously captured media object, wherein the shadow of the first virtual object is constrained by a first simulated surface corresponding to the first physical surface that is determined based on the first depth data. For example, if a still image captures a couch that has curved armrests and a flat seating area, a virtual letter A that is placed on the curved surface of the armrest and then falls sideways to the flat surface of the seating area will have a shadow with its shape changing in accordance with the surface that the virtual letter A is currently on, and the current orientation of the virtual letter A relative to the surface. In some embodiments, a three-dimensional or quasi-three-dimensional mesh is generated based on the depth data associated with the image or video, the mesh surface exhibits shape characteristics of the physical environment captured in the image or video, the shadow is cast on the mesh surface based on a simulated light source and the position and orientation of the virtual object relative to the mesh surface. Displaying a virtual object with a shadow that is constrained by a simulated surface corresponding to a physical surface based on depth data of a previously captured media object, without requiring further input (e.g., to identify a surface in the previously captured media object) enhances the operability of the device. Performing an operation without requiring further user input makes the user-device interface more efficient, which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first user request is (1124) a user request to place a virtual first textual object at a first location in a respective image in the first previously captured media object. For example, the user request is an input provided at virtual text object 7064 for initiating an editing mode of virtual text object 7064, as described with regard to
In some embodiments, displaying the first virtual object over at least a portion of a respective image in the first previously captured media object includes (1128): in accordance with a determination that a simulated surface proximate to a current location of the first virtual object in the respective image is a horizontal surface, displaying the first virtual object on top of the horizontal surface (e.g., as opposed to under the horizontal surface); and in accordance with a determination that a simulated surface proximate to the current location of the first virtual object in the respective image is a vertical surface, displaying the first virtual object in front of the vertical surface. Displaying a virtual object on top of or in front of a surface proximate to the virtual object, depending on whether the surface is a horizontal surface or a vertical surface, without requiring further input (e.g., to indicate whether a surface is a horizontal surface or a vertical surface) enhances the operability of the device. Performing an operation without requiring further user input makes the user-device interface more efficient, which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, displaying the first virtual object over at least a portion of a respective image in the first previously captured media object includes (1130): in accordance with a determination that the respective image includes a first simulated surface (e.g., a foreground object) and a second simulated surface (e.g., a background object) with different depths in proximity to a current location of the first virtual object in the respective image, displaying the first virtual object at a depth between the first simulated surface and the second simulated surface (e.g., with at least a first portion of the first virtual object occluded by the first simulated surface, and with at least a second portion of the first virtual object occluding at least a portion of the second simulated surface; or under an object represented by first simulated surface). For example, as described with regard to
In some embodiments, the device detects (1132) an object positioning input (e.g., a drag input or a tap input) by a contact on the touch-sensitive surface that is directed to the first virtual object, wherein the object positioning input specifies a placement location for the first virtual object on the respective image corresponding to a final location (and, optionally, final movement speed and direction) of the contact on the touch-sensitive surface. For example, an object positioning input is an input by contact 7066 for positioning a virtual text object 7064 as described with regard to
In some embodiments, the first virtual object includes (1134) a simulated spotlight (e.g., virtual spotlight object 7118, as described with regard to
In some embodiments, the first virtual object includes (1136) a graphical object (e.g., a two-dimensional or three-dimensional emoji), and displaying the first virtual object over at least a portion of a respective image in the first previously captured media object includes: displaying the graphical object at a location in the respective image that corresponds to free space in the physical environment (e.g., the emoji floats in the air in the physical environment at a location selected by a user's finger contact). For example, the graphical object is a virtual emoji object 7098 as described with regard to
In some embodiments, the device detects (1138) two concurrent contacts on the touch-sensitive surface and, in response to detecting the two concurrent contacts, the device displays a first measurement object with two respective ends located at respective locations on the respective image corresponding to respective locations of the two concurrent contacts on the touch-sensitive surface. For example, in response to detecting concurrent contacts 7132 and 7134, a virtual measurement object 7136 is displayed with ends at locations that correspond to the locations of the contacts, as described with regard to
In some embodiments, displaying the first measurement object includes (1140): in accordance with a determination that the two respective ends of the first measurement object are located on two sides of a simulated foreground surface corresponding to a physical surface captured in the respective image (e.g., the first measure object goes through the simulated foreground surface), displaying a first portion of the first measurement object located on a first side of the simulated foreground surface with a first appearance, and displaying a second portion, distinct from the first portion, of the first measurement object located on a second side, distinct from the first side, of the simulated foreground surface with a second appearance, wherein the second appearance is different from the first appearance (e.g., the first side of the measurement object is foreground and fully visible, and the second side of the measurement object is shielded by the foreground surface and has a shaded appearance). For example, in
In some embodiments, displaying the first measurement object includes (1142): while displaying the first measurement object with a first end and a second end in the respective image, detecting a positioning input by a contact on the touch-sensitive surface, wherein the positioning input specifies a new end location of the first measurement object in the respective image; and in response to detecting the positioning input by the contact, moving one of the first and second ends of the first measurement object that is closer to the new end location in the respective image as specified by the positioning input. For example, a positioning input by contact 7152, as described with regard to
It should be understood that the particular order in which the operations in
The device sends (1202) a request (e.g., in response to a user request to enter the shared annotation mode) to a remote device (e.g., a server or a second device) to initiate a shared annotation session with a second device that includes a second display generation component, a second set of one or more input devices, and a second set of one or more cameras. For example, as described with regard to
In response to sending the request to initiate the shared annotation session with the second device, the device receives (1204) (e.g., from the server or the second device) an indication of acceptance of the request to initiate the shared annotation session In some embodiments, the request is sent to the second device (e.g., directly without going through a server, or via a server), and the second device displays a notification of the request to initiate the shared annotation session with the first device. For example, in
In response to receiving the indication of acceptance of the request to initiate the shared annotation session, the device displays (1206), via the first display generation component, a first prompt to move the first device toward the second device (e.g., an animation showing representations of the first and second devices moving toward each other). For example, first device 100-1 displays a prompt 8022 including an instruction to move device 100-1 toward a representation of device 100-2, as described with regard to
After displaying the first prompt, in accordance with a determination that connection criteria for the first device and the second device are met (e.g., after movements of the first device and the second device toward each other, and after analysis of the physical space captured in the field of views of the first and second sets of cameras), the device displays (1208) a representation of a field of view of the first set of cameras in the shared annotation session with the second device. For example, as described with regard to
In some embodiments, during the shared annotation session, the one or more first virtual annotations corresponding to the annotation input (e.g., drawings, virtual objects, text, etc.) directed to the respective location in the physical environment (e.g., through direct annotation on a still image of the field of view or directly on the live feed of the field of view of the cameras) by the first device is displayed (1210) (e.g., overlaid on a representation of the field of view of the second set of cameras) via the second display generation component and the one or more second virtual annotations corresponding to the annotation input (e.g., drawings, virtual objects, text, etc.) directed to the respective location in the physical environment (e.g., through direct annotation on a still image of the field of view or directly on the live feed of the field of view of the cameras) by the second device is displayed (e.g., overlaid on the representation of the field of view of the second set of cameras) via the second display generation component, provided that the respective location is included in the field of view of the second set of cameras (e.g., in accordance with a determination of such made through analysis of the field of view (e.g., including image and depth data) and the device movement data of the first and/or second devices during the shared annotation session). For example, the display of second device 100-2 displays annotation 8050-2 that was input as second device 100-2 and annotation 8056-2 that was input at first device 100-1, as described with regard to
In some embodiments, during the shared annotation session, the one or more first virtual annotations corresponding to the annotation input (e.g., drawings, virtual objects, text, etc.) directed to the respective location in the physical environment (e.g., through direct annotation on a still image of the field of view or directly on the live feed of the field of view of the cameras) by the first device is displayed (1212) (e.g., overlaid on a representation of the field of view of the second set of cameras) via the second display generation component and not via the first display generation component, provided that the respective location is included in the field of view of the second set of cameras and not included in the field of view of the first set of cameras (e.g., in accordance with a determination of such made through analysis of the field of view (e.g., including image and depth data) and the device movement data of the first and/or second devices during the shared annotation session). For example, annotations 8050-1, 8050-2 and 8056-1, 8056-2 are received as direct annotation input directed to representations 8038b and 8038c (in a field of view of cameras of devices 101-1 and 101-2, respectively) of physical poster 8038a. Displaying, at a second display, the annotation input while the first display does not display the annotation input, provided that the location is included in the field of view of the second device and not included in the field of view of the first device, provides visual feedback to the user (e.g., indicating that the annotation corresponds to a location in the physical environment). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing users to collaborate in an annotation session in which annotations by different users appear relative to the same location in space), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, after displaying the first prompt, in accordance with a determination that the connection criteria for the first device and the second device are met (e.g., after movements of the first device and the second device toward each other, and after the analysis of the physical space captured in the field of views of the first and second sets of cameras), the device displays (1214) a notification (e.g., a pop-up or banner notification with an avatar of the second device shown, or appearance of the controls that are provided in the shared annotation session) in the representation of the field of view of the first set of cameras that the shared annotation session with the second device has been established. For example, as described with regard to
In some embodiments, the first prompt includes (1216) an animation illustrating representations of the first and second devices moving toward each other (e.g., as described with regard to
In some embodiments, during the shared annotation session: while displaying, via the first display generation component, the representation of the field of view of the first set of cameras, in accordance with a determination that a first annotation input directed to a portion of the physical environment captured in the field of view of the first set of cameras is received from the second device, the device displays (1220) an avatar of the second device at a location in the representation of the field of view of the first set of cameras that corresponds to a location to which the first annotation input is directed. For example, as described with regard to
In some embodiments, during the shared annotation session: while displaying, via the first display generation component, the representation of the field of view of the first set of cameras, the device displays (1222) a virtual object (e.g., a two-dimensional virtual object or a three-dimensional virtual object (e.g., a virtual basketball hoop, an avatar of the second device or second user) that is linked with the second device) in the representation of the field of view of the first set of cameras with a location (and, optionally, a perspective) that corresponds to a current location of the second device, including: detecting movement of the second device from a first location to a second location in the physical environment; and displaying movement of the virtual object (and optionally, change in viewing perspective of the virtual object) in the representation of the field of view of the first set of cameras that corresponds to the movement of the second device from the first location to the second location in the physical environment, provided that the first location and the second location are within the field of view of the first set of cameras during the movement of the second device from the first location to the second location in the physical environment (e.g., the second device is captured by the first set of cameras in the field of view of the first set of cameras during the movement of the second device from the first location to the second location in the physical environment, and visible on the representation of the field of view of the first set of cameras). For example, as described with regard to
In some embodiments, during the shared annotation session, the first device displays (1224) the representation of the field of view of the first set of cameras via the first display generation component and the second device displays the representation of the field of view of the first set of cameras via the second display generation component (e.g., the field of view of the first set of cameras is provided to the second device (e.g., directly or via a server), such that the same field of view is presented at both the first and second devices). In some embodiments, the second device has a different field of view from the second set of cameras, but does not display the field of view from the second set of cameras when it is displaying the field of view of the first set of cameras. Displaying, by the first display and the second display, the field of view of the first device camera(s), provides visual feedback to the user (e.g., indicating that the displayed view is a shared view). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient, (e.g., to allow the second device to experience the point of view of the first device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, during the shared annotation session, the first device displays (1226) the representation of the field of view of the first set of cameras via the first display generation component and the second device displays the representation of the field of view of the second set of cameras via the second display generation component (e.g., different field of views are presented at the first and second devices, when the devices are at different locations and/or pointing at different directions in the physical environment). Displaying the field of view of the first device camera(s) at the first display and displaying the field of view of the second device camera(s) at the second display provides visual feedback to the user (e.g., indicating that the displayed view is not a shared view). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient, (e.g., by allowing the first and second device to maintain individual points of reference relative to the physical world) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, during the shared annotation session, in accordance with a determination that the connection criteria are no longer met (e.g., after movements of the first device and the second device away from each other, and after the analysis of the physical space captured in the field of views of the first and second sets of cameras), the device terminates (1228) the shared annotation session. For example, as described with regard to
In some embodiments, during the shared annotation session, in accordance with a determination that an amount of overlap between the field of view of the first set of cameras and the field of view of the second set of cameras (or more generally, between the portion of physical environment captured in the field of view of the first set of camera and the portion of the physical environment captured in the field of view of the second set of cameras) is below a first threshold amount (e.g., after movements of the first device and the second device away from each other), the device generates (1230), via the first display generation component, a second prompt to move the first device toward the second device. For example, as described with regard to
In some embodiments, during the shared annotation session, in accordance with a determination that an amount of overlap between the field of view of the first set of cameras and the field of view of the second set of cameras (or more generally, between the portion of physical environment captured in the field of view of the first set of camera and the portion of the physical environment captured in the field of view of the second set of cameras) is below a first threshold amount (e.g., after movements of the first device and the second device away from each other), the device displays (1232), via the first display generation component, an indication of a current relative spatial relationship between the first device and the second device (e.g., a dynamically moving visual indicators on the edge of the representation of the field of view of the first set of cameras, which is concurrently displayed with the second prompt to move the first device toward the second device). Displaying an indication of a current spatial relationship between the first device and the second device in accordance with a determination that the view of the first camera(s) does not overlap by at least a threshold amount from the view of the second camera(s) provides visual feedback to the user (e.g., indicating that movement of the camera(s) is needed to view the shared annotation session). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing a user to quickly and precisely move the device to enable the shared annotation session), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
It should be understood that the particular order in which the operations in
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best use the invention and various described embodiments with various modifications as are suited to the particular use contemplated.
This application is a continuation of U.S. application Ser. No. 18/107,381, filed Feb. 8, 2023, which is a continuation of U.S. application Ser. No. 17/716,984, filed Apr. 8, 2022, now U.S. Pat. No. 11,632,600, which is a continuation of U.S. application Ser. No. 16/997,860, filed Aug. 19, 2020, now U.S. Pat. No. 11,303,812, which is a continuation of U.S. application Ser. No. 16/574,029, filed Sep. 17, 2019, now U.S. Pat. No. 10,785,413, which claims priority to U.S. Provisional Application No. 62/739,178, filed Sep. 29, 2018, which are incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 7072810 | Ramanathan et al. | Jul 2006 | B2 |
| 8244462 | Zhu | Aug 2012 | B1 |
| 8365081 | Amacher et al. | Jan 2013 | B1 |
| 8982156 | Maggiore | Mar 2015 | B2 |
| 9152209 | Jeong et al. | Oct 2015 | B2 |
| 9495794 | Masumoto | Nov 2016 | B2 |
| 9661308 | Wang et al. | May 2017 | B1 |
| 9665960 | Masters et al. | May 2017 | B1 |
| 9678651 | Moha et al. | Jun 2017 | B2 |
| 9696897 | Garcia | Jul 2017 | B2 |
| 9767606 | Kapinos et al. | Sep 2017 | B2 |
| 9846027 | Kimura et al. | Dec 2017 | B2 |
| 9870644 | Ha et al. | Jan 2018 | B2 |
| 9953434 | Natori et al. | Apr 2018 | B2 |
| 10049504 | Chen et al. | Aug 2018 | B2 |
| 10074179 | Arita et al. | Sep 2018 | B2 |
| 10083537 | Moore et al. | Sep 2018 | B1 |
| 10268266 | Mathey-Owens et al. | Apr 2019 | B2 |
| 10296869 | Hulth | May 2019 | B2 |
| 10347033 | Masumoto | Jul 2019 | B2 |
| 10445867 | Glatfelter et al. | Oct 2019 | B2 |
| 10540699 | Prabhu et al. | Jan 2020 | B1 |
| 10606075 | Choi et al. | Mar 2020 | B2 |
| 10606609 | Energin | Mar 2020 | B2 |
| 10762716 | Paul et al. | Sep 2020 | B1 |
| 10861241 | Ghaleb | Dec 2020 | B2 |
| 10999629 | Cieslak et al. | May 2021 | B1 |
| 11204678 | Baker et al. | Dec 2021 | B1 |
| 11523063 | Ith et al. | Dec 2022 | B2 |
| 20080008361 | Nozaki et al. | Jan 2008 | A1 |
| 20080222233 | Shi et al. | Sep 2008 | A1 |
| 20080255961 | Livesey | Oct 2008 | A1 |
| 20090002719 | Chang et al. | Jan 2009 | A1 |
| 20100235726 | Ording | Sep 2010 | A1 |
| 20110022942 | Flemings et al. | Jan 2011 | A1 |
| 20110107270 | Wang et al. | May 2011 | A1 |
| 20110216167 | Katz et al. | Sep 2011 | A1 |
| 20110249117 | Yoshihama et al. | Oct 2011 | A1 |
| 20110252405 | Meirman et al. | Oct 2011 | A1 |
| 20110279381 | Tong et al. | Nov 2011 | A1 |
| 20110279445 | Murphy et al. | Nov 2011 | A1 |
| 20110304607 | Ito | Dec 2011 | A1 |
| 20120121134 | Yoshizumi | May 2012 | A1 |
| 20120194544 | Yokohata | Aug 2012 | A1 |
| 20120249741 | Maciocci et al. | Oct 2012 | A1 |
| 20130044128 | Liu et al. | Feb 2013 | A1 |
| 20130127895 | Miller et al. | May 2013 | A1 |
| 20130215230 | Miesnieks et al. | Aug 2013 | A1 |
| 20130332892 | Matsuki | Dec 2013 | A1 |
| 20140071130 | Piedmonte | Mar 2014 | A1 |
| 20140098191 | Rime et al. | Apr 2014 | A1 |
| 20140125668 | Steed et al. | May 2014 | A1 |
| 20150062120 | Reisner-Kollmann et al. | Mar 2015 | A1 |
| 20150062123 | Yuen | Mar 2015 | A1 |
| 20150067588 | Shim et al. | Mar 2015 | A1 |
| 20150074711 | Spitz et al. | Mar 2015 | A1 |
| 20150169525 | Palm et al. | Jun 2015 | A1 |
| 20150187119 | Masumoto | Jul 2015 | A1 |
| 20150221345 | Zhao et al. | Aug 2015 | A1 |
| 20150227645 | Childs et al. | Aug 2015 | A1 |
| 20160026253 | Bradski et al. | Jan 2016 | A1 |
| 20160040981 | Kang et al. | Feb 2016 | A1 |
| 20160049011 | Kasahara et al. | Feb 2016 | A1 |
| 20160063714 | Middleton et al. | Mar 2016 | A1 |
| 20160086322 | Arita et al. | Mar 2016 | A1 |
| 20160147408 | Bevis et al. | May 2016 | A1 |
| 20160148433 | Petrovskaya et al. | May 2016 | A1 |
| 20160170624 | Zambetti et al. | Jun 2016 | A1 |
| 20160189426 | Thomas et al. | Jun 2016 | A1 |
| 20160329006 | Weber et al. | Jun 2016 | A1 |
| 20160210602 | Siddique et al. | Jul 2016 | A1 |
| 20160240011 | Metaio et al. | Aug 2016 | A1 |
| 20160363990 | Key | Dec 2016 | A1 |
| 20170021273 | Rios | Jan 2017 | A1 |
| 20170053621 | Chen et al. | Feb 2017 | A1 |
| 20170061696 | Li et al. | Mar 2017 | A1 |
| 20170115488 | Ambrus et al. | Apr 2017 | A1 |
| 20170132841 | Morrison | May 2017 | A1 |
| 20170212585 | Kim et al. | Jul 2017 | A1 |
| 20170220887 | Fathi et al. | Aug 2017 | A1 |
| 20170230641 | Scavezz et al. | Aug 2017 | A1 |
| 20170277670 | Smith et al. | Sep 2017 | A1 |
| 20170289221 | Khalid et al. | Oct 2017 | A1 |
| 20170316576 | Colbert et al. | Nov 2017 | A1 |
| 20170358142 | Lee et al. | Dec 2017 | A1 |
| 20170372510 | Ye et al. | Dec 2017 | A1 |
| 20180004283 | Mathey-Owens et al. | Jan 2018 | A1 |
| 20180088794 | Graham et al. | Mar 2018 | A1 |
| 20180114372 | Nagy et al. | Apr 2018 | A1 |
| 20180165888 | Duan et al. | Jun 2018 | A1 |
| 20180203561 | Chang et al. | Jul 2018 | A1 |
| 20180203581 | Takeda | Jul 2018 | A1 |
| 20180204385 | Sarangdhar et al. | Jul 2018 | A1 |
| 20180300952 | Evans et al. | Oct 2018 | A1 |
| 20180336732 | Schuster | Nov 2018 | A1 |
| 20180336737 | Varady et al. | Nov 2018 | A1 |
| 20190033058 | Tsurumi | Jan 2019 | A1 |
| 20190051054 | Jovanovic et al. | Feb 2019 | A1 |
| 20190065027 | Hauenstein et al. | Feb 2019 | A1 |
| 20190068889 | Lee et al. | Feb 2019 | A1 |
| 20190172261 | Alt et al. | Jun 2019 | A1 |
| 20190180506 | Gebbi et al. | Jun 2019 | A1 |
| 20190180512 | Fedosov et al. | Jun 2019 | A1 |
| 20190213389 | Peruch et al. | Jul 2019 | A1 |
| 20190221035 | Clark et al. | Jul 2019 | A1 |
| 20190221041 | Lin | Jul 2019 | A1 |
| 20190310757 | Lee et al. | Oct 2019 | A1 |
| 20190311512 | VanBlon et al. | Oct 2019 | A1 |
| 20190333278 | Palangie et al. | Oct 2019 | A1 |
| 20190339058 | Dryer et al. | Nov 2019 | A1 |
| 20190339839 | Paul, Sr. et al. | Nov 2019 | A1 |
| 20190340799 | Dryer et al. | Nov 2019 | A1 |
| 20190355121 | Nelson | Nov 2019 | A1 |
| 20190369404 | Joshi et al. | Dec 2019 | A1 |
| 20200005538 | Neeter | Jan 2020 | A1 |
| 20200020164 | Coffman | Jan 2020 | A1 |
| 20200027201 | Chen | Jan 2020 | A1 |
| 20200053318 | Li et al. | Feb 2020 | A1 |
| 20200098140 | Jagnow et al. | Mar 2020 | A1 |
| 20200106965 | Lam et al. | Apr 2020 | A1 |
| 20200143593 | Rudman et al. | May 2020 | A1 |
| 20200184667 | Miller et al. | Jun 2020 | A1 |
| 20200200794 | Niles | Jun 2020 | A1 |
| 20200232783 | Dryer et al. | Jul 2020 | A1 |
| 20200261799 | Cahill et al. | Aug 2020 | A1 |
| 20200312029 | Heinen | Oct 2020 | A1 |
| 20200322595 | Abe et al. | Oct 2020 | A1 |
| 20200382718 | Malia et al. | Dec 2020 | A1 |
| 20210004996 | Murillo et al. | Jan 2021 | A1 |
| 20210019946 | Sonasath et al. | Jan 2021 | A1 |
| 20210096726 | Faulkner et al. | Apr 2021 | A1 |
| 20210097768 | Malia et al. | Apr 2021 | A1 |
| 20210097776 | Faulkner et al. | Apr 2021 | A1 |
| 20210174596 | Zhang et al. | Jun 2021 | A1 |
| 20210191600 | Lemay et al. | Jun 2021 | A1 |
| 20210158427 | Jobetto et al. | Aug 2021 | A1 |
| 20210241483 | Dryer et al. | Aug 2021 | A1 |
| 20210241505 | Dryer et al. | Aug 2021 | A1 |
| 20210254962 | Dryer et al. | Aug 2021 | A1 |
| 20210286502 | Lemay et al. | Sep 2021 | A1 |
| 20210295602 | Scalpel et al. | Sep 2021 | A1 |
| 20210304465 | Dryer et al. | Sep 2021 | A1 |
| 20220036648 | Wang et al. | Feb 2022 | A1 |
| 20220091722 | Faulkner et al. | Mar 2022 | A1 |
| 20220092861 | Sharma et al. | Mar 2022 | A1 |
| 20220130118 | Malia et al. | Apr 2022 | A1 |
| 20220239842 | Malia et al. | Jul 2022 | A1 |
| 20220276041 | Dryer et al. | Sep 2022 | A1 |
| 20220335697 | Harding et al. | Oct 2022 | A1 |
| 20230199296 | Malia et al. | Jun 2023 | A1 |
| 20230368458 | Dryer et al. | Nov 2023 | A1 |
| 20230386146 | Scapel et al. | Nov 2023 | A1 |
| 20240011764 | Dryer et al. | Jan 2024 | A1 |
| 20240045564 | Dryer et al. | Feb 2024 | A1 |
| 20240153219 | Queen et al. | May 2024 | A1 |
| 20240273832 | Newman et al. | Aug 2024 | A1 |
| 20240290051 | Malia et al. | Aug 2024 |
| Number | Date | Country |
|---|---|---|
| 2018101226 | Sep 2018 | AU |
| 2019100486 | Jun 2019 | AU |
| 1629888 | Jun 2005 | CN |
| 102607423 | Jul 2012 | CN |
| 103218854 | Jul 2013 | CN |
| 105103198 | Nov 2015 | CN |
| 105164999 | Dec 2015 | CN |
| 105554247 | May 2016 | CN |
| 105579946 | May 2016 | CN |
| 105589199 | May 2016 | CN |
| 105608746 | May 2016 | CN |
| 106164934 | Nov 2016 | CN |
| 106251185 | Dec 2016 | CN |
| 106575299 | Apr 2017 | CN |
| 112189220 | Jan 2021 | CN |
| 1563370 | Aug 2005 | EP |
| 2 394 714 | Dec 2011 | EP |
| 2 983 139 | Feb 2016 | EP |
| 2 988 486 | Feb 2016 | EP |
| 3017591 | May 2016 | EP |
| 6264665 | Nov 2002 | JP |
| 2008-287691 | Nov 2008 | JP |
| 2011-199560 | Oct 2011 | JP |
| 2014-143453 | Aug 2014 | JP |
| 2015-146173 | Aug 2015 | JP |
| 2016-110676 | Jun 2016 | JP |
| 2017-536618 | Dec 2017 | JP |
| 20100003252 | Jan 2010 | KR |
| 20130108684 | Oct 2013 | KR |
| 20150018828 | Feb 2015 | KR |
| 101629134 | Jun 2016 | KR |
| 20160141688 | Dec 2016 | KR |
| 20170087501 | Jul 2017 | KR |
| 20180066276 | Jun 2018 | KR |
| 20210031894 | Mar 2021 | KR |
| 20210081904 | Jul 2021 | KR |
| WO 2011029209 | Mar 2011 | WO |
| WO 2013096052 | Jun 2013 | WO |
| WO 2013099616 | Jul 2013 | WO |
| WO 2013176830 | Nov 2013 | WO |
| WO 2014013689 | Jan 2014 | WO |
| WO 2014157340 | Oct 2014 | WO |
| WO 2014197631 | Dec 2014 | WO |
| WO 2016017254 | Feb 2016 | WO |
| WO 2017134886 | Aug 2017 | WO |
| WO 2018164932 | Sep 2018 | WO |
| WO 2019032736 | Feb 2019 | WO |
| WO 2019217148 | Nov 2019 | WO |
| WO 2020068073 | Apr 2020 | WO |
| WO 2021158427 | Aug 2021 | WO |
| Entry |
|---|
| Notice of Allowance, dated Nov. 13, 2023, received in U.S. Appl. No. 17/720,227, 5 pages. |
| Office Action, dated Dec. 22, 2023, received in Korean Patent Application No. 2020-0123687, which corresponds with U.S. Appl. No. 17/018,980, 9 pages. |
| Office Action, dated Nov. 24, 2023, received in Korean Patent Application No. 2023-7019367, which corresponds with U.S. Appl. No. 17/307,957, 7 pages. |
| Office Action, dated Dec. 8, 2023, received in Japanese Patent Application No. 2022-142210, which corresponds with U.S. Appl. No. 17/344,846, 5 pages. |
| Office Action, dated Dec. 11, 2023, received in Korean Patent Application No. 2023-7012345, which corresponds with U.S. Appl. No. 17/716,984, 10 pages. |
| International Search Report and Written Opinion, dated Dec. 14, 2023, received in International Patent Application No. PCT/US2023/021563, which corresponds with U.S. Appl. No. 18/144,746, 29 pages. |
| Aakash G Technical, “App Review #1 / Measure—Tango AR / How to Use”, https://www.youtube.com/watch?v=fj2iiOg36KE, May 13, 2017, 2 pages. |
| Anonymous, “How to Select Surface and Image Anchors”, https:helpx.adobe.com/aeor/how-to-surface-and-image-anchors.html, Oct. 20, 2020, 6 pages. |
| Apple, “MeasureKit—AR ruler app for iOS 11”, https://measurekit.com, Sep. 15, 2017, 10 pages. |
| Berthiaume, “Augmented Reality Scanning Enables Retail Innovation (Video)”, https://www.scandit.com/gb/augmented-reality-scanning-enables-retail-innovation-video, Oct. 3, 2017, 5 pages. |
| Bhalwankar, “Triple Tap to Zoom Feature in Android Phones”, https://www.youtube.com/watch?v=KInbLhA2jg8, Jan. 25, 2014, 2 pages. |
| Burns, “Google Measure it Demo with Tango”, https://www.youtube.com/watch?v=b74VtGGJPBg, May 20, 2016, 2 pages. |
| IPhoneWave, “How to Use iPhone, [online]”, http://web.archive.org/web/20111012000236/http:www.ipodwave.com:80/iphone/howto/camera_video.html, Oct. 12, 2011, 5 pages. |
| Jain et al., “OverLay: Practical Mobile Augmented Reality”, Proceedings of the 13th Annual International conference on Mobile Systems, Applications, and Services. May 18, 2015, 14 pages. |
| LaanLabs, “AirMeasure—AR Tape & Ruler”, https://itunes.apple.com/us/app/airmeasure-ar-tape-ruler/id1251282152, Jun. 4, 2018, 3 pages. |
| LaanLabs, “AirMeasure—The Augmented Reality Toolkit”, https://www.youtube.com/watch?v=9ycpvj6hbdE, Sep. 12, 2017, 2 pages. |
| Langlotz et al., “Sketching up the World: in Situ Authoring for Mobile Augmented reality”, http://mooslechner.infor/workperformed/at/smartphone2010.pdf, Jul. 27, 2011, 8 pages. |
| Lenovo, Lenovo Tech World 2016—Keynote Livestream from San Francisco, https://www.youtube.com/watch?v=MBgQLraVGJQ, Jun. 9, 2016, 2 pages. |
| Lenovo, “Lenovo_PHAB2_Pro_User_Guide V1.0”, https://pcsupport.lenovo.com/do/en/products/tablets/phab-series/phab2-pro-documentation/doc_userguide, Aug. 29, 2017, 10 pages. |
| Lynch, “How to Zoom in on iPhone: The Quick Tutorial!”, https://www.payetteforward.com/how-to-zoom-in-on-iphone-quck-tutorial, Feb. 26, 2018, 4 pages. |
| Mapletree Apps, “Apple ARKit iPhone Demo—Measure 3D Pro—Ruler on iOS (1)”, https://www.youtube.com/watch?v=fzn3RsveJss, Oct. 1, 2017, 2 pages. |
| Mapletree Apps, “Apple ARKit iPhone Demo—Measure 3D Pro—Ruler on iOS (2)”, https://www.youtube.com/watch?v=fzn3RsveJss, Oct. 1, 2017, 2 pages. |
| Mapletree Apps, “Measure 3D Tutorial series #1—How to Measure a Room”, https://www.youtube.com/watch?v=HGV18HXXZqw, Apr. 19, 2018, 2 pages. |
| Mapletree Apps, Measure 3D Tutorial series #4—How to Measure Length in Horizonal and Vertical Planes, https://www.youtube.com/watch?V-2PjcbrgS50Q, Apr. 19, 2018, 2 pages. |
| Mapletree Appls, “Measure 3D Tutorial #5—How to Measure Rectangle Shapes”, https://www.youtube.com/watch?v=8Gg0SMwkvQU, Apr. 19, 2018, 2 pages. |
| Marriott, Adobe Aero: Getting Started with AR/Tutorial, https://www.youtube.com/watch?v=EU2V8Pn0GE4, Nov. 19, 2019, 3 pages. |
| Miller, “Apple Shares Detailed Human Interface Guidelines for Developers Building ARKit Apps”, https://9to5mac.com/2017/08/29/arkit-human-interface-guidelines/, Aug. 29, 2017, 5 pages. |
| Nuernberger et al., “SnapToReality: Aligning Augmented Reality to the Real World”, http://eyalofek.org/Papers/CHI2016_Snap2Reality.pdf., May 7-12, 2016, 12 pages. |
| Occipital HQ, “TapMeasure Spatial Utility to Capture and Measure Your Space”, https://www.youtube.com/watch?v=Hy1Ex2MAXM, Sep. 19, 2017, 2 pages. |
| Perhiniak, “Yes I'm a Designer: Designing an Augmented Reality Scene in Adobe Aero” https://wwwyoutube.com/watch?v=fo8a?G0, Jan. 27, 2020, 14 pages. |
| SmartPicture, “PLNAR—Your AR Measurement Tool”, https://www.youtube.com/watch?v=H_cqZqKLjws, Sep. 28, 2017, 2 pages. |
| SmarPicture Tech, “Mobile App Design for Bay Area—Rely on the Reinvently Agency”, https://appadvice.com/app/plnar/1282049921, Sep. 21, 2018, 5 pages. |
| YouTube, “A1 Corner & Edge Detection (beta)”, https://www.youtube.com/watch?v=YSNklighUtxA, Nov. 21, 2020, 2 pages. |
| YouTube, “How Do I Use the iPhone Measure App? How Accurate Is It?”, https://www.youtube.com/watch?v=RvhZ074Vs7c, Aug. 8, 2018, 3 pages. |
| YouTube, “Third Aurora: Adobe Aero Tutorial—How to get Started with Adobe Aero”, https://www.youtube.com/watch?v=EU2v8P, Nov. 18, 2019, 3 pages. |
| YouTube, AR Measure—Automatic Measure in Augmented Reality, https://www.youtube.com/watch?v=70CQfH76vg4, Mar. 16, 2019, 2 pages. |
| Youtube, Huawei P30 Pro AR Measure / Measure length, depth, area and volume, hxos plus, https;//www.youtube.com/watch?v=0OX5QaK7YY, Mar. 26, 2019, 2 pages. |
| YouTube, Yes, I'm a Designer: “Designing an Augmented Reality Scene in Adobe Aero”, https:www.youtube.com/watch?v=fo8aGOvCY7k, Jan. 27, 2020, 3 pages. |
| Office Action, dated Feb. 21, 2019, received in U.S. Appl. No. 16/145,015, 34 pages. |
| Notice of Allowance, dated Jun. 5, 2019, received in U.S. Appl. No. 16/145,015, 12 pages. |
| Office Action, dated Aug. 31, 2018, received in Danish Patent Application No. 201870350, which corresponds with U.S. Appl. No. 16/145,015, 11 pages. |
| Office Action, dated May 28, 2019, received in Danish Patent Application No. 201870350, which corresponds with U.S. Appl. No. 16/145,015, 6 pages. |
| Office Action, dated Feb. 21, 2020, received in Danish Patent Application No. 201870350, which corresponds with U.S. Appl. No. 16/145,015, 3 pages. |
| Intention to Grant, dated Mar. 30, 2023, received in European Patent Application No. 21178349.3, which corresponds with U.S. Appl. No. 16/145,015, 8 pages. |
| Office Action, dated Sep. 19, 2023, received in European Patent Application No. 21178349.3, which corresponds with U.S. Appl. No. 16/145,015, 11 pages. |
| Notice of Allowance, dated Nov. 22, 2019, received in U.S. Appl. No. 16/138,779, 17 pages. |
| Office Action, dated Jul. 7, 2021, received in Australian Patent Application No. 2019267352, which corresponds with U.S. Appl. No. 16/138,779, 5 pages. |
| Notice of Acceptance, dated Aug. 9, 2021, received in Australian Patent Application No. 2019267352, which corresponds with U.S. Appl. No. 16/138,779, 3 pages. |
| Patent, dated Dec. 2, 2021, received in Australian Patent Application No. 2019267352, which corresponds with U.S. Appl. No. 16/138,779, 3 pages. |
| Office Action, dated Aug. 31, 2018, received in Danish Patent Application No. 201870351, which corresponds with U.S. Appl. No. 16/138,779, 11 pages. |
| Office Action, dated Feb. 13, 2020, received in Danish Patent Application No. 201870351, which corresponds with U.S. Appl. No. 16/138,779, 10 pages. |
| Office Action, dated Mar. 21, 2019, received in U.S. Appl. No. 16/145,025, 14 pages. |
| Final Office Action, dated Sep. 19, 2019, received in U.S. Appl. No. 16/145,025, 15 pages. |
| Office Action, dated Jun. 12, 2020, received in U.S. Appl. No. 16/145,025, 17 pages. |
| Final Office Action, dated Dec. 18, 2020, received in U.S. Appl. No. 16/145,025, 17 pages. |
| Notice of Allowance, dated Mar. 17, 2021, received in U.S. Appl. No. 16/145,025, 5 pages. |
| Innovation Patent, dated May 22, 2019, received in Australian Patent Application No. 2019100486, which corresponds with U.S. Appl. No. 16/138,779, 3 pages. |
| Certificate of Examination, dated Jul. 19, 2019, received in Australian Patent Application No. 2019100486, which corresponds with U.S. Appl. No. 16/138,779, 5 pages. |
| Office Action, dated Aug. 3, 2020, received in Chinese Patent Application No. 201910261469.3, which corresponds with U.S. Appl. No. 16/138,779, 5 pages. |
| Office Action, dated Jan. 20, 2021, received in Chinese Patent Application No. 201910261469.3, which corresponds with U.S. Appl. No. 16/138,779, 11 pages. |
| Notice of Allowance, dated Apr. 20, 2021, received in Chinese Patent Application No. 201910261469.3, which corresponds with U.S. Appl. No. 16/138,779, 6 pages. |
| Patent, dated Jul. 13, 2021, received in Chinese Patent Application No. 201910261469.3, which corresponds with U.S. Appl. No. 16/138,779, 6 pages. |
| Office Action, dated Sep. 28, 2018, received in Danish Patent Application No. 201870352, which corresponds with U.S. Appl. No. 16/145,025, 7 pages. |
| Office Action, dated Jan. 31, 2019, received in Danish Patent Application No. 201870352, which corresponds with U.S. Appl. No. 16/145,025, 4 pages. |
| Office Action, dated Sep. 16, 2019, received in Danish Patent Application No. 201870352, which corresponds with U.S. Appl. No. 16/145,025, 3 pages. |
| Office Action, dated Aug. 27, 2020, received in Danish Patent Application No. 201870352, which corresponds with U.S. Appl. No. 16/145,025, 2 pages. |
| Intention to Grant, dated Mar. 10, 2021, received in Danish Patent Application No. 201870352, which corresponds with U.S. Appl. No. 16/145,025, 2 pages. |
| Decision to Grant, dated Jul. 2, 2021, received in Danish Patent Application No. 201870352, which corresponds with U.S. Appl. No. 16/145,025, 2 pages. |
| Patent, dated Nov. 9, 2021, received in Danish Patent Application No. 201870352, which corresponds with U.S. Appl. No. 16/145,025, 3 pages. |
| Office Action, dated Jul. 17, 2019, received in European Patent Application No. 19159743.4, which corresponds with U.S. Appl. No. 16/145,025, 8 pages. |
| Office Action, dated Oct. 5, 2020, received in European Patent Application No. 19159743.4, which corresponds with U.S. Appl. No. 16/145,025, 6 pages. |
| Decision to Grant, dated Jun. 24, 2021, received in European Patent Application No. 19159743.4, which corresponds with U.S. Appl. No. 16/145,025, 2 pages. |
| Certificate of Grant, dated Aug. 13, 2021, received in European Patent Application No. 19159743.4, which corresponds with U.S. Appl. No. 16/145,025, 3 pages. |
| Office Action, dated Dec. 13, 2021, received in Japanese Patent Application No. 2020-562126, which corresponds with U.S. Appl. No. 16/145,025, 2 pages. |
| Notice of Allowance, dated May 30, 2022, received in Japanese Patent Application No. 2020-562126, which corresponds with U.S. Appl. No. 16/145,025, 2 pages. |
| Patent, dated Jun. 30, 2022, received in Japanese Patent Application No. 2020-562126, which corresponds with U.S. Appl. No. 16/145,025, 3 pages. |
| Office Action, dated Oct. 26, 2022, received in Korean Patent Application No. 2020-7032392, which corresponds with U.S. Appl. No. 16/145,025, 5 pages. |
| Notice of Allowance, dated May 19, 2023, received in Korean Patent Application No. 2020-7032392, which corresponds with U.S. Appl. No. 16/145,025, 2 pages. |
| Patent, dated Jun. 8, 2023, received in Korean Patent Application No. 2020-7032392, which corresponds with U.S. Appl. No. 16/145,025, 4 pages. |
| Office Action, dated Sep. 20, 2022, received in Indian Patent Application No. 202017052984, which corresponds with U.S. Appl. No. 16/145,025, 11 pages. |
| Notice of Allowance, dated May 15, 2020, received in U.S. Appl. No. 16/574,029, 10 pages. |
| Office Action, dated Jan. 20, 2022, received in Australian Patent Application No. 2019349408, which corresponds with U.S. Appl. No. 16/574,029, 3 pages. |
| Notice of Acceptance, dated Jul. 29, 2022, received in Australian Patent Application No. 2019349408, which corresponds with U.S. Appl. No. 16/574,029, 3 pages. |
| Notice of Allowance, dated Mar. 2, 2022, received in Chinese Patent Application No. 202110369762.9, which corresponds with U.S. Appl. No. 16/574,029, 7 pages. |
| Patent, dated Mar. 29, 2022, received in Chinese Patent Application No. 202110369762.9, which corresponds with U.S. Appl. No. 16/574,029, 6 pages. |
| Notice of Allowance, dated Apr. 25, 2022, received in Japanese Patent Application No. 2021-510765, which corresponds with U.S. Appl. No. 16/574,029, 2 pages. |
| Patent, dated May 12, 2022, received in Japanese Patent Application No. 2021-510765, which corresponds with U.S. Appl. No. 16/574,029, 3 pages. |
| Office Action, dated Dec. 29, 2022, received in Indian Patent Application No. 202117008282, which corresponds with U.S. Appl. No. 16/574,029, 10 pages. |
| Office Action, dated Feb. 24, 2023, received in Indian Patent Application No. 202117008282, which corresponds with U.S. Appl. No. 16/574,029, 7 pages. |
| Office Action, dated Jul. 6, 2022, received in Korean Patent Application No. 2021-7005584, which corresponds with U.S. Appl. No. 16/574,029, 13 pages. |
| Notice of Allowance, dated Mar. 22, 2023, received in Korean Patent Application No. 2021-7005584, which corresponds with U.S. Appl. No. 16/574,029, 2 pages. |
| Patent, dated Apr. 11, 2023, received in Korean Patent Application No. 2021-7005584, which corresponds with U.S. Appl. No. 16/574,029, 4 pages. |
| Office Action, dated Apr. 30, 2021, received in U.S. Appl. No. 17/030,209, 27 pages. |
| Office Action, dated Jan. 8, 2021, received in U.S. Appl. No. 17/018,958, 27 pages. |
| Notice of Allowance, dated Apr. 20, 2021, received in U.S. Appl. No. 17/018,958, 12 pages. |
| Office Action, dated Aug. 13, 2021, received in Australian Patent Application No. 2020239688, which corresponds with U.S. Appl. No. 17/018,958, 4 pages. |
| Office Action, dated Nov. 5, 2021, received in Australian Patent Application No. 2020239688, which corresponds with U.S. Appl. No. 17/018,958, 4 pages. |
| Notice of Allowance, dated Feb. 22, 2022, received in Australian Patent Application No. 2020239688, which corresponds with U.S. Appl. No. 17/018,958, 3 pages. |
| Certificate of Grant, dated Jun. 23, 2022, received in Australian Patent Application No. 2020239688, which corresponds with U.S. Appl. No. 17/018,958, 4 pages. |
| Office Action, dated Dec. 18, 2020, received in Danish Patent Application No. 202070602, which corresponds with U.S. Appl. No. 17/018,958, 10 pages. |
| Office Action, dated Mar. 14, 2022, received in Danish Patent Application No. 202070602, which corresponds with U.S. Appl. No. 17/018,958, 5 pages. |
| Office Action, dated Nov. 14, 2022, received in Danish Patent Application No. 202070602, which corresponds with U.S. Appl. No. 17/018,958, 2 pages. |
| Office action, dated Dec. 3, 2021, received in Indian Patent Application No. 202014041448, which corresponds with U.S. Appl. No. 17/018,958, 10 pages. |
| Notice of Allowance, dated Dec. 20, 2021, received in Japanese Patent Application No. 2020-159787, which corresponds with U.S. Appl. No. 17/018,958, 2 pages. |
| Notice of Allowance, dated Feb. 18, 2022, received in Japanese Patent Application No. 2022-005327, which corresponds with U.S. Appl. No. 17/018,958, 2 pages. |
| Patent, dated Mar. 14, 2022, received in Japanese Patent Application No. 2022-005327, which corresponds with U.S. Appl. No. 17/018,958, 3 pages. |
| Office Action, dated Nov. 8, 2021, received in Korean Patent Application No. 2020-0124085, which corresponds with U.S. Appl. No. 17/018,958, 9 pages. |
| Notice of Allowance, dated Jul. 13, 2022, received in Korean Patent Application No. 2020-0124085, which corresponds with U.S. Appl. No. 17/018,958, 2 pages. |
| Patent, dated Jul. 22, 2022, received in Korean Patent Application No. 2020-0124085, which corresponds with U.S. Appl. No. 17/018,958, 4 pages. |
| Office Action, dated Aug. 13, 2021, received in U.S. Appl. No. 17/202,233, 19 pages. |
| Final Office Action, dated Feb. 15, 2022, received in U.S. Appl. No. 17/202,233, 24 pages. |
| Office Action, dated Aug. 16, 2022, received in U.S. Appl. No. 17/202,233, 25 pages. |
| Notice of Allowance, dated Mar. 22, 2023, received in U.S. Appl. No. 17/202,233, 8 pages. |
| Office Action, dated Feb. 21, 2021, received in U.S. Appl. No. 16/841,550, 8 pages. |
| Notice of Allowance, dated May 4, 2021, received in U.S. Appl. No. 16/841,550, 12 pages. |
| Notice of Allowance, dated Dec. 7, 2021, received in U.S. Appl. No. 16/997,860, 10 pages. |
| Office Action, dated Jan. 22, 2021, received in U.S. Appl. No. 17/018,980, 17 pages. |
| Office Action, dated May 14, 2021, received in U.S. Appl. No. 17/018,980, 4 pages. |
| Notice of Allowance, dated May 28, 2021, received in U.S. Appl. No. 17/018,980, 5 pages. |
| Office Action, dated Aug. 20, 2021, received in Australian Patent Application No. 2020239675, which corresponds with U.S. Appl. No. 17/018,980, 4 pages. |
| Office Action, dated Dec. 16, 2021, received in Australian Patent Application No. 2020239675, which corresponds with U.S. Appl. No. 17/018,980, 2 pages. |
| Notice of Allowance, dated Jan. 21, 2022, received in Australian Patent Application No. 2020239675, which corresponds with U.S. Appl. No. 17/018,980, 3 pages. |
| Certificate of Grant, dated May 26, 2022, received in Australian Patent Application No. 2020239675, which corresponds with U.S. Appl. No. 17/018,980, 3 pages. |
| Office Action, dated Dec. 18, 2020, received in Danish Patent Application No. 202070603, which corresponds with U.S. Appl. No. 17/018,980, 9 pages. |
| Office Action, dated Feb. 25, 2022, received in Danish Patent Application No. 202070603, which corresponds with U.S. Appl. No. 17/018,980, 2 pages. |
| Office Action, dated Feb. 17, 2023, received in Danish Patent Application No. 202070603, which corresponds with U.S. Appl. No. 17/018,980, 4 pages. |
| Office Action, dated Aug. 10, 2021, received in Indian Patent Application No. 202014040937, which corresponds with U.S. Appl. No. 17/018,980, 7 pages. |
| Office Action, dated Dec. 20, 2021, received in Japanese Patent Application No. 2020-159788, which corresponds with U.S. Appl. No. 17/018,980, 2 pages. |
| Notice of Allowance, dated Feb. 18, 2022, received in Japanese Patent Application No. 2022-005328, which corresponds with U.S. Appl. No. 17/018,980, 2 pages. |
| Patent, dated Mar. 14, 2022, received in Japanese Patent Application No. 2022-005328, which corresponds with U.S. Appl. No. 17/018,980, 3 pages. |
| Office Action, dated Jan. 7, 2021, received in U.S. Appl. No. 17/018,994, 7 pages. |
| Notice of Allowance, dated Feb. 23, 2021, received in U.S. Appl. No. 17/018,994, 8 pages. |
| Office Action, dated Aug. 13, 2021, received in Australian Patent Application No. 2020239691, U.S. Appl. No. 17/018,994, 5 pages. |
| Office Action, dated Nov. 15, 2021, received in Australian Patent Application No. 2020239691, U.S. Appl. No. 17/018,994, 4 pages. |
| Notice of Allowance, dated Mar. 2, 2022, received in Australian Patent Application No. 2020239691, U.S. Appl. No. 17/018,994, 3 pages. |
| Office Action, dated Jan. 12, 2021, received in Danish Patent Application No. 2020-70604, which corresponds with U.S. Appl. No. 17/018,994, 8 pages. |
| Office Action, dated Feb. 4, 2022, received in Danish Patent Application No. 2020-70604, which corresponds with U.S. Appl. No. 17/018,994, 3 pages. |
| Office Action, dated Nov. 2, 2022, received in Danish Patent Application No. 2020-70604, which corresponds with U.S. Appl. No. 17/018,994, 3 pages. |
| Office Action, dated Dec. 2, 2021, received in Indian Patent Application No. 202014041104, which corresponds with U.S. Appl. No. 17/018,994, 7 pages. |
| Office Action, dated Jan. 7, 2022, received in Japanese Patent Application No. 2020-159789, which corresponds with U.S. Appl. No. 17/018,994, 5 pages. |
| Notice of Allowance, dated Aug. 8, 2022, received in Japanese Patent Application No. 2020-159789, which corresponds with U.S. Appl. No. 17/018,994, 1 page. |
| Office Action, dated Sep. 14, 2023, received in U.S. Appl. No. 17/720,227, 5 pages. |
| Patent, dated Sep. 9, 2022, received in Japanese Patent Application No. 2020-159789, which corresponds with U.S. Appl. No. 17/018,994, 3 pages. |
| Office Action, dated Apr. 5, 2022, received in U.S. Appl. No. 17/307,957, 10 pages. |
| Notice of Allowance, dated May 4, 2022, received in U.S. Appl. No. 17/307,957, 12 pages. |
| Office Action, dated Aug. 31, 2022, received in Australian Patent Application No. 2021240284, which corresponds with U.S. Appl. No. 17/307,957, 2 pages. |
| Notice of Allowance, dated Sep. 14, 2022, received in Australian Patent Application No. 2021240284, which corresponds with U.S. Appl. No. 17/307,957, 3 pages. |
| Patent, dated Jan. 19, 2023, received in Australian Patent Application No. 2021240284, which corresponds with U.S. Appl. No. 17/307,957, 3 pages. |
| Office Action, dated Nov. 2, 2022, received in Chinese Patent Application No. 202110660753.5, 2 pages. |
| Patent, dated Jun. 20, 2023, received in Chinese Patent Application No. 202110660753.5, 7 pages. |
| Office Action, dated Sep. 1, 2023, received in Japanese Patent Application No. 2022-103836, which corresponds with U.S. Appl. No. 17/307,957, 2 pages. |
| Office Action, dated Jul. 22, 2022, received in U.S. Appl. No. 17/344,846, 8 pages. |
| Final Office Action, dated Dec. 23, 2022, received in U.S. Appl. No. 17/344,846, 8 pages. |
| Notice of Allowance, dated Apr. 28, 2023, received in U.S. Appl. No. 17/344,846, 5 pages. |
| Office Action, dated Mar. 29, 2023, received in Australian Patent Application No. 2022202851, which corresponds with U.S. Appl. No. 17/344,846, 3 pages. |
| Office Action, dated Feb. 3, 2023, received in U.S. Appl. No. 17/568,624, 44 pages. |
| Noticed of Allowance, dated Dec. 7, 2022, received in U.S. Appl. No. 17/716,984, 10 pages. |
| Office Action, dated Sep. 4, 2023, received in Australian Patent Application No. 2022235625, which corresponds with U.S. Appl. No. 17/568,624, 3 pages. |
| Office Action, dated Jun. 2, 2023, received in Japanese Patent Application No. 2022-077644, which corresponds with U.S. Appl. No. 17/716,984, 6 pages. |
| Office Action, dated May 17, 2023, received in U.S. Appl. No. 17/750,133, 23 pages. |
| Notice of Allowance, dated Jun. 28, 2023, received in U.S. Appl. No. 17/750,133, 10 pages. |
| Office Action, dated Jul. 5, 2023, received in Australian Patent Application No. 2022231686, which corresponds with U.S. Appl. No. 17/750,133, 2 pages. |
| Notice of Allowance, dated Jul. 6, 2023, received in U.S. Appl. No. 18/107,381, 24 pages. |
| European Search Report, dated Sep. 23, 2021, received in European Patent Application No. 21178349.3, which corresponds with U.S. Appl. No. 16/145,015, 4 pages. |
| Invitation to Pay Additional Fees, dated Jul. 15, 2019, received in International Patent Application No. PCT/US2019/029904, which corresponds with U.S. Appl. No. 16/145,015, 29 pages. |
| International Search Report and Written Opinion, dated Sep. 9, 2019, received in International Patent Application No. PCT/US2019/029904, which corresponds with U.S. Appl. No. 16/145,015, 31 pages. |
| European Search Report, dated Jul. 4, 2019, received in European Patent Application No. 19158743.4, which corresponds with U.S. Appl. No. 16/145,025, 4 pages. |
| Invitation to Pay Additional Fees, dated Dec. 12, 2019, received in International Patent Application No. PCT/US2019052140, which corresponds with U.S. Appl. No. 16/574,029, 18 pages. |
| International Search Report and Written Opinion, dated Feb. 5, 2020, received in International Patent Application No. PCT/US2019052140, which corresponds with U.S. Appl. No. 16/574,029, 22 pages. |
| Invitation to Pay Additional Fees, dated Jan. 19, 2021, received in International Patent Application No. PCT/US2020/052641, which corresponds with U.S. Appl. No. 17/030,209, 15 pages. |
| International Search Report and Written Opinion, dated Mar. 12, 2021, received in International Patent Application No. PCT/US2020/052641, which corresponds with U.S. Appl. No. 17/030,209, 21 pages. |
| Invitation to Pay Additional Fees, dated Jun. 23, 2021, received in International Patent Application No. PCT/US2021/022378, which corresponds with U.S. Appl. No. 17/200,676, 15 pages. |
| International Search Report and Written Opinion, dated Aug. 13, 2021, received in International Patent Application No. PCT/US2021/022378, which corresponds with U.S. Appl. No. 17/200,676, 19 pages. |
| Invitation to Pay Additional Fees, dated May 17, 2021, received in International Patent Application No. PCT/US2021/015556, which corresponds with U.S. Appl. No. 17/018,958, 19 pages. |
| International Search Report and Written Opinion, dated Jul. 8, 2021, received in International Patent Application No. PCT/US2021/015556, which corresponds with U.S. Appl. No. 17/018,958, 26 pages. |
| Invitation to Pay Additional Fees, dated Jul. 26, 2022, received in International Patent Application No. PCT/US2022/024894, which corresponds with U.S. Appl. No. 17/720,227, 34 pages. |
| Notice of Allowance, dated Dec. 13, 2021, received in U.S. Appl. No. 17/030,209, 10 pages. |
| Final Office Action, dated May 15, 2023, received in U.S. Appl. No. 17/568,624, 31 pages. |
| Office Action, dated Oct. 27, 2023, received in U.S. Appl. No. 17/568,624, 33 pages. |
| Final Office Action, dated Jun. 2, 2023, received in Japanese Patent Application No. 2022-077644, which corresponds with U.S. Appl. No. 17/716,984, 4 pages. |
| Invitation to Pay Additional Fees, dated Oct. 5, 2023, received in International Patent Application No. PCT/US2023/021563, which corresponds with U.S. Appl. No. 18/144,746, 19 pages. |
| Office Action, dated May 23, 2024, received in European Patent Application No. 21717681.7, which corresponds with U.S. Appl. No. 17/202,233, 6 pages. |
| Notice of Allowance, dated Mar. 5, 2024, received in Japanese Patent Application No. 2022-103836, which corresponds with U.S. Appl. No. 17/307,957, 1 page. |
| Notice of Allowance, dated Mar. 25, 2024, received in Australian Patent Application No. 2022202851, which corresponds with U.S. Appl. No. 17/344,846, 3 pages. |
| Patent, dated May 13, 2024, received in Japanese Patent Application No. 2022-142210, which corresponds with U.S. Appl. No. 17/344,846, 3 pages. |
| Notice of Allowance, dated Feb. 15, 2024, received in U.S. Appl. No. 17/568,624, 8 pages. |
| Notice of Allowance, dated Mar. 25, 2024, received in Australian Patent Application No. 20222356255, which corresponds with U.S. Appl. No. 17/568,624, 3 pages. |
| Notice of Allowance, dated Feb. 9, 2024, received in Australian Patent Application No. 2022231686, which corresponds with U.S. Appl. No. 17/750,133, 3 pages. |
| Extended European Search Report, dated Apr. 26, 2024, received in European Patent Application No. 24151350.6, which corresponds with U.S. Appl. No. 17/750,133, 8 pages. |
| Fukiage et al., “Reduction of Contradictory Partial Occlusion in Mixed Reality by Using Characteristics of Transparency Perception”, 2012 IEEE International Symposium on, IEEE, Nov. 5, 2012, 11 pages. |
| Joaquim, et al., “Dynamic Occlusion Handling for Real-Time AR Applications”, https://doi.org/10.1145335/99973365700, Nov. 2019, 10 pages. |
| Final Office Action, dated Jul. 5, 2024, received in Korean Patent Application No. 2023-7019367, which corresponds with U.S. Appl. No. 17/307,957, 3 pages. |
| Grant Certificate, dated Jul. 25, 2024, received in Australian Patent Application No. 2022202851, which corresponds with U.S. Appl. No. 17/344,846, 3 pages. |
| Grant Certificate, dated Jul. 25, 2024, received in Australian Patent Application No. 2022235625, which corresponds with U.S. Appl. No. 17/568,624, 3 pages. |
| Certificate of Grant, dated Jun. 13, 2024, received in Australian Patent Application No. 2022231686, which corresponds with U.S. Appl. No. 17/750,133, 3 pages. |
| Office Action, dated Sep. 6, 2024, received in U.S. Appl. No. 18/219,627, 17 pages. |
| Office Action, dated Jun. 20, 2024, received in U.S. Appl. No. 18/382,444, 14 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 62739178 | Sep 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 18107381 | Feb 2023 | US |
| Child | 18388176 | US | |
| Parent | 17716984 | Apr 2022 | US |
| Child | 18107381 | US | |
| Parent | 16997860 | Aug 2020 | US |
| Child | 17716984 | US | |
| Parent | 16574029 | Sep 2019 | US |
| Child | 16997860 | US |
