Patent Description:
The present description relates generally to extended reality environments.

Augmented reality technology aims to bridge a gap between virtual environments and a physical environment by providing an enhanced physical environment that is augmented with electronic information. As a result, the electronic information appears to be part of the physical environment as perceived by a user while the user views the physical environment via the augmented reality technology. Reference is made to <CIT> which relates to virtual object hand-off and manipulation.

A physical environment refers to a physical world that people can sense and/or interact with without aid of electronic devices. The physical environment may include physical features such as a physical surface or a physical object. For example, the physical environment corresponds to a physical park that includes physical trees, physical buildings, and physical people. People can directly sense and/or interact with the physical environment such as through sight, touch, hearing, taste, and smell. In contrast, an extended reality (XR) environment refers to a wholly or partially simulated environment that people sense and/or interact with via an electronic device. For example, the XR environment may include augmented reality (AR) content, mixed reality (MR) content, virtual reality (VR) content, and/or the like. With an XR system, a subset of a person's physical motions, or representations thereof, are tracked, and, in response, one or more characteristics of one or more virtual objects simulated in the XR environment are adjusted in a manner that comports with at least one law of physics. As one example, the XR system may detect head movement and, in response, adjust graphical content and an acoustic field presented to the person in a manner similar to how such views and sounds would change in a physical environment. As another example, the XR system may detect movement of the electronic device presenting the XR environment (e.g., a mobile phone, a tablet, a laptop, or the like) and, in response, adjust graphical content and an acoustic field presented to the person in a manner similar to how such views and sounds would change in a physical environment. In some situations (e.g., for accessibility reasons), the XR system may adjust characteristic(s) of graphical content in the XR environment in response to representations of physical motions (e.g., vocal commands).

There are many different types of electronic systems that enable a person to sense and/or interact with various XR environments. Examples include head mountable systems, projection-based systems, heads-up displays (HUDs), vehicle windshields having integrated display capability, windows having integrated display capability, displays formed as lenses designed to be placed on a person's eyes (e.g., similar to contact lenses), headphones/earphones, speaker arrays, input systems (e.g., wearable or handheld controllers with or without haptic feedback), smartphones, tablets, and desktop/laptop computers. A head mountable system may have one or more speaker(s) and an integrated opaque display. Alternatively, a head mountable system may be configured to accept an external opaque display (e.g., a smartphone). The head mountable system may incorporate one or more imaging sensors to capture images or video of the physical environment, and/or one or more microphones to capture audio of the physical environment. Rather than an opaque display, a head mountable system may have a transparent or translucent display. The transparent or translucent display may have a medium through which light representative of images is directed to a person's eyes. The display may utilize digital light projection, OLEDs, LEDs, uLEDs, liquid crystal on silicon, laser scanning light source, or any combination of these technologies. The medium may be an optical waveguide, a hologram medium, an optical combiner, an optical reflector, or any combination thereof. In some implementations, the transparent or translucent display may be configured to become opaque selectively. Projection-based systems may employ retinal projection technology that projects graphical images onto a person's retina. Projection systems also may be configured to project virtual objects into the physical environment, for example, as a hologram or on a physical surface.

Implementations of the subject technology described herein provide transfer of content, editing control of the content, and/or control of one or more applications from one device to another device, using an XR system. For example, with the subject technology, a user drafting an email on their smart phone can place the smartphone in the field of view of an XR device (e.g., a tablet device or a head mountable system) and continue drafting the email in an XR environment created by the XR device. In another example, with the subject technology, a user using an XR device (e.g., a user holding a tablet device or wearing a head mountable system) in a physical environment that includes a smart speaker device and the user's smart phone may look at or gesture toward the smart speaker device. Responsive to a detection of the user looking at or gesturing toward the smart speaker device by the XR device, a song that is playing on the user's phone can be transferred to play on the smart speaker device. Three-dimensional information regarding the devices in the physical environment can be gathered by the XR device, and used to facilitate smooth and continuous transfer of control and/or content between the devices and/or the XR device.

<FIG> illustrates an example system architecture <NUM> including various electronic devices that may implement the subject system in accordance with one or more implementations. Not all of the depicted components may be used in all implementations, however, and one or more implementations may include additional or different components than those shown in the figure. Variations in the arrangement and type of the components may be made without departing from the scope of the claims as set forth herein Additional components, different components, or fewer components may be provided.

The system architecture <NUM> includes an electronic device <NUM>, a handheld electronic device <NUM>, an electronic device <NUM>, an electronic device <NUM>, a smart speaker device <NUM>, and a server <NUM>. For explanatory purposes, the system architecture <NUM> is illustrated in <FIG> as including the electronic device <NUM>, the handheld electronic device <NUM>, the electronic device <NUM>, the electronic device <NUM>, the smart speaker device <NUM>, and the server <NUM>; however, the system architecture <NUM> may include any number of electronic devices, and any number of servers or a data center including multiple servers. In some implementations, the electronic device <NUM>, the handheld electronic device <NUM>, the electronic device <NUM>, the electronic device <NUM>, and/or the smart speaker device <NUM> may be registered to and/or associated with a same user account, such as via the server <NUM>.

The electronic device <NUM> may be an XR device such as a smartphone, a tablet, or a head mountable portable system (e.g., a head mountable display device that can be worn by a user), that includes a display system capable of presenting a visualization of an extended reality environment to the user. The electronic device <NUM> may be powered with a battery and/or another power supply. In an example, the display system of the electronic device <NUM> provides a stereoscopic presentation of the extended reality environment, enabling a three-dimensional visual display of a rendering of a particular scene, to the user. In one or more implementations, instead of, or in addition to, utilizing the electronic device <NUM> to access an extended reality environment, the user may use a handheld electronic device <NUM>, such as a tablet, watch, mobile device, and the like.

The electronic device <NUM> may include one or more cameras such as camera(s) <NUM> (e.g., visible light cameras, infrared cameras, etc.) Further, the electronic device <NUM> may include various sensors <NUM> including, but not limited to, cameras, image sensors, touch sensors, microphones, inertial measurement units (IMU), heart rate sensors, temperature sensors, Lidar sensors, time-of-flight sensors, radar sensors, sonar sensors, GPS sensors, Wi-Fi sensors, near-field communications sensors, radio frequency sensors, eye-tracking sensors, etc. Moreover, the electronic device <NUM> may include hardware elements that can receive user input such as hardware buttons or switches. User input detected by such sensors and/or hardware elements correspond to various input modalities for initiating generating supplemental virtual content within a given extended reality environment. For example, such input modalities may include, but are not limited to, facial tracking, eye tracking (e.g., gaze direction), hand tracking, gesture tracking, biometric readings (e.g., heart rate, pulse, pupil dilation, breath, temperature, electroencephalogram, olfactory), recognizing speech or audio (e.g., particular hotwords), and activating buttons or switches, etc. The electronic device <NUM> may also detect a presence of a person, object, device, and/or an occurrence of an event in a scene to initiate providing supplemental virtual content within the extended reality environment.

