Camera user interface for generating content

Abstract

In one or more implementations, the camera user interface of the client application can be accessed from the third-party application. In one or more examples, the camera user interface can be generated according to a camera user interface developer framework provided by a service provider associated with the client application based at least in part on information provided by the developer of the third-party application. User content can be created using the camera user interface. The user content can be returned to the third-party application for use within the third-party application.

Description

[0001] Priority claim

[0002] This patent application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 046,218 filed on June 30, 2020 and U.S. Patent Application No. 17 / 354,860 filed on June 22, 2021, which are incorporated herein by reference in their entirety. Background Art

[0003] Applications executed by client devices can be used to generate content. For example, client applications can be used to generate message content, image content, video content, audio content, media overlays, documents, creative works, combinations of the above, etc. In various cases, user content can be modified by augmented reality content or other authoring tools. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] In the accompanying 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 highest digit or digits in the reference numeral refer to the figure number in which the element is first introduced. Some implementations are shown by way of example and not limitation.

[0005] Figure 1 is a diagrammatic representation of an architecture for exchanging data (eg, messages and associated content) over a network according to one or more example implementations.

[0006] Figure 2 is a diagrammatic representation of a system that may have both client-side and server-side functionality, according to some examples.

[0007] Figure 3 is a schematic diagram illustrating data that may be stored in a database of a server system according to one or more example implementations.

[0008] Figure 4 is a diagram illustrating an example framework of content that may be accessed via a client application according to one or more example implementations.

[0009] Figure 5 is a diagrammatic representation of an architecture showing accessing a client application from a third-party application and returning content from the client application to the third-party application, according to one or more example implementations.

[0010] Figure 6is a flow diagram illustrating example operations of a process for implementing a framework used by a third party to generate a camera user interface for a client application that can be used to generate content provided to the third party application, according to one or more example implementations.

[0011] Figure 7 is a flow diagram illustrating example operations of a process of accessing a camera user interface of a client application from a third-party application and generating content for the third-party application via the camera user interface, according to one or more example implementations.

[0012] Figure 8 is an illustration of a user interface showing a view of a camera and formatted according to a framework used by developers of third-party applications, according to one or more example implementations.

[0013] Fig. 9 is an illustration of a user interface showing a view of user content captured by a camera and including a plurality of user interface elements that can be selected to apply one or more authoring tools to the user content.

[0014] Fig.10 is a block diagram illustrating components of a machine in the form of a computer system that may read and execute instructions from one or more machine-readable media to perform any one or more of the methodologies described herein, according to one or more example implementations.

[0015] Fig.11 is a block diagram illustrating a representative software architecture that may be used in conjunction with one or more hardware architectures described herein, according to one or more example implementations. DETAILED DESCRIPTION

[0016] Users can access or create content through a number of applications that can be executed by computing devices such as mobile computing devices, smart phones, tablet computing devices, laptop computing devices, portable gaming devices, etc. These applications can be referred to as "apps". In various cases, each app can be targeted at one or more specified types of functions. For example, some apps can be associated with merchants or service providers and used to access goods or services available for purchase provided by merchants or service providers. In other examples, apps can be used for communication in social environments or business environments. Apps can also be used to create content, such as media content, word processing documents, spreadsheets, presentations, etc.

[0017] In many cases, users of applications may wish to create content captured via the camera of a client device and edit the content for use within the application. However, due to the complexity of adding camera functionality to client applications, many client applications may not include tools that can access camera functionality or can be used to edit content captured by a camera. For example, users of social networking applications may wish to use the camera of a client device to generate content. In one or more scenarios, users of social networking applications may also wish to edit content before making the content available to other users of the social networking application. In another example, users of e-commerce applications may wish to use the camera of a client device to generate content of one or more items to be sold via an e-commerce application. In addition, users of e-commerce applications may wish to edit content before providing access to content in conjunction with selling one or more items using an e-commerce application. In various scenarios, social networking applications and e-commerce applications may not be able to create content using the camera of a client device. Social networking applications and e-commerce applications may also not be able to edit content generated using the camera of a client device.

[0018] The systems, methods, techniques, instruction sequences, and computer program products described herein relate to: starting a client application from a third-party application to create content using the tools of the client application, and then sending the created content back to the third-party application for use in the third-party application. For example, an instance of the client application can be accessed from a third-party application. The camera user interface of the client application can be displayed in the client application, and the camera user interface can be used to generate user content by capturing at least one of the image content or video content in the field of view of the camera of the client device of the instance of the client application being executed. Then, one or more authoring tools of the client application can be used to modify the user content. For illustration, at least one of text content, image content, or video content can be added to the user content. In addition, one or more authoring tools of the client application can be used to modify the appearance of one or more objects included in the user content. After the user content has been generated, and in some cases after the user content has been modified, the user content can be returned to the third-party application. Then the user content can be used in the third-party application.

[0019] In addition, the systems, methods, techniques, instruction sequences, and computer program products described herein relate to providing a framework that enables developers of third-party applications to customize user experiences within client applications. In one or more examples, a service provider that develops, maintains, or implements a client application may provide a framework that enables developers of third-party applications to access functionality of the client application and determine features to be included in a camera user interface of the client application. The framework may include a software development kit (SDK) that includes at least one of a tool, library, document, computer-readable code, process, requirement, or application programming interface (API) that is related to at least one of generating or modifying user content using a tool of a client application and then returning the user content to a third-party application for use within the third-party application.

[0020] In one or more implementations, developers can use the framework to create a camera user interface for a client application. The camera user interface can display the field of view captured by one or more cameras of the client device. The camera user interface can also include multiple user interface elements that can be selected to activate functions of the client application. In one or more examples, at least a portion of the user interface elements included in the camera user interface can be related to capturing content using the camera of the client device. For example, at least a portion of the user interface elements included in the camera user interface can be related to capturing content within the field of view of the camera, such as at least a portion of the user interface elements such as a grid tool, flash-related settings, timer tools, etc. The camera user interface can also include one or more user interface elements related to applying augmented reality content to content within the field of view of the camera of the client device.

[0021] In addition, the camera user interface developer framework can enable developers of third-party applications to add at least one of information or user interface elements to customize the camera user interface. In one or more examples, the camera user interface may include user interface elements that can be selected to return content generated by the client application to the third-party application and also return to the third-party application. In various examples, the camera user interface developer framework can also enable developers of third-party applications to add content related to the third-party application, such as at least one of text content, image content, or video content, to the camera user interface. In one or more illustrative examples, developers of third-party applications can add identifiers of third-party applications or logos of third-party applications to the camera user interface. In one or more examples, the camera user interface developer framework can enable developers of third-party applications to modify the default version of the camera user interface. For illustration, developers of third-party applications can remove one or more user interface elements in the default version of the camera user interface to create a customized version of the camera user interface for third-party applications.

[0022] The implementation described herein enables developers of third-party applications to utilize functionality of client applications that may be unavailable or limited within third-party applications, while also enabling developers of third-party applications to customize user experience within client applications. Due to a developer framework that includes software tools, computer-readable code, rules, API information, or a combination thereof that are unavailable to developers relative to existing systems, methods, and client applications, the customization of the camera user interface described herein with respect to each implementation is available. In this way, third-party applications can be enhanced by enabling users of third-party applications to utilize camera tools of client applications to generate user content and return user content to third-party applications for use within third-party applications. In addition, the implementation described herein can provide users of third-party applications with access to augmented reality content corresponding to client applications, which would otherwise be unavailable to users of third-party applications.

[0023] Figure 11 is a diagrammatic representation of an architecture 100 for exchanging data (e.g., messages and associated content) over a network. The architecture 100 may include a plurality of client devices 102. The client devices 102 may individually include, but are not limited to, mobile phones, desktop computers, laptop computing devices, portable digital assistants (PDAs), smart phones, tablet computing devices, ultrabooks, netbooks, multiprocessor systems, microprocessor-based or programmable consumer electronics systems, game consoles, set-top boxes, in-vehicle computers, wearable devices, one or more combinations of the foregoing, or any other communication device that a user may use to access one or more components included in the architecture 100.

[0024] Each client device 102 can host multiple applications, including client applications 104 and one or more third-party applications 106. Users can use client applications 104 to create content, such as videos, images (e.g., photos), audio, and media overlays. In one or more illustrative examples, client applications 104 may include social networking functions that enable users to create and exchange content. In various examples, client applications 104 may include messaging functions that can be used to send messages between instances of client applications 104 executed by various client devices 102. Messages created using client applications 104 may include videos, one or more images, audio, media overlays, text, content made using one or more authoring tools, annotations, etc. In one or more implementations, client applications 104 may be used to view and generate interactive messages, view the locations of other users of client applications 104 on a map, chat with other users of client applications 104, etc.

[0025] One or more users may be a person, machine, or other device that interacts with a client device (e.g., client device 102). In an example implementation, a user may not be part of architecture 100, but may interact with one or more components of architecture 100 via client device 102 or other device. In various examples, a user may provide input (e.g., touch screen input or alphanumeric input) to client device 102, and the input may be transmitted to other entities in architecture 100. In this case, in response to the user input, other entities in architecture 100 may transmit information to client device 102 for presentation to the user. In this manner, a user may interact with various entities in architecture 100 using client device 102.

[0026] The architecture 100 may also include one or more developer devices 108. The one or more developer devices 108 may individually include, but are not limited to, a mobile phone, a desktop computer, a laptop computing device, a portable digital assistant (PDA), a smart phone, a tablet computing device, an ultrabook, a netbook, a multiprocessor system, a microprocessor-based or programmable consumer electronic system, a game console, a set-top box, a car computer, a wearable device, one or more combinations of the foregoing, or any other communication device that a user may use to access one or more components included in the architecture 100. The developer device 108 may be used by one or more developers to at least one of create or modify a third-party application 106. As used herein, the terms "developer," "third-party developer," and "third-party application developer" are not limited to the actual developers themselves, but may include people and entities that host, provide, maintain, create, or have ownership rights with respect to a third-party application 106.

[0027] The developer device 108 may at least one of store or execute a content access application 110. The content access application 110 may enable the developer device 108 to at least one of obtain, view, or communicate with respect to a server, website, application, data storage device, or other content repository. In one or more illustrative examples, the content access application 110 may include a browser application. In one or more additional examples, the content access application 110 may access content that may be used in connection with the development, modification, or creation of at least one of the third-party application 106 or the client application 104.

[0028] Each instance of the client application 104 and the content access application 110 is capable of communicating and exchanging data with at least one of another instance of the client application 104, one or more third-party applications 106, another instance of the content access application 110, or a server system 112. The data exchanged between instances of the client application 104, between third-party applications 106, between instances of the content access application 110, between instances of the client application 104 and third-party applications 106, between instances of the content access application 110 and server system 112, and between instances of the client application 104 and server system 112 includes functionality (e.g., commands to activate functionality) and payload data (e.g., text, audio, image, video, or other multimedia data). Data exchanged between instances of client applications 104, between third-party applications 106, between at least one instance of client applications 104 and at least one instance of content access application 110, and between at least one instance of client applications 104 and at least one third-party application 106 can be exchanged directly from instances of applications executed by client device 102 and instances of applications executed by additional client devices 102 or by developer devices 108. In addition, data exchanged between client applications 104, between third-party applications 106, between content access application 110 and at least one of third-party applications 106 or client applications 104, and between at least one client application 104 and at least one third-party application 106 can be transmitted indirectly (e.g., via one or more intermediary servers) from an instance of an application executed by client device 102 to another instance of an application executed by an additional client device 102 or by a developer device 108. In one or more illustrative examples, the one or more intermediary servers used for indirect communication between applications can be included in server system 112.

[0029] The third-party application 106 may be separate from and distinct from the client application 104. The third-party application 106 may be downloaded and installed by the client device 102 separately from the client application 104. In various implementations, the third-party application 106 may be downloaded and installed by the client device 102 before or after the client application 104 is downloaded and installed. The third-party application 106 may be an application provided by an entity or organization different from the entity or organization providing the client application 104. The client device 102 may access the third-party application 106 using login credentials separate from the client application 104. That is, the third-party application 106 may maintain a first user account, while the client application 104 may maintain a second user account. In one or more implementations, the client device 102 may access the third-party application 106 to perform various activities and interactions, such as listening to music, watching videos, tracking workouts, viewing graphical elements (e.g., stickers), communicating with other users, and the like. As examples, third-party applications 106 may include social networking applications, dating applications, ride or car sharing applications, shopping applications, trading applications, gaming applications, imaging applications, music applications, video browsing applications, exercise tracking applications, health monitoring applications, graphic element or sticker browsing applications, or any other suitable application.

[0030] The server system 112 provides server-side functionality to at least one of the client application 104 or the content access application 110 via one or more networks 114. According to some example implementations, the server system 112 may be a cloud computing environment. For example, in one illustrative example, the server system 112 and one or more servers associated with the server system 112 may be associated with a cloud-based application. In one or more implementations, the client device 102 and the server system 112 may be coupled via one or more networks 114.

[0031] The server system 112 supports various services and operations provided to the client applications 104. Such operations include: sending data to the client applications 104; receiving data from the client applications 104; and processing data generated by the client applications 104. As an example, the data may include message content, media content, client device information, geolocation information, media annotations and overlays, message content persistence conditions, social network information, and live event information. The exchange of data within the architecture 100 is activated and controlled by functions available via a user interface (UI) of the client applications 104. The server system 112 may be at least one of implemented or maintained by a service provider that provides one or more services via the client applications 104. The one or more services may be related to social networking, messaging, content creation, content consumption, online retail, or one or more combinations thereof.

[0032] Although certain functions of the architecture 100 are described herein as being performed by the client application 104 or by the server system 112, the location of the functions within the client application 104 or within the server system 112 is a design choice. For example, it may be technically preferable to initially deploy certain technologies and functions within the server system 112, but later migrate the technologies and functions to the client application 104 where the client device 102 has sufficient processing power.

[0033] The server system 112 includes an application programming interface (API) server 116 that is coupled to and provides a programming interface to an application server 118. The application server 118 is communicatively coupled to a database server 120 that facilitates access to one or more databases 122. The one or more databases 122 may store data associated with information processed by the application server 118. The one or more databases 122 may be storage devices that store information such as unprocessed media content, original media content from a user (e.g., high-quality media content), processed media content (e.g., media content formatted for sharing with and viewing on a client device 102), contextual data associated with media content items, contextual data associated with a user device (e.g., a computing device or client device 102), media overlays, media overlay smart widgets or smart elements, user data, user device information, media content (e.g., videos and images), media content data (e.g., data associated with videos and images), computing device context data, serialization data, session data items, user device location data, mapping information, interactive message usage data, interactive message metrics data, etc. The one or more databases 122 may also store information associated with third-party servers, client devices 102, client applications 104, users, third-party applications 106, etc.

[0034] The API server 116 receives and sends data (e.g., commands and message payloads) between at least one of the client device 102 or the developer device 108 and the application server 118. Specifically, the application program interface (API) server 116 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the client application 104 to activate the functionality of the application server 118. The application program interface (API) server 116 exposes various functions supported by the application server 118, including: account registration, login functionality, sending messages from one instance of the client application 104 to another instance of the client application 104 via the application server 118, sending media files (e.g., images, audio, video) from the client application 104 to the application server 118 and possible access by another client application 104, setting up a collection of media content (e.g., a gallery, story, message collection, or media collection), retrieving a friend list of the user of the client device 102, retrieving such a collection, retrieving messages and content, adding friends to and removing friends from the social graph, locating friends within the social graph, and opening application events (e.g., related to the client application 104). The API server 116 may also provide the developer device 108 access to a framework that can be used to modify or customize the camera user interface relative to content corresponding to the third-party application 106.

[0035] The server system 112 may also include a web server 124. The web server 124 is coupled to the application server 118 and provides a web-based interface to the application server 118. To this end, the web server 124 handles incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0036] The application server 118 hosts multiple applications and subsystems, including a messaging application system 126, a media content processing system 128, a social networking system 130, a camera user interface system 132, and a content return communication system 134. The messaging application system 126 implements multiple message processing technologies and functions, particularly related to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the client application 104. For example, the messaging application system 126 can use email (email), instant messaging (IM), short message service (SMS), text, fax, or voice (e.g., voice over IP (VoIP)) messages to deliver messages via a wired network (e.g., the Internet), a plain old telephone service (POTS), or a wireless network (e.g., mobile, cellular, WIFI, long term evolution (LTE) or Bluetooth). The messaging application system 126 can aggregate text and media content from multiple sources into collections of content. The messaging application system 126 then makes these collections available to the client application 104. Given the hardware requirements for other processor and memory intensive processing of data, such processing may also be performed on the server side by the messaging application system 126 .

[0037] The media content processing system 128 is dedicated to performing various media content processing operations, typically on images, audio, or video received within the payload of a message or other content item at the messaging application system 126. The media content processing system 128 can access one or more data storage devices (e.g., database 122) to retrieve stored data to use and store the results of the processed media content when processing the media content.

[0038] The social networking system 130 supports various social networking functions and services and makes these functions and services available to the messaging application system 126. To do this, the social networking system 130 maintains and accesses an entity graph within the database 122. Examples of functions and services supported by the social networking system 130 include identifying other users of the client application 104 with whom a particular user has a relationship or is "following," and identifying other entities and interests of a particular user. The social networking system 130 may access location information associated with each of the user's friends or other social network connections to determine where they live or are currently located. In addition, the social networking system 130 may maintain a location profile for each of the user's friends that indicates the geographic location where the user's friends reside.

[0039] The camera user interface (UI) system 132 may be used to generate various versions of a camera user interface that is displayed via the client application 104. The camera user interface may display the field of view of at least one camera of the client device 102. Various versions of the camera user interface may be customized by a developer of the third-party application 106. In one or more scenarios, the customized version of the camera user interface may include modifications to a default version of the camera user interface.

[0040] In one or more implementations, the camera UI system 132 may obtain information from the developer device 108 to generate a version of the camera user interface corresponding to the third-party application 106. In one or more examples, the camera UI system 132 may provide the developer device 108 with access to the camera UI developer information 136 stored by the database 122. In various examples, the developer device 108 may access the camera UI developer information 136 via the content access application 110. The camera UI developer information 136 may include at least one of a tool, a library, a document, a computer-readable code, a process, a guide, one or more combinations of the foregoing, etc. that may be used to generate a version of the camera user interface associated with the third-party application 106. In various examples, the camera UI developer information 136 may include an SDK that may be used to create a camera user interface for the client application 104. In one or more additional examples, the camera UI developer information 136 may include one or more APIs that may be used to create a camera user interface for the client application 104. In one or more additional examples, the camera UI developer information 136 may indicate that at least a portion of features in a default version of the camera user interface may not be at least one of modified or removed by a developer of the third-party application 106 .

[0041] The camera UI system 132 may provide the developer device 108 with one or more user interfaces that may be used to design a camera user interface of the client application 104 based on the camera UI developer information 136. For example, the camera UI system 132 may provide one or more user interfaces that enable a developer of a third-party application 106 to add one or more user interface elements from a library of user interface elements to the camera user interface of the client application 104. In one or more examples, the camera UI developer information 136 may provide the developer of the third-party application 106 with one or more tools for designing user interface elements that may be selected to perform actions within the client application 104. In one or more additional examples, the camera UI developer information 136 may include a plurality of previously generated user interface elements corresponding to one or more actions that may be performed by the client application 104. In these scenarios, the developer of the third-party application 106 may select one or more user interface elements to be included in the camera user interface of the client application 104 from the plurality of previously generated user interface elements.

[0042] In addition, the camera UI system 132 may provide one or more user interfaces that enable developers of third-party applications to create layouts of features of the camera user interface of the client application 104. To illustrate, the camera UI system 132 may provide one or more user interface elements that enable developers of third-party applications 106 to indicate at least one of formatting or placement related to information included in the camera user interface of the client application 104. In these scenarios, the developers of the third-party applications 106 may indicate the location of at least one of image content, text content, video content, or user interface elements within the camera user interface of the client application 104. The developers of the third-party applications 106 may also indicate size information, font information, visual effect information, color information, or one or more combinations thereof for at least one of the text content, video content, or image content to be displayed in the version of the camera user interface based on the camera UI developer information 136. In addition, the camera UI system 132 may provide one or more user interfaces that enable the developer of the third-party application 106 to add content related to the third-party application 106 to the camera user interface of the client application 104 according to the camera UI developer information 136. In various examples, the content added to the camera user interface of the client application 104 may include at least one of image content, text content, or video content corresponding to the third-party application 106.

[0043] The one or more databases 122 may also store a third-party camera UI profile 138. The third-party camera UI profile 138 may indicate a customized version of the camera user interface of the client application 104 relative to the third-party application 106. In various examples, the third-party camera UI profile 138 may include information for generating a camera user interface when the client application 104 is launched or called from the corresponding third-party application 106. For example, the third-party camera UI profile 138 may indicate one or more user interface elements to be included in the camera user interface associated with the corresponding third-party application 106. The third-party camera UI profile 138 may also indicate layout and formatting information related to one or more user interface elements included in the camera user interface associated with the corresponding third-party application 106. In addition, the third-party camera UI profile 138 may include third-party camera UI data 140, which includes image content, text content, video content, or one or more combinations thereof obtained from the developer of the third-party application 106. The third-party camera UI data 140 may include data related to a logo of the third-party application 106, an identifier (e.g., a brand, company name, product name, etc.) related to the third-party application 106, animations related to the third-party application 106, augmented reality content related to the third-party application 106, or one or more combinations thereof. In one or more examples, at least a portion of the individual third-party camera UI profile 138 may include features of a default camera user interface of the client application 104. In various examples, the third-party camera UI profile 138 may indicate modifications to the default version of the camera user interface of the client application 104 for creating a customized version of the camera user interface for the third-party application 106.

[0044] In one or more illustrative examples, a user of client device 102 may launch an instance of third-party application 106. The instance of third-party application 106 may be launched in response to a selection of a user interface element, such as an icon, corresponding to third-party application 106. The selection of the user interface element corresponding to third-party application 106 may cause at least one user interface of third-party application 106 to be displayed via a display device of client device 102. In one or more examples, at least one user interface of third-party application 106 may include a user interface element that may be selected to launch an instance of client application 104 on client device 102. In various examples, launching an instance of client application 104 from third-party application 106 may cause at least one user interface of client application 104 to be displayed via client device 102. In one or more scenarios, after the instance of client application 104 is launched from third-party application 106, third-party application 106 may operate in the background. The user interface element corresponding to client application 104 included in the user interface of third-party application 106 may be associated with a uniform resource identifier, such as a link or address, which causes the camera user interface of client application 104 to be displayed.

[0045] Launching the client application 104 from the third-party application 106 may cause the camera user interface of the client application 104 to be displayed via the display device of the client device 102. In one or more examples, the client application 104 may obtain content to be included in the camera user interface from the server system 112. For example, the camera UI system 132 may determine a third-party camera UI profile 138 corresponding to the third-party application 106 and generate a data packet that may be sent to the client device 102 for the client application 104 to generate the camera user interface. In one or more illustrative examples, in response to receiving an indication from at least one of the client application 104 or the third-party application 106 that the client application 104 is being launched from the third-party application 106, the camera UI system 132 may query the database 122 to determine the third-party camera UI profile 138 corresponding to the third-party application 106. The camera UI system 132 may then extract information from the corresponding third-party camera UI profile 138 and send the information to the client device 102.

[0046] The image content or video content displayed in the camera user interface can be captured and sent back to the third-party application 106. For example, the camera user interface can be used to generate a photo or video and returned to the third-party application 106 for use within the third-party application 106. In various examples, the image content or video content can be modified using one or more authoring tools of the client application 104 to generate user content, which is then returned to the third-party application 106. In one or more additional examples, augmented reality content can be applied to the image content or video content, which is then provided back to the third-party application 106. The augmented reality content of the client application 104 can be used to modify the appearance of one or more objects included in the image content or video content captured via the camera user interface.

[0047] In one or more implementations, the content return communication system 134 can be implemented to send user content generated via the camera user interface of the client application 104 back to the third-party application 106. For example, the camera user interface of the client application 104 associated with the third-party application 106 can include such a user interface element that can be selected to return the user content created using the client application 104 to the third-party application 106. In these cases, the content return communication system 134 can receive an indication that the user interface element for sending the user content back to the third-party application 106 has been selected. In addition, the content return communication system 134 can also obtain the user content generated using the camera user interface of the client application 104. The content return communication system 134 can then access the content return data 142 stored in the database 122. The content return data 142 may include a uniform resource indicator or other address information associated with the user interface within the corresponding third-party application 106, where the user content created via the camera user interface of the client application 104 is to be provided to the corresponding third-party application 106. In one or more examples, the content return data 142 may indicate that user content created using the camera user interface of the client application 104 may be returned to a user interface of the third-party application 106 that is the same as the user interface from which the client application 104 was launched. In other examples, the content return data 142 may indicate that user content created using the camera user interface of the client application 104 may be provided to a user interface of the third-party application 106 that is different from the user interface from which the client application 104 was launched.

[0048] After determining the destination user interface for the user content created using the camera user interface of the client application 104, the content return communication system 134 can provide the user content to the third-party application 106 along with an indicator of the destination user interface of the third-party application 106. In this manner, the third-party application 106 can display the user content within the third-party application 106 and the user content can be used within the third-party application 106. In one or more illustrative examples where the third-party application 106 includes an e-commerce application, the user content generated by the camera user interface of the client application 104 can be added to a list of products being offered for purchase via the e-commerce application.

[0049] Figure 2 1 is a block diagram showing additional details about the server system 112 according to some examples. Specifically, the server system 112 is shown as including the client application 104 and the application server 118. The server system 112 contains multiple subsystems, which are supported on the client side by the client application 104 and on the server side by the application server 118. These subsystems include, for example, a transient timer system 202, a collection management system 204, an enhancement system 206, a map system 208, a game system 210, and a camera UI system 132.

[0050] The transient timer system 202 is responsible for enforcing temporary or time-limited access to content by the client applications 104 and the messaging application system 126. The transient timer system 202 incorporates a plurality of timers that selectively enable access (e.g., for presentation and display) of messages and associated content via the client applications 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.

[0051] 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, video, text, and audio) can be organized into "event galleries" or "event stories." Such collections can be made available for a specified time period (e.g., for 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 to the user interface of the client application 104 that provides notification that a particular collection exists.

[0052] In addition, the collection management system 204 includes a curation interface 212 that enables collection managers to manage and curate specific content collections. For example, the curation interface 212 enables an event organizer to curate a collection of content related to a specific event (e.g., to remove 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, users may be paid compensation for including user-generated content in a collection. In such cases, the collection management system 204 operates to automatically pay such users for using their content.

[0053] The enhancement system 206 provides various functions that enable a user to enhance (e.g., annotate or otherwise modify or edit) media content associated with content (e.g., messages) generated via the client application 104. For example, the enhancement system 206 provides functions related to generating and publishing media overlays for content processed by the server system 112. The enhancement system 206 is operable to provide media overlays or enhancements (e.g., image filters) to the client application 104 based on the geographic location of the client device 102. In another example, the enhancement system 206 is operable to provide media overlays to the client application 104 based on other information (e.g., 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 or images that can be superimposed on photos taken by the client device 102. In another example, the media overlay includes a location identification overlay (e.g., Venice Beach), a live event name, or a business name overlay (e.g., Beach Cafe). In another example, the augmentation system 206 uses the geolocation of the client device 102 to identify a media overlay that includes a business name at the geolocation of the client device 102. The media overlay may include other tags associated with the business. The media overlay may be stored in the database 122 and accessed through the database server 116.

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

[0055] In other examples, the enhancement system 206 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 enhancement system 206 associates the media overlays of the highest bidding merchant with the corresponding geographic location for a predefined amount of time.

[0056] The mapping system 208 provides various geo-location functions and supports the presentation of map-based media content and messages by the client application 104. For example, the mapping system 208 enables the display of (e.g., stored in Figure 3 A user icon or avatar (in the profile data 308 of the client application 104) is displayed to indicate the current location or past location of the user's "friends" and media content (e.g., a collection of messages including photos and videos) generated by these friends within the context of the map. For example, a message posted by the user to the server system 112 from a specific geographic location can be displayed to the "friends" of the particular user on the map interface of the client application 104 within the context of the specific location on the map. The user can also share his or her location and status information with other users of the server system 112 via the client application 104 (e.g., using an appropriate status avatar), where the location and status information is similarly displayed to the selected user within the context of the map interface of the client application 104.

[0057] The gaming system 210 provides various gaming functions within the context of the client application 104. The client application 104 provides a gaming interface that provides a list of available games that can be launched by a user within the context of the client application 104 and played with other users of the server system 112. The server system 112 also enables a particular user to invite other users to play a particular game by sending an invitation to such other users from the client application 104. The client application 104 also supports both voice messaging and text messaging (e.g., chatting) within the context of the game, provides leaderboards for the game, and also supports the provision of in-game rewards (e.g., coins and items).

[0058] The camera UI system 132 can obtain information from the developer of the third-party application that can be used to generate a customized version of the client application 104. In one or more examples, the camera UI system 132 can enable the developer of the third-party application 106 to design a camera user interface for the client application 104. The camera user interface can be used to generate user content accessible to the third-party application 106. In one or more examples, the user content can be modified with respect to the augmented reality content applied to the user content via the augmentation system 206 before being provided to the third-party application 106. In addition, the content return communication system 134 can be used to determine that the third-party application 106 from which the client application 104 was launched is to be returned from the client application 104. In response to returning the third-party application 106 from the client application 104, the content return communication system 134 can provide the third-party application 106 with access to the user content generated using the client application 104.

[0059] Figure 3 is a schematic diagram illustrating a data structure 300 that may be stored in a database 122 of a server system 112 according to one or more example implementations. Although the contents of the database 122 are illustrated as including a plurality of tables, it should be understood that data may be stored in other types of data structures (e.g., as an object-oriented database).

[0060] The database 122 includes message data stored in a message table 302. For any particular message, the message data includes at least message sender data, message recipient (or receiver) data, and a payload.

[0061] The entity table 304 stores entity data and is linked (e.g., referenced) to the entity graph 306 and profile data 308. The entities whose records are maintained within the entity table 304 may include individuals, corporate entities, organizations, objects, places, events, etc. Regardless of the entity type, any entity about which the server system 112 stores data may be an identified entity. Each entity is provided with a unique identifier and an entity type identifier (not shown).

[0062] The entity graph 306 stores information about relationships and associations between entities. As examples only, such relationships may be interest-based or activity-based social relationships, professional relationships (e.g., working in a common company or organization).

[0063] Profile data 308 stores multiple types of profile data about a particular entity. Based on the privacy settings specified by the particular entity, profile data 308 can be selectively used and presented to other users of the architecture 100. In the case where the entity is a person, profile data 308 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. A particular user can then selectively include one or more of these avatar representations in the content of messages or other data transmitted via the architecture 100 and on a map interface displayed to other users by the client application 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 choose to transmit at a particular time.

[0064] Where the entity is a group, the profile data 308 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).

[0065] Database 122 also stores enhancement data, such as overlays or filters, in enhancement table 310. Enhancement data is associated with and applied to videos (whose data is stored in video table 314) and images (whose data is stored in image table 316).

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

[0067] Another type of filter is a data filter, which can be selectively presented to the sending user by the client application 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 the sending user is traveling, the battery life of the client device 102, or the current time.

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

[0069] As described above, augmented data includes augmented reality content items, overlays, image transformations, AR images, and similar terms referring to modifications that can be applied to image data (e.g., videos or images). This includes real-time modifications, which are captured using the device sensor (e.g., one or more cameras) of the client device 102 and then used to modify the image when the image is displayed on the screen of the client device 102. This also includes modifications to stored content (e.g., video clips in a gallery that can be modified). For example, in a client device 102 with access rights 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 same content, multiple augmented reality content items that apply different pseudo-random motion 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 being captured by the sensor of the client device 102 will modify the captured data. Such data may be displayed only on the screen and not 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 feature may simultaneously display how different augmented reality content items will look within different windows of the display. For example, this may enable viewing multiple windows with different pseudo-random animations on the display at the same time.

[0070] Thus, data and various systems using augmented reality content items or other such transformation systems using such data to modify content 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 modifying or transforming such objects as they are tracked. In various implementations, 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 and animated textures of the models within a video to implement the transformations. In other examples, tracking of points on an object may be used to place an image or texture (which may be two-dimensional or three-dimensional) at the tracked location. In yet other examples, 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 through object detection, tracking, and placement.

[0071] Real-time video processing can be performed using any type of video data (e.g., video streams, video files, etc.) stored in the memory of any type of computerized system. For example, a user can load a video file and save it in the memory of the device, or a video stream can be generated using the device's sensors. In addition, computer animation models can be used to process any object, such as human faces and parts of the human body, animals, or non-living things (e.g., chairs, cars, or other objects).

[0072] 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 frame of the video, the element to be transformed is detected and tracked. The elements of the object are modified according to the modification request, 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 frame transformations that mainly involve changing the form of the elements of the object, the feature points of each element of the object are calculated (for example, using active shape models (ASM) or other known methods). Then, a grid based on the feature points is generated for each element of at least one element of the object. 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 set of first points is generated for each element based on the modification request, and a set of second points is generated for each element based on the set of first points and the modification request. Then, the frame of the video stream can be transformed by modifying the elements of the object based on the set of first points and the set of second points and the grid. In such a method, the background of the modified object can also be changed or distorted by tracking and modifying the background.

[0073] In some examples, a transformation that changes certain areas of an object using elements of an object can be performed by calculating feature points of 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 are generated based on these points. Then, the elements of the object are tracked by aligning the area of ​​each element with the position of 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 part 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 implementations, 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 the entire state space to be used to determine options for model animation.

[0074] In some examples of 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.

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

[0076] In various examples, a landmark search begins with a mean shape aligned with the position and size of a face determined by a global face detector. Such a search then repeats the steps of suggesting 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 a global shape model until convergence occurs. In one or more systems, template matching alone is 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.

[0077] 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, emotion transformations (e.g., changing a face from a frown to a smile), state transitions (e.g., aging an object, reducing apparent age, changing gender), style transfer, 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.

[0078] The computer animation model for transforming image data can be used by the following system: in the system, a user can use a client device 102 having a neural network operating as part of a client application 104 operating on the client device 102 to capture an image or video stream of the user (e.g., a selfie). The transformation system operating within the client application 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 image data, or the computer animation model can exist in association with the interface described herein. The modification icon includes the following changes, which can be the basis for modifying the face of the user within the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates the process of transforming the image of the user 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 is selected, the modification result is presented to the user in real time or near real time. In addition, when the video stream is being captured, the modification can be persistent and the selected modification icon remains toggled. A machine-learned neural network can be used to implement such modification.

[0079] 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 the selection of a particular computer animation model and content capture (e.g., initiated from a content creator user interface). In various implementations, the modifications can be persistent after the initial selection of the modification icon. The user can 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 to other areas of the imaging application. In the case of multiple faces being modified by the transformation system, the user can globally turn the modification on or off by tapping or selecting a single face modified and displayed within the graphical user interface. In some implementations, individual faces in a group of multiple faces can be modified individually, or such modifications can be individually switched by tapping or selecting an individual face or a series of individual faces displayed within the graphical user interface.

[0080] The story table 312 stores data about a collection of messages and associated images, video or audio data that are compiled into a collection (e.g., a story or gallery). The creation of a particular collection can be initiated by a particular user (e.g., each user whose record is stored in the entity table 304). 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 client application 104 may include a user-selectable icon to enable the sending user to add specific content to his or her personal story.

[0081] 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 different locations and events. Users whose client devices have location services enabled and who are at a co-located event at a particular time may be presented with the option of contributing content to a particular live story, for example, via a user interface of the client application 104. Live stories may be identified to the user by the client application 104 based on his or her location. The end result is a "live story" told from a community perspective.

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

[0083] As mentioned above, the video table 314 stores video data, which in one example is associated with a message whose record is saved in the message table 302. Similarly, the image table 316 stores image data associated with a message whose message data is stored in the entity table 304. The entity table 304 can associate various enhancements from the enhancement table 310 with the various images and videos stored in the image table 316 and the video table 314.

[0084] The database 122 may also store a third-party UI data table 318. The third-party UI data table 318 may include data structures of various third-party applications 106 for launching an instance of the client application 104. The data structure included in the UI data table 318 regarding the corresponding third-party application 106 may indicate information that may be used to generate a camera user interface of the client application 104. The information may indicate at least one of text content, image content, or video content that may be included in the camera user interface of the client application 104. In various examples, the data structure included in the third-party UI data table 318 may indicate a storage location of information to be included in the camera user interface of the client application 104, such as at least one of one or more uniform resource indicators, one or more links, one or more addresses, or one or more file paths. The data structure included in the third-party UI data table 318 may also store information indicating a layout of features included in the camera user interface of the client application 104. The layout may include one or more user interface elements to be included in the camera user interface and the corresponding positions of the one or more user interface elements. The layout may also include location information of content related to the corresponding third-party application 106 within the camera user interface of the client application 104. In one or more additional examples, for the corresponding third-party application 106, the data structure included in the third-party UI data table 318 may include at least one of information indicating editing actions that a user of the client application 104 can perform on content included in the camera user interface or actions that can be performed within the client application 104 on content generated using the camera user interface of the client application 104.

[0085] In addition, the database 122 can store a content return data table 320 that includes information indicating the destination of user content generated using the client application 104 and returned to the third-party application 106. For example, in response to returning from the third-party application 106 to the client application 104, the content return data table 320 can include, for each third-party application 106, one or more uniform resource indicators corresponding to the destination location of the user content.

[0086] Figure 44 is a schematic diagram showing an example framework of content 400 according to some implementations. Content 400 may be generated by a client application 104. In various examples, content 400 may be generated by a first instance of client application 104 and transmitted to at least one of a second instance of client application 104 or server system 112. In the event that content 400 includes messages, content 400 may be used to populate message table 302 stored in database 122 and accessible by application server 114. In one or more implementations, content 400 may be stored in memory as "in-transit" or "in-flight" data of at least one of client device 102 or application server 114. Content 400 is shown as including at least a portion of the following components:

[0087] Content identifier 402 : a unique identifier that identifies the content 400 .

[0088] Content text payload 404 : text to be generated by a user via the user interface of the client device 102 and included in the content 400 .

[0089] Content image payload 406 : Image data captured by the camera component of the client device 102 or retrieved from the memory component of the client device 102 and included in the content 400 . The image data for the content 400 sent or received may be stored in the image table 316 .

[0090] Content 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 content 400 . The video data for the content 400 sent or received may be stored in the video table 314 .

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

[0092] Content enhancement data 412: Enhancement data (e.g., filters, stickers, or other annotations or enhancements) representing enhancements to be applied to the content image payload 406, content video payload 408, or content audio payload 410 of the content 400. The enhancement data for the transmitted or received content 400 may be stored in the enhancement table 310.

[0093] Content duration parameter 414: A parameter value indicating the amount of time, in seconds, that one or more portions of content 400 (e.g., content image payload 406, content video payload 408, content audio payload 410) are to be presented to or made accessible to a user via client application 104.

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

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

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

[0097] • Content 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 content 400 was generated and from which the content 400 was sent.

[0098] • Content 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 content 400 is addressed.

[0099] Modified camera user interface identifier 426: One or more identifiers of additional content related to the third-party application 106 that may be included in the content 400 or accessible via the client application 104. The modified camera user interface identifier 426 may correspond to text content, image content, video content, audio content, or one or more combinations thereof related to the third-party application 106.

[0100] • Content return identifier 428: One or more identifiers that indicate a destination for the content. The content return identifier 428 may indicate a user interface of the third party application 106 to which the content 400 is accessible.

[0101] The data (e.g., values) of the various components of the content 400 may correspond to pointers to locations in the table where the data is stored. For example, the image value in the content image payload 406 may be a pointer (or address) to a location within the image table 316. Similarly, the value within the content video payload 408 may point to data stored within the video table 314, the value stored within the content enhancement data 412 may point to data stored in the enhancement table 310, the value stored within the content story identifier 418 may point to data stored in the story table 312, and the values ​​stored within the content sender identifier 422 and the content recipient identifier 424 may point to user records stored within the entity table 304. The modified camera user interface identifier 426 may point to information related to the third-party application 106 stored by the third-party UI data table 318, which may be presented by the client application 104 in conjunction with the content 400. In addition, the content return identifier 428 may point to information in the content return data table 320, such as a uniform resource indicator, which may indicate the destination of the content 400 when the content 400 is returned to the third-party application 106.

[0102] Figure 5 is a diagrammatic representation of an architecture 500 illustrating accessing a client application 104 from a third-party application 106 and returning content from the client application 104 to the third-party application 106, according to one or more example implementations. The architecture 500 may include a server system 112 including a camera user interface system 132 and a content return communication system 134. The camera user interface system 132 may enable a developer of a third-party application 106 to customize a camera user interface of the client application 104. For example, an instance of the client application 104 may be launched from an instance of the third-party application 106, and a target user interface displayed when the client application 104 is launched may include a customized version of the camera user interface of the client application 104. In this manner, a customized version of the camera user interface of the client application 104 may be displayed in response to launching the client application 104 from the third-party application 106, rather than a default home page of the client application 104. Additionally, the content return communication system 134 may provide the third party application 106 access to user content created within the client application 104 after the client application 104 is launched from the third party application 106 .

[0103] The camera user interface system 132 may provide a camera user interface developer framework 502 that developers of third-party applications 106 may use to generate customized versions of camera user interfaces for client applications 104. The camera user interface developer framework 502 may include a plurality of tools that developers of third-party applications 106 may use to design camera user interfaces for client applications 104. For example, the camera user interface developer framework 502 may include a software developer toolkit that may be used to design and generate camera user interfaces for client applications 104. Additionally, the camera user interface developer framework 502 may include example software code, rules, one or more application programming interfaces, or one or more combinations thereof. In various examples, the rules included in the camera user interface developer framework 502 may include specifications for designing and generating content and parameters for a camera user interface so as to efficiently implement a customized version of a camera user interface for a client application 104 through the server system 112. In one or more examples, the rules of the camera user interface developer framework 502 may indicate file types supported by the camera user interface for the client application 104. The rules of the camera user interface developer framework 502 may also indicate modifiable features of the camera user interface of the client application 104 and non-modifiable features of the camera user interface of the client application 104. In addition, the camera user interface developer framework 502 may indicate a number of user interface elements that may be included in a customized version of the camera user interface of the client application 104, actions that may be performed on content included in the camera user interface of the client application 104, or a combination thereof.

[0104] The server system 112 may provide developer devices 108 of developers of third-party applications 106 with access to the camera user interface developer framework 502. In various examples, the camera user interface system 132 may provide camera user interface developer framework information 504 to one or more developer devices 108. In one or more examples, the camera user interface developer framework information 504 may include or be provided via one or more user interfaces that may display information related to the camera user interface developer framework 502 and may include one or more user interface elements that may be selected to implement features of the camera user interface developer framework 502. The camera user interface developer framework information 504 may include one or more user interface elements that may capture input indicating at least one of: user interface elements to be included in a custom camera user interface of a client application 104, information related to a third-party application 106 to be displayed within a custom camera user interface of a client application 104, or information about a custom camera user interface of a client application 104 and a layout of user interface elements.

[0105] In one or more implementations, the developer device 108 may send the camera UI information 506 to the server system 112 according to the camera user interface developer framework 502. The camera UI information 506 may indicate changes made to the default version of the camera user interface of the client application 104 for generating a customized version of the camera user interface. In one or more examples, the camera UI information 506 may indicate at least one of one or more user interface elements that may be added to the camera user interface or one or more user interface elements that may be removed from the camera user interface. The camera UI information 506 may also indicate at least one of an information layout or a user interface element layout of the camera user interface of the client application 104. In another example, the camera UI information 506 may indicate operations that may be performed on content that may be displayed via the camera user interface. In various examples, the camera UI information 506 may also include brand information related to the third-party application 106, such as the name of the third-party application, a logo of the third-party application 106, and the like. In another example, the camera UI information 506 may include at least one of image content, video content, audio content, or text content related to the third-party application 106. The camera UI information 506 may be used to generate a camera user interface profile for the third-party application 106.

[0106] The developer device 108 may also send content communication information 508 to the server system 112. The content communication information 508 may include a destination within the third-party application 106 for the user content generated using the client application 104. In one or more examples, the content communication information 508 may include a uniform resource indicator corresponding to the destination of the user content within the third-party application. In various examples, the content communication information 508 may indicate the following user interface of the third-party application 106: the user interface is used to display the user content when returning to the third-party application 106 from the client application 104.

[0107] In various implementations, a user 510 of a client device 102 can launch an instance of a third-party application 106. The third-party application 106 can include a gaming application, a health and fitness application, a media consumption application, a content access application, a navigation application, an e-commerce application, a social networking application, one or more combinations of the foregoing, and the like. A third-party application user interface 512 can be displayed via the third-party application 106 and can include content 514. The third-party application user interface 512 can also include a user interface element 516 that can be selected to launch an instance of the client application 104 on the client device 102. In one or more examples, the third-party application 106 can continue to operate after launching the instance of the client application 104.

[0108] In various examples, in response to the selection of the user interface element 516, a client application launch request can be sent to the server system 112 to obtain camera UI information 506 that can be used to generate a camera user interface 518 within the client application 104. For example, in response to receiving the client application launch request, the camera user interface system 132 can retrieve information for presenting a camera user interface 518 associated with the third-party application 106. The information retrieved by the camera user interface system 132 in response to the client application launch request can include at least a portion of the information included in the camera user interface profile of the third-party application 106. The camera user interface system 132 can assemble the information associated with the third-party application 106 to be used to generate the camera user interface 518 and send the information to the client device 102. The client application 104 can then generate the camera user interface 518 using the information obtained from the camera user interface system 132. In one or more examples, the camera user interface system 132 may instruct another system—eg, a system implemented and maintained by a third party providing the third party application 106 —to send information to the client device 102 to generate the camera user interface 518 .

[0109] The camera user interface 518 may include content 520. The content 520 may include at least one of image content or video content contained in the field of view of at least one camera of the client device 102. For example, the content 520 may include live content being captured by at least one camera of the client device 102. In one or more additional examples, the camera user interface 518 may include content that was previously included in the live field of view of the camera and subsequently captured, so that at least one of the image data or the video data is generated based on the live content. In addition, the camera user interface 518 may include a set of user interface elements 522. The set of user interface elements 522 may include a plurality of user interface elements that may be selected to perform at least one of the following: modify the settings of the camera of the client device 102 or activate one or more tools that can be used to generate a modified version of the user content 520.

[0110] In addition, the camera user interface 518 may include an additional user interface element 524. In one or more examples, the additional user interface element 524 may be selectable for capturing live content displayed in the camera user interface 518. In additional examples, where the camera user interface 518 displays user content 520 that has been captured or received from other sources, such as a third-party application 106, the additional user interface element 524 may be selectable for returning the user content 520 to the third-party application 106. In various examples, returning the third-party application 106 may include initiating execution of an instance of the third-party application 106 by the client device 102, or reinstantiating an instance of the third-party application 106 that was operating in the background while the user 510 was generating the user content 520 using the client application 104.

[0111] In various examples, after user content is generated in response to selection of additional user interface element 524, a subsequent user interface ( Figure 5510). In one or more examples, the subsequent user interface may include a user interface element that can be selected to apply one or more authoring tools to the user content 520. The one or more authoring tools may apply at least one of text content, audio content, video content, or image content to the user content 520. The one or more authoring tools may also modify the appearance of one or more objects included in the user content 520 by applying one or more visual effects to the user content 520. The one or more authoring tools may implement at least one of overlays, annotations, filters, or augmented reality content for the user content 520. In addition, the subsequent user interface may include one or more user interface elements that can be selected to distribute the user content 520 or a modified version of the user content 520. In one or more illustrative examples, the user content 520 or a modified version of the user content 520 may be shared with one or more additional users of the client application 104, such as one or more users of the client application 104 included in the social network of the user 510.

[0112] In one or more implementations, in response to a request from the client application 104 to return the third-party application 106, a content return request 526 may be sent from the client device 102 to the server system 112. In one or more examples, the content return request 526 may include an identifier of the third-party application 106. The content return communication system 134 may identify content return information 528 related to the third-party application 106 based on the identifier of the third-party application 106 included in the content return request 526. The content return communication system 134 may send the content return information 528 to the client device 102, and the client device 102 may use the content return information 528 to determine a destination user interface within the third-party application 106. In various examples, at least one of the client device 102 or the server system 112 may use the content return information 528 to provide the third-party application 106 with access to the user content 520.

[0113] After the client device 102 returns to displaying the user interface related to the third-party application 106 after exiting the client application 104, the client application user content 530 may be displayed via the additional user interface 532 of the third-party application 106. The client application user content 530 may include at least one of image content, video content, or audio content captured via one or more input devices of the client device 102. In addition, the client application user content 530 may include an edited version of the content captured via the client device 102, such as content that has been edited using one or more authoring tools of the client application 104 or by applying one or more augmented reality content items to the content captured via one or more input devices of the client device 102. In addition to displaying the client application user content 530, the additional user interface 532 of the third-party application 106 may include additional information 534. In one or more examples, the additional user interface 532 may be used to incorporate the client application user content 530 into the third-party application 106. In the case where the third-party application 106 is an e-commerce application, the client application user content 530 may include at least one of image content or video content of one or more items that can be purchased via the e-commerce platform. In these cases, client application user content 530 may be incorporated into a listing associated with an offer for sale of one or more items. In one or more additional examples, third-party application 106 may include a social networking application, and client application user content 530 may include at least one of image content or video content containing user 510. In these scenarios, client application user content 530 may be incorporated into an account of user 510 with the social networking application, such as a profile picture.

[0114] Figure 6 and Figure 7 A flowchart of one or more implementations of a process for accessing a camera user interface of a client application from a third-party application and providing user content generated using the camera user interface back to the third-party application. These processes may be embodied in computer-readable instructions for execution by one or more processors, such that the operations of these processes may be performed in part or in whole by functional components of at least one of the client application 104 or the server system 112. Thus, in some cases, the following reference to Figure 6 and Figure 7 These processes are described by way of example. However, in other implementations, Figure 6 and Figure 7 At least some of the operations in the described processes may be deployed on various other hardware configurations. Figure 6 and Figure 7The described processing is not intended to be limited to the server system 112 or the client device 102, but may be implemented in whole or in part by one or more additional components. Although the described flowcharts may display the operations as sequential processing, many operations may be performed in parallel or simultaneously. In addition, the order of the operations may be rearranged. When the operations of the processing are completed, the processing terminates. The processing may correspond to a method, a process, an algorithm, etc. The operations of a method may be performed in whole or in part, may be performed in combination with some or all operations in other methods, and may be performed by any number of different systems (e.g., the systems described herein) or any part thereof (e.g., a processor included in any system).

[0115] Figure 6 600 is a flowchart showing an example operation of a process 600 according to one or more example implementations, the process 600 being used to implement a framework for generating a camera user interface for a client application by a third party, the camera user interface being used to generate content provided to the third party application. The process 600 may include: at operation 602, generating a framework associated with creating a camera user interface displayed via a client application. The framework may provide at least one of a parameter or feature corresponding to a modification to the camera user interface. In one or more examples, the framework may include at least one of a software developer toolkit, computer-readable instructions, one or more application programming interfaces, or one or more rules for creating a customized version of a camera user interface for a third party application. In one or more illustrative examples, the camera user interface may be created by modifying a default version of the camera user interface according to the framework. In addition, the framework may enable content generated using a client application via the camera user interface to be provided from the client application to the third party application.

[0116] The framework may include camera user interface developer information accessible to an additional computing device of a developer of a third-party application. In various examples, the camera user interface developer information may be accessed via one or more user interfaces. The one or more user interfaces may include user interface elements that capture input associated with creating a version of the camera user interface corresponding to the third-party application. In one or more examples, the one or more user interfaces may capture a first input for adding one or more user interface elements to the camera user interface. In various examples, the first input may also involve removing one or more user interface elements from the version of the camera user interface. The user interface elements included in the initial version of the camera user interface may be selectable for causing one or more operations supported by the client application to occur. One or more user interfaces associated with the framework may also capture a second input for adding content to the camera user interface. For illustration, the second input may correspond to adding content associated with a third-party application to the camera user interface. In one or more illustrative examples, the content associated with the third-party application added to the camera user interface may correspond to at least one of text content, image content, video content, or audio content associated with the third-party application.

[0117] In one or more implementations, the framework may indicate features that cannot be removed from the default version of the camera user interface. That is, when generating a customized version of the camera user interface for a third-party application, the framework may impose one or more restrictions on the features included in the default version of the camera user interface. In one or more examples, the framework may indicate at least one of: one or more user interface elements that can be modified in the default version of the camera user interface, or one or more user interface elements that cannot be modified in the default version of the camera user interface. In various examples, the framework may enable developers of third-party applications to specify the layout of features included in the camera user interface.

[0118] At operation 604, processing 600 may include receiving content communication information from an additional computing device of a developer of a third-party application and camera user interface information corresponding to the framework. The camera user interface may include multiple user interface elements for generating user content including at least one of image content or video content. The image content or video content may be captured by at least one camera of a client device. In various examples, the image content or video content may be included in the field of view of the camera. In one or more examples, at least a portion of the multiple user interface elements may be selectable for capturing image content or video content using at least one camera to generate user content. In addition, at least a portion of the multiple user interface elements may be selectable for modifying the user content by using one or more authoring tools of a client application related to the user content or by applying augmented reality content to at least one of the user content.

[0119] The content communication information may indicate a user interface of the third-party application for displaying the user content. For example, the content communication information may include a uniform resource indicator corresponding to a destination user interface of the third-party application to which the user content is provided from the client application. In one or more examples, the destination user interface may be the same user interface of the third-party application as the user interface from which the client application was launched. In addition, the destination user interface may be a user interface of the third-party application that is different from the user interface from which the client application was launched.

[0120] A customized version of the camera user interface of the client application generated according to the framework by one or more developers of the third-party application can be stored in one or more databases. In various examples, features of the customized version of the camera user interface can be stored in association with an identifier of the third-party application. In this way, when the client application is launched from the third-party application, features of the camera user interface associated with the third-party application can be retrieved and used to generate a customized version of the camera user interface that is displayed when the client application is launched from the third-party application.

[0121] In addition, at operation 606, processing 600 may include determining a third-party camera user interface profile corresponding to the third-party application. In one or more implementations, a server system associated with a service provider that maintains or implements at least one of the client applications may receive a request to launch an instance of the client application from the third-party application. The request may include or indicate an identifier corresponding to the third-party application. In these scenarios, the server system may query a database using the third-party application identifier and identify a camera user interface profile corresponding to the third-party application. In one or more examples, the third-party application may be associated with multiple camera user interface profiles that are associated with different user interfaces of the third-party application from which the client application may be launched. In these cases, each camera user interface profile associated with the third-party application may be associated with a different identifier.

[0122] After identifying the third-party camera user interface profile corresponding to the third-party application, process 600 may include sending information corresponding to the third-party camera user interface profile to the client device at operation 608. The client application may use the information to generate a login user interface from the third-party application to the client application. The login user interface may include a customized version of the camera user interface corresponding to the third-party application.

[0123] The camera user interface can be used to create user content by capturing at least one of the image content or video content within the field of view of the camera of the client device using one or more user interface elements of the camera user interface. The user content can also be modified using one or more authoring tools of the client application or at least one of the augmented reality content that can be executed by the client application. In various examples, at least one of the one or more authoring tools or augmented reality content items that can be used to modify the user content can be provided by one or more developers of third-party applications. In one or more illustrative examples, at least one of the one or more authoring tools or augmented reality content can be applied to the user content via one or more subsequent user interfaces different from the initial user interface for capturing at least one of the image content or video content. In various examples, one or more subsequent user interface elements can be designed by one or more developers of third-party applications according to the framework.

[0124] In addition, the process 600 may include, at operation 610, determining to return user content created using the camera user interface to the third-party application. In one or more examples, at least one user interface of the client application for generating user content may include a user interface element that can be selected to provide the user content back to the third-party application. In response to the selection of the user interface element, a request for providing the third-party application with access to the user content may be sent to the server system. The determination to return the user content to the third-party application may be based on receiving the request for providing access to the user content.

[0125] At operation 612, processing 600 may include causing user content to be provided to a third-party application according to content communication information. For example, after determining that user content is to be provided to a third-party application, the identifier of the third-party application may be used to retrieve content communication information indicating the destination of the user content in the third-party application, such as a uniform resource indicator, storage location, path or address. In one or more examples, the server system may send user content to an additional server system that maintains or implements at least one of the third-party application according to the content communication information. The additional server system may then communicate with the client device to initiate the execution of an instance of the third-party application and display the user interface of the third-party application including the user content. In one or more illustrative examples, user content may be sent to the additional server system according to one or more API calls associated with an API provided by one or more developers of the third-party application. In one or more additional examples, the server system may send user content to the client device according to the content communication information without first sending the user content to the additional server system.

[0126] Figure 7 700 for accessing a camera user interface of a client application from a third-party application and generating content for the third-party application via the camera user interface, according to one or more example implementations. At operation 702, process 700 may include generating a user interface of the third-party application, the user interface including a user interface element that may be selected to initiate execution of an instance of the client application. In various examples, a developer of a third-party application may provide access to the client application from a third-party application by adding a user interface element to one or more user interfaces of the third-party application that causes the client application to be launched.

[0127] Additionally, at operation 704, processing 700 may include receiving input indicating a selection of a user interface element. In one or more examples, in response to the selection of the user interface element, at least one request may be sent to a service provider to obtain information that may be used to present and display a camera user interface of the client application. In one or more examples, the selection of the user interface element may cause a uniform resource indicator corresponding to a target user interface or a destination user interface generated when the client application is launched to be identified. In one or more illustrative examples, the target user interface may include a camera user interface of the client application that partially displays a field of view of at least one camera of the client device.

[0128] Process 700 may include generating a camera user interface for the client application in response to the input and based on the third-party camera user interface data, at operation 706. The third-party camera user interface data may indicate user interface elements to be included in a customized version of the camera user interface associated with the third-party application. The customized version of the camera user interface data may also indicate a layout of features of the camera user interface. In addition, the camera user interface data may indicate information related to the third-party application that may be displayed in the camera user interface, such as an identifier of the third-party application.

[0129] At operation 708, processing 700 may include generating user content via a camera user interface, the user content including at least one of image content or video content captured by a camera of a client device executing an instance of a client application. In one or more examples, the user content may be generated in response to a selection of a user interface element of the camera user interface, the selection of the user interface element causing a data structure to be created, the data structure including at least one of: image data or video data corresponding to at least one of image content or video content included in a field of view of the camera when the user interface element is selected. In the case where image data is captured, the user interface element may be selected a single time for each image data structure generated. Additionally, in the case where video data is captured, the user interface element may be selected multiple times for each video data structure generated.

[0130] In addition, at operation 710, processing 700 may include generating an additional user interface of a client application, the additional user interface including user content and additional user interface elements, which may be selected to initiate the execution of an instance of a third-party application and provide user content to the third-party application. For example, after generating user content by capturing at least one of image content or video content and creating a data structure storing at least one of image content or video content, an additional user interface including at least one of image content or video content containing user content may be displayed. In this way, the camera user interface captures the live field of view of the camera of the client device, while the additional user interface includes at least one of image content or video content generated based on live field of view data. In one or more scenes, the additional user interface may include a user interface element that may be selected to apply one or more authoring tools to user content. In various examples, augmented reality content may be applied to user content within the additional user interface based on the selection of one or more user interface elements corresponding to the augmented reality content item. In an additional example, in response to selection of one or more augmented reality content user interface elements corresponding to one or more augmented reality content items, augmented reality content can be applied to at least one of image content or video content shown in a live field of view of the camera user interface.

[0131] In response to the selection of the additional user interface element, the third-party application can be launched, and the user content can be provided to the destination user interface of the third-party application. The user content can then be used within the third-party application. In one or more examples, the user content can be retrieved from the memory of the client device, and the user content can be provided to the third-party application based on the content communication information indicating the destination user interface of the third-party application. In other cases, the third-party application can receive the user content from a server system, such as a server system associated with the client application or a server system associated with the third-party application.

[0132] Figure 8 8 is an illustration of a user interface 800 showing a view of a camera and formatted according to a framework used by a developer of a third-party application, according to one or more example implementations. The user interface 800 may be displayed via a display device of a client device 102 and generated by a client application (e.g., client application 104) executed by the client device 102. The user interface 800 may be displayed in response to launching the client application 104 from a third-party application 106. Figure 8In an illustrative example of , the third-party application 106 may include an e-commerce application. In one or more examples, the user interface 800 may include a customized version of the camera user interface of the client application 104, which is designed by one or more developers of the e-commerce application using a framework provided by a service provider associated with the client application 104.

[0133] The user interface 800 may include a layout of information and user interface elements designed by one or more developers of the third-party application 106. For example, the user interface 800 may include live content 802 captured in the field of view of the camera 804 of the client device 102. In addition, the user interface 800 may include an identifier 806 of an e-commerce application. In one or more examples, the identifier 806 may correspond to third-party application information provided by the developer of the e-commerce application. The user interface 800 may also include a set of user interface elements 808. The set of user interface elements 808 may include a plurality of user interface elements that may be selected to implement various actions related to generating user content based on the live content 802, for example, capturing at least one of image content or video content based on the live content 802. In one or more examples, the set of user interface elements 808 may include a user interface element for rotating the view of the field of view content 802 (e.g., rotating from a longitudinal view to a transverse view or from a transverse view to a longitudinal view). In addition, the set of user interface elements 808 may include a user interface element for modifying a flash setting of the camera 804, a user interface element for implementing a timer for capturing content within the field of view of the camera 804, and a user interface element that can be selected to add a grid to the user interface 800, etc.

[0134] In addition, user interface 800 may include user interface element 810, which may be selected to capture live content 802 and create a data structure for storing at least one of image data or video data corresponding to the captured live content 802. In various examples, capturing live content 802 may generate user content stored in the data structure. The user interface element may be selected a single time to generate image content from live content 802, and may be selected multiple times to generate video content from live content 802, such as a first time to start recording video content, and a second time to end recording video content. Although in Figure 8104, but the user interface 800 may include one or more user interface elements that can be selected to apply one or more augmented reality content items to the live content. In addition, the user interface 800 may include one or more additional user interface elements to navigate within the client application 104 or implement at least one of the search functions of the client application 104.

[0135] Fig. 9 804 and includes a plurality of user interface elements that can be selected to apply one or more authoring tools to the user content. User interface 900 can be displayed via a display device of client device 102 and generated by a client application, such as client application 104, executed by client device 102. In various examples, user interface 900 can be displayed after user interface 800. For illustration, user interface 900 can be displayed after the user interface 800. Figure 8 The user interface 900 is displayed after one or more selections are made to the user interface element 810 of the display. In addition, the user content 902 may be associated with the user interface element 810 in response to the user interface element 810. Figure 8 One or more selections of user interface elements 810 are captured Figure 8 The live content 802 is related.

[0136] In various examples, user interface 900 may include a set of user interface elements 904. The set of user interface elements 904 may relate to tools of client application 104 that may be used to modify user content 902. The tools may be used to apply one or more overlays, one or more annotations, one or more augmented reality content items, one or more combinations of the foregoing, etc. to user content. Applying at least one of the tools to user content 902 may create a modified version of user content 902.

[0137] User interface 900 may also include user interface element 906 that may be selected to provide at least one of user content 902 or an edited version of user content 902 to a third-party application 106 from which client application 104 was launched. In one or more illustrative examples, in response to selection of user interface element 906, an additional user interface that is part of third-party application 106 and includes user content 902 or a modified version of user content 902 may be displayed. Fig. 9902. Although not shown in the illustrative example of FIG. 904, the user interface 900 may include one or more additional user interface elements that may be selected to distribute at least one of the user content 902 or the modified version of the user content 902 using the client application 104. For example, the user interface 900 may include a user interface element that may be selected to generate a message with one or more recipients that includes at least one of the user content 902 or the edited version of the user content 902. Additionally, the user interface 900 may also include the following user interface elements that may be selected to make at least one of the user content 902 or the modified version of the user content 902 accessible to one or more additional users of the client application 104, such as one or more users of the client application 104 included in the social network of the user of the client application 104 that created the user content 902.

[0138] Fig.10 1 is a block diagram illustrating components of a machine 1000 capable of reading instructions from a machine-readable medium (e.g., a machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some example implementations. Specifically, Fig.10A diagrammatic representation of a machine 1000 in the example form of a computer system is shown, within which instructions 1002 (e.g., software, programs, applications, applet, app, or other executable code) for causing the machine 1000 to perform any one or more of the methods discussed herein may be executed. Thus, the instructions 1002 may be used to implement the modules or components described herein. The instructions 1002 convert 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. In alternative implementations, the machine 1000 operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1000 may operate as 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, web appliances, a network router, a network switch, a network bridge, or any machine capable of executing instructions 1002 that specify actions to be taken by the machine 1000, either sequentially or otherwise. In addition, while only a single machine 1000 is shown, the term "machine" should also be taken to include a collection of machines that individually or jointly execute instructions 1002 to perform any one or more of the methodologies discussed herein.

[0139] The machine 1000 may include a processor 1004, a memory / storage device 1006, and an I / O component 1008, which may be configured to communicate with each other, for example, via a bus 1010. In an example implementation, the processor 1004 (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 1012 and a processor 1014 that may execute instructions 1002. The term "processor" is intended to include a multi-core processor 1004, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions 1002 simultaneously. Although Fig.10Multiple processors 1004 are shown, but the machine 1000 may include: a single processor 1012 with a single core, a single processor 1012 with multiple cores (e.g., a multi-core processor), multiple processors 1012, 1014 with a single core, multiple processors 1012, 1014 with multiple cores, or any combination thereof.

[0140] The memory / storage 1006 may include memory such as a main memory 1016 or other memory storage and a storage unit 1018, both of which may be accessed by the processor 1004, for example, via the bus 1010. The storage unit 1018 and the main memory 1016 store instructions 1002 embodying any one or more of the methods or functions described herein. The instructions 1002 may also reside, completely or partially, within the main memory 1016, within the storage unit 1018, within at least one of the processors 1004 (e.g., within a cache memory of the processor), or any suitable combination thereof during execution thereof by the machine 1000. Thus, the main memory 1016, the storage unit 1018, and the memory of the processor 1004 are examples of machine-readable media.

[0141] The I / O components 1008 may include various components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurements, etc. The specific I / O components 1008 included in a particular machine 1000 will depend on the type of machine. For example, a portable machine such as a mobile phone will most likely include a touch input device or other such input mechanism, while a headless server machine will most likely not include such a touch input device. It will be appreciated that the I / O components 1008 may include Fig.101008 are grouped according to function only to simplify the following discussion, and the grouping is by no means limiting. In various example implementations, the I / O components 1008 may include user output components 1020 and user input components 1022. The user output components 1020 may include visual components (e.g., displays such as plasma display panels (PDPs), light emitting diode (LED) displays, liquid crystal displays (LCDs), projectors, or cathode ray tubes (CRTs)), acoustic components (e.g., speakers), tactile components (e.g., vibration motors, resistance mechanisms), other signal generators, etc. The user input components 1022 may include alphanumeric input components (e.g., keyboards, touch screens configured to receive alphanumeric input, optical keyboards, or other alphanumeric input components), point-based input components (e.g., mice, touch pads, trackballs, joysticks, motion sensors, or other pointing instruments), tactile input components (e.g., physical buttons, touch screens that provide the location or force of touch or touch gestures, or other tactile input components), audio input components (e.g., microphones), etc.

[0142] In other example implementations, the I / O component 1008 may include a biometric component 1024, a motion component 1026, an environmental component 1028, or a positioning component 1030, as well as various other components. For example, the biometric component 1024 may include a component 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 a person (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1026 may include an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, a rotation sensor component (e.g., a gyroscope), etc. The environment component 1028 may include, for example, an illumination sensor component (e.g., a photometer), a temperature sensor component (e.g., one or more thermometers that detect ambient temperature), a humidity sensor component, a pressure sensor component (e.g., a barometer), an acoustic sensor component (e.g., one or more microphones that detect background noise), a proximity sensor component (e.g., an infrared sensor that detects nearby objects), a gas sensor (e.g., a gas detection sensor for detecting concentrations of hazardous gases for safety or for measuring pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment. The positioning component 1030 may include a position sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects air pressure from which the altitude can be derived), an orientation sensor component (e.g., a magnetometer), etc.

[0143] Various technologies may be used to implement communications. The I / O components 1008 may include a communications component 1032 operable to couple the machine 1000 to a network 1034 or a device 1036. For example, the communications component 1032 may include a network interface component or other suitable device that interfaces with the network 1034. In other examples, the communications component 1032 may include a wired communications component, a wireless communications component, a cellular communications component, a near field communications (NFC) component, Parts (e.g. Low energy consumption), Device 1036 may be another machine 1000 or any peripheral device among various peripheral devices (eg, a peripheral device coupled via USB).

[0144] In addition, the communication component 1032 can detect the identifier or include a component operable to detect the identifier. For example, the communication component 1032 may 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 tagged audio signals). In addition, various information can be obtained via the communication component 1032, such as location via Internet Protocol (IP) geolocation, ... Signal triangulation to obtain location, location obtained via detection of NFC beacon signals that can indicate a specific location, etc.

[0145] Fig.11 is a block diagram illustrating a system 1100 including an example software architecture 1102 that can be used in conjunction with the various hardware architectures described herein. Fig.11 is a non-limiting example of a software architecture, and it will be appreciated that many other architectures may be implemented to facilitate the functionality described herein. The software architecture 1102 may be implemented in hardware such as Fig.10 1000, which includes a processor 1004, a memory / storage device 1006, and an input / output (I / O) component 1008. A representative hardware layer 1104 is shown and can represent, for example Fig.10The machine 1000 of the embodiment of the present invention. The representative hardware layer 1104 includes a processing unit 1106 having associated executable instructions 1108. The executable instructions 1108 represent executable instructions of the software architecture 1102, including implementations of the methods, components, etc. described herein. The hardware layer 1104 also includes at least one of a memory or storage module memory / storage device 1110 also having executable instructions 1108. The hardware layer 1104 may also include other hardware 1112.

[0146] exist Fig.11 In the example architecture of , software architecture 1102 can be conceptualized as a stack of layers, each of which provides specific functionality. For example, software architecture 1102 can include layers such as operating system 1114, library 1116, framework / middleware 1118, application 1120, and presentation layer 1122. In operation, application 1120 or other components within a layer can activate API call 1124 through the software stack and receive message 1126 in response to API call 1124. The layers shown are representative in nature, and not all software architectures have all layers. For example, some mobile operating systems or dedicated operating systems may not provide framework / middleware 1118, while other operating systems may provide such a layer. Other software architectures may include additional or different layers.

[0147] The operating system 1114 can manage hardware resources and provide public services. The operating system 1114 can include, for example, a kernel 1128, a service 1130, and a driver 1132. The kernel 1128 can be used as an abstraction layer between the hardware and other software layers. For example, the kernel 1128 can be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, etc. The service 1130 can provide other public services for other software layers. The driver 1132 is responsible for controlling or interfacing with the underlying hardware. For example, depending on the hardware configuration, the driver 1132 includes a display driver, a camera driver, drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), Drivers, audio drivers, power management drivers, etc.

[0148] The library 1116 provides a common infrastructure used by at least one of the applications 1120, other components or layers. The library 1116 provides the following functions, which allow other software components to perform tasks in an easier way than directly interfacing with the underlying operating system 1114 functions (e.g., core 1128, service 1130 or driver 1132). The library 1116 may include a system library 1134 (e.g., C standard library), which may provide functions such as memory allocation functions, string operation functions, mathematical functions, etc. In addition, the library 1116 may include an API library 1136, such as a media library (e.g., a library that supports the presentation and operation of various media formats such as MPEG4, H.264, MP3, AAC, AMR, JPG, PNG), a graphics library (e.g., an OpenGL framework that can be used to present two-dimensional and three-dimensional graphics content on a display), a database library (e.g., SQLite that can provide various relational database functions), a web library (e.g., WebKit that can provide web browsing functions), etc. The library 1116 may also include various other libraries 1138 to provide numerous other APIs to the applications 1120 and other software components / modules.

[0149] Framework / middleware 1118 (sometimes also referred to as middleware) provides a higher level common infrastructure that can be used by applications 1120 or other software components / modules. For example, framework / middleware 1118 can provide various graphical user interface functions, advanced resource management, advanced location services, etc. Framework / middleware 1118 can provide a wide range of other APIs that can be used by applications 1120 or other software components / modules, some of which can be specific to a particular operating system 1114 or platform.

[0150] Applications 1120 include built-in applications 1140 and third-party applications 1142. Examples of representative built-in applications 1140 may include, but are not limited to, contact applications, browser applications, book reader applications, location applications, media applications, messaging applications, or game applications. Third-party applications 1142 may include applications that are developed by entities other than the vendor of a particular platform using ANDROID TM or IOS TM Software Development Kit (SDK) for developing applications and can be used on platforms such as IOS TM ANDROID TM , Mobile software running on the phone's mobile operating system or other mobile operating system. Third-party applications 1142 can activate API calls 1124 provided by the mobile operating system (eg, operating system 1114) to facilitate the functionality described herein.

[0151] Applications 1120 may use built-in operating system functionality (e.g., kernel 1128, services 1130, drivers 1132), libraries 1116, and framework / middleware 1118 to create a UI to interact with a user of the system. Alternatively or additionally, in some systems, interaction with the user may occur through a presentation layer, such as presentation layer 1122. In these systems, the application / component "logic" may be separated from the aspects of the application / component that interact with the user.

[0152] Glossary:

[0153] A "carrier signal" in this context refers to any intangible medium capable of storing, encoding, or carrying transitory or non-transitory instructions 1002 for execution by the machine 1000 and includes digital or analog communications signals or other intangible media to facilitate communication of such instructions 1002. The instructions 1002 may be sent or received over the network 114, 1034 using a transitory or non-transitory transmission medium via a network interface device and using any of a number of well-known transmission protocols.

[0154] A "client device" in this context refers to any machine 1000 that interfaces with a communication network 114, 1034 to obtain resources from one or more server systems or other client devices 102. A client device 102 may be, but is not limited to, a mobile phone, a desktop computer, a laptop computer, a PDA, a smart phone, a tablet computer, an ultrabook, a netbook, a laptop computer, a multiprocessor system, a microprocessor-based or programmable consumer electronics, a game console, a set-top box, or any other communication device that a user may use to access a network 114, 1034.

[0155] The "communication network" in this context refers to one or more parts of the network 114, 1034, 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 part of the Internet, a part of the public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, network, other types of networks, or a combination of two or more such networks. For example, the network 114, 1034, or a portion of the network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a global mobile communication system (GSM) connection, or other types of cellular or wireless coupling. In this example, the coupling may 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, including the third generation partnership project (3GPP) of 3G, fourth generation wireless (4G) network, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standard, other standards defined by various standard setting organizations, other remote protocols, or other data transmission technologies.

[0156] A "transient message" in this context refers to a message that can be accessed for a limited duration of time. A transient message can be text, an image, a video, etc. The access time of a transient message 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.

[0157] "Machine-readable medium" in this context refers to a component, device, or other tangible medium capable of temporarily or permanently storing instructions 1002 and data, and may include, but is not limited to, random access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of storage devices (e.g., erasable programmable read-only memory (EEPROM)), and / or any suitable combination thereof. The term "machine-readable medium" may be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) capable of storing instructions 1002. The term "machine-readable medium" should also be taken to include any medium or combination of multiple media capable of storing instructions 1002 (e.g., code) executed by the machine 1000, such that the instructions 1002, when executed by one or more processors 1004 of the machine 1000, cause the machine 1000 to perform any one or more of the methods described herein. Thus, "machine-readable medium" refers to a single storage device or device, as well as a "cloud-based" storage system or storage network comprising multiple storage devices or devices. The term "machine-readable medium" does not include the signal itself.

[0158] "Component" in this context refers to a device, physical entity or logic with boundaries defined by function or subroutine calls, branch points, APIs or other technologies that provide partitioning or modularization for specific processing or control functions. Components can be combined with other components via their interfaces to perform machine processing. Components can be packaged functional hardware units designed for use with other components, and can be part of a program that generally performs a specific function of a related function. Components can constitute software components (e.g., codes embodied on machine-readable media) or hardware components. "Hardware components" are tangible units that can perform certain operations and can be configured or arranged in a certain physical manner. In various example implementations, one or more computer systems (e.g., independent computer systems, client computer systems or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured by software (e.g., applications or application parts) to operate to perform certain operations as described herein. Hardware components.

[0159] The hardware components may also be implemented mechanically, electronically, or in any suitable combination thereof. For example, the hardware components may include a dedicated circuit system or logic that is permanently configured to perform certain operations. The hardware components may be a dedicated processor, such as a field programmable gate array (FPGA) or an ASIC. The hardware components may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, the hardware components may include software executed by a general-purpose processor 1004 or other programmable processor. Once configured by such software, the hardware components become a specific machine (or a specific component of the machine 1000) that is uniquely customized to perform the configured function and are no longer a general-purpose processor 1004. It will be understood that it may be decided for cost and time considerations whether to implement the hardware components 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, that is, 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. Given implementations where hardware components are temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each hardware component at any one time. For example, where the hardware components include a general-purpose processor 1004 that is configured by software to be a special-purpose processor, the general-purpose processor 1004 can be configured to be a different special-purpose processor (e.g., including different hardware components) at different times. The software configures the specific processor 1012, 1014 or processor 1004 accordingly, for example, to constitute a specific hardware component at one time and to constitute a different hardware component at a different time.

[0160] 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 (for example, by appropriate circuits and buses) between or among two or more hardware components in these hardware components, signal transmission is performed. In the implementation mode that multiple hardware components are configured or instantiated at different times, communication between such hardware components can be realized, for example, by storing information in a memory structure accessed by multiple hardware components and retrieving information in the memory structure. For example, a hardware component can perform an operation, and the output of the operation is stored in a memory device coupled in communication with it. Then, other hardware components can access the memory device at a subsequent time to retrieve the stored output and process it.

[0161] The hardware component can also initiate communication with an input device or an output device, and can operate on a resource (e.g., a collection of information). The various operations of the example methods described herein can be performed at least in part by one or more processors 1004 that are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether it is a temporary configuration or a permanent configuration, such a processor 1004 can 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 1004. Similarly, the method described herein can be implemented at least in part by a processor, wherein a specific processor 1012, 1014 or processor 1004 is an example of hardware. For example, at least some operations in the operation of the method can be performed by one or more processors 1004 or processor-implemented components. In addition, one or more processors 1004 can 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 operations may be performed by a computer group (as an example of a machine 1000 including a processor 1004), where these operations can be accessed via a network 114 (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs). The execution of certain operations may be distributed among processors, not only residing within a single machine 1000, but also deployed across multiple machines. In some example implementations, the processor 1004 or a processor-implemented component may be located in a single geographic location (e.g., in a home environment, an office environment, or a server farm). In other example implementations, the processor 1004 or a processor-implemented component may be distributed across multiple geographic locations.

[0162] A "processor" in this context refers to any circuit or virtual circuit (a physical circuit emulated by logic executed on an actual processor 1004) that manipulates data values ​​according to control signals (e.g., "commands," "opcodes," "machine codes," etc.) and generates corresponding output signals used to operate the machine 1000. For example, the processor 1004 may be a CPU, a RISC processor, a CISC processor, a GPU, a DSP, an ASIC, an RFIC, or any combination thereof. The processor 1004 may also be a multi-core processor having two or more independent processors 1004 (sometimes referred to as "cores") that can execute instructions 1002 simultaneously.

[0163] A "timestamp" in this context refers to a sequence of characters or coded information that identifies when some event occurred, for example, giving a date and time of day, sometimes accurate to a fraction of a second.

[0164] Changes and modifications may be made to the disclosed implementations 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.

[0165] Example Aspects of the Disclosure

[0166] Aspect 1. A method, comprising: generating, by one or more computing devices, a framework related to creating a camera user interface displayed via a client application, the camera user interface comprising a plurality of interface elements for generating user content comprising at least one of image content or video content; receiving, by at least one computing device among the one or more computing devices, content communication information and camera user interface information corresponding to the framework from an additional computing device of a developer of a third-party application, the camera user interface information indicating at least one user interface element among the plurality of user interface elements, and the content communication information indicating a user interface of the third-party application for displaying the user content; At least one of the one or more computing devices determines a third-party camera user interface profile corresponding to the third-party application, the third-party camera user interface profile indicating a layout of the camera user interface, and the layout indicating corresponding positions of the plurality of user interface elements; at least one of the one or more computing devices sends information corresponding to the third-party camera user interface profile to the client device; at least one of the one or more computing devices determines that the user content is to be returned to the third-party application; and at least one of the one or more computing devices causes the user content to be provided to the third-party application based on the content communication information.

[0167] Aspect 2. The method according to Aspect 1 includes: storing the camera device user interface information and the content communication information in association with the identifier of the third-party application in one or more databases by at least one of the one or more computing devices; and generating the third-party camera device user interface profile based on the camera device user interface information and the content communication information by at least one of the one or more computing devices.

[0168] Aspect 3. A method according to Aspect 2, wherein the third-party camera device user interface profile includes third-party camera device user interface data, the third-party camera device user interface data includes at least one of text content, image content or video content to be displayed in the camera device user interface, and the third-party camera device user interface data corresponds to the third-party application.

[0169] Aspect 4. The method according to Aspect 2 includes: receiving, by at least one of the one or more computing devices, an indication of a request from the client device to access the client application from the third-party application; determining, by at least one of the one or more computing devices, that an identifier of the third-party application is included in the indication of the request to access the client application from the third-party application; and querying, by at least one of the one or more computing devices, one or more databases based on the identifier to retrieve information corresponding to the third-party camera user interface profile from the one or more databases.

[0170] Aspect 5. The method according to Aspect 2 includes: receiving, by at least one of the one or more computing devices, a content return request from the client application, the content return request indicating an identifier of the third-party application; and retrieving, by at least one of the one or more computing devices, the content communication information from one or more databases based on the identifier of the third-party application.

[0171] Aspect 6. A method according to Aspect 5, wherein the content return request includes the user content; and the method includes: at least one computing device among the one or more computing devices sends the user content and the content communication information to a server system related to the third-party application.

[0172] Aspect 7. The method according to aspect 5, wherein the additional user interface of the client application includes the user content and a user interface element that can be selected to generate the content return request.

[0173] Aspect 8. The method according to any one of Aspects 1 to 7 comprises: receiving a message including the user content by at least one of the one or more computing devices; determining one or more recipients of the message by at least one of the one or more computing devices; and making the user content available to one or more recipients of the message by at least one of the one or more computing devices.

[0174] Aspect 9. The method according to any one of Aspects 1 to 8 further includes: receiving, by at least one of the one or more computing devices, an indication to apply an augmented reality content item to at least one of image content or video content included in the user content; and modifying, by at least one of the one or more computing devices, the user content based on applying the augmented reality content item to one or more objects in at least one of the image content or video content included in the user content.

[0175] Aspect 10. The method according to Aspect 9, wherein the augmented reality content item is created by a developer of the third-party application.

[0176] Aspect 11. A system, comprising: one or more hardware processors and one or more non-transitory computer-readable storage media including computer-readable instructions. The computer-readable instructions, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations, the operations comprising: generating a framework related to creating a camera user interface displayed via a client application, the camera user interface including a plurality of interface elements for generating user content including at least one of image content or video content; receiving camera user interface information and content communication information from an additional computing device of a developer of a third-party application, the camera user interface information indicating at least one of the plurality of user interface elements, and the content communication information indicating a user interface of the third-party application for displaying the user content; determining a third-party camera user interface profile corresponding to the third-party application, the third-party camera user interface profile indicating a layout of the camera user interface, the layout indicating respective positions of the plurality of user interface elements; sending information corresponding to the third-party camera user interface profile to the client device; determining that the user content is to be returned to the third-party application; and causing the user content to be provided to the third-party application according to the content communication information.

[0177] Aspect 12. The system according to aspect 11, wherein the framework includes at least one of a software developer toolkit, computer readable instructions, one or more application programming interfaces, or one or more rules for modifying the camera user interface.

[0178] Aspect 13. A system according to Aspect 11 or 12, wherein the one or more non-transitory computer-readable storage media include additional computer-readable instructions, which, when executed by the one or more hardware processors, cause the one or more hardware processors to perform additional operations, the additional operations including: generating user interface data corresponding to one or more user interfaces, the one or more user interfaces capturing at least one of a first input indicating at least one of the multiple user interface elements or a second input indicating the layout; and sending the user interface data to the additional computing device of the developer.

[0179] Aspect 14. A system according to any one of Aspects 11 to 13, wherein the one or more non-transitory computer-readable storage media include additional computer-readable instructions, which, when executed by the one or more hardware processors, cause the one or more hardware processors to perform additional operations, the additional operations including: generating user interface data corresponding to one or more user interfaces corresponding to the framework, the one or more user interfaces capturing input indicating the content return information; determining that the user content is to be returned to the third-party application; and sending the user content to a server system associated with the third-party application using one or more application programming interface calls provided by the developer of the third-party application.

[0180] Aspect 15. A method, comprising: generating a user interface for a third-party application by one or more computing devices, the user interface including a first user interface element that can be selected to initiate execution of an instance of a client application; receiving input indicating a selection of the user interface element by at least one of the one or more computing devices; generating a camera user interface for the client application by at least one of the one or more computing devices in response to the input and based on third-party camera user interface data, the third-party camera user interface data indicating multiple features of the camera user interface; generating user content by at least one of the one or more computing devices via the camera user interface, the user content including: at least one of image content or video content captured using a camera of a client device that executes the instance of the client application; and generating an additional user interface for the client application by at least one of the one or more computing devices, the additional user interface including the user content and a second user interface element, the second user interface element being selectable to initiate execution of the instance of the third-party application and provide the user content to the third-party application.

[0181] Aspect 16. A method according to Aspect 15, wherein: the camera device user interface of the client application includes a third user interface element, which can be selected to create the user content based on at least one of the image content or video content included in the field of view of the camera device; and the additional user interface of the client application includes one or more fourth user interface elements, which can be selected to apply one or more creation tools to the user content.

[0182] Aspect 17. The method according to Aspect 16 includes: at least one of the one or more computing devices applying at least one of the one or more creation tools to the user content to generate modified user content; and in response to selection of the second user interface element, at least one of the one or more computing devices sending a request for providing the modified user content to the third-party application.

[0183] Aspect 18. The method according to any one of Aspects 15 to 17 comprises: determining, by at least one of the one or more computing devices, an augmented reality content item to be applied to at least one of the image content or video content captured by the camera of the client device; modifying, by at least one of the one or more computing devices, the appearance of one or more objects included in at least one of the image content or video content by applying the augmented reality content item to the one or more objects to generate modified user content; and in response to selection of the second user interface element, sending, by at least one of the one or more computing devices, a request for providing the modified user content to the third-party application.

[0184] Aspect 19. The method according to any one of Aspects 15 to 18 includes: receiving the third-party camera device user interface data from a server system corresponding to the client application by at least one computing device among the one or more computing devices; and wherein the third-party camera device user interface data indicates at least one of the following: the layout of multiple user interface elements within the camera device user interface, or information corresponding to the third-party application to be displayed within the camera device user interface.

[0185] Aspect 20. The method according to any one of Aspects 15 to 19 comprises: receiving the user content and a uniform resource indicator by at least one of the one or more computing devices; determining, by at least one of the one or more computing devices, that the uniform resource indicator corresponds to an additional user interface of the third-party application; and launching an instance of the third-party application by at least one of the one or more computing devices so that the user content is displayed in the user interface of the third-party application.

Claims

1. A method comprising: generating, by one or more computing devices, a framework associated with creating a camera user interface for display via a client application, the camera user interface comprising a plurality of user interface elements for generating user content comprising at least one of image content or video content; receiving, by at least one of the one or more computing devices, content communication information and camera user interface information corresponding to the framework from an additional computing device of a developer of a third-party application, the camera user interface information indicating at least one user interface element of the plurality of user interface elements, and the content communication information indicating a user interface of the third-party application for displaying the user content; determining, by at least one of the one or more computing devices, a third-party camera user interface profile corresponding to the third-party application, the third-party camera user interface profile indicating a layout of the camera user interface, the layout indicating respective positions of the plurality of user interface elements; Sending, by at least one of the one or more computing devices, information corresponding to the third-party camera user interface profile to a client device; receiving, by at least one of the one or more computing devices, an indication to apply an augmented reality content item to at least one of image content or video content included in the user content, the indication corresponding to a selection of a user interface element different from the at least one user interface element included in the camera user interface information, and the augmented reality content item being different from the camera user interface information; modifying, by at least one of the one or more computing devices, the user content based on applying the augmented reality content item to one or more objects included in at least one of image content or video content of the user content to generate modified user content; determining, by at least one of the one or more computing devices, to return the modified user content to the third-party application; as well as The modified user content is caused, by at least one of the one or more computing devices, to be provided from the client application to the third-party application in accordance with the content communication information.

2. The method according to claim 1, comprising: storing, by at least one of the one or more computing devices, the camera user interface information and the content communication information in association with an identifier of the third-party application in one or more databases; as well as The third-party camera user interface profile is generated by at least one computing device of the one or more computing devices based on the camera user interface information and the content communication information.

3. The method according to claim 2, wherein: The third-party camera user interface profile includes third-party camera user interface data, which includes at least one of text content, image content or video content to be displayed in the camera user interface, and the third-party camera user interface data corresponds to the third-party application.

4. The method according to claim 2, comprising: receiving, by at least one of the one or more computing devices, an indication of a request from the client device to access the client application from the third-party application; determining, by at least one of the one or more computing devices, that an identifier of the third-party application is included in the indication of the request to access the client application from the third-party application; as well as One or more databases are queried by at least one of the one or more computing devices based on the identifier to retrieve information corresponding to the third-party camera user interface profile from the one or more databases.

5. The method according to claim 2, comprising: receiving, by at least one of the one or more computing devices, a content return request from the client application, the content return request indicating an identifier of the third-party application; as well as The content communication information is retrieved from one or more databases by at least one of the one or more computing devices based on an identifier of the third party application.

6. The method according to claim 5, wherein: The content return request includes the modified user content; And the method further comprises: The modified user content and the content communication information are sent, by at least one computing device of the one or more computing devices, to a server system associated with the third-party application.

7. The method according to claim 5, wherein: An additional user interface of the client application includes the modified user content and a user interface element that is selectable to generate the content return request.

8. The method according to claim 1, comprising: receiving, by at least one of the one or more computing devices, a message including the modified user content; determining, by at least one of the one or more computing devices, one or more recipients of the message; as well as The modified user content is made available, by at least one of the one or more computing devices, to one or more recipients of the message.

9. The method according to claim 1, wherein: The third party camera user interface profile includes one or more first features of a default camera user interface and one or more second features corresponding to one or more modifications of the default camera user interface.

10. The method according to claim 1, wherein: The augmented reality content item is created by a developer of the third-party application.

11. A system comprising: one or more hardware processors; as well as One or more non-transitory computer-readable storage media including computer-readable instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations comprising: generating a framework associated with creating a camera user interface displayed via a client application, the camera user interface comprising a plurality of user interface elements for generating user content including at least one of image content or video content; receiving camera user interface information and content communication information from an additional computing device of a developer of a third-party application, the camera user interface information indicating at least one user interface element of the plurality of user interface elements, and the content communication information indicating a user interface of the third-party application for displaying the user content; Determining a third-party camera user interface profile corresponding to the third-party application, the third-party camera user interface profile indicating a layout of the camera user interface, the layout indicating corresponding positions of the plurality of user interface elements; Sending information corresponding to the third-party camera user interface profile to the client device; receiving an instruction to apply an augmented reality content item of the client application to at least one of image content or video content included in the user content; modifying the user content based on applying the augmented reality content item to one or more objects included in at least one of image content or video content of the user content to generate modified user content; determining to return the modified user content to the third-party application; and The modified user content is caused to be provided from the client application to the third party application in accordance with the content communication information.

12. The system according to claim 11, wherein: The framework includes at least one of a software developer toolkit, computer readable instructions, one or more application programming interfaces, or one or more rules for modifying the camera user interface.

13. The system according to claim 11, wherein: The one or more non-transitory computer-readable storage media include additional computer-readable instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform additional operations, including: generating user interface data corresponding to one or more user interfaces that capture at least one of a first input indicative of at least one user interface element of the plurality of user interface elements or a second input indicative of the layout; and The user interface data is sent to the attached computing device of the developer.

14. The system according to claim 11, wherein: The one or more non-transitory computer-readable storage media include additional computer-readable instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform additional operations, including: generating user interface data corresponding to one or more user interfaces corresponding to the framework, the one or more user interfaces capturing input indicating content return information; determining to return the modified user content to the third-party application; and The modified user content is sent to a server system associated with the third-party application using one or more application programming interface calls provided by a developer of the third-party application.

15. A method comprising: generating, by one or more computing devices, a user interface of the third-party application, the user interface including a first user interface element selectable to initiate execution of an instance of the client application; receiving, by at least one of the one or more computing devices, input indicating a selection of the first user interface element; generating, by at least one of the one or more computing devices, a camera user interface for the client application in response to the input and based on third-party camera user interface data, the third-party camera user interface data indicating a plurality of features of the camera user interface; generating, by at least one of the one or more computing devices via the camera user interface, user content comprising: at least one of image content or video content captured using a camera of a client device executing an instance of the client application; receiving, by at least one of the one or more computing devices, additional user input for applying an augmented reality content item to at least one of image content or video content included in the user content, the augmented reality content item being different from the third-party camera user interface data; modifying, by at least one of the one or more computing devices, the user content based on applying the augmented reality content item to one or more objects included in at least one of image content or video content of the user content to generate modified user content; and An additional user interface for the client application is generated by at least one of the one or more computing devices, the additional user interface including the modified user content and a second user interface element, the second user interface element being selectable to initiate execution of an instance of the third-party application and provide the modified user content to the third-party application.

16. The method of claim 15, wherein: the camera user interface of the client application includes a third user interface element selectable to create the user content based on at least one of image content or video content included in a field of view of the camera; and The additional user interface of the client application includes one or more fourth user interface elements selectable to apply one or more authoring tools to the user content or the modified user content.

17. The method according to claim 16, comprising: applying, by at least one of the one or more computing devices, at least one of the one or more authoring tools to the user content to generate additional modified user content; as well as In response to selection of the second user interface element, a request is sent, by at least one of the one or more computing devices, to provide the additional modified user content to the third-party application.

18. The method according to claim 15, comprising: In response to selection of the second user interface element, a request is sent, by at least one of the one or more computing devices, to provide the modified user content to the third-party application.

19. The method according to claim 15, comprising: receiving, by at least one of the one or more computing devices, the third-party camera user interface data from a server system corresponding to the client application; and The third-party camera device user interface data indicates at least one of the following: a layout of a plurality of user interface elements within the camera device user interface, or information corresponding to the third-party application to be displayed within the camera device user interface.

20. The method according to claim 15, comprising: receiving, by at least one of the one or more computing devices, the user content and a uniform resource indicator; determining, by at least one of the one or more computing devices, that the uniform resource indicator corresponds to an additional user interface of the third-party application; as well as The instance of the third-party application is launched by at least one computing device of the one or more computing devices, so that the user content is displayed in a user interface of the third-party application.

Images