Augmented reality experience using dual camera devices

Abstract

Methods and systems for generating an AR experience on a messaging platform are disclosed. These methods and systems perform operations including: detecting a real-world object depicted in a first image captured by a first camera of a client device, the client device including a second camera; extracting one or more textures from the real-world object depicted in the first image; selecting a target object depicted in a second image captured by a second imaging device, the second image being captured by the second imaging device while the first image is captured by the first imaging device; generating an augmented reality (AR) element comprising a target object modified based on one or more textures extracted from the real-world object depicted in the first image; and causing the AR element to be displayed within the second image.

Description

[0001] Priority claim

[0002] This application claims the benefit of priority to U.S. Provisional Application Serial No. 63 / 334,866 filed on April 26, 2022 and U.S. Patent Application Serial No. 17 / 662,745 filed on May 10, 2022, each of which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure generally relates to generating augmented reality (AR) experiences on messaging applications. Background Art

[0004] Augmented reality (AR) is a modification of a virtual environment. For example, in virtual reality (VR), the user is completely immersed in a virtual world, while in AR, the user is immersed in a world that combines virtual objects with the real world or superimposes virtual objects on the real world. AR systems are designed to generate and present virtual objects that realistically interact with the real world environment and with each other. Examples of AR applications can include single-player or multi-player video games, instant messaging systems, etc. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] In the drawings, which are not necessarily drawn to scale, similar reference numerals may describe similar components in different views. To easily identify the discussion of any particular element or action, the most significant digit or digits in the reference numeral refer to the figure number in which the element is first introduced. Some non-limiting examples are shown in the figures of the accompanying drawings, in which:

[0006] Figure 1 is a diagrammatic representation of a networking environment in which the present disclosure may be deployed, according to some examples.

[0007] Figure 2 is a diagrammatic representation of a messaging client application according to some examples.

[0008] Figure 3 is a diagrammatic representation of data structures as maintained in a database according to some examples.

[0009] Figure 4 is a graphical representation of messages according to some examples.

[0010] Figure 5 is a block diagram illustrating an example multi-camera AR experience system according to some examples.

[0011] Figure 6 , Figure 7 , Fig. 8A , Figure 8B and Figure 8C is a diagrammatic representation of the output of a multi-camera AR experience system according to some examples.

[0012] Fig. 9A and Fig. 9B is a flow chart illustrating example operations of a multi-camera AR experience system according to some examples.

[0013] Fig.10 is a diagrammatic representation of a machine in the form of a computer system according to some examples within which a set of instructions may be executed for causing the machine to perform any one or more of the methodologies discussed herein.

[0014] Fig.11 is a block diagram illustrating a software architecture in which examples may be implemented. DETAILED DESCRIPTION

[0015] The following description includes systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative examples of the present disclosure. In the following description, for the purpose of illustration, many specific details are set forth to provide an understanding of various examples. However, it will be apparent to those skilled in the art that examples may be practiced without these specific details. Typically, known instruction instances, protocols, structures, and techniques are not necessarily shown in detail.

[0016] Messaging applications typically enable end users to access various AR experiences by launching an AR experience bundle or package that includes AR content associated with the AR experience. These AR experiences typically present AR elements that can be modified by the user in some way so that images captured by a single camera can be modified to include AR elements. Sometimes, these AR experiences are accessed by devices that include multiple cameras such as a front camera and a rear camera. This enables the user to switch the camera used as the source of the image being modified. To do this, the user can select a switch option that activates the front camera instead of the rear camera when the rear camera is used as the source of the image being modified, and vice versa.

[0017] The activation of these cameras typically takes some time (on the order of a few seconds), which can cause the user to experience some delay when switching cameras. For example, if the user is modifying an image captured by the rear camera and selects the swap option, a blank screen may be temporarily presented (or the screen may freeze) while the rear camera is deactivated and the front camera is activated to obtain the image. Such delays introduce lag and can ruin the overall enjoyment of accessing the AR experience and can waste system resources. Even worse, if video is being recorded while the cameras are swapping, gaps may be introduced in the recorded video, which can reduce the overall quality of the content being produced.

[0018] Furthermore, because typical systems operate the AR experience with only a single camera at a time, valuable opportunities to capture content from both cameras may be missed. For example, an AR experience may allow a user to modify an image captured by the rear camera, but the user's reaction (which may be detected by the front camera) is a valuable missed opportunity. Furthermore, limiting the AR experience to being generated using one primary camera at a time prevents the AR experience from being improved based on information that could be collected by another camera that is not being used. For example, another camera may provide valuable information about lighting conditions, which may improve the quality of the video or images captured by the primary camera. The lack of use of this information also results in the production of poor quality video, which results in missed opportunities and wasted resources.

[0019] The disclosed technology solves these technical problems by enabling developers to create AR experiences that can use images or content captured by multiple cameras (e.g., a front camera and a rear camera) at the same time. For example, an AR development platform can be provided that presents a user interface to an AR experience developer so that the AR developer can activate an option for causing simultaneous activation of multiple cameras (e.g., cameras pointing in opposite directions). The user interface can also enable the developer to specify conditions that need to be met in order to allow such multi-camera activation. This provides developers with a greater amount of flexibility to create useful, interesting, and engaging AR experiences without being limited by the resource constraints of the messaging application and / or client device running the AR experience.

[0020] In some examples, the disclosed technology detects a real-world object depicted in a first image captured by a first camera of a client device, and extracts one or more textures from the real-world object depicted in the first image. The disclosed technology selects a target object depicted in a second image captured by a second camera of the client device. The second image may be captured by the second camera at the same time as the first image is captured by the first camera. The disclosed technology generates an AR element and causes the AR element to be displayed within the second image, the AR element including the target object modified based on one or more textures extracted from the real-world object depicted in the first image. This improves the overall user experience and reduces the amount of resources consumed by the AR experience.

[0021] For example, the disclosed technology may allow a user to select a configuration or layout of which of the first camera and the second camera is used as the primary camera and which camera is used as the secondary camera. Specifically, a first video stream is captured using the first camera of the client device, and a second video stream is captured using the second camera of the client device. AR output is generated by using the first video stream as a primary input to a first AR experience bundle and using the second video stream as a secondary input to the first AR experience bundle. A presentation of the AR output is provided on the client device.

[0022] In some embodiments, the disclosed technology can use information obtained or extracted from the image of the primary camera to perform modifications to the image captured and presented by the secondary camera. In this way, the user is provided with the flexibility to apply textures or attributes from the primary camera to the real-world environment depicted in the image captured by the secondary camera. In some examples, textures or AR elements can be added to the image captured by each camera simultaneously. As referred to herein, the term "texture" includes visual attributes, colors, features, and style of at least a portion of an underlying image or video.

[0023] In some examples, the disclosed technology provides a seamless and fast way to switch, flip or toggle primary / secondary images captured and received by a primary camera and a secondary camera. Since the two cameras are activated simultaneously, the display presented to the user can quickly swap (modify its configuration) images from the two cameras with minimal or no delay. This results in an improved way of generating content. In some examples, the disclosed technology can obtain lighting information from the secondary camera to modify the display properties of the image obtained and captured by the primary camera, and vice versa. This also results in images or videos with improved quality, where the lighting of the space is automatically determined and adjusted in the captured images or videos.

[0024] In some examples, swapping cameras (e.g., modifying the configuration of the cameras) results only in modifying the display position at which the primary / secondary images from the cameras are presented on the display of the device. In some examples, swapping cameras (e.g., modifying the configuration of the cameras) results only in changing which camera is designated as the primary camera and which camera is designated as the secondary camera. The result of swapping the primary / secondary camera designations (e.g., modifying the configuration of the cameras) results in changes in which image is used to provide textures and attributes to modify objects depicted in the target image or which image is used as input for each applied texture. In some examples, swapping cameras (e.g., modifying the configuration of the cameras) results in modifying both the display position and changing the primary / secondary camera designations. Thus, end users are provided with greater flexibility in creating AR content that can be shared with other users.

[0025] Networked computing environment

[0026] Figure 1 1 is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of a client device 102, each of which hosts several applications, including a messaging client 104 and other external applications 109 (e.g., third-party applications). Each messaging client 104 is communicatively coupled to other instances of the messaging client 104 (e.g., hosted on corresponding other client devices 102), a messaging server system 108, and an external application server 110 via a network 112 (e.g., the Internet). The messaging client 104 may also communicate with locally hosted third-party applications (e.g., external applications 109) using an application program interface (API).

[0027] The client device 102 can operate as a stand-alone device, or can be coupled (e.g., networked) to other machines. In a networked deployment, the client device 102 can operate with the capabilities of a server machine or a client machine in a server-client network environment, or operate as a peer machine in a peer-to-peer (or distributed) network environment. The client device 102 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, web devices, network routers, network switches, network bridges, or any machine capable of performing the disclosed operations. In addition, although only a single client device 102 is shown, the term "client device" should also be considered to include a collection of machines that perform the disclosed operations individually or jointly.

[0028] In some examples, client device 102 may include AR glasses or an AR head-mounted device, wherein virtual content is displayed within the lenses of the glasses while the user views the real world environment through the lenses. For example, an image may be presented on a transparent display that allows the user to simultaneously view the content presented on the display and real-world objects.

[0029] In some examples, the client device 102 includes a first camera 103 and a second camera 105. The first camera 103 may include one or more cameras embedded in or included on a display portion of the client device 102. The display portion of the client device 102 may include a touch screen display or other display screen that presents content to the user. In some cases, the first camera 103 is referred to as a self-viewing camera because it generally faces the user. The second camera 105 may include one or more cameras embedded in or included on a side of the client device 102 opposite to the first camera 103. The opposite side may be the back side of the client device 102. In some cases, the back side of the client device 102 includes a display screen, while in other cases, the back side of the client device 102 does not include a display screen. The second camera 104 may be referred to as a world camera because the camera generally faces the user's real-world environment.

[0030] In some examples, the client device 102 may be operated by an AR experience developer. In this case, the AR experience developer (or AR developer) accesses an AR experience development platform. The AR experience development platform allows AR developers to generate an AR experience bundle that includes a set of AR elements. The AR developer may select one or more options for enabling simultaneous activation of both the first camera 103 and the second camera 105 of the end user's client device 102. As part of enabling simultaneous activation of both the first camera 103 and the second camera 105 (or multiple cameras), the AR developer may specify parameters for the AR experience. These parameters may include the layout of images or videos obtained from multiple cameras at the same time. Alternatively, throughout the specification, the term layout is referred to as a configuration. The layout may specify the display position of an image or video, such as an image obtained from the first camera 103 is displayed on the top of the display screen, while an image obtained from the second camera 105 is displayed on the bottom of the display. The layout may specify that the image obtained from the first camera 103 is displayed on the left portion of the display screen and the image obtained from the second camera 105 is displayed on the right portion of the display screen. The layout may specify that the image obtained from the first camera 103 is to be displayed in full screen, and that the image obtained from the second camera 105 is to be displayed within or on top of the full screen of the first camera 103 image. The layout may specify that the image obtained from the first camera 103 is to be used as a green screen basis for one or more objects obtained from the image from the second camera 105 to form a single image or video. The layout may specify a face builder layout in which cutouts of facial elements depicted in the image obtained from the first camera 103 are superimposed on top of the image obtained from the second camera 105.

[0031] The parameters may include an indication of which of the multiple camera images is used as a source image and which is used as a target image for providing an AR experience. For example, an AR developer may specify a parameter indicating the type of real-world object in a target image that will be modified using one or more textures extracted from a real-world object depicted in a source image. In this case, the AR experience may detect an object, such as a face, in an image captured by the first camera 103. The AR experience may extract one or more textures (e.g., textures of eyes and mouth) from the face. The AR experience may detect a real-world object in a target image captured by the second camera 105. The AR experience may generate an AR element using features of the real-world object and one or more textures extracted from the face. The AR element may visually represent the face as included in the real-world object in the target image, and display the target image including the AR element to the end user. That is, the AR element may replace or overlay the real-world object depicted in the target image. As facial features change (e.g., lips move) in subsequent images captured by the first camera 103, the AR experience continuously updates the AR element to continuously modify the target image captured by the second camera 105. This makes it appear to the user as if the user's face is embedded in the real-world object of the target image captured by the second camera 105 .

[0032] In some examples, an AR developer may specify a parameter indicating that the type of AR object in a target image (e.g., a 2D or 3D avatar displayed within a real-world environment) is modified using one or more textures extracted from a real-world object depicted in a source image. In this case, the AR experience may detect an object in an image captured by the first camera 103, such as a user's body. The AR experience may extract one or more textures (e.g., arm position, torso position, body posture, facial features, etc.) from the user's body. The AR experience may recognize or generate a display of an AR object in a real-world environment depicted in a target image captured by the second camera 105. The AR experience may generate an AR element using features of the AR object and one or more textures extracted from the user's body. The AR experience may modify features of the AR object (e.g., an avatar) to match textures extracted from the user's body, such as arm position, torso position, body posture, facial features, etc. The AR experience may then present a display of the modified AR object in the image captured by the second camera 105. As features change in subsequent images captured by the first camera 103, the AR experience continuously updates the AR elements to continuously modify the target image captured by the second camera 105. This makes it appear to the user that the user's body is reflected by the AR objects in the real-world environment depicted in the target image captured by the second camera 105.

[0033] An AR experience developed by an AR developer may be launched on the end-user client device 102, for example, in response to receiving a user selection of an option to simultaneously activate both the first camera 103 and the second camera 105. In some examples, the option is represented as a camera icon with a forward arrow and a backward arrow. The AR experience launched by the client device 102 may detect a real-world object depicted in a first image captured by the first camera 103. The client device 102 may extract one or more textures from the real-world object depicted in the first image, and select a target object depicted in a second image captured by the second camera 105. The second image is captured by the second camera 105 at the same time as the first image is captured by the first camera 103. The client device 102 may: generate an AR element including a target object modified based on one or more textures extracted from the real-world object depicted in the first image; and display the AR element, in some cases together with the first image, in the second image.

[0034] The messaging clients 104 are able to communicate and exchange data with other messaging clients 104 and messaging server systems 108 via the network 112. The data exchanged between the messaging clients 104 and between the messaging clients 104 and messaging server systems 108 include functions (e.g., commands to activate functions) and payload data (e.g., text, audio, video, or other multimedia data).

[0035] The messaging server system 108 provides server-side functionality to specific messaging clients 104 via the network 112. Although certain functions of the messaging system 100 are described herein as being performed by the messaging client 104 or by the messaging server system 108, the location of certain functions within the messaging client 104 or within the messaging server system 108 may be a design choice. For example, it may be technically preferable to initially deploy certain technologies and functions within the messaging server system 108, but later migrate the technologies and functions to the messaging client 104 where the client device 102 has sufficient processing power.

[0036] The messaging server system 108 supports various services and operations provided to the messaging clients 104. Such operations include sending data to the messaging clients 104, receiving data from the messaging clients 104, and processing data generated by the messaging clients 104. As examples, the data may include message content, client device information, geographic location information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. The exchange of data within the messaging system 100 is activated and controlled by functions available via the user interface (UI) of the messaging client 104.

[0037] Turning now specifically to the messaging server system 108, an application program interface (API) server 116 is coupled to and provides a programming interface to the application server 114. The application server 114 is communicatively coupled to a database server 120, which facilitates access to a database 126 that stores data associated with messages processed by the application server 114. Similarly, a web server 128 is coupled to the application server 114 and provides a web-based interface to the application server 114. To this end, the web server 128 processes incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0038] The API server 116 receives and sends message data (e.g., commands and message payloads) between the client device 102 and the application server 114. Specifically, the API server 116 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client 104 to activate the functionality of the application server 114. The API server 116 exposes various functions supported by the application server 114, including: account registration; login functionality; sending messages from a particular messaging client 104 to another messaging client 104 via the application server 114; sending media files (e.g., images or videos) from the messaging client 104 to the messaging server 118 and for possible access by another messaging client 104; setting up a collection of media data (e.g., a story); retrieving a list of friends of the user of the client device 102; retrieving such a collection; retrieving messages and content; adding and removing entities (e.g., friends) from an entity graph (e.g., a social graph); locating friends within a social graph; and opening application events (e.g., related to the messaging client 104).

[0039] The application server 114 hosts several server applications and subsystems, including, for example, a messaging server 118, an image processing server 122, and a social network server 124. The messaging server 118 implements several message processing technologies and functions, particularly those related to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the messaging client 104. As will be described in further detail, text and media content from multiple sources can be aggregated into collections of content (e.g., called stories or galleries). These collections are then made available to the messaging client 104. In view of the hardware requirements of other processor- and memory-intensive data processing, such processing can also be performed on the server side by the messaging server 118.

[0040] The application server 114 also includes an image processing server 122 that is dedicated to performing various image processing operations, typically with respect to images or videos within the payload of messages sent from or received at the messaging server 118 .

[0041] The image processing server 122 is used to implement the enhancement system 208 ( Figure 2 ). The scanning functionality includes activating and providing one or more augmented reality experiences on the client device 102 when an image is captured by the client device 102. Specifically, the messaging application 104 on the client device 102 can be used to activate the camera. The camera displays one or more real-time images or videos to the user along with one or more icons or identifiers of one or more augmented reality experiences. The user can select a given one of the identifiers to launch the corresponding augmented reality experience or perform a desired image modification (e.g., replace or recolor a garment worn by a user in the video or modify the garment based on a gesture performed by the user).

[0042] The social network server 124 supports various social networking functions and services and makes them available to the messaging server 118. To this end, the social network server 124 maintains and accesses an entity graph 308 (e.g., Figure 3 ). Examples of functions and services supported by the social networking server 124 include identifying other users of the messaging system 100 that have a relationship with a particular user or that the particular user is "following," and also identifying interests and other entities of a particular user.

[0043] Returning to the messaging client 104, the features and functions of the external resource (e.g., a third-party application 109 or an applet) are available to the user via the interface of the messaging client 104. The messaging client 104 receives a user selection of an option for launching or accessing features of an external resource (e.g., a third-party resource) such as an external application 109. The external resource can be a third-party application (external application 109) installed on the client device 102 (e.g., a "native application"), or a small-scale version of a third-party application (e.g., a "mini-program") hosted on the client device 102 or remote from the client device 102 (e.g., on a third-party server 110). The small-scale version of the third-party application includes a subset of the features and functions of the third-party application (e.g., a full-scale native version of a third-party standalone application) and is implemented using a markup language document. In one example, the small-scale version of the third-party application (e.g., a "mini-program") is a web-based markup language version of the third-party application and is embedded in the messaging client 104. In addition to using markup language documents (eg, *ml files), applets may include scripting languages ​​(eg, .*js files or .json files) and style sheets (eg, *ss files).

[0044] In response to receiving a user selection of an option for launching or accessing a feature of an external resource (external application 109), the messaging client 104 determines whether the selected external resource is a web-based external resource or a locally installed external application. In some cases, the external application 109 locally installed on the client device 102 can be launched independently of the messaging client 104 and separately from the messaging client 104, for example, by selecting an icon corresponding to the external application 109 on the home screen of the client device 102. A small-scale version of such an external application can be launched or accessed via the messaging client 104, and in some examples, no part of the small-scale external application can be (or a limited part can be) accessed outside the messaging client 104. The small-scale external application can be launched by the messaging client 104 receiving a markup language document associated with the small-scale external application from the external application server 110 and processing such a document.

[0045] In response to determining that the external resource is a locally installed external application 109, the messaging client 104 instructs the client device 102 to launch the external application 109 by executing the locally stored code corresponding to the external application 109. In response to determining that the external resource is a web-based resource, the messaging client 104 communicates with the external application server 110 to obtain a markup language document corresponding to the selected resource. The messaging client 104 then processes the obtained markup language document to present the web-based external resource within the user interface of the messaging client 104.

[0046] The messaging client 104 may notify the user of the client device 102 or other users (e.g., "friends") associated with such a user of activities occurring in one or more external resources. For example, the messaging client 104 may provide a participant in a conversation (e.g., a chat session) in the messaging client 104 with a notification related to the current or recent use of an external resource by one or more members of a user group. One or more users may be invited to join an active external resource or to start an external resource that was recently used but is currently inactive (in a friend group). The external resource may provide the participants in the conversation (each participant using a corresponding messaging client 104) with the ability to share items, conditions, states, or locations in the external resource with one or more members of a user group in the chat session. The shared item may be an interactive chat card that members of the chat may interact with, for example, to start a corresponding external resource, view specific information within an external resource, or bring members of the chat to a specific location or state within an external resource. Within a given external resource, a response message may be sent to a user on the messaging client 104. The external resource may selectively include different media items in the response based on the current context of the external resource.

[0047] The messaging client 104 may present a list of available external resources (e.g., third-party or external applications 109 or applets) to the user to launch or access a given external resource. The list may be presented in a context-sensitive menu. For example, icons representing different external applications in the external applications 109 (or applets) may vary based on how the user launches the menu (e.g., from a conversational interface or from a non-conversational interface).

[0048] The messaging client 104 may allow a user to simultaneously activate the first camera 103 and the second camera 105 of the client device 102. The messaging client 104 may present an option for simultaneously activating the first camera 103 and the second camera 105. In response to receiving a selection of the option, the messaging client 104 may present a list of different layouts as separate options. The different layouts may include an option for activating a horizontal layout in which a first image obtained from the first camera 103 is displayed at the top of the screen and a second image obtained from the second camera 105 is displayed at the bottom of the screen. The different layouts may include an option for activating a vertical layout in which a first image is displayed on a left portion of the screen and a second image is displayed on a right portion of the screen. The different layouts may include an option for activating a picture-in-picture (PIP) layout in which the first image is displayed in full screen and the second image is displayed within the full screen, the PIP layout enabling the user to reposition the second image within the full screen. The different layouts may include an option to activate a green screen layout in which a portion of the first image is superimposed on a portion of the second image based on one or more object segmentation models. The different layouts may include an option to activate a face builder layout in which cutouts of facial elements depicted in the first image are superimposed on the second image.

[0049] Depending on which layout is selected, the messaging client 104 activates the first camera 103 and the second camera 105 and generates a display including an image obtained or captured by the first camera 103 and the second camera 105 or a representation derived from such an image. The messaging client 104 may receive input from a user for accessing an AR experience. In response, the messaging client 104 searches for multiple AR experiences based on a parameter indicating simultaneous activation of multiple cameras. The messaging client 104 identifies a subset of multiple AR experiences that is configured to perform AR operations using multiple cameras simultaneously. That is, the messaging client 104 identifies a subset of AR experiences associated with a parameter indicating that simultaneous activation of multiple cameras has been enabled for the corresponding AR experience. In this way, the messaging client 104 displays multiple icons representing each AR experience in the subset and excluding AR experiences that do not enable simultaneous activation of multiple cameras (e.g., the first camera 103 and the second camera 105).

[0050] In some examples, certain AR experiences are developed to utilize multiple cameras simultaneously. This allows the AR experience to automatically activate multiple cameras simultaneously without receiving a specific user request to activate multiple cameras or receiving a specific layout request from the user. That is, in response to receiving a selection from the user of an AR experience associated with multiple cameras, multiple cameras are activated simultaneously and their respective outputs are generated for display or configured according to a layout associated with a given AR experience.

[0051] The messaging client 104 may receive input from a user selecting a given AR experience using the displayed icons representing a subset of AR experiences. In response, the messaging client 104 retrieves configuration information from the given AR experience. The configuration information may specify a layout of images obtained from multiple cameras. The messaging client 104 simultaneously presents images obtained from the first camera 103 and the second camera 105 according to the layout of the configuration information. The messaging client 104 may present a prompt or message informing the user that both the first camera 103 and the second camera 105 are activated.

[0052] In some examples, the messaging client 104 presents a flip option or a swap option. In response to receiving a user selection of the flip option or the swap option, the messaging client 104 reconfigures the layout of the images obtained from the first camera 103 and the second camera 105. For example, the messaging client 104 may modify the position of the images captured by the first camera 103 and the second camera 105 within the display or the source image from which one or more textures are extracted. For example, the messaging client 104 may initially display the image captured by the first camera 103 at a first position on the display and the image captured by the second camera 105 at a second position on the display. In response to receiving a selection of the flip option or the swap option, the messaging client 104 selects a new real-world object depicted in the second image and extracts a set of textures from the new real-world object. The messaging client 104 modifies one or more objects depicted in the first image based on the set of textures extracted from the new real-world object, rather than modifying the target object in the second image. The messaging client 104 may also or in the alternative modify the position of the image so that in response to receiving a selection of the flip option or the swap option, the second image is presented in the first position and the first image is presented in the second position. As another example, the messaging client 104 may display the first image in a first position on the display and the second image in a second position on the display, and in response to receiving a selection of the flip option or the swap option, the second image may be positioned in the first position and the first image may be positioned in the second position.

[0053] In some examples, the messaging client 104 may present an AR developer interface. In this case, as discussed below, the messaging client 104 may be operated by an AR developer to develop and create one or more AR experiences. The AR developer interface enables the developer to specify whether simultaneous activation of multiple cameras is enabled for a given AR experience. The AR developer may select one or more options for enabling simultaneous activation of both the first camera 103 and the second camera 105 of the end user's client device 102 by specifying parameters for the AR experience. These parameters may include the layout of images or videos obtained from multiple cameras simultaneously.

[0054] System Architecture

[0055] Figure 2 1 is a block diagram showing additional details about the messaging system 100 according to some examples. Specifically, the messaging system 100 is shown to include a messaging client 104 and an application server 114. The messaging system 100 contains several subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a transient timer system 202, a collection management system 204, an enhancement system 208, a map system 210, a game system 212, and an external resource system 220.

[0056] The transient timer system 202 is responsible for implementing temporary or time-limited access to content by the messaging client 104 and the messaging server 118. The transient timer system 202 includes several timers that selectively enable access (e.g., for presentation and display) to messages and associated content via the messaging client 104 based on duration and display parameters associated with a message or a collection of messages (e.g., a story). Additional details regarding the operation of the transient timer system 202 are provided below.

[0057] The collection management system 204 is responsible for managing collections or collections of media (e.g., collections of text, images, video, and audio data). Collections of content (e.g., messages, including images, videos, text, and audio) can be organized into "event libraries" or "event stories." Such collections can be made available for a specified time period (e.g., the duration of an event related to the content). For example, content related to a concert can be made available as a "story" for the duration of the concert. The collection management system 204 can also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the messaging client 104.

[0058] In addition, the collection management system 204 also includes a curation interface 206, which enables collection managers to manage and curate specific content collections. For example, the curation interface 206 enables event organizers to curate collections of content related to specific events (e.g., deleting inappropriate content or redundant messages). In addition, the collection management system 204 uses machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, compensation can be paid to users for including user-generated content in a collection. In such a case, the collection management system 204 operates to automatically pay such users for using their content.

[0059] The enhancement system 208 provides various functions that enable users to enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the enhancement system 208 provides functions related to generating and publishing media overlays (media overlays) for messages processed by the messaging system 100. The enhancement system 208 is operable to provide media overlays or enhancements (e.g., image filters) to the messaging client 104 based on the geographic location of the client device 102. In another example, the enhancement system 208 is operable to provide media overlays to the messaging client 104 based on other information such as social network information of the user of the client device 102. The media overlay can include audio and visual content and visual effects. Examples of audio and visual content include pictures, text, logos, animations, and sound effects. Examples of visual effects include color overlays. Audio and visual content or visual effects can be applied to media content items (e.g., photos) at the client device 102. For example, the media overlay can include text, graphic elements, or images that can be superimposed on the top of a photo taken by the client device 102. In another example, the media overlay includes a location identification overlay (e.g., Venice Beach), the name of a live event, or a business name overlay (e.g., Beach Cafe). In another example, the augmentation system 208 uses the geographic location of the client device 102 to identify a media overlay that includes the name of a business at the geographic location of the client device 102. The media overlay may include other logos associated with the business. The media overlay may be stored in the database 126 and accessed through the database server 120.

[0060] In some examples, the enhancement system 208 provides a user-based publishing platform that enables a user to select a geographic location on a map and upload content associated with the selected geographic location. The user can also specify situations in which a particular media overlay should be provided to other users. The enhancement system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geographic location.

[0061] In other examples, the augmentation system 208 provides a merchant-based publishing platform that enables merchants to select specific media overlays associated with a geographic location via a bidding process. For example, the augmentation system 208 associates the media overlay of the highest bidding merchant with the corresponding geographic location for a predefined amount of time. The augmentation system 208 communicates with the image processing server 122 to obtain an augmented reality experience, and presents an identifier of such an experience in one or more user interfaces (e.g., as an icon on a real-time image or video, or as a thumbnail or icon in an interface dedicated to the identifier of the augmented reality experience presented). Once the augmented reality experience is selected, one or more images, videos, or augmented reality graphical elements are retrieved and presented as an overlay on the image or video captured by the client device 102. In some cases, the camera is switched to a front view (e.g., the front camera of the client device 102 is activated in response to the activation of a particular augmented reality experience), and an image from the front camera of the client device 102, rather than the rear camera of the client device 102, begins to be displayed on the client device 102. One or more images, videos, or augmented reality graphical elements are retrieved and presented as an overlay on top of the image captured and displayed by the front-facing camera of the client device 102 .

[0062] In other examples, the augmentation system 208 can communicate and exchange data with another augmentation system 208 on another client device 102 and with a server via the network 112. For example, the data exchanged during a video call between multiple users or participants may include: a session identifier identifying a shared AR session; a transformation between a first client device 102 and a second client device 102 (e.g., the multiple client devices 102 include the first device and the second device), the transformation used to align the shared AR session to a common origin; a common coordinate system; functionality (e.g., commands for activating functions) and other payload data (e.g., text, audio, video, or other multimedia data).

[0063] The augmentation system 208 sends the transformation to the second client device 102 so that the second client device 102 can adjust the AR coordinate system based on the transformation. In this way, the first client device 102 and the second client device 102 synchronize their coordinate systems and frames to display the content in the AR session. Specifically, the augmentation system 208 calculates the origin of the second client device 102 in the coordinate system of the first client device 102. The augmentation system 208 can then determine an offset in the coordinate system of the second client device 102 based on the position of the origin in the coordinate system of the second client device 102 from the perspective of the second client device 102. The transformation is generated using the offset so that the second client device 102 generates AR content according to a common coordinate system with the first client device 102.

[0064] The augmentation system 208 can communicate with the client device 102 to establish an individual or shared AR session. The augmentation system 208 can also be coupled to the messaging server 118 to establish an electronic group communication session (e.g., group chat, instant messaging, video call, group video call, etc.) for the client device 102 in the shared AR session. The electronic group communication session can be associated with a session identifier provided by the client device 102 to obtain access to the electronic group communication session and the shared AR / VR session. In one example, the client device 102 first obtains access to the electronic group communication session, and then obtains a session identifier in the electronic group communication session that allows the client device 102 to access the shared AR / VR session. In some examples, the client device 102 is able to access the shared AR / VR session without the assistance of the augmentation system 208 in the application server 114 or communication with the augmentation system 208 in the application server 114.

[0065] The mapping system 210 provides various geo-location functions and supports presentation of map-based media content and messages by the messaging client 104. For example, the mapping system 210 enables display of (e.g., stored in Figure 3The user icons or avatar representations (in the profile data 316 shown) are provided to indicate the current or past locations of the user's "friends", as well as media content (e.g., a collection of messages including photos and videos) generated by such friends within the context of the map. For example, messages posted by the user to the messaging system 100 from a particular geographic location can be displayed to the particular user's "friends" on the map interface of the messaging client 104 within the context of that particular location on the map. The user can also share his or her location and status information with other users of the messaging system 100 (e.g., using appropriate status avatars) via the messaging client 104, where the location and status information is similarly displayed to selected users within the context of the map interface of the messaging client 104.

[0066] The gaming system 212 provides various gaming functions within the context of the messaging client 104. The messaging client 104 provides a gaming interface that provides a list of available games (e.g., web-based games or web-based applications) that can be launched by a user within the context of the messaging client 104 and played with other users of the messaging system 100. The messaging system 100 also enables a particular user to invite other users to participate in playing a particular game by sending an invitation to such other users from the messaging client 104. The messaging client 104 also supports both voice and text messaging (e.g., chat) within the context of gaming, provides leaderboards for gaming, and supports providing in-game rewards (e.g., gaming coins and items).

[0067] The external resource system 220 provides the messaging client 104 with an interface for communicating with the external application server 110 to launch or access external resources. Each external resource (application) server 110 hosts, for example, a small-scale version of an application based on a markup language (e.g., HTML5) or an external application (e.g., a game, utility, payment, or ride-sharing application outside the messaging client 104). The messaging client 104 can launch the web-based resource by accessing an HTML5 file from an external resource (application) server 110 associated with a web-based resource (e.g., application). In some examples, the application hosted by the external resource server 110 is programmed in JavaScript using a software development kit (SDK) provided by the messaging server 118. The SDK includes an application programming interface (API) with functions that can be called or activated by a web-based application. In some examples, the messaging server 118 includes a JavaScript library that provides access to certain user data of the messaging client 104 to a given third-party resource. HTML5 is used as an example technology for programming games, but applications and resources programmed based on other technologies can be used.

[0068] In order to integrate the functionality of the SDK into the web-based resource, the SDK is downloaded from the messaging server 118 by the external resource (application) server 110 or received by the external resource (application) server 110 in other ways. Once downloaded or received, the SDK will be included as part of the application code of the web-based external resource. The code of the web-based resource can then call or activate certain functions of the SDK to integrate the features of the messaging client 104 into the web-based resource.

[0069] The SDK stored on the messaging server 118 effectively provides a bridge between external resources (e.g., a third party or external application 109 or applet and the messaging client 104). This provides users with a seamless experience of communicating with other users on the messaging client 104 while retaining the look and feel of the messaging client 104. In order to bridge the communication between the external resources and the messaging client 104, in some examples, the SDK facilitates the communication between the external resource server 110 and the messaging client 104. In some examples, the WebViewJavaScriptBridge running on the client device 102 establishes two one-way communication channels between the external resources and the messaging client 104. Messages are sent asynchronously via these communication channels between the external resources and the messaging client 104. Each SDK function call is sent as a message and a callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with the callback identifier.

[0070] By using the SDK, not all information from the messaging client 104 is shared with the external resource server 110. The SDK limits which information is shared based on the needs of the external resource. In some examples, each external resource server 110 provides an HTML5 file corresponding to a web-based external resource to the messaging server 118. The messaging server 118 can add a visual representation (e.g., box art or other graphics) of the web-based external resource in the messaging client 104. Once the user selects the visual representation or instructs the messaging client 104 to access the features of the web-based external resource through the GUI of the messaging client 104, the messaging client 104 obtains the HTML5 file and instantiates the resources required to access the features of the web-based external resource.

[0071] The messaging client 104 presents a graphical user interface (e.g., a login page or title screen) for the external resource. During, before, or after presenting the login page or title screen, the messaging client 104 determines whether the launched external resource has been previously authorized to access the user data of the messaging client 104. In response to determining that the launched external resource has been previously authorized to access the user data of the messaging client 104, the messaging client 104 presents another graphical user interface of the external resource including the functions and features of the external resource. In response to determining that the launched external resource has not been previously authorized to access the user data of the messaging client 104, after a threshold time period (e.g., 3 seconds) of displaying the login page or title screen of the external resource, the messaging client 104 slides up a menu for authorizing the external resource to access the user data (e.g., animating the menu to emerge from the bottom of the screen to the middle or other portion of the screen). The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving the user selection of the accept option, the messaging client 104 adds the external resource to the list of authorized external resources and enables the external resource to access the user data from the messaging client 104. In some examples, the messaging client 104 authorizes the external resource to access the user data according to the OAuth 2 framework.

[0072] The messaging client 104 controls the type of user data shared with the external resource based on the type of external resource that is authorized. For example, access to a first type of user data (e.g., only a two-dimensional (2D) avatar of a user with or without different avatar features) is provided to an external resource including a full-scale external application (e.g., a third party or external application 109). As another example, access to a second type of user data (e.g., payment information, a two-dimensional avatar of a user, a three-dimensional avatar of a user, and an avatar with various avatar features) is provided to an external resource including a small-scale version of an external application (e.g., a web-based version of a third-party application). Avatar features include different ways to customize the look and feel of an avatar (e.g., different poses, facial features, clothing, etc.).

[0073] The multi-camera AR experience system 224 may allow a user to access an AR experience with simultaneous activation of multiple cameras enabled, and / or select an option for simultaneously and independently activating the first camera 103 and the second camera 105 of the client device 102. In response to receiving a selection of an option and / or an AR experience, the multi-camera AR experience system 224 may present a list of different layouts as separate options. The multi-camera AR experience system 224 generates a display including images obtained or captured by the first camera 103 and the second camera 105 or representations derived from the images. The multi-camera AR experience system 224 retrieves configuration information from a given AR experience and presents images obtained simultaneously from the first camera 103 and the second camera 105 according to the layout of the configuration information. The multi-camera AR experience system 224 may present a prompt or message informing the user that both the first camera 103 and the second camera 105 are activated. The multi-camera AR experience system 224 may present a flip or swap option for changing the layout or configuration of the images obtained from the first camera 103 and the second camera 105 instantly and without delay.

[0074] The multi-camera AR experience system 224 can allow AR developers to create AR experiences that use multiple cameras simultaneously, and the AR experience has AR elements or assets. AR elements can include any combination of 3D mesh objects, two-dimensional (2D) meshes, machine learning models, graphical elements, avatars, sounds, or videos. The multi-camera AR experience system 224 can present a user interface for the AR developer platform. The user interface can be used to select whether to enable simultaneous activation of multiple cameras for a given AR experience, and to specify one or more parameters including a layout for the simultaneous activation of such multiple cameras. The graphical user interface presents a list of AR experiences and includes a first option associated with a first AR experience for enabling simultaneous activation of multiple cameras for the first AR experience. The graphical user interface may include options for specifying one or more parameters for the simultaneous activation of multiple cameras for the first AR experience.

[0075] This provides developers with a greater amount of flexibility to create useful, interesting, and engaging AR experiences without being limited by the resource constraints of the messaging application and / or client device running the AR experience.

[0076] Data Architecture

[0077] Figure 3is a diagram illustrating a data structure 300 that may be stored in a database 126 of a messaging server system 108 according to some examples. Although the contents of the database 126 are illustrated as including several tables, it should be understood that data may be stored in other types of data structures (e.g., in an object-oriented database).

[0078] Database 126 includes message data stored in message table 302. For any particular message, the message data includes at least message sender data, message recipient (or receiver) data, and payload. Figure 4 Additional details regarding information that may be included in a message and included within the message data stored in message table 302 are described.

[0079] The entity table 306 stores entity data and is linked (e.g., by reference) to the entity graph 308 and profile data 316. The entities for which records are maintained within the entity table 306 may include individuals, corporate entities, organizations, objects, places, events, etc. Regardless of the entity type, any entity for which the messaging server system 108 stores data may be an identified entity. Each entity is provided with a unique identifier as well as an entity type identifier (not shown).

[0080] The entity graph 308 stores information about relationships and associations between entities. Such relationships may be social, professional (e.g., working in a common company or organization), interest-based, or activity-based, by way of example only.

[0081] Profile data 316 stores multiple types of profile data about a particular entity. Based on the privacy settings specified by the particular entity, profile data 316 can be selectively used and presented to other users of the messaging system 100. In the case where the entity is a person, profile data 316 includes, for example, a user name, phone number, address, settings (e.g., notification and privacy settings), and an avatar representation (or a collection of such avatar representations) selected by the user. The particular user can then selectively include one or more of these avatar representations within the content of messages transmitted via the messaging system 100 and on a map interface displayed to other users by the messaging client 104. The collection of avatar representations can include a "status avatar" that presents a graphical representation of a status or activity that a user can select to convey at a particular time.

[0082] Where the entity is a group, the profile data 316 for the group may similarly include one or more avatar representations associated with the group, in addition to the group name, members, and various settings related to the group (eg, notifications).

[0083] Database 126 also stores enhancement data, such as overlays or filters, in enhancement table 310. Enhancement data is associated with and applied to videos (data for videos is stored in video table 304) and images (data for images is stored in image table 312).

[0084] The database 126 may also store data related to individual and shared AR sessions. The data may include data transmitted between an AR session client controller of a first client device 102 and another AR session client controller of a second client device 102, and data transmitted between an AR session client controller and the augmented system 208. The data may include data for establishing a common coordinate system for a shared AR scene, transformations between devices, session identifiers, images depicting the body, skeletal joint positions, wrist joint positions, feet, and the like.

[0085] In one example, a filter is an overlay displayed as an overlay on an image or video during presentation to a recipient user. Filters may be of various types, including filters selected by a user from a set of filters presented to a sending user by messaging client 104 when the sending user is composing a message. Other types of filters include geolocation filters (also referred to as geofilters), which may be presented to a sending user based on a geographic location. For example, a geolocation filter specific to a nearby or specific location may be presented by messaging client 104 within a user interface based on geographic location information determined by a global positioning system (GPS) unit of client device 102.

[0086] Another type of filter is a data filter, which can be selectively presented to the sending user by the messaging client 104 based on other input or information collected during the message creation process by the client device 102. Examples of data filters include the current temperature at a particular location, the current speed at which the sending user is traveling, the battery life of the client device 102, or the current time.

[0087] Other augmented data that may be stored in the image table 312 include augmented reality content items (eg, corresponding to an applied augmented reality experience). Augmented reality content items or augmented reality items may be real-time special effects and sounds that may be added to an image or video.

[0088] As described above, augmented data includes augmented reality content items, overlays, image transformations, AR images, AR logos or badges, and similar items involving modifications that can be applied to image data (e.g., videos or images). This includes real-time modifications that modify the image when it is captured using the device sensor (e.g., one or more cameras) of the client device 102 and then display the image on the screen of the client device 102 with the modification. This also includes modifications to stored content (e.g., video clips in a library that can be modified). For example, in a client device 102 that has access to multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to see how different augmented reality content items will modify the stored clips. For example, by selecting different augmented reality content items for the content, multiple augmented reality content items that apply different pseudo-random movement models can be applied to the same content. Similarly, real-time video capture can be used with the modifications shown to show how the video image currently captured by the sensor of the client device 102 will modify the captured data. Such data may simply be displayed on the screen without being stored in memory, or content captured by the device sensors may be recorded and stored in memory with or without modification (or both). In some systems, a preview function may simultaneously show how different augmented reality content items will look in different windows of the display. This may, for example, enable viewing of multiple windows with different pseudo-random animations on the display at the same time.

[0089] Thus, data and various systems using augmented reality content items or other such transformation systems that modify content using such data may involve detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.) in video frames, tracking of such objects as they leave, enter, and move around the field of view, and modification or transformation of such objects as they are tracked. In various examples, different methods for implementing such transformations may be used. Some examples may involve: generating a three-dimensional mesh model of one or more objects; and using transformations of the model and animated textures within a video to implement the transformations. In other examples, tracking of points on an object may be utilized to place an image or texture (which may be two-dimensional or three-dimensional) at the tracked location. In yet another example, a neural network analysis of a video frame may be used to place an image, model, or texture in content (e.g., an image or video frame). Thus, augmented reality content items refer to both images, models, and textures used to create transformations in content, as well as additional modeling and analysis information required to implement such transformations using object detection, tracking, and placement.

[0090] Real-time video processing can be performed using any kind of video data (e.g., video streams, video files, etc.) stored in the memory of any kind of computerized system. For example, a user can load video files and store them in the memory of the device, or a sensor of the device can be used to generate a video stream. In addition, any object, such as a human face and parts of a human body, an animal, or a non-living thing (e.g., a chair, a car, or other objects) can be processed using computer animation models.

[0091] In some examples, when a specific modification is selected together with the content to be transformed, the element to be transformed is identified by the computing device, and then if the element to be transformed is present in the video frame, the element to be transformed is detected and tracked. The elements of the object are modified according to the request for modification, thereby transforming the frame of the video stream. For different types of transformations, the transformation of the frame of the video stream can be performed by different methods. For example, for a frame transformation that mainly involves changing the form of the elements of the object, the feature points for each element of the object are calculated (for example, using an active shape model (Active Shape Model, ASM) or other known methods). Then, for each element of at least one element of the object, a grid based on the feature points is generated. The grid is used for the subsequent stage of tracking the elements of the object in the video stream. During the tracking process, the grid mentioned for each element is aligned with the position of each element. Then, additional points are generated on the grid. A first group of first points is generated for each element based on the request for modification, and a group of second points is generated for each element based on the group of first points and the request for modification. Then, the frame of the video stream can be transformed by modifying the elements of the object based on the group of first points and the group of second points and the grid. In such methods, the background of the modified object may also be changed or distorted by tracking and modifying the background of the modified object.

[0092] In some examples, a transformation that changes some areas of an object using elements of an object can be performed by calculating feature points for each element of the object and generating a grid based on the calculated feature points. Points are generated on the grid, and then various areas based on the points are generated. Then, the elements of the object are tracked by aligning the area for each element with the position for each element of at least one element, and the properties of the area can be modified based on the request for modification, thereby transforming the frame of the video stream. Depending on the specific modification request, the properties of the mentioned area can be transformed in different ways. Such modifications may involve: changing the color of the area; removing at least some parts of the area from the frame of the video stream; including one or more new objects in the area based on the modification request; and modifying or distorting the elements of the area or object. In various examples, any combination of such modifications or other similar modifications may be used. For certain models to be animated, some feature points may be selected as control points for determining the entire state space of options for model animation.

[0093] In some examples of using computer animation models that use face detection to transform image data, faces are detected on an image using a specific face detection algorithm (e.g., Viola-Jones). An active shape model (ASM) algorithm is then applied to the face region of the image to detect facial feature reference points.

[0094] Other methods and algorithms suitable for face detection can be used. For example, in some examples, landmarks are used to locate features, which represent distinguishable points that exist in most of the images considered. For example, for facial landmarks, the location of the left pupil can be used. If the initial landmarks are not recognizable (for example, if the person is wearing an eye patch), secondary landmarks can be used. Such a landmark identification process can be used for any such object. In some examples, a set of landmarks forms a shape. The coordinates of the points in the shape can be used to represent the shape as a vector. One shape is aligned with another shape using a similarity transformation (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between the shape points. The average shape is the average of the aligned training shapes.

[0095] In some examples, the landmark search begins with an average shape that aligns with the location and size of the face determined by a global face detector. Such a search then repeats the steps of proposing tentative shapes by adjusting the positions of shape points by template matching of the image texture around each point, and then conforming the tentative shapes to the global shape model until convergence occurs. In some systems, individual template matches are unreliable, and the shape model pools the results of weak template matches to form a stronger overall classifier. The entire search is repeated at each level of the image pyramid from coarse to fine resolution.

[0096] The transformation system can capture an image or video stream on a client device (e.g., client device 102) and perform complex image manipulations locally on the client device 102 while maintaining an appropriate user experience, computational time, and power consumption. Complex image manipulations can include size and shape changes, emotional transformations (e.g., changing a face from a frown to a smile), state transformations (e.g., aging a subject, reducing apparent age, changing gender), style transformations, application of graphical elements, and any other suitable image or video manipulations enabled by a convolutional neural network that has been configured to execute efficiently on the client device 102.

[0097] In some examples, a computer animation model for transforming image data can be used by a system in which a user can capture an image or video stream of the user (e.g., a selfie) using a client device 102 having a neural network that operates as part of a messaging client 104 operating on the client device 102. A transformation system operating within the messaging client 104 determines the presence of a face within the image or video stream and provides a modification icon associated with the computer animation model to transform the data image, or the computer animation model can be present in association with an interface described herein. The modification icon includes a change that can be a basis for modifying the user's face within the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates a process of transforming the user's image to reflect the selected modification icon (e.g., generating a smiley face on the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream can be presented in a graphical user interface displayed on the client device 102. The transformation system can implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, a user can capture an image or video stream, and once a modification icon has been selected, the modified result can be presented in real time or near real time. In addition, the modification can be persistent while the video stream is being captured and the selected modification icon remains toggled. A machine learning neural network can be used to implement such modification.

[0098] The graphical user interface presenting the modifications performed by the transformation system can provide additional interactive options to the user. Such options can be based on the interface used to initiate content capture and the selection of a specific computer animation model (e.g., initiated from a content creator user interface). In various examples, the modifications can be persistent after the initial selection of the modification icon. The user can switch to turn the modification on or off by tapping or otherwise selecting the face being modified by the transformation system, and store it for later viewing or browsing other areas of the imaging application. In the case where multiple faces are modified by the transformation system, the user can globally switch the modification to on or off by tapping or selecting a single face modified and displayed within the graphical user interface. In some examples, individual faces in a group of multiple faces can be modified individually, or such modifications can be switched individually by tapping or selecting an individual face or a series of faces displayed within the graphical user interface.

[0099] The story table 314 stores data about a collection of messages and associated image, video, or audio data that are compiled into a collection (e.g., a story or library). The creation of a particular collection can be initiated by a particular user (e.g., each user for whom a record is maintained in the entity table 306). A user can create a "personal story" in the form of a collection of content that has been created and sent / broadcasted by the user. To this end, the user interface of the messaging client 104 may include a user-selectable icon to enable the sending user to add specific content to his or her personal story.

[0100] A collection may also constitute a "live story," which is a collection of content from multiple users created manually, automatically, or using a combination of manual and automatic techniques. For example, a "live story" may constitute a curated stream of user-submitted content from various locations and events. Users whose client devices have location services enabled and who are at a common location event at a particular time may be presented with the option to contribute content to a particular live story, for example, via the user interface of the messaging client 104. Live stories may be identified to a user by the messaging client 104 based on his or her location. The end result is a "live story" told from a community perspective.

[0101] Another type of content collection is called a "location story," which enables users whose client devices 102 are located in a particular geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some implementations, contributions to location stories may require secondary authentication to verify that the end user belongs to a particular organization or other entity (e.g., is a student on a university campus).

[0102] As mentioned above, the video table 304 stores video data, which in one example is associated with a message for which a record is maintained within the message table 302. Similarly, the image table 312 stores image data, which is associated with a message for which message data is stored in the entity table 306. The entity table 306 may associate various enhancements from the enhancement table 310 with the various images and videos stored in the image table 312 and the video table 304.

[0103] Data communication architecture

[0104] Figure 4 is a schematic diagram illustrating the structure of a message 400 according to some examples, which message 400 is generated by a messaging client 104 for transmission to another messaging client 104 or a messaging server 118. The content of a particular message 400 is used to populate a message table 302, which is stored in a database 126 and accessible by a messaging server 118. Similarly, the content of the message 400 is stored in memory as "in-flight" or "in-flight" data of a client device 102 or an application server 114. The message 400 is shown as including the following example components:

[0105] Message identifier 402 : a unique identifier that identifies the message 400 .

[0106] Message text payload 404 : Text to be generated by a user via the user interface of the client device 102 and included in the message 400 .

[0107] Message image payload 406 : Image data captured by the camera component of the client device 102 or retrieved from the memory of the client device 102 and included in the message 400 . Image data for a message 400 sent or received may be stored in the image table 312 .

[0108] Message video payload 408 : Video data captured by the camera component or retrieved from the memory component of the client device 102 and included in the message 400 . The video data for a message 400 sent or received may be stored in the video table 304 .

[0109] Message audio payload 410 : audio data captured by a microphone or retrieved from a memory component of the client device 102 and included in the message 400 .

[0110] Message enhancement data 412 : enhancement data (eg, filters, stickers, or other annotations or enhancements) representing enhancements to be applied to the message image payload 406 , message video payload 408 , or message audio payload 410 of the message 400 . The enhancement data for a sent or received message 400 may be stored in the enhancement table 310 .

[0111] Message duration parameter 414: A parameter value indicating the amount of time in seconds that the content of the message (eg, message image payload 406, message video payload 408, message audio payload 410) will be presented to or made accessible to the user via the message client 104.

[0112] Message geolocation parameters 416: Geolocation data (e.g., latitude and longitude coordinates) associated with the content payload of the message. Multiple message geolocation parameter 416 values ​​may be included in the payload, each of which is associated with a content item included in the content (e.g., a specific image within a message image payload 406, or a specific video within a message video payload 408).

[0113] Message story identifier 418: An identifier value that identifies one or more content collections (e.g., a "story" identified in story table 314) associated with a particular content item in message image payload 406 of message 400. For example, an identifier value may be used to associate multiple images within message image payload 406 with each of multiple content collections.

[0114] Message tags 420: Each message 400 may be tagged with a plurality of tags, each of which indicates the subject of the content included in the message payload. For example, where a particular image included in the message image payload 406 depicts an animal (e.g., a lion), a tag value indicating the relevant animal may be included within the message tags 420. The tag values ​​may be manually generated based on user input, or may be automatically generated using, for example, image recognition.

[0115] • Message sender identifier 422: An identifier (eg, a messaging system identifier, an email address, or a device identifier) ​​that indicates the user of the client device 102 on which the message 400 was generated and from which the message 400 was sent.

[0116] • Message recipient identifier 424: An identifier (eg, a messaging system identifier, an email address, or a device identifier) ​​that indicates the user of the client device 102 to which the message 400 is addressed.

[0117] The content (e.g., value) of various components of message 400 may be pointers to locations in a table in which content data values ​​are stored. For example, an image value in message image payload 406 may be a pointer to (or the address of) a location in image table 312. Similarly, a value within message video payload 408 may point to data stored in video table 304, a value stored within message enhancement data 412 may point to data stored in enhancement table 310, a value stored within message story identifier 418 may point to data stored in story table 314, and values ​​stored within message sender identifier 422 and message recipient identifier 424 may point to user records stored in entity table 306.

[0118] Multi-camera AR experience system

[0119] Figure 5 is a block diagram illustrating an example multi-camera AR experience system 224 according to some examples. The multi-camera AR experience system 224 includes an AR experience development module 500, a multi-camera AR selection module 510, a multi-camera AR asset generation module 520, a multi-camera layout module 530, and a multi-camera metric generation module 540.

[0120] The AR experience development module 500 may generate a user interface for presentation to the AR developer on the AR developer client device 102. The user interface may enable the AR developer to enable simultaneous activation of multiple cameras for a corresponding AR experience. The user interface may enable the AR developer to select an AR experience bundle. In response, the user interface may present a prompt having one or more options for enabling simultaneous activation of multiple cameras (e.g., a front camera and a rear camera) when launching an AR experience on the client device 102. The prompt may also enable the AR developer to specify one or more parameters for simultaneous activation of multiple cameras.

[0121] As referred to herein, an “AR experience bundle” or “AR bundle” refers to a set of AR elements (including standard AR elements and linked AR elements) and corresponding configuration data and code that indicate the visual appearance, interactions, and behaviors of each AR element. An AR bundle includes code required for a client device 102 to launch and execute an AR experience associated with the AR bundle. The configuration data may specify: whether the AR experience is associated with parameters for enabling simultaneous activation of multiple cameras; the layout or configuration of images obtained from multiple cameras (e.g., a first camera 103 and a second camera 105); filters or visual effects to be applied to images obtained from each camera; and / or which image is used as a source image (e.g., which camera is a primary camera that provides a source image) and which image is used as a target image (e.g., which camera is a secondary camera that provides a target image) when generating and rendering an AR element.

[0122] In some examples, AR experience development module 500 receives a request to access a developer user interface from developer client device 102. AR experience development module 500 may receive login credentials from developer client device 102. AR experience development module 500 may search for an account associated with the login credentials, and may generate a graphical user interface associated with the account for presentation to developer client device 102. AR experience development module 500 may present multiple AR experience bundles associated with the account in the graphical user interface. In some cases, an account may be accessible by an organization, in which case multiple users within the organization may share access to the account and may view the same set of AR experience bundles.

[0123] AR experience development module 500 may receive input from developer client device 102 selecting a given AR experience bundle. In response to receiving the input, AR experience development module 500 may present graphical user interface 600 ( Figure 6 ). The AR experience development module 500 may include an identifier of the AR experience bundle and a list of AR objects or AR elements 620 included in the AR experience bundle in the graphical user interface 600. The AR elements may include 2D meshes, 3D meshes, videos, audio files, image files, avatars, graphical elements, and / or machine learning models. The AR experience development module 500 may receive input selecting a given AR element 622 (e.g., an effect element) in the AR objects or AR elements 620.

[0124] In response, AR experience development module 500 presents prompt 610 on end-user client device 102 that lists options for enabling simultaneous activation of multiple cameras. For example, prompt 610 may include option 630 to enable simultaneous activation of multiple cameras. In response to receiving a selection of option 630, AR experience development module 500 updates the configuration data for the given AR experience bundle to indicate that simultaneous activation of multiple cameras has been enabled. Prompt 610 may also include layout or configuration selection option 640. In response to receiving a selection of option 640, AR experience development module 500 updates the configuration data to indicate the selected layout of the given AR experience.

[0125] In some examples, in response to receiving a selection of option 640, a list of different layouts or configurations may be presented to the AR developer. For example, the list of different layouts may include a first layout option. In response to selecting the first layout option, instructions for routing and displaying images or videos obtained from multiple cameras are stored. For example, the AR experience bundle may control the image input so that an image obtained from one camera (e.g., first camera 103 or primary camera) (e.g., a primary image) will be routed to the display screen and displayed at the top of the display screen (e.g., the top half or top quarter), and an image obtained from another camera (e.g., second camera 105 or secondary camera) (e.g., an auxiliary image) will be routed to the display and displayed at the bottom of the display (e.g., the bottom half or bottom quarter or bottom three quarters). As another example, a second layout option may be included in the list of layouts, and when the layout is selected, instructions are stored for routing an image (e.g., a main image) obtained from one camera (e.g., the first camera 103 or the primary camera) to the display screen and displayed on the left portion (e.g., the left half or the left quarter) of the display screen, and routing an image obtained from another camera (e.g., the second camera 105 or the secondary camera) to the display screen and displayed on the right portion (e.g., the right half or the right quarter or the right 3 / 4) of the display screen. Alternatively, the images may be controlled (through the AR experience bundle) so that the image (e.g., the main image) obtained from the second camera 105 is routed to the display screen and displayed on the upper portion (e.g., the upper half or the upper quarter) of the display screen, and the image (e.g., the auxiliary image) obtained from the first camera 103 is routed to the display screen and displayed on the bottom (e.g., the lower half or the lower quarter or the bottom three quarters) of the display screen.

[0126] The list of different layouts may include a third layout option. In response to selecting the third layout option, instructions are stored for routing and displaying an image (e.g., a primary image) obtained from one camera (e.g., the first camera 103 or the primary camera) in full screen and routing an image (e.g., an auxiliary image) obtained from another camera (e.g., the second camera 105 or the secondary camera) and displaying it within or above the full screen image. This may be referred to as a PIP layout. Alternatively, instructions may be stored for routing and displaying an image (e.g., a primary image) obtained from the second camera 105 in full screen and routing an image (e.g., an auxiliary image) obtained from the first camera 103 and displaying it within or above the full screen image.

[0127] The list of different layouts may include a fourth layout option. In response to receiving a selection of the fourth layout option, instructions may be stored for routing an image (e.g., a primary image) obtained from one camera (e.g., a second camera 105 or a secondary camera) and using it as a green screen basis for one or more objects obtained from an image (e.g., a secondary image) from another camera (e.g., a first camera 103 or a primary camera) to form a single image or video. In this case, the image (e.g., a secondary image) obtained from the second camera 105 (e.g., a secondary camera) is processed by the AR experience bundle to identify the background and foreground. The foreground may be removed on a pixel-by-pixel basis. The background may then be used as a green screen. The primary image obtained from the first camera 103 or the primary camera may be similarly processed by the AR experience bundle to identify the background and foreground. In some examples, real-world objects such as people may be identified and used as the foreground of the image obtained from the first camera 103. The foreground of the image from the first camera 103 (primary camera) can then be superimposed on the background of the image obtained from the second camera 105 to generate a new image. The new image can then be displayed on a separate portion of the display (e.g., together with the images obtained from the first camera 103 and the second camera 105), or replace one of the images obtained from the first camera 103 and the second camera 105.

[0128] The list of different layouts may include a fifth layout option. In response to receiving a selection of the fifth layout option, instructions for providing a face builder layout may be stored in which a cutout of an object segmentation (e.g., a facial element) depicted in an image (e.g., a primary image) obtained from the first camera 103 (e.g., a primary camera) is superimposed on an image (e.g., a secondary image) obtained from the second camera 105, or vice versa. For example, the fifth layout option may include a selection of one or more object segmentation models. The object segmentation model may include a facial segmentation model, a body segmentation model, an animal segmentation model, a body part segmentation model, etc. An input from an AR developer selecting one or more of the object segmentation models may be received. Using the selected object segmentation model, a source image (e.g., an image obtained from one camera such as the first camera 103 or the primary camera) is processed to segment one or more objects using an object segmentation model (e.g., a facial segmentation model). Segmentation is used to extract one or more features from the segmented portion of the image. The segmented portions and extracted features are then superimposed and combined into the real world or AR object depicted in a target image (eg, an image obtained from another camera such as the second camera 105 or a secondary camera).

[0129] The multi-camera AR selection module 510 can receive configuration data from the AR experience development module 500. The multi-camera AR selection module 510 can present options on the end-user client device 102 for using multiple cameras simultaneously to generate an AR experience. For example, the multi-camera AR selection module 510 can present icons or options for enabling or activating multiple cameras of the client device 102. The icons can visually depict the cameras using forward and backward arrows. In response to receiving a selection of an option, the multi-camera AR selection module 510 can present a list of different layouts for the user to select from. When a different layout is selected, an updated AR output is generated by the AR experience bundle by modifying and / or changing the layout of the video stream input received simultaneously from multiple cameras.

[0130] In some examples, multi-camera AR selection module 510 receives a request from a user to access a list of AR experiences. In response, multi-camera AR selection module 510 may search multiple AR experiences (e.g., configuration data associated with multiple AR experiences) to identify a subset of AR experiences for which simultaneous activation of multiple cameras is enabled. Multi-camera AR selection module 510 may generate a list of icons, each icon representing a corresponding AR experience in the AR experiences for which simultaneous activation of multiple cameras is enabled. Multi-camera AR selection module 510 may receive input selecting a given AR experience from the list.

[0131] The multi-camera AR selection module 510 retrieves configuration data for a given AR experience that has been selected. If the first camera 103 and the second camera 105 were not previously activated, the multi-camera AR selection module 510 also automatically activates the two cameras. The multi-camera AR selection module 510 can obtain the layout or configuration of the given AR experience from the configuration data. For example, the configuration data may specify that the layout or configuration of the given AR experience is associated with the face builder layout. In this case, the multi-camera AR selection module 510 obtains the object segmentation model (e.g., the face segmentation model) specified by the configuration data. The multi-camera AR selection module 510 applies the object segmentation model to the first image obtained from the first camera 103 (e.g., a video captured by the primary camera) to extract one or more features of the object corresponding to the object segmentation model. Then, the multi-camera AR selection module 510 identifies the target object (e.g., a real-world object or an AR object) in the second image obtained from the second camera 105 (e.g., a video captured by the secondary camera). The target object may be specified by the user, for example, by clicking on an object presented to the user on a display of the client device 102. The target object may be specified by an object type in the configuration data of the AR experience. In this case, the multi-camera AR selection module 510 applies an object classifier to the second image to classify the objects depicted in the second image and searches for objects that match the object type specified in the configuration data. As mentioned herein, a primary camera may provide primary input to an AR experience bundle, and a secondary camera may provide secondary input to the same AR experience bundle to generate an AR output.

[0132] The multi-camera AR selection module 510 may then provide the one or more features of the object corresponding to the object segmentation model and the target object to the multi-camera AR asset generation module 520. The multi-camera AR asset generation module 520 may modify the target object using the one or more features of the object corresponding to the object segmentation model. For example, the multi-camera AR asset generation module 520 may generate an AR output by using the first video stream received from the primary camera as an input to the corresponding AR experience bundle and using the second video stream as a secondary input to the AR experience bundle. The AR output may include an AR element that includes some visual properties of the target object (from the second image received from the secondary input as the second video stream from the secondary camera) and some visual properties of one or more features of the object (from the first image received from the primary camera or the primary input) corresponding to the object segmentation model. For example, the multi-camera AR asset generation module 520 superimposes the features of the object from the first image onto the target object from the second image. The multi-camera AR asset generation module 520 then incorporates the generated AR object into the first image or the second image.

[0133] For example, Figure 7 As shown, the client device 102 can present a user interface 700 corresponding to a given AR experience associated with the simultaneous activation of multiple cameras or generated by the given AR experience. The user interface 700 may include a message (not shown) indicating that both the first camera 103 and the second camera 105 are activated simultaneously. The user interface 700 includes a first image 720 captured or received by the first camera 103 of the client device 102. The first image 720 may depict a real-world object, such as a human face. The user interface 700 simultaneously presents a second image 710 captured or received by the second camera 105 of the client device 102. The second image 710 may depict a real-world environment including a target real-world object 730. The first image 720 and the second image 710 may be displayed, for example, in a PIP display layout, a horizontal display layout, or a vertical display layout according to the configuration data of the given AR experience.

[0134] The client device 102 may access configuration data to extract one or more features of the real-world object depicted in the first image 720. For example, the client device 102 may extract eyes and a mouth from a face depicted in the first image 720. The client device 102 may then overlay the features 740 of the eyes and mouth onto the target real-world object 730 depicted in the second image 710. As the features of the eyes and mouth change or move in subsequent images captured by the first camera 103, the client device 102 continuously updates the features 740 of the eyes and mouth overlaid onto subsequent images depicting the target real-world object 730 captured by the second camera 105. The messaging client 102 may receive input selecting a record option. In response, the client device 102 may record a video (of a specified duration) representing the movement of the features 740 of the eyes and mouth overlaid onto subsequent images depicting the target real-world object 730 captured by the second camera 105. The recorded video may be shared with one or more other users.

[0135] The client device 102 may receive input selecting an alternative target object depicted in the image captured by the second camera 105. The input may be received by tapping an area of ​​the screen where the alternative target object is displayed. In response, the client device 102 may move the eyes and mouth features from being superimposed on the target real-world object 730 to being superimposed on the alternative target object. The client device 102 may allow the user to rotate, scale, and / or place the eyes and mouth features 740 at any user-selected point within the second image 710.

[0136] In some examples, client device 102 may receive a request to swap images by selecting an on-screen swap option. In response, client device 102 may change the display layout or configuration of first image 720 and second image 710. That is, client device 102 may swap: which camera is used as the primary camera to provide primary input to the AR experience bundle for generating AR output; which camera is used as the secondary camera to provide secondary input to the AR experience bundle. The client device may then generate updated AR output by using the second video stream as the primary input to the AR experience bundle and using the first video stream as the secondary input to the AR experience bundle. For example, client device 102 may display the second image 710 with a modified target object in an area of ​​the display where the first image 720 is displayed, and may display the first image 720 in an area of ​​the display where the second image 710 is displayed. In some examples, in addition to or as an alternative to swapping display positions, in response to receiving a selection for the swap option, client device 102 may also apply a segmentation model to extract one or more features of a given object depicted in second image 710, and use the extracted features to modify another target object depicted in first image 720. That is, client device 102 may, in response to receiving a selection for the swap option, replace which camera image is used as a source image (e.g., primary input to an AR experience bundle) for extracting features of an object and which camera image is used as a target image (e.g., secondary input to an AR experience bundle) for embedding or modifying an object using the extracted features of the source image.

[0137] In some examples, before the client device 102 activates the first camera 103 and the second camera 105 simultaneously, the client device 102 may determine whether any of the cameras is currently activated. For example, the client device 102 may determine that the first camera 103 is currently activated and used to display images when receiving a request to activate both cameras simultaneously (e.g., by selecting a given AR experience or selecting a dedicated multi-camera activation option). The client device 102 may store an indication that the first camera 103 is activated, and then may activate both the camera 103 and the camera 105 in response to the request. The client device 102 may receive a request to stop the simultaneous activation of the first camera 103 and the second camera 105, for example, by selecting an exit option, deselecting a dedicated multi-camera activation option, selecting a different AR experience that disables simultaneous activation of multiple cameras, and / or turning off the AR experience. In response, the client device 102 may access a previously stored indication of which camera was previously activated, and may keep the camera in an activated state. For example, due to a stored indication that first camera 103 was active prior to receiving a request to simultaneously activate both cameras, client device 102 may, in response to receiving a request to stop simultaneous activation, deactivate second camera 105 while keeping first camera 103 active.

[0138] In some examples, a client device 102 may receive a request to make a call to another client device 102 or to participate in a video call to another client device 102. This may be performed while activating both the first camera 103 and the second camera 105. During the video call, images from both the first camera 103 and the second camera 105 may be simultaneously sent to the recipient client device 102 according to one of the layouts selected by the user.

[0139] In some examples, the client device 102 can use the first camera 103 and the second camera 105 to help the user conduct a shopping AR experience to see how different AR objects look on different parts of the user's body depicted in different images captured by the first camera 103 and the second camera 105, respectively. For example, the client device 102 can receive input selecting a shopping AR experience. In response, the shopping AR experience is started and the user is told to position a first body part (e.g., head) within the perspective of the first camera 103 and position a second body part (e.g., foot) within the perspective of the second camera 105. The client device 102 can receive a first image captured by the first camera 103 and depicting the first body part, and can receive a second image captured by the second camera 105 and depicting the second body part. The first image can be provided as a primary input to the shopping AR experience bundle, and the second image can be used as a secondary input to the shopping AR experience bundle.

[0140] The client device 102 can segment the first body part and the second body part using the corresponding body segmentation model type. The client device 102 can then select an AR object corresponding to each body part. For example, the client device 102 can select a hat or glasses AR object for the first body part that can be the head, and can select a shoe or pants AR object for the second body part that can be the foot. In some examples, the client device 102 can present a display of a hat or glasses AR object on a portion of the image depicting the first body part obtained from the first camera 103, and simultaneously present a display of a shoe or pants AR object on a portion of the image depicting the second body part obtained from the second camera 105. In some examples, the client device 102 displays the two images separately. In some examples, the client device 102 generates a combined image depicting two parts of the user's body together with the corresponding AR objects and displays the combined image to the user. In this way, the client device 102 can use the AR shopping experience bundle to apply a first AR effect to a primary input (e.g., a first image captured by the first camera 103) and a second AR effect to a secondary input (e.g., a second image captured by the second camera 105).

[0141] Return to reference Figure 5, the multi-camera metric generation module 540 can track the usage of multiple cameras on various client devices 102 for one or more AR experiences. The multi-camera metric generation module 540 can generate statistics or metrics representing such usage and present the metrics to the AR developer. For example, the multi-camera metric generation module 540 can count the number of times each client device activates the first camera 103 and the second camera 105 simultaneously. The multi-camera metric generation module 540 can count the number of client devices 102 that can activate multiple cameras simultaneously. The multi-camera metric generation module 540 can count the number of failures and successes that occur when activating multiple cameras simultaneously on the corresponding client devices 102.

[0142] The multi-camera layout module 530 enables a user to activate multiple cameras simultaneously and modify the layout or configuration of images obtained from the first camera 103 and the second camera 105. Prior to receiving a user request, the multiple cameras may be activated simultaneously, or may all be disabled upon receiving a user request. For example, the multi-camera layout module 530 may present a set of options for selecting a given layout or configuration. The set of options may be presented when at least one of the first camera 103 and the second camera 105 is not capturing video. In response to receiving a selection of one of the options, after activating the two cameras simultaneously (if neither camera was activated when the request was received), the layout or configuration of the images received from the corresponding cameras is switched. Specifically, as Fig. 8A As shown, a user interface 800 including a menu of options is presented on the client device 102. The menu includes a multi-camera activation option 810. In response to receiving an input selecting the multi-camera activation option 810, the client device 102 may present a menu 820 having a layout option list 822. The layout option list 822 may include a vertical layout option, a horizontal layout option, a PIP layout option, and a face builder layout option. Option 810 may be presented when at least one of the first camera 103 and the second camera 105 is not capturing video or when both cameras are capturing video.

[0143] In response to receiving input selecting the horizontal layout option, client device 102 activates both cameras (if not already activated) and presents the first image 830 received from first camera 103 on the top of the screen and the second image 840 received from second camera 105 on the bottom of the screen. Figure 8BAs shown, in response to receiving input selecting the vertical layout option, the client device 102 presents a user interface 801 in which a first image 831 received from the first camera 103 is displayed on a left portion of the screen, and a second image 841 received from the second camera 105 is displayed on a right portion of the screen. The client device 102 may include an indication 824 of the selected layout along with the displayed images. Figure 8C As shown, in response to receiving input selecting the PIP layout option, the client device 102 presents a user interface 802 in which a first image 832 received from the first camera 103 is displayed in a window over a full screen display of a second image 842 received from the second camera 105. The client device 102 may include an indication 826 of the selected layout along with the displayed image.

[0144] Fig. 9A and Fig. 9B Flowcharts of processes 900 and 910 performed by a multi-camera AR experience system 224 according to some examples. Although the flowchart may describe the operations as a sequential process, many of these operations may be performed in parallel or simultaneously. In addition, the order of the operations may be rearranged. The process terminates when its operations are completed. A process may correspond to a method, a program, or the like. The steps of a method may be performed in whole or in part, may be performed in combination with some or all of the steps in other methods, and may be performed by any number of different systems or any part thereof (e.g., a processor included in any system).

[0145] At operation 901 , as discussed above, multi-camera AR experience system 224 (eg, client device 102 or a server) detects a real-world object depicted in a first image captured by a first camera of a client device that includes a second camera.

[0146] At operation 902 , as discussed above, the multi-camera AR experience system 224 extracts one or more textures from a real-world object depicted in a first image.

[0147] At operation 903 , as discussed above, the multi-camera AR experience system 224 selects a target object depicted in a second image captured by a second camera, the second image being captured by the second camera at the same time as the first image was captured by the first camera.

[0148] At operation 904 , as discussed above, the multi-camera AR experience system 224 generates an augmented reality (AR) element that includes a target object modified based on one or more textures extracted from a real-world object depicted in the first image.

[0149] At operation 905 , as discussed above, the multi-camera AR experience system 224 causes display of an AR element within the second image.

[0150] At operation 911, as discussed above, the multi-camera AR experience system 224 (e.g., client device 102 or a server) uses a first camera of the client device to capture a first video stream, and uses a second camera of the client device to capture a second video stream, the first video stream and the second video stream being captured simultaneously.

[0151] At operation 912 , as discussed above, the multi-camera AR experience system 224 generates an augmented reality (AR) output by using the first video stream as a primary input to the first AR experience bundle and using the second video stream as a secondary input to the first AR experience bundle.

[0152] At operation 913 , the multi-camera AR experience system 224 causes the AR output to be presented on a display of the client device, as discussed above.

[0153] Machine Architecture

[0154] Fig.101000 within which instructions 1008 (e.g., software, programs, applications, applet, app, or other executable code) may be executed for causing the machine 1000 to perform any one or more of the methods discussed herein. For example, the instructions 1008 may cause the machine 1000 to perform any one or more of the methods described herein. The instructions 1008 transform a general purpose, unprogrammed machine 1000 into a specific machine 1000 that is programmed to perform the functions described and illustrated in the manner described. The machine 1000 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1000 may operate in the performance of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1000 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of sequentially or otherwise executing instructions 1008 specifying actions to be taken by the machine 1000. In addition, although only a single machine 1000 is shown, the term "machine" should also be considered to include a collection of machines that individually or jointly execute instructions 1008 to perform any one or more of the methods discussed herein. For example, the machine 1000 may include a client device 102 or any one of several server devices that form part of the messaging server system 108. In some examples, the machine 1000 may also include both a client system and a server system, wherein certain operations of a particular method or algorithm are performed on the server side and certain operations of a particular method or algorithm are performed on the client side.

[0155] The machine 1000 may include a processor 1002, a memory 1004, and an input / output (I / O) component 1038 that may be configured to communicate with each other via a bus 1040. In an example, the processor 1002 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 1006 that executes instructions 1008 and a processor 1010. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions simultaneously. Although Fig.10 Multiple processors 1002 are shown, but the machine 1000 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

[0156] The memory 1004 includes a main memory 1012, a static memory 1014, and a storage unit 1016, which are all accessible by the processor 1002 via the bus 1040. The main memory 1012, the static memory 1014, and the storage unit 1016 store instructions 1008 that embody any one or more of the methodologies or functions described herein. The instructions 1008 may also reside, completely or partially, within the main memory 1012, within the static memory 1014, within a machine-readable medium within the storage unit 1016, within at least one of the processors 1002 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 1000.

[0157] I / O components 1038 may include various components that receive input, provide output, generate output, send information, exchange information, capture measurements, etc. The specific I / O components 1038 included in a particular machine will depend on the type of machine. For example, a portable machine (e.g., a mobile phone) may include a touch input device or other such input mechanism, while a headless server machine will likely not include such a touch input device. It should be understood that I / O components 1038 may include Fig.101024 and 1026. In various examples, the I / O components 1038 may include a user output component 1024 and a user input component 1026. The user output component 1024 may include a visual component (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), an acoustic component (e.g., a speaker), a tactile component (e.g., a vibration motor, a resistance mechanism), other signal generators, etc. The user input component 1026 may include an alphanumeric input component (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input component), a point-based input component (e.g., a mouse, a touch pad, a trackball, a joystick, a motion sensor, or other pointing instrument), a tactile input component (e.g., a physical button, a touch screen or other tactile input component that provides the location and force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.

[0158] In other examples, I / O component 1038 may include biometric component 1028, motion component 1030, environment component 1032, or position component 1034, as well as various other components. For example, biometric component 1028 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweat, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. Motion component 1030 includes acceleration sensor components (e.g., accelerometers), gravity sensor components, and rotation sensor components (e.g., gyroscopes).

[0159] Environmental components 1032 include, for example, one or more cameras (with still image / photo and video capabilities), lighting sensor components (e.g., photometers), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometers), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors that detect concentrations of hazardous gases for safety or measure pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

[0160] With respect to cameras, client device 102 can have a camera system including, for example, a front-facing camera on a front surface of client device 102 and a rear-facing camera on a rear surface of client device 102. The front-facing camera can, for example, be used to capture still images and videos (e.g., “selfies”) of a user of client device 102, which can then be enhanced using the enhancement data (e.g., filters) described above. The rear-facing camera can, for example, be used to capture still images and videos in a more traditional camera mode, where the images are similarly enhanced using the enhancement data. In addition to the front-facing camera and the rear-facing camera, client device 102 can also include a 360° camera for capturing 360° photos and videos.

[0161] Additionally, the camera system of the client device 102 may include dual rear cameras (e.g., a primary camera and a depth sensing camera), or even triple, quad, or quintuple rear camera configurations on the front and back sides of the client device 102. For example, these multi-camera systems may include a wide-angle camera, an ultra-wide-angle camera, a telephoto camera, a macro camera, and a depth sensor.

[0162] The position component 1034 includes a position sensor component (eg, a GPS receiver component), an altitude sensor component (eg, an altimeter or a barometer that detects air pressure, from which the altitude can be obtained), an orientation sensor component (eg, a magnetometer), and the like.

[0163] A variety of technologies may be used to achieve communication. The I / O components 1038 also include a communication component 1036 that is operable to couple the machine 1000 to the network 1020 or the device 1022 via a corresponding coupling or connection. For example, the communication component 1036 may include a network interface component or other suitable device that interfaces with the network 1020. In other examples, the communication component 1036 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, a Bluetooth component (e.g., Bluetooth low energy), a Wi-Fi component, and other communication components that provide communication via other modalities. The device 1022 may be another machine or any of a variety of peripheral devices (e.g., a peripheral device coupled via USB).

[0164] In addition, the communication component 1036 can detect the indication or include a component operable to detect the indication. For example, the communication component 1036 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional bar codes such as universal product codes (UPC) bar codes, multi-dimensional bar codes such as quick response (QR) codes, Aztec codes, data matrix, data symbols (Dataglyph), MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar codes and other optical codes) or an acoustic detection component (e.g., a microphone for identifying an audio signal of a tag). In addition, various information can be derived via the communication component 1036, such as a location derived via Internet Protocol (IP) geolocation, a location derived via Wi-Fi signal triangulation, a location derived via detection of NFC beacon signals that can indicate a specific location, etc.

[0165] Various memories (e.g., main memory 1012, static memory 1014, and memory of processor 1002) and storage unit 1016 may store one or more sets of instructions and data structures (e.g., software) implemented or used by any one or more of the methods or functions described herein. When executed by processor 1002, these instructions (e.g., instructions 1008) cause various operations to implement the disclosed examples.

[0166] The instructions 1008 may be sent or received over the network 1020 via a network interface device (e.g., a network interface component included in the communication component 1036) using a transmission medium and using any of a number of well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)). Similarly, the instructions 1008 may be sent or received via a coupling (e.g., a peer-to-peer coupling) with the device 1022 using a transmission medium.

[0167] Software Architecture

[0168] Fig.111100 is a block diagram illustrating a software architecture 1104 that may be installed on any one or more of the devices described herein. The software architecture 1104 is supported by hardware, such as a machine 1102 including a processor 1120, a memory 1126, and an I / O component 1138. In this example, the software architecture 1104 may be conceptualized as a stack of layers, each of which provides specific functionality. The software architecture 1104 includes layers such as an operating system 1112, a library 1110, a framework 1108, and an application 1106. In operation, the application 1106 invokes an API call 1150 through the software stack and receives a message 1152 in response to the API call 1150.

[0169] The operating system 1112 manages hardware resources and provides public services. The operating system 1112 includes, for example, a core 1114, a service 1116, and a driver 1122. The core 1114 is used as an abstraction layer between the hardware and other software layers. For example, the core 1114 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. The service 1116 can provide other public services for other software layers. The driver 1122 is responsible for controlling the underlying hardware or interfacing with the underlying hardware. For example, the driver 1122 may include a display driver, a camera driver, a Bluetooth or Bluetooth low energy driver, a flash drive, a serial communication driver (e.g., a USB driver), a WI-FI driver, an audio driver, a power management driver, etc.

[0170] The libraries 1110 provide a common low-level infrastructure used by the applications 1106. The libraries 1110 may include a system library 1118 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the libraries 1110 may include an API library 1124, such as a media library (e.g., a library for supporting the presentation and manipulation of various media formats, such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), a graphics library (e.g., an OpenGL framework for presenting in two dimensions (2D) and three dimensions (3D) in graphical content on a display), a database library (e.g., SQLite providing various relational database functions), a web library (e.g., WebKit providing web browsing functions), etc. The library 1110 may also include various other libraries 1128 to provide many other APIs to the application 1106 .

[0171] The framework 1108 provides a common high-level infrastructure used by the applications 1106. For example, the framework 1108 provides various graphical user interface (GUI) functions, high-level resource management, and high-level location services. The framework 1108 can provide a wide range of other APIs that can be used by the applications 1106, some of which can be specific to a particular operating system or platform.

[0172] In the example, applications 1106 may include home applications 1136, contact applications 1130, browser applications 1132, book reader applications 1134, location applications 1142, media applications 1144, messaging applications 1146, game applications 1148, and various other applications such as external applications 1140. Applications 1106 are programs that execute functions defined in programs. Various programming languages ​​can be used to create one or more applications in applications 1106 constructed in various ways, such as object-oriented programming languages ​​(e.g., Objective-C, Java, or C++) or procedural programming languages ​​(e.g., C or assembly language). In a specific example, external applications 1140 (e.g., applications developed by entities other than suppliers of a specific platform using ANDROID or IOS software development kits (SDKs)) can be mobile software running on mobile operating systems such as IOS, ANDROID, WINDOWS Phone, or other mobile operating systems. In this example, external applications 1140 can activate API calls 1150 provided by operating system 1112 to facilitate the functions described herein.

[0173] Glossary

[0174] "Carrier signal" refers to any intangible medium that can store, encode or carry instructions for execution by a machine and includes digital or analog communications signals or other intangible media that facilitates communication of such instructions. Instructions may be sent or received over a network using a transmission medium via a network interface device.

[0175] "Client Device" refers to any machine that interfaces with a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, a desktop computer, a laptop computer, a portable digital assistant (PDA), a smart phone, a tablet computer, an ultrabook, a netbook, a laptop computer, a multiprocessor system, a microprocessor-based or programmable consumer electronics product, a game console, a set-top box, or any other communications device that a user may use to access a network.

[0176] A "communication network" refers to one or more portions of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of a public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi network, other types of networks, or a combination of two or more such networks. For example, a network or a portion of a network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a global system for mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling can implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rates for GSM evolution (EDGE) technology, the third generation partnership project (3GPP) including 3G, fourth generation wireless (4G) networks, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standards, other data transmission technologies defined by various standard setting organizations, other long distance protocols, or other data transmission technologies.

[0177] "Component" means a logical, device, or physical entity having boundaries defined by function or subroutine calls, branch points, APIs, or other techniques that provide partitioning or modularity of specific processing or control functions. Components may be combined with other components via their interfaces to perform machine processing. A component may be a packaged functional hardware unit designed for use with other components and may be part of a program that typically performs a specific one of the related functions.

[0178] Components may constitute software components (e.g., code implemented on a machine-readable medium) or hardware components. A "hardware component" is a tangible unit that is capable of performing certain operations and that can be configured or arranged in some physical manner. In various examples, one or more computer systems (e.g., stand-alone computer systems, client computer systems, or server computer systems) or one or more hardware components of a computer system (e.g., a processor or group of processors) may be configured by software (e.g., an application or application portion) as hardware components that operate to perform certain operations described herein.

[0179] Hardware components may also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component may include a dedicated circuit or logic that is permanently configured to perform certain operations. A hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). A hardware component may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of a machine) that is uniquely customized to perform the configured function, rather than a general-purpose processor. It should be recognized that it may be determined for cost and time considerations whether to implement the hardware component mechanically in a dedicated and permanently configured circuit system or in a temporarily configured (e.g., configured by software) circuit system. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, i.e., an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in some way or perform certain operations described herein.

[0180] Consider an example where hardware components are temporarily configured (e.g., programmed), without configuring or instantiating each of the hardware components at any one time. For example, where the hardware components include a general-purpose processor that is configured by software to be a special-purpose processor, the general-purpose processor can be configured to be a different special-purpose processor (e.g., including different hardware components) at different times. The software accordingly configures one or more specific processors to, for example, constitute a specific hardware component at one time and to constitute a different hardware component at a different time.

[0181] Hardware components can provide information to other hardware components and receive information from other hardware components. Therefore, the described hardware components can be considered to be coupled in communication. In the case of multiple hardware components simultaneously, communication can be realized by signal transmission between two or more hardware components in the hardware components (for example, by appropriate circuits and buses). In the example where multiple hardware components are configured or instantiated at different times, the communication between such hardware components can be realized, for example, by storing information in a memory structure that multiple hardware components can access and retrieving information in the memory structure. For example, a hardware component can perform an operation and store the output of the operation in a memory device to which it is coupled in communication. Then, another hardware component can access the memory device at a subsequent time to retrieve the stored output and process the stored output. The hardware component can also initiate communication with an input device or an output device, and can operate on a resource (for example, a collection of information).

[0182] The various operations of the example methods described herein may be performed at least in part by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether temporarily configured or permanently configured, such a processor may constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refer to hardware components implemented using one or more processors. Similarly, the methods described herein may be implemented at least in part by a processor, wherein a specific one or more processors are examples of hardware. For example, at least some of the operations of the method may be performed by one or more processors 1002 or processor-implemented components. In addition, the one or more processors may also operate to support the execution of related operations in a "cloud computing" environment or as a "software as a service" (SaaS) operation. For example, at least some of the operations in the operation may be performed by a group of computers (as an example of a machine including a processor), wherein these operations may be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). The execution of certain operations in the operation can be distributed among processors, not resident only in a single machine, but deployed across several machines. In some examples, the processor or the components implemented by the processor can be located in a single geographic location (e.g., in a home environment, an office environment, or a server farm). In other examples, the processor or the components implemented by the processor can be distributed across several geographic locations.

[0183] "Computer-readable storage media" refers to both machine storage media and transmission media. Therefore, these terms include both storage devices / media and carrier / modulated data signals. The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure.

[0184] "Ephemeral messages" are messages that are accessible for a limited duration. Ephemeral messages can be text, images, videos, etc. The access time for ephemeral messages can be set by the sender of the message. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transient.

[0185] "Machine storage media" refers to a single or multiple storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Thus, the term should be considered to include, but is not limited to, solid-state memory and optical and magnetic media, including memory internal or external to the processor. Specific examples of machine storage media, computer storage media, and device storage media include: non-volatile memory, including, for example, semiconductor memory devices such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage media", "device storage media", and "computer storage media" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage media", "computer storage media", and "device storage media" expressly exclude carrier waves, modulated data signals, and other such media, at least some of which are encompassed by the term "signal media".

[0186] “Non-transitory computer-readable storage medium” refers to tangible media capable of storing, encoding, or carrying instructions to be executed by a machine.

[0187] "Signal media" refers to other intangible media that can store, encode or carry instructions executed by a machine and includes digital or analog communication signals or other intangible media that facilitate the communication of software or data. The term "signal media" should be deemed to include any form of modulated data signals, carrier waves, etc. The term "modulated data signal" refers to a signal that has one or more of its characteristics set or changed to encode information therein. The terms "transmission medium" and "signal medium" refer to the same thing and may be used interchangeably in this disclosure.

[0188] Changes and modifications may be made to the disclosed examples without departing from the scope of the present disclosure. These and other changes or modifications are intended to be included within the scope of the present disclosure as expressed in the appended claims.

Claims

1. A method comprising: A client device captures a first video stream using a first camera of the client device and a second video stream using a second camera of the client device, wherein the first video stream and the second video stream are captured simultaneously; generating an augmented reality (AR) output by using the first video stream as a primary input to a first AR experience bundle and using the second video stream as a secondary input to the first AR experience bundle; as well as The AR output is caused to be presented on a display of the client device.

2. The method according to claim 1, further comprising: An input for modifying the configuration of the first camera and the second camera is received.

3. The method according to any one of claims 1 to 2, further comprising: In response to receiving the input, generating an updated AR output by using the second video stream as a primary input to the first AR experience bundle and using the first video stream as a secondary input to the first AR experience bundle; as well as The updated AR output is caused to be presented on a display of the client device.

4. The method according to any one of claims 1 to 3, wherein: The primary input is presented at a first display location within the AR output, and the secondary input is presented at a second display location within the AR output, the method further comprising: In response to receiving the input, generating an updated AR output, wherein the primary input is presented at a second display location within the AR output and the secondary input is presented at the first location within the AR output; and The updated AR output is caused to be presented on a display of the client device.

5. The method according to claim 4, wherein: Generating the updated AR output further includes: The second video stream is used as a primary input to the first AR experience bundle, and the first video stream is used as a secondary input to the first AR experience bundle.

6. The method according to any one of claims 1 to 5, wherein: The first AR experience bundle applies a first AR effect to the primary input and a second AR effect to the secondary input.

7. The method according to any one of claims 1 to 6, further comprising: When at least one of the first camera and the second camera is not capturing video, receiving input for launching the first AR bundle; as well as In response to receiving the input, the first camera is caused to capture the first video stream and the second camera is caused to capture the second video stream.

8. The method according to any one of claims 1 to 7, wherein: The first camera is a front camera located on a display side of the client device, and the second camera is a rear camera located on a back side of the client device.

9. The method according to any one of claims 1 to 8, wherein: The AR output includes at least a first image included in the primary video stream presented together with a second image included in the secondary video stream.

10. The method according to any one of claims 1 to 9, further comprising: While at least one of the first camera and the second camera is not capturing video, input is received selecting an option associated with simultaneous activation of the first camera and the second camera.

11. The method according to claim 10, further comprising: In response to receiving the input, displaying a plurality of display layouts; receiving a selection of a first layout from the plurality of layouts; enabling the first camera to capture the first video stream, and enabling the second camera to capture the second video stream; as well as The images included in the first video stream and the second video stream are displayed on a display of the client device according to the first display layout.

12. The method according to any one of claims 1 to 11, wherein: The plurality of display layouts include at least one of the following: a horizontal layout in which an image included in the first video stream is displayed on a top portion of a screen, and an image included in the second video stream is displayed on a bottom portion of the screen; a vertical layout in which images included in the first video stream are displayed on a left portion of the screen and images included in the second video stream are displayed on a right portion of the screen; a picture-in-picture (PIP) layout in which an image included in the first video stream is displayed in a full screen, and an image included in the second video stream is displayed within the full screen; a green screen layout in which a portion of an image included in the first video stream is superimposed on a portion of an image included in the second video stream based on one or more object segmentation models; or A face builder layout in which cutouts of facial elements depicted in the image included in the first video stream are superimposed over images included in the second video stream.

13. The method according to any one of claims 1 to 12, further comprising: Receive a request to view a list of AR experience bundles; Searching a plurality of AR experience bundles to identify a subset of AR experience bundles associated with simultaneous activation of the first camera and the second camera; In response to the request, displaying an icon representing the subset of the AR experience bundle; as well as In response to detecting a selection of the icon representing the first AR experience bundle, launching the first AR experience bundle.

14. The method according to any one of claims 1 to 13, wherein: Generating the AR output includes: detecting a real world object depicted in a first image included in the primary video stream; extracting one or more textures from the real-world object depicted in the first image; selecting a target object depicted in a second image included in the secondary video stream; and An AR element is generated, the AR element including the target object modified based on the one or more textures extracted from the real-world object depicted in the first image, the AR output including the AR element within the second image.

15. The method according to claim 14, wherein: The one or more textures depict a face of a first user, and the target object is a second user, and the AR element depicts the second user using the face of the first user instead of the face of the second user.

16. The method according to any one of claims 1 to 15, wherein: Generating the AR output further includes: extracting one or more textures depicting a face of the second user depicted in the second image; and A second AR element is generated that depicts the first user using the second user's face instead of the first user's face, and the AR output includes both the AR element and the second AR element.

17. The method according to any one of claims 1 to 16, wherein: Generating the AR output includes: The presentation of the first avatar is animated based on the detected movement of the object identified in the first video stream.

18. The method according to claim 17, wherein: Generating the AR output further includes: The presentation of the second avatar is animated based on the detected movement of the object identified in the second video stream.

19. A client device comprising: one or more computer processors; as well as One or more computer-readable media storing instructions that, when executed by the one or more computer processors, cause the client device to perform operations comprising: capturing a first video stream using a first camera of the client device and capturing a second video stream using a second camera of the client device, wherein the first video stream and the second video stream are captured simultaneously; generating an augmented reality (AR) output by using the first video stream as a primary input to a first AR experience bundle and using the second video stream as a secondary input to the first AR experience bundle; and The AR output is caused to be presented on a display of the client device.

20. A non-transitory computer-readable medium storing instructions that, when executed by one or more computer processors of a client device, cause the client device to perform operations comprising: capturing a first video stream using a first camera of the client device and capturing a second video stream using a second camera of the client device, wherein the first video stream and the second video stream are captured simultaneously; generating an augmented reality (AR) output by using the first video stream as a primary input to a first AR experience bundle and using the second video stream as a secondary input to the first AR experience bundle; as well as The AR output is caused to be presented on a display of the client device.

Images