The electronic device <NUM> may be communicatively coupled to a base device such as the electronic device <NUM> and/or the electronic device <NUM>. Such a base device may, in general, include more computing resources and/or available power in comparison with the electronic device <NUM>. In an example, the electronic device <NUM> may operate in various modes. For instance, the electronic device <NUM> can operate in a standalone mode independent of any base device. When the electronic device <NUM> operates in the standalone mode, the number of input modalities may be constrained by power and/or processing limitations of the electronic device <NUM> such as available battery power of the device. In response to power limitations, the electronic device <NUM> may deactivate certain sensors within the device itself to preserve battery power and/or to free processing resources.

The electronic device <NUM> may also operate in a wireless tethered mode (e.g., connected via a wireless connection with a base device), working in conjunction with a given base device. The electronic device <NUM> may also work in a connected mode where the electronic device <NUM> is physically connected to a base device (e.g., via a cable or some other physical connector) and may utilize power resources provided by the base device (e.g., where the base device is charging the electronic device <NUM> while physically connected).

When the electronic device <NUM> operates in the wireless tethered mode or the connected mode, a least a portion of processing user inputs and/or rendering the extended reality environment may be offloaded to the base device thereby reducing processing burdens on the electronic device <NUM>. For instance, in an implementation, the electronic device <NUM> works in conjunction with the electronic device <NUM> or the electronic device <NUM> to generate an extended reality environment including physical and/or virtual objects that enables different forms of interaction (e.g., visual, auditory, and/or physical or tactile interaction) between the user and the generated extended reality environment in a real-time manner. In an example, the electronic device <NUM> provides a rendering of a scene corresponding to the extended reality environment that can be perceived by the user and interacted with in a real-time manner. Additionally, as part of presenting the rendered scene, the electronic device <NUM> may provide sound, and/or haptic or tactile feedback to the user. The content of a given rendered scene may be dependent on available processing capability, network availability and capacity, available battery power, and current system workload.

In some implementations, a transfer of editing control of, for example, a word processing document, an email, a text message, and/or or content for another application can be provided from one device to another (e.g., from electronic device <NUM> to electronic device <NUM>) when one device is detected within the proximity of the other device to initiate the transfer of control. In this type of proximity based transfer, electronic device <NUM> may indicate to electronic device <NUM> that it is providing editing control of the word processing document to electronic device <NUM>, and can provide the current state of the document to electronic device <NUM>. However, in this type of proximity-based transfer, electronic device <NUM> is not aware of the 3D position or orientation of the electronic device <NUM>, nor of the state and/or display characteristics of the displayed UI on the electronic device <NUM>.

In an implementation, electronic device <NUM> can transfer content from one device to another (e.g., from electronic device <NUM> to electronic device <NUM>, from electronic device <NUM> to smart speaker device <NUM>, from electronic device <NUM> to smart speaker device <NUM>), including from an application running on one device to an application running on another device. For example, electronic device <NUM> may transfer drafting of an email on electronic device <NUM> for continued drafting of the email using electronic device <NUM> in an XR space. In another example, while a song is playing in a media application running on electronic device <NUM>, a user of electronic device <NUM> may gesture or look at smart speaker device <NUM> to transfer the song that is currently playing to the smart speaker device <NUM> for continuous, uninterrupted play of the song.

In an implementation, the electronic device <NUM> can obtain (e.g., from the processor of electronic device <NUM> and/or using a camera of the electronic device <NUM>), the state and/or display characteristics of the displayed UI on the electronic device <NUM> and can transfer control of the editing of the displayed UI to the electronic device <NUM> while maintaining the state and/or display characteristics of the previously displayed UI.

The network <NUM> may communicatively (directly or indirectly) couple, for example, the electronic device <NUM>, the electronic device <NUM>, the smart speaker device <NUM>, and/or the electronic device <NUM> with each other device and/or the server <NUM>. In one or more implementations, the network <NUM> may be an interconnected network of devices that may include, or may be communicatively coupled to, the Internet.

The electronic device <NUM> may include a touchscreen and may be, for example, a smartphone that includes a touchscreen, a portable computing device such as a laptop computer that includes a touchscreen, a peripheral device that includes a touchscreen (e.g., a digital camera, headphones), a tablet device that includes a touchscreen, a wearable device that includes a touchscreen such as a watch, a band, and the like, any other appropriate device that includes, for example, a touchscreen, or any electronic device with a touchpad. In one or more implementations, the electronic device <NUM> may not include a touchscreen but may support touchscreen-like gestures, such as in an extended reality environment. In one or more implementations, the electronic device <NUM> may include a touchpad. In <FIG>, by way of example, the electronic device <NUM> is depicted as a mobile smartphone device with a touchscreen. In one or more implementations, the electronic device <NUM>, the handheld electronic device <NUM>, and/or the electronic device <NUM> may be, and/or may include all or part of, the electronic device discussed below with respect to the electronic system discussed below with respect to <FIG>. In one or more implementations, the electronic device <NUM> may be another device such as an Internet Protocol (IP) camera, a tablet, or a peripheral device such as an electronic stylus, etc..

The electronic device <NUM> may be, for example, desktop computer, a portable computing device such as a laptop computer, a smartphone, a peripheral device (e.g., a digital camera, headphones), a tablet device, a set-top box configured to interface with an external display such as a television. a wearable device such as a watch, a band, and the like. In <FIG>, by way of example, the electronic device <NUM> is depicted as a desktop computer. The electronic device <NUM> may be, and/or may include all or part of, the electronic system discussed below with respect to <FIG>.

The server <NUM> may form all or part of a network of computers or a group of servers <NUM>, such as in a cloud computing or data center implementation. For example, the server <NUM> stores data and software, and includes specific hardware (e.g., processors, graphics processors and other specialized or custom processors) for rendering and generating content such as graphics, images, video, audio and multi-media files for extended reality environments. In an implementation, the server <NUM> may function as a cloud storage server that stores any of the aforementioned extended reality content generated by the above-discussed devices and/or the server <NUM>, and/or information for generating/rendering such content.

Smart speaker device <NUM> may include one or more microphones for accepting audio (e.g., voice) input, one or more acoustic devices such as speakers, communications circuitry for communicating with electronic device <NUM>, electronic device <NUM>, network <NUM>, electronic device <NUM>, and/or handheld electronic device <NUM>, memory for storing information and/or code for one or more applications, and/or processing circuitry. The smart speaker device <NUM> may be, and/or may include all or part of, the electronic system discussed below with respect to <FIG>.

<FIG> illustrates an example of a physical environment in which an electronic device <NUM>, electronic device <NUM>, and smart speaker device <NUM> are provided. In the example of <FIG>, a user <NUM> wears an electronic device <NUM> in a physical environment <NUM>. The physical environment <NUM>, in the example of <FIG>, includes a physical object <NUM>, a portion of which can be viewed by user <NUM> via display <NUM> (e.g., based on images (from one or more cameras such as camera(s) <NUM>) that are provided to an opaque implementation of display <NUM> or directly through a transparent or translucent implementation of display <NUM>) and portions of which can be viewed directly by the user without the use of any technology (if not otherwise blocked from view).

In the example of <FIG>, computer-generated content is being displayed by display <NUM> (e.g., overlaid on or in front of portions of physical environment <NUM>) in an XR environment. In this example, an application window <NUM> (e.g., a file manager application window, a browser window, a social medial application window, a media player application window, a content editor application window, or any other application user interface) representing an application is displayed by display <NUM>, with which user <NUM> can interact in the XR environment. In this example, smart speaker device <NUM> is partially visible via display <NUM>, and a user interface <NUM> of an application running on electronic device <NUM> is separately displayed, by electronic device <NUM>, on a display <NUM> of electronic device <NUM>.

<FIG> illustrates the environment of <FIG>, in an arrangement in which the electronic device <NUM> is within the field of view of an electronic device such as electronic device <NUM>, and visible via a display such as display <NUM> of electronic device <NUM>. Although various examples are discussed herein in connection with electronic device <NUM>, it should be appreciated that other electronic devices having one or more cameras and/or one or more depth sensors and/or other sensors can be used to perform some or all of the operations described connection with electronic device <NUM>. In various implementations, electronic device <NUM> obtains three-dimensional (3D) information about electronic device <NUM> to facilitate transfer of control of the application running on electronic device <NUM> (and/or content associated therewith) to an application running on electronic device <NUM>. In an example, electronic device <NUM> detects (e.g., using camera(s) <NUM> and/or sensors <NUM> and/or using information provided by electronic device <NUM> to electronic device <NUM> such as via wireless communication between the electronic device <NUM> and electronic device <NUM>) the 3D location, orientation, and/or display location of a UI <NUM> of an application running on the electronic device <NUM>. As shown in <FIG>, using the 3D location, orientation, and/or display location, electronic device <NUM> may display an additional UI <NUM>, with display <NUM> of electronic device <NUM>, that is overlying and aligned with display <NUM> (e.g., overlaid on and aligned with the UI <NUM> that is still displayed on display <NUM>) of electronic device <NUM>.

UI <NUM> displayed by display <NUM> may be displayed with a size, a location, an orientation, and/or display characteristics that mimic the UI <NUM> displayed by display <NUM>. For example, if the UI <NUM> on display <NUM> includes a partially drafted document in a word processing application or an email application with a flashing cursor at the location of a next text input, UI <NUM> displayed by display <NUM> can include the same partially drafted document in a word processing application or an email application at electronic device <NUM>, with a flashing cursor displayed overlaid on the location of the flashing cursor on display <NUM>. In one or more implementations, the UI <NUM> may include three-dimensional effects added to the UI <NUM> displayed by display <NUM>. In this way, control of editing of the partially drafted document can be smoothly transitioned from electronic device <NUM> to electronic device <NUM>. Because the electronic device <NUM> exists within the XR environment of electronic device <NUM> (e.g., within the field of view of the electronic device <NUM> and/or within the area corresponding to display <NUM>), when the electronic device <NUM> takes control of the input to the UI, both the input that is accepted by the electronic device <NUM> and the output (e.g., display, tactile, audio) provided to the user responsive to the input is, at least initially, dependent on the detected characteristics and the state of the electronic device <NUM>.

<FIG> illustrates an example in which the UI <NUM> on display <NUM> has been moved (e.g., by a gesture input from user <NUM> and/or a gaze-based input from user <NUM> to electronic device <NUM>) away from the location of electronic device <NUM>. In the example of <FIG>, control of the UI and/or the content therein has been completely transferred to electronic device <NUM>. In the example of <FIG>, display <NUM> of electronic device <NUM> no longer displays the UI <NUM> after electronic device <NUM> assumes control. For example, display <NUM> may be powered off or changed to a low power state, and/or the UI <NUM> and the associated application on electronic device <NUM> can be closed or deactivated when electronic device <NUM> determines that control of the application has been passed to electronic device <NUM>. In various implementations, UI <NUM> and/or display <NUM> can be closed, powered off, and/or otherwise deactivated at the time that UI <NUM> is first displayed, after a period of time following the time when UI <NUM> is first displayed, when user input to UI <NUM> is detected, or when UI <NUM> is moved away from the location of display <NUM> (e.g., by a gesture input or other input from user <NUM>). For example, electronic device <NUM> can send (e.g., via near-field communications, Wi-Fi communications, etc.) a notification to electronic device <NUM> that electronic device <NUM> has assumed control of the application content when the UI <NUM> is displayed or when the UI <NUM> is moved away from the location of electronic device <NUM>.

In the example of a word processing UI, the UI <NUM> that is generated by the electronic device <NUM> allows the user <NUM> to continue editing the word processing document that was being edited in UI <NUM> on electronic device <NUM>, via input to the electronic device <NUM> (e.g., via detection of the user's finger movements by the camera(s) <NUM> and/or sensor <NUM>). After transfer of control to UI <NUM>, UI <NUM> can be modified from an initially displayed UI that has a size, a position, an orientation, and/or an appearance that matches, and is (at least initially) overlaid on the corresponding UI <NUM> displayed on the electronic device <NUM>. For example, UI <NUM> can be modified to a UI that leverages the advantages of electronic device <NUM>. For example, UI <NUM> can be expanded in size, moved to a more convenient location in the XR environment, broken out into multiple (e.g., 3D distributed portions), etc..

In the example of <FIG>, a system is described that includes a first device (e.g., electronic device <NUM>) configured to display a first user interface (e.g., UI <NUM>) of an application running on the first device; and a second device (e.g., electronic device <NUM>) configured to display computer generated content (e.g., application window <NUM>) overlaid on a view of a physical environment (e.g., physical environment <NUM>). In this example, the second device is configured to detect a position and an orientation of the first device in the physical environment; obtain a state of the first user interface of the application running on the first device; and display, at least partially overlaid on a view of the first device (see, e.g., <FIG>) and based on the detected position and orientation of the first device, a second user interface (e.g., UI <NUM>) corresponding to the application. The second user interface (e.g., UI <NUM>) is displayed with the obtained state of the first user interface (e.g., UI <NUM>).

In this example, in one or more implementations, the second user interface (e.g., UI <NUM>) may be used to extend the first user interface (e.g., UI <NUM>) beyond the bounds of the first device into the extended reality of the second device. For example, in one or more implementations, the first device may be a desktop computer or a laptop computer having a mouse or trackpad and a keyboard, with the second device continuing to provide an extended reality. With the trackpad or the mouse of the first device (or using a gesture input to the second device), a user may drag content, such as a window or application displayed within the bounds of the display of the first device, to a location that is outside of the bounds of the display of the first device and that is visible in the extended reality environment of the second device. In one or more implementations, applications running on the first device may be configured to define accessory windows for XR display outside the boundaries of that device, when an extended reality device is available. For example, a content editing application running on the first device can receive input from an additional toolbar displayed, by the second device, outside the bounds of the first device display (e.g., positioned closely to the display of the first device within the extended reality environment of the second device).

In the example of <FIG>, the second device may also be configured to receive a user input and, responsive to the user input, move the second user interface from a first location on a display of the second device to a second location on the display of the second device responsive to the user input (see, e.g., <FIG>). The second device may also operate an application, at the second device, that corresponds to the application running on the first device, and provide an indication to the first device to deactivate the application at the first device. In one example, the application is a content editor application, and the state of the first user interface includes content previously input to the first device that is currently displayed in the first user interface (e.g., prior text or image input to a word processor, an email composer, or a messaging application), and an active indicator of an area within the first user interface for input of additional content. For example, the content editor application may include a text entry field, and the active indicator may be a cursor in the text entry field.

In another example, the application is a media player application, and the state of the first user interface includes an indicator (e.g., a name or another identifier) of media (e.g., a song or a video) that is currently being played by the second device, and an indicator of a current playback time of the media in the media player application. In another example, the application is a social media application, and the state of the first user interface includes an indication of a selectable link displayed in the social media application. For example, the selectable link may be a link to another social media user page, a link to a "like" button, etc. that can be replicated (e.g., in appearance and/or function) in the second user interface to provide continuous functionality before and after transfer of control from the electronic device <NUM> to the electronic device <NUM>.

<FIG> illustrates how, for example, using camera(s) <NUM> and/or sensors <NUM> (e.g., depth sensors) of electronic device <NUM> can detect and track the position, orientation, and size of the electronic device <NUM>, display <NUM>, and/or UI <NUM>. For example, images from camera(s) <NUM> and/or sensor data from sensors <NUM> of electronic device <NUM> can be provided to a processor <NUM> of the electronic device <NUM>. Processor <NUM> may determine the state, location, orientation, and/or appearance of the UI <NUM> currently being displayed on display <NUM> of electronic device <NUM>, using the images from camera(s) <NUM> and/or sensor data from sensors <NUM> of electronic device <NUM>. Processor <NUM> can then generate UI <NUM> having the same or similar state and appearance as UI <NUM>. <FIG> also illustrates how alternatively, or in addition, the state and appearance of the UI <NUM> currently being displayed by display <NUM> can be provided to the processor <NUM> separately (e.g., wirelessly from the electronic device <NUM> or via the cloud, such as via server <NUM>) for use in generating UI <NUM> having the same or similar state and appearance as UI <NUM>.

Electronic device <NUM> may, in one or more implementations, send the electronic device <NUM> state and/or context information regarding the application that is being used by electronic device <NUM> (e.g., that a document that is open, etc.). Handoff logic between electronic device <NUM> and electronic device <NUM> may include, for example, a handoff request from electronic device <NUM> to electronic device <NUM> (e.g., responsive to a detection of electronic device <NUM> by electronic device <NUM>), handoff operations performed by electronic device <NUM> and/or electronic device <NUM>, and/or a handoff confirmation provided from electronic device <NUM> to electronic device <NUM>. This handoff logic can be via a direct peer-to-peer connection and/or facilitated by a cloud server such as server <NUM>. Electronic device <NUM>, electronic device <NUM>, smart speaker device <NUM>, and/or other devices of system architecture <NUM> may be associated with a same user account which allows the devices to form a secure communication channel for communicating, such as by using a private key associated with the user account.

In one or more implementations, continuous communication between the devices may occur throughout the handoff process. In some examples described herein, electronic device <NUM> may take a snapshot of the UI <NUM> displayed on the electronic device <NUM> and then display that snapshot again through the electronic device <NUM>. In other examples described herein, the UI <NUM> generated by the electronic device <NUM> can also, or alternatively, be driven by UI data provided by the electronic device <NUM>. The electronic device <NUM> can render a UI <NUM>, for display in an XR environment, based UI information (e.g., information describing the content and/or layout of the UI <NUM> and/or a rendered UI) sent from the electronic device <NUM> to the electronic device <NUM>. The UI information may include a display tree that includes nodes corresponding to each of the UI elements displayed in the UI <NUM> on the electronic device <NUM>. The electronic device <NUM> may then use the provided display tree and re-render UI <NUM> for an XR environment. Re-rendering UI <NUM> for the XR environment may including determining the size, location, and/or orientation of the UI <NUM> based on the images from camera(s) <NUM> and/or the three-dimensional information from sensors <NUM> (e.g., including depth sensor information). Electronic device <NUM> may continue to send updates to the UI information when the UI <NUM> changes and while the handoff to electronic device <NUM> is still in progress.

In various implementations, while the UI <NUM> is overlaid on UI <NUM> (e.g., as in the example of <FIG>), new inputs from user <NUM> (e.g., to continue editing a document therein or controlling a media player therein) can be provided to electronic device <NUM> (e.g., by touch inputs on display <NUM> or other inputs to electronic device <NUM>) or to electronic device <NUM> (e.g., via detection of the user's finger movements, other gestures, voice inputs, or eye-tracking inputs with camera(s) <NUM> and/or sensors <NUM>), such as depending on whether the handoff has been completed.

For example, <FIG> illustrates an example in which, UI <NUM> is overlaid on UI <NUM> and a touch input (indicated by arrow <NUM>) is provided to display <NUM> of electronic device <NUM>. In this example (which may occur immediately after the UI <NUM> is initially displayed but before electronic device <NUM> assumes control of the content within UI <NUM>), the touch input at a particular location <NUM> on display <NUM> is accepted by electronic device <NUM> (e.g., by a processor of electronic device <NUM>) and used to modify the UI <NUM> displayed on display <NUM>. Information indicating the corresponding change to UI <NUM> (e.g., and/or information indicating the touch input location) can also be provided to processor <NUM> of electronic device <NUM> (e.g., via a wireless communication from electronic device <NUM> to electronic device <NUM>) and/or can be detected by one or more camera(s) <NUM> and/or sensors <NUM> of electronic device <NUM>. Based on the indication of the change to UI <NUM> (e.g., and/or the indication of the touch location), processor <NUM> makes a corresponding modification to UI <NUM>.

In one operational scenario, if the user taps display <NUM> at a location <NUM> corresponding to a "skip" function of a media player application to skip a song or a video paying in the UI <NUM> to a next song or video, electronic device <NUM> may skip to the next song, make a corresponding update to UI <NUM> to indicate the next song is playing, and provide an indication of the update to UI <NUM> and the state of the next song that is playing to processor <NUM>. Processor <NUM> may then update UI <NUM> to indicate the next song is playing, thus mimicking the change to UI <NUM>, as if a gesture input had been received by processor <NUM> at a corresponding location <NUM> on UI <NUM>. In another example, electronic device <NUM> detects the update to UI <NUM> directly (e.g., using camera(s) <NUM>) and updates UI <NUM> accordingly based on the detection, as if a gesture input had been received by processor <NUM> at a corresponding location <NUM> on UI <NUM>.

In another example operational scenario, electronic device <NUM> detects the application running on the electronic device <NUM>, launches a local version of the application at electronic device <NUM>, and then receives, from the electronic device <NUM>, information describing any content being displayed by the electronic device <NUM>. For example, the information describing the content may include a filepath corresponding to a file, a document, etc. In this example scenario, the electronic device <NUM> may translate touch inputs on the phone to touch inputs through the electronic device <NUM> version of the UI.

In the example of <FIG>, UI <NUM> is displayed (e.g., under UI <NUM>) while UI <NUM> is overlaid on the location of display <NUM>. However, it should also be appreciated that, in the arrangement of <FIG>, UI <NUM> may be disabled or deactivated, such that, although the processor(s) of electronic device <NUM> continue to control operation of the application corresponding to UI <NUM>, UI <NUM> functions, at least temporarily, as the UI for the application running on electronic device <NUM> (e.g., by detecting inputs to UI <NUM> and providing the inputs to electronic device <NUM> to control the application accordingly).

In the example of <FIG>, while UI <NUM> is displayed over display <NUM>, control of the application corresponding to UI <NUM> and/or UI <NUM> is maintained, at least initially, by electronic device <NUM>. However, <FIG> illustrates another example in which, while UI <NUM> is displayed over display <NUM>, control of the application corresponding to UI <NUM> has been transferred to processor <NUM> of electronic device <NUM>. This transfer of control to electronic device <NUM> can be performed using the handoff logic described above in connection with, for example, <FIG>. In this example, UI <NUM> can continue to be displayed by display <NUM>, or display <NUM> can be powered off or discontinue display of UI <NUM>.

As illustrated in <FIG>, when the user provides a touch input at what appears to the user to be a location <NUM> on display <NUM> (e.g., as indicated by arrow <NUM>), that touch input can be received by processor <NUM> (e.g., using camera(s) <NUM> and/or sensors <NUM>) as a gesture input to UI <NUM> at a corresponding location <NUM>. In this example, the gesture input at location <NUM> of UI <NUM> is obtained by processor <NUM>, and processor <NUM> makes a corresponding update to UI <NUM>, the content therein, and/or the application corresponding thereto. In an operational scenario in which UI <NUM> continues to be displayed on display <NUM>, processor <NUM> may also provide an indication of the gesture input at location <NUM> or of the corresponding update to UI <NUM> and/or the underlying application to electronic device <NUM>, so that electronic device <NUM> can make a corresponding update to UI <NUM>. In the examples of <FIG>, <FIG>, and <FIG>, UI <NUM> is shown as being partially overlapping and separated spatially from the surface of electronic device <NUM>. However, it should be appreciated that the UI <NUM> can be spatially separated as shown, or can be displayed by display <NUM> to appear to be directly on and/or completely overlapping the surface of electronic device <NUM>.

As illustrated in <FIG>, after the UI <NUM> provided by electronic device <NUM> is moved away from electronic device <NUM> (e.g., and display <NUM> stops displaying UI <NUM>, deactivates UI <NUM>, and/or display <NUM> is powered off or placed in a low power mode), control of the application corresponding to UI <NUM>, control of UI <NUM> itself, and control of the content therein is handled by processor <NUM> of electronic device <NUM> (e.g., without further interaction with electronic device <NUM>). In this example, UI <NUM> can be moved to any desired location in the XR environment of electronic device <NUM>, resized, and/or otherwise modified while providing continuous control of the UI and/or the application previously provided by electronic device <NUM>.

As shown in <FIG>, a gesture input (e.g., as indicated by arrow <NUM>) to UI <NUM> can be detected by processor <NUM> (e.g., based on images from camera(s) <NUM> and/or sensor data from sensors <NUM>). The detected gesture input can be used by processor <NUM> to control the application corresponding to UI <NUM> and running on processor <NUM>. Processor <NUM> may also make a modification to UI <NUM> corresponding to the detected gesture input. For example, arrow <NUM> may indicate user gesturing a tap on a key in a virtual keyboard displayed by display <NUM>. Processor <NUM> may display the letter corresponding to the tapped key.

In order to return control of the content of UI <NUM> to electronic device <NUM> (e.g., including the letter added when the virtual keyboard was tapped by the user), the UI <NUM> can, for example be moved (e.g., using gesture or voice inputs to electronic device <NUM>) to the location of display <NUM>. Moving the UI <NUM> over at least a portion of display <NUM> may, for example, cause processor <NUM> to provide state information (e.g., including an indication of the newly input letter) for the content in UI to electronic device <NUM>, and cause processor <NUM> to provide instructions to electronic device <NUM> to power on display <NUM> and open or activate UI <NUM> using the provided state information. In this way, continuity of control of various applications can be provided between various components of system architecture <NUM>.

In the examples of <FIG>, when the electronic device <NUM> is detected by electronic device <NUM> with a UI <NUM> displayed on display <NUM>, a "matching" UI <NUM> (e.g., having the same size, location, orientation, and/or appearance) is generated over the display <NUM>. However, in some operational scenarios, prior to or separately from generating a "matching" UI for display with the electronic device <NUM>, the electronic device <NUM> can also act as an input device to the UI <NUM> and the associated application at electronic device <NUM>.

<FIG> illustrates an example in which electronic device <NUM> can act as an input device to the UI <NUM> and the associated application at electronic device <NUM>, while the UI <NUM> on the phone is being displayed within the view of the electronic device <NUM>. This can be useful in circumstances in which, for example, the user and/or the system determine that the processing power of electronic device <NUM> can be used to operate the application corresponding to UI <NUM>, while still allowing the user to leverage the XR environment to provide input to the UI <NUM>. For example, user can be composing an email in UI <NUM> on electronic device <NUM>, set electronic device <NUM> down on a table, put on electronic device <NUM>, and continue composing the email using a supplemental user interface <NUM> displayed by display <NUM> of the electronic device <NUM>.

In this example, the user <NUM> can provide gesture or other (e.g., voice) inputs to supplemental UI <NUM> displayed by display <NUM>. The inputs to supplemental UI <NUM> are provided (e.g., by processor <NUM> of electronic device <NUM>) to electronic device <NUM> (e.g., to one or more processors of the electronic device <NUM>) for control of the application corresponding to UI <NUM> and/or updating of the UI <NUM>. The supplemental UI <NUM> may be, for example, a reduced functionality interface relative to UI <NUM> (e.g., a virtual keypad, a virtual keypad with a text entry field in the example of an email application, or a virtual start button, virtual stop button, and virtual skip buttons for a media player application), or a UI that substantially mimics the UI <NUM> but without overlaying the UI <NUM> (in this example).

In this example, the user <NUM> can provide additional input to electronic device <NUM> (e.g., a movement of the supplemental UI <NUM>) to transfer control of the editing of the email to electronic device <NUM>. Transferring control to electronic device <NUM> may include launching a corresponding application at electronic device <NUM>, closing or deactivating the UI <NUM> on electronic device <NUM>, and upgrading the supplemental UI <NUM> to a primary UI (e.g., UI <NUM> discussed herein) for composing the email (e.g., using processor <NUM> of electronic device <NUM>).

In the examples described herein in connection with, for example, <FIG>, smooth and continuous transfer of control of applications is provided between an electronic device such as electronic device <NUM> and electronic device <NUM>, using the location, orientation, and/or display characteristics of the electronic device. In other examples, electronic device <NUM> can use the detected position, location, and/or display characteristics of a first electronic device (e.g., electronic device <NUM>) and a detected position, location, and/or other characteristics of a second electronic device (e.g., a smart speaker device <NUM>, a set-top box, or another electronic device such as electronic device <NUM>, a laptop, etc.), along with input (e.g., gesture input, voice input, eye tracking input, etc.) to the electronic device <NUM>, to transfer continuous control between the first device and the second device.

For example, <FIG> illustrates a scenario in which UI <NUM> is displayed by display <NUM>, and an input (indicated by arrow <NUM>) is provided to electronic device <NUM>, the input indicating motion from a detected location of electronic device <NUM> to or toward a detected location of smart speaker device <NUM> (e.g., or any other device such as electronic device <NUM>, handheld electronic device <NUM>, a set-top box, a desktop computer, etc.). In this example, the UI <NUM> may be a UI of a media player application that is playing a song. In this example, the user input may be a hand gesture in which the user moves their hand from a location corresponding to the location of the electronic device <NUM> to a location corresponding to the location of smart speaker device <NUM>, or may be an eye-tracking input in which electronic device <NUM> detects user <NUM> looking from the location of the electronic device <NUM> to the location of smart speaker device <NUM>. In another example, electronic device <NUM> may detect a user pinch gesture at a location associated with the location of the electronic device <NUM> and a release gesture at or near the location of the smart speaker device <NUM>. Electronic device <NUM> may detect the user input using one or more camera(s) <NUM> and/or one or more sensors <NUM> (e.g., one or more depth sensors, and/or one or more eye-tracking sensors).

Responsive to the detected input corresponding to arrow <NUM>, electronic device <NUM> may obtain state information for the UI <NUM> and the corresponding application (e.g., the name of a song and a current playback time of the song) from electronic device <NUM>, provide an indication to electronic device <NUM> to stop playback of the song by the application corresponding to UI <NUM>, provide the state information to smart speaker device <NUM>, and provide an indication to smart speaker device <NUM> to begin playback of the same song starting at the same playback time as determined by the state information. Electronic device <NUM> and/or smart speaker device <NUM> may store the song locally for playback, or may obtain the song from a remote location (e.g., from the other of electronic device <NUM> or smart speaker device <NUM>, from another electronic device in system architecture <NUM>, or from a server such as server <NUM>). In one or more implementations, the electronic device <NUM> may fade out playback of the song as the smart speaker device <NUM> synchronously fades in playback of the song. In one example implementation, electronic device <NUM> may initiate a transfer of playback of a song from electronic device <NUM> to smart speaker device <NUM> (or vice versa) by detecting an input including motion between the location of the electronic device <NUM> and the location of the smart speaker device <NUM> (or vice versa), and providing an indication to server <NUM> to discontinue streaming the song to electronic device <NUM> and to continue streaming to song playback of the song by smart speaker device <NUM>.

In some circumstances, transfer of control of an application can be transferred directly between devices such as electronic device <NUM>, electronic device <NUM>, and/or smart speaker device <NUM> based on proximity between the devices. However, using the capabilities of electronic device <NUM> to detect the locations of devices in the physical environment of the electronic device <NUM> (e.g., using camera(s) <NUM> and/or sensors <NUM>), continuous transfer of control can be provided between the devices without moving the devices, without direct input from the user to either device, and without requiring proximity between the two devices.

<FIG> illustrates a flow diagram of an example process <NUM> for continuous transfer of control between electronic devices using location information, in accordance with one or more implementations of the subject technology. For explanatory purposes, the process <NUM> is primarily described herein with reference to the electronic device <NUM> of <FIG>. However, the process <NUM> is not limited to the electronic device <NUM> of <FIG>, and one or more blocks (or operations) of the process <NUM> may be performed by one or more other components of other suitable devices, including the electronic device <NUM>, the electronic device <NUM>, and/or the servers <NUM>. Further for explanatory purposes, some of the blocks of the process <NUM> are described herein as occurring in serial, or linearly. However, multiple blocks of the process <NUM> may occur in parallel. In addition, the blocks of the process <NUM> need not be performed in the order shown and/or one or more blocks of the process <NUM> need not be performed and/or can be replaced by other operations.

As illustrated in <FIG>, at block <NUM>, a first device (e.g., electronic device <NUM>) that is configured to display a first user interface (e.g., UI <NUM>) of an application running on the first device is detected by a second device such as electronic device <NUM> (e.g., using camera(s) <NUM> and/or sensors <NUM>).

At block <NUM>, the second device detects (e.g., using camera(s) <NUM> and/or sensors <NUM>) a position and an orientation of the first device. For example, depth sensors included in sensors <NUM> can be used to determine the position and the orientation of electronic device as indicated in <FIG>).

At block <NUM>, the second device obtains a state of the first user interface of the application running on the first device. The second device can obtain the state of the first user interface by capturing images of the first user interface and/or by communicating with the first electronic device to obtain the state of the application and/or the first user interface. The state of the first user interface may include partially completed text input that has been provided to the first user interface, a color, a texture, or a theme of the user interface itself, and/or other information that describes the content and the appearance of the first user interface as currently displayed by the first device.

At block <NUM>, the second device displays, at least partially overlaid on a view of the first device and based on the detected position and orientation of the first device, a second user interface (e.g., UI <NUM>) corresponding to the application. The second user interface is displayed with the obtained state of the first user interface. Displaying the second user interface may include displaying the second user interface at least partially overlaid on a view of a display (e.g., display <NUM>) of the first device at least temporarily while the display of the first device displays the first user interface (e.g., as illustrated in <FIG>, <FIG>, and/or <NUM>).

In some implementations, the second device may track (e.g., using eye-tracking cameras and/or sensors in sensors <NUM>) a gaze direction of at least one eye of a user, and may display the second user interface responsive to a detection of the gaze direction corresponding to the detected position of the first device while the first user interface is displayed by the first device. For example, when a user <NUM> wearing electronic device <NUM> is determined, by eye tracking sensors of electronic device <NUM>, to be looking at the first user interface displayed on electronic device <NUM>, electronic device <NUM> can responsively generate the second user interface overlaid on the user's view of the first user interface.

The first user interface, the application corresponding thereto, and/or the display (e.g., display <NUM>) of the first device may be deactivated when the second device displays the second user interface, when the user interacts with the second user interface, when the second user interface is moved away from the location of the first device by the user, or after a period of time following the time when the second user interface is generated (as examples). In one example, (e.g., responsive to a user gesture input or eye tracking input) the second device may display the second user interface at a location away from the view of the first device (e.g., as illustrated in <FIG> or <FIG>), may provide an indication to the first device (e.g., electronic device <NUM>) to deactivate the application at the first device, and may activate a local copy of the application at the second device (e.g., for control of the application via the second user interface).

The second device may also receive an input to the second user interface (e.g., using camera(s) <NUM> and/or sensors <NUM> to detect a user gesture at a location corresponding to a displayed location of the UI <NUM>). The second device may also provide the received input to the application running on the first device for control of the application running on the first device (e.g., as described above in connection with <FIG> or <FIG>).

The second device may also identify a change to the first user interface, the change being responsive to a user input to the first device (e.g., as indicated in <FIG>); and update the second user interface (e.g., UI <NUM>) based on the identified change to the first user interface. The second device may include at least one camera (e.g., camera(s) <NUM>), and identifying the change to the first user interface may include identifying the change to the first user interface using the at least one camera (e.g., using an image of display <NUM> from the camera). Identifying the change to the first user interface may also, or alternatively, include identifying the change to the first user interface based on a communication received from the first device (e.g., a wireless communication from the electronic device <NUM> to electronic device <NUM>) responsive to the user input to the first user interface at the first device.

The second device may also receive a gesture input (e.g., using camera(s) <NUM> and/or sensors <NUM>) from a user to the second user interface and may provide an input based on the detected gesture input to the first device for control of the application running on the first device, in some examples.

<FIG> illustrates a flow diagram of another example process <NUM> for continuous transfer of control between electronic devices using location information, in accordance with one or more implementations of the subject technology. For explanatory purposes, the process <NUM> is primarily described herein with reference to the electronic device <NUM> of <FIG>. However, the process <NUM> is not limited to the electronic device <NUM> of <FIG>, and one or more blocks (or operations) of the process <NUM> may be performed by one or more other components of other suitable devices, including the electronic device <NUM>, the electronic device <NUM>, and/or the servers <NUM>. Further for explanatory purposes, some of the blocks of the process <NUM> are described herein as occurring in serial, or linearly. However, multiple blocks of the process <NUM> may occur in parallel. In addition, the blocks of the process <NUM> need not be performed in the order shown and/or one or more blocks of the process <NUM> need not be performed and/or can be replaced by other operations.

As illustrated in <FIG>, at block <NUM>, a first device (e.g., electronic device <NUM>, such as a smartphone, a tablet, or a head mountable device) at a first location detects a second device (e.g., electronic device <NUM>) at a second location and a third device (e.g., smart speaker device <NUM> or a set-top box) at a third location (e.g., locations in a physical environment such as physical environment <NUM> of <FIG>). In some scenarios, the second location and the third location may be spaced apart by a distance that is larger than the distance within which near-field communications between the second device and the third device can be exchanged.

At block <NUM>, the first device receives a user input (e.g., as illustrated by arrow <NUM> of <FIG>) associated with the second location and the third location (e.g., a gesture input moving from the first location to the second location, or an eye tracking movement of a gaze location from the first location to the second location).

At block <NUM>, responsive to the user input, the first device causes the third device to run a local copy of an application that is running on the second device, using a state of the application that is running on the second device. For example, as described above in connection with <FIG>, the second device may be a smart phone, the third device may be a smart speaker device, the application may be a media player application, and the state of the application may include an identifier of media (e.g., a song or a video) being played by the media player application and a playback time of the media (e.g., the current playback time at the time of the received input). In this example, causing the third device (e.g., smart speaker device <NUM>) to run the local copy of the application that is running on the second device, using the state of the application that is running on the second device, may include causing the smart phone to stop playing the media and causing the smart speaker device to begin playing the media beginning at the playback time. In this way, continuous play of the media can be transferred from one device to another device, based on a location-based input to electronic device <NUM>.

In some implementations, causing the third device to run the local copy of the application using the state of the application includes obtaining, with the first device, the state of an application running on the second device (e.g., using camera(s) <NUM> or via wireless communications between the electronic device <NUM> and the electronic device <NUM>); providing, with the first device, the state of the application running on the second device to the third device (e.g., via wireless communications between the electronic device <NUM> and the smart speaker device <NUM>); providing, with the first device, an indication to the third device to run the local copy of the application beginning with the provided state of the application (e.g., via wireless communications between the electronic device <NUM> and the smart speaker device <NUM>); and providing an indication to the second device (e.g., via wireless communications between the electronic device <NUM> and the electronic device <NUM>) to deactivate the application at the second device. Deactivating the application may include closing the application, or keeping the application open in an inactive state of the application and/or an inactive state of the device. Deactivating the application may also include deactivating the display of the second device (e.g., by operating the display in a low power mode or by powering off the display), in some implementations.

In some implementations, causing the third device to run the local copy of the application using the state of the application may include providing, with the first device, an indication to a server (e.g., server <NUM>) that is communicatively coupled to the first device, the second device, and the third device of a user instruction to transfer control of the application from the second device to the third device. For example, in one implementation, the application running on the electronic device <NUM> may be a media player application that controls streaming of media from server <NUM> to electronic device <NUM>. While the media player application is streaming a song to the electronic device <NUM> from server <NUM>, the user of electronic device <NUM> may gesture from the electronic device <NUM> toward smart speaker device <NUM>. Upon detecting this gesture, electronic device <NUM> may provide an indication to the server <NUM> to transfer the control of the streaming of the song from electronic device <NUM> to a media player application at the smart speaker device <NUM>. In this example, server <NUM> may provide instructions to electronic device <NUM> and/or smart speaker device to end and/or begin streaming of the song.

As described above, one aspect of the present technology is the gathering and use of data available from specific and legitimate sources for continuous transfer of control of applications and/or user input between electronic devices. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to identify a specific person. Such personal information data can include video data, three-dimensional geometry data, demographic data, location-based data, online identifiers, telephone numbers, email addresses, home addresses, biometric data or records relating to a user's health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other personal information.

The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used for continuous transfer of control of applications, content, and/or user input between electronic devices with an XR system.

Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of transferring content and/or control between devices, the present technology can be configured to allow users to select to "opt in" or "opt out" of participation in the collection and/or sharing of personal information data during registration for services or anytime thereafter. In addition to providing "opt in" and "opt out" options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.

De-identification may be facilitated, when appropriate, by removing identifiers, controlling the amount or specificity of data stored (e.g., collecting location data at city level rather than at an address level or at a scale that is insufficient for facial recognition), controlling how data is stored (e.g., aggregating data across users), and/or other methods such as differential privacy.

<FIG> illustrates an electronic system <NUM> with which one or more implementations of the subject technology may be implemented. The electronic system <NUM> can be, and/or can be a part of, the electronic device <NUM>, the handheld electronic device <NUM>, the electronic device <NUM>, the electronic device <NUM>, the smart speaker device <NUM>, and/or the server <NUM> as shown in <FIG>. The electronic system <NUM> may include various types of computer readable media and interfaces for various other types of computer readable media. The electronic system <NUM> includes a bus <NUM>, one or more processing unit(s) <NUM>, a system memory <NUM> (and/or buffer), a ROM <NUM>, a permanent storage device <NUM>, an input device interface <NUM>, an output device interface <NUM>, and one or more network interfaces <NUM>, or subsets and variations thereof.

In one or more implementations, the processes of the subject disclosure are stored in the system memory <NUM>, the permanent storage device <NUM>, and/or the ROM <NUM> (which are each implemented as a non-transitory computer-readable medium).

Finally, as shown in <FIG>, the bus <NUM> also couples the electronic system <NUM> to one or more networks and/or to one or more network nodes, such as the electronic device <NUM> shown in <FIG>, through the one or more network interface(s) <NUM>. In this manner, the electronic system <NUM> can be a part of a network of computers (such as a LAN, a wide area network ("WAN"), or an Intranet, or a network of networks, such as the Internet. Any or all components of the electronic system <NUM> can be used in conjunction with the subject disclosure.

These functions described above can be implemented in computer software, firmware or hardware. The techniques can be implemented using one or more computer program products. Programmable processors and computers can be included in or packaged as mobile devices. The processes and logic flows can be performed by one or more programmable processors and by one or more programmable logic circuitry. General and special purpose computing devices and storage devices can be interconnected through communication networks.

Some implementations include electronic components, such as microprocessors, storage and memory that store computer program instructions in a machine-readable or computer-readable medium (also referred to as computer-readable storage media, machine-readable media, or machine-readable storage media). Some examples of such computer-readable media include RAM, ROM, read-only compact discs (CD-ROM), recordable compact discs (CD-R), rewritable compact discs (CD-RW), read-only digital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), a variety of recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.), magnetic and/or solid state hard drives, read-only and recordable Blu-Ray® discs, ultra density optical discs, any other optical or magnetic media, and floppy disks. The computer-readable media can store a computer program that is executable by at least one processing unit and includes sets of instructions for performing various operations. Examples of computer programs or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter.

While the above discussion primarily refers to microprocessor or multi-core processors that execute software, some implementations are performed by one or more integrated circuits, such as application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs). In some implementations, such integrated circuits execute instructions that are stored on the circuit itself.

To provide for interaction with a user, implementations of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; e.g., feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; e.g., by sending web pages to a web browser on a user's client device in response to requests received from the web browser.

A client and server are generally remote from each other and may interact through a communication network.

In accordance with aspects of the disclosure, method is provided according to claim <NUM>.

In accordance with aspects of the disclosure, a system is provided according to claim <NUM>.

The described functionality may be implemented in varying ways for each particular application.

It is understood that the specific order or hierarchy of steps in the processes disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged. Some of the steps may be performed simultaneously. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description provides various examples of the subject technology, and the subject technology is not limited to these examples. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more. Headings and subheadings, if any, are used for convenience only and do not limit the invention described herein.

The term website, as used herein, may include any aspect of a website, including one or more web pages, one or more servers used to host or store web related content, etc. Accordingly, the term website may be used interchangeably with the terms web page and server. For example, a processor configured to monitor and control an operation or a component may also mean the processor being programmed to monitor and control the operation or the processor being operable to monitor and control the operation.

The term automatic, as used herein, may include performance by a computer or machine without user intervention; for example, by instructions responsive to a predicate action by the computer or machine or other initiation mechanism. The word "example" is used herein to mean "serving as an example or illustration. " Any aspect or design described herein as "example" is not necessarily to be construed as preferred or advantageous over other aspects or designs.

Claim 1:
A method, comprising:
detecting, by a second device (<NUM>), an application running on a first device (<NUM>), the application displaying a first user interface (<NUM>);
detecting, with the second device (<NUM>), a position and an orientation of the first device (<NUM>);
obtaining, with the second device (<NUM>), a state of the first user interface (<NUM>) of the application running on the first device (<NUM>), wherein the state includes content previously input to the first device;
responsive to detecting the application, activating a local version of the detected application at the second device (<NUM>);
providing an indication to the first device (<NUM>) to close the detected application at the first device (<NUM>) and to transfer control of the application to the local version of the application displayed at the second device (<NUM>); and
displaying, with the second device (<NUM>) and at least partially overlaid on a view of the first device (<NUM>) and based on the detected position and orientation of the first device (<NUM>), a second user interface (<NUM>) corresponding to the local version of the application,
wherein the second user interface (<NUM>) of the local version of the application is displayed having a state that continues from the obtained state of the first user interface (<NUM>).