Interacting with visual codes within messaging system

Abstract

Aspects of the present disclosure relate to a system including a computer-readable storage medium storing a program and a method for interacting with a visual code within a messaging system. Programs and methods enable: displaying, by a messaging application, captured image data comprising a visual code, the visual code comprising a custom graphic and being decodable to access a first feature of the messaging application; receiving a user input selecting a visual code; displaying the updated version of the user-defined graph; providing an animation depicting an updated version of the custom graphic to move from the visual code to an interface element comprising a set of icons, each icon in the set of icons being selectable by the user to access a respective second feature of the messaging application; and updating the set of icons to include additional icons that are selectable by the user to access the first feature of the messaging application.

Description

[0001] Priority Claim

[0002] This patent application claims the benefit of priority to U.S. application serial number 17 / 820,674, filed on August 18, 2022, which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure generally relates to messaging systems, including interacting with visual codes to access features within the messaging system. Background Art

[0004] The messaging system provides the exchange of message contents between users.For example, the messaging system allows a user to exchange message contents (e.g., text, images) with one or more other users. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] In the accompanying drawings (which are not necessarily drawn to scale), the same 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 non-limiting examples are shown in the figures of the accompanying drawings, in which:

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

[0007] Figure 2 is a diagrammatic representation of a messaging system having both client-side and server-side functionality according to some examples.

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

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

[0010] Figure 5 is an interaction diagram illustrating a process for interacting with a visual code to access features within a messaging system according to some examples.

[0011] Figure 6 A user interface is shown in which a visual code is displayed within captured image data according to some example embodiments.

[0012] Figure 7 A user interface is shown where a user selects a visual code to activate an augmented reality content item according to some example embodiments.

[0013] Figure 8A user interface is shown in which a custom graphic of a visual code is updated in response to a user selection of the visual code according to some example embodiments.

[0014] Fig. 9 A user interface is shown in which an updated custom graphic is animated to move toward and inserted into a carousel interface according to some example embodiments.

[0015] FIG. 10A to FIG. 10C User interfaces corresponding to different ways in which an augmented reality content item corresponding to a visual code is downloaded and activated are shown according to some example embodiments.

[0016] Fig.11 is a flow diagram illustrating a process for interacting with a visual code to access features within a messaging system according to some examples.

[0017] Fig.12 is a flow diagram for an access restriction process according to some examples.

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

[0019] Fig.14 is a block diagram illustrating a software architecture within which examples may be implemented. DETAILED DESCRIPTION

[0020] Messaging systems typically enable users to exchange media content items (e.g., messages, images, and / or videos) with each other in a message thread. As described herein, messaging systems can provide visual codes, such as QR codes, one-dimensional barcodes, data matrices, Aztec codes, which are scannable to access specific features of the messaging system.

[0021] The disclosed embodiments relate to a messaging system for interacting with a visual code to access features of the messaging system. In other systems, after selecting a visual code, a separate message box (e.g., an overlay) is presented to the user prompting the user to download and / or activate the feature. The message box may be distracting because it diverts the user's attention away from the current interface related to the feature.

[0022] The disclosed embodiments enable a messaging client to update a custom graphic within a visual code in response to a user selection of a visual code. The messaging client animates the movement of the custom graphic from the visual code area of ​​a display to a carousel interface. The carousel interface includes user-selectable icons representing various features of the messaging system. The messaging client updates the carousel interface to include additional icons corresponding to the visual code, and downloads a code (e.g., an asset) for accessing the corresponding feature. The downloading and activation of the feature can be automatic (e.g., without additional prompting to the user) to reduce the amount of interaction required from the end user.

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

[0024] The messaging client 104 can communicate and exchange data with other messaging clients 104 and with the messaging server system 108 via the network 112. The data exchanged between the messaging clients 104 and between the messaging clients 104 and the messaging server system 108 includes functions (e.g., commands for activating functions) and payload data (e.g., text, audio, video, or other multimedia data). In some embodiments, the messaging client 104 activates the camera of the client device 102 (e.g., when the messaging client 104 is started).

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

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

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

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

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

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

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

[0032] Returning to the messaging client 104, the features and functions of the external resource (e.g., application 106 or applet) are available to the user via the interface of the messaging client 104. In this context, "external" refers to the fact that the application 106 or applet is outside the messaging client 104. External resources are usually provided by a third party, but can also be provided by the creator or provider of the messaging client 104. The messaging client 104 receives a user selection of an option to launch or access the features of such an external resource. The external resource can be an application 106 (e.g., a "local app") installed on the client device 102, or a small-scale version of an application (e.g., a "applet") hosted on the client device 102 or located at the far end of the client device 102 (e.g., on a third-party server 110). The small-scale version of the application includes a subset of the features and functions of the application (e.g., a full-scale local version of the application) and is implemented using a markup language document. In one example, the small-scale version of the application (e.g., a "applet") is a web-based markup language version of the application and is embedded in the messaging client 104. In addition to using markup language documents (eg, *ml files), applets may include scripting languages ​​(eg, *js files or json files) and style sheets (eg, *ss files).

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

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

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

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

[0037] Figure 2 1 is a block diagram showing additional details about the messaging system 100 according to some examples. Specifically, the messaging system 100 is shown as including a messaging client 104 and an application server 114. The messaging system 100 contains a number of subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a transient timer system 202, a collection management system 204, an enhancement system 208, a mapping system 210, an external resource system 212, and a visual code scanner system 214.

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

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

[0040] In addition, the collection management system 204 includes a curation interface 206 that enables a collection manager to manage and curate a particular collection of content. For example, the curation interface 206 enables an event organizer to curate a collection of content related to a particular event (e.g., to remove inappropriate content or redundant messages). In addition, the collection management system 204 employs machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, compensation may be paid to a user for including user-generated content in a collection. In such a case, the collection management system 204 operates to automatically pay such a user for using his or her content.

[0041] The enhancement system 208 provides various functions that enable users to enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the enhancement system 208 provides functions related to the generation and publication of media overlays for messages processed by the messaging system 100. The enhancement system 208 is operable to provide media overlays or enhancements (e.g., image filters) to the messaging client 104 based on the geographic location of the client device 102. In another example, the enhancement system 208 is operable to provide media overlays to the messaging client 104 based on other information such as social network information of the user of the client device 102. The media overlay can include audio and visual content and visual effects. Examples of audio and visual content include pictures, text, logos, animations, and sound effects. Examples of visual effects include color overlays. Audio and visual content or visual effects can be applied to media content items (e.g., photos) at the client device 102. For example, the media overlay can include text 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 208 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 126 and accessed through the database server 120.

[0042] In some examples, the enhancement system 208 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 208 generates a media overlay including the uploaded content and associates the uploaded content with the selected geolocation.

[0043] In other examples, the enhancement system 208 provides a merchant-based publishing platform that enables merchants to select specific media overlays associated with a geographic location via a bidding process. For example, the enhancement system 208 associates the highest bidding merchant's media overlay with the corresponding geographic location for a predefined amount of time.

[0044] In other examples, such as the following Figure 3As discussed, the augmentation system 208 enables presentation of augmented reality content in association with images or video captured by a camera of the client device 102. The augmentation system 208 may implement or otherwise access augmented reality content items (e.g., corresponding to application lenses or augmented reality experiences) to provide real-time special effects and / or sounds that may be added to images or video.

[0045] The mapping system 210 provides various geolocation functions and supports the presentation of map-based media content and messages by the messaging client 104. For example, the mapping system 210 enables the display of a user icon or avatar (e.g., stored in the profile data 302) on a map 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 such friends in the context of the map. For example, a message posted by a user to the messaging system 100 from a particular geolocation can be displayed to the "friends" of a particular user on the mapping interface of the messaging client 104 within the context of that particular location on the map. The user can also share his or her location and status information with other users of the messaging system 100 (e.g., using appropriate status avatars) via the messaging client 104, where the location and status information is similarly displayed to selected users within the context of the mapping interface of the messaging client 104.

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

[0047] To integrate the functionality of the SDK into a web-based resource, the SDK is downloaded by the third-party server 110 from the messaging server 118, or received by the third-party server 110 in other ways. Once downloaded or received, the SDK is included as part of the application code of the web-based external resource. The code of the web-based resource can then call or activate certain functions of the SDK to integrate the features of the messaging client 104 into the web-based resource.

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

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

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

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

[0052] The visual code scanner system 214 implements various functions for scanning visual codes related to the messaging system 100. For example, the visual code may correspond to a QR code, a one-dimensional barcode (1Barcode), a data matrix, an Aztec code, etc. In one or more embodiments, the client device 102 may access image data (e.g., still images, videos) including the visual code. For example, the image data may be captured in real time by the client device 102 (e.g., a real-time image feed from a camera sensor of the client device 102). In another example, the image data is stored on the client device 102 or received by the client device 102 based on previous image capture via the client device 102 or another device. The visual code scanner system 214 is configured to access image data including the visual code. In an embodiment where the image data is a video, the visual code scanner system 214 is configured to analyze individual frames of the video or a combination of multiple frames of the video to detect and decode the visual code.

[0053] In one or more embodiments, the visual code scanner system 214 is configured to identify a custom graphic (e.g., a ghost icon) in an image and use the custom graphic as an alignment pattern for decoding the data included in the visual code. For example, the visual code scanner system 214 extracts candidate shape features from the image data of the image. Subsequently, the visual code scanner system 214 determines whether the candidate features meet certain rules and standards to filter out irrelevant shape features or shape features with a low probability of becoming custom graphics. The visual code scanner system 214 then compares the candidate shape features that meet the shape feature standards or rules with the reference shape features of the custom graphics. In the example, the visual code scanner system 214 identifies the custom graphics based on a match between the candidate shape features and the reference shape features (e.g., a match score that exceeds a threshold).

[0054] After identifying the custom graphic, the visual code scanner system 214 uses the custom graphic as an alignment pattern for decoding. For example, the visual code scanner system 214 extracts the spatial properties of the custom graphic in the image, and compares the extracted spatial properties with the reference spatial properties to determine the alignment of the custom graphic. The visual code scanner system 214 can then generate a transformed image of the image based on the alignment (e.g., rotation or de-skew). After generating the transformed image, the visual code scanner system 214 decodes the data encoded in a portion of the transformed image. For example, the points of the visual code are converted into data shown as 1 for the points and 0 for the non-points, although this is merely an illustrative example and other schemes may be employed. In this way, the visual code scanner system 214 uses the custom graphic included in the visual code as one or more functional patterns such as a finder pattern or an alignment pattern.

[0055] Based on decoding the data encoded in the image, the visual code scanner system 214 facilitates access to features and / or unique content of the messaging system 100. The data encoded in a portion of the image may indicate a particular feature (e.g., an action to be performed) or include information to be used in conjunction with a particular feature. Example features include, but are not limited to: accessing / activating an augmented reality content item (e.g., unlocking a lens), adding a friend, linking to a website, connecting to specific content, etc. For example, a unique visual code may be assigned to each augmented reality content item (e.g., when the augmented reality content item is generated), friend, website, and / or other content to provide access thereto by decoding the corresponding unique visual code.

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

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

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

[0059] The entity graph 304 stores information about the relationships and associations between entities. As examples only, such relationships may be social relationships, professional relationships (e.g., working in a common company or organization) based on interests or activities.

[0060] Profile data 302 stores multiple types of profile data about a particular entity. Based on the privacy settings specified by the particular entity, profile data 302 can be selectively used and presented to other users of messaging system 100. In the case where the entity is a person, profile data 302 includes, for example, 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 within the content of messages transmitted via messaging system 100 and on a map interface displayed to other users by messaging client 104. The collection of avatar representations can include a "status avatar" that presents a graphical representation of a status or activity that a user can choose to transmit at a particular time.

[0061] Where the entity is a group, profile data 302 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 for the relevant group (eg, notifications).

[0062] In one or more embodiments, the profile data 302 includes a corresponding visual code for each entity. For example, the visual code for a particular entity is scannable to access (eg, add) the entity as a friend.

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

[0064] 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 the sending user by the messaging client 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 the sending user based on geolocation. For example, a geolocation filter specific to a nearby or special location can be presented by the messaging client 104 within a user interface based on geolocation information determined by a global positioning system (GPS) unit of the client device 102.

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

[0066] Other augmented data that may be stored in augmented table 310 (e.g., in conjunction with image table 316 and / or video table 314) include augmented reality content items (e.g., corresponding to application lenses or augmented reality experiences). Augmented reality content items may provide real-time special effects and / or sounds that may be added to images or videos. Each of the augmented reality content items may be available for selection and activation by messaging client 104.

[0067] 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 modify the image when it is captured using the device sensor (e.g., one or more cameras) of the client device 102 and then display the modified image 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 that accesses 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 can be displayed only on the screen without being stored in the memory, or the content captured by the device sensor can be recorded and stored in the memory with or without modification (or both). In some systems, the preview feature can show how different augmented reality content items will look in different windows in the display at the same time. For example, this can enable viewing multiple windows with different pseudo-random animations on the display at the same time.

[0068] Thus, data and various systems using augmented reality content items or other such transformation systems using the data to modify content may involve: detection of various objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.) in video frames, tracking of such objects as they leave, enter, and move around the field of view, and modification or transformation of such objects as they are tracked. In various examples, different methods for implementing such transformations may be used. Some examples may involve generating a three-dimensional mesh model of one or more objects, and using transformations 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 further examples, neural network analysis of video frames may be used to place an image, model, or texture in content (e.g., an image or video frame). Thus, augmented reality content items involve both images, models, and textures used to create transformations in content, and additional modeling and analysis information required to implement such transformations using object detection, tracking, and placement.

[0069] Real-time video processing can be performed using any kind of video data (e.g., video streams, video files, etc.) stored in the memory of any kind of computerized system. For example, a user can load 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).

[0070] 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 exists 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, so the frame of the video stream is transformed. For different types of transformations, the transformation of the frame of the video stream can be performed by different methods. For example, for a frame transformation that mainly involves changing the form of the elements of the object, the characteristic points of each element of the object are calculated (for example, using an active shape model (Active Shape Model, ASM) or other known methods). Then, a grid based on the characteristic points is generated for each of at least one element of the object. The grid is used for the subsequent stages of tracking the elements of the object in the video stream. During the tracking process, the grid mentioned for each element is aligned with the position of each element. Then, additional points are generated on the grid. A first group of first points is generated for each element based on the modification request, and a group of second points is generated for each element based on the group 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 a group of first points, a group of second points and a grid. In such a method, the background of the modified object may also be changed or distorted by tracking and modifying the background.

[0071] In some examples, a transformation that changes some areas of an object using the elements of an object can be performed by calculating characteristic points of each element of the object and generating a grid based on the calculated characteristic points. Points are generated on the grid, and then various areas based on these points are generated. Then, the elements of the object are tracked by aligning the area of ​​each element with the position of each of at least one element, and the properties of the area can be modified based on the modification request, 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 examples, any combination of such modifications or other similar modifications may be used. For certain models to be animated, some characteristic points may be selected as control points for determining the entire state space of options for model animation.

[0072] 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.

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

[0074] In some examples, a landmark search begins with an average shape that aligns with the location and size of a face as determined by a global face detector. Such a search then repeats the steps of suggesting tentative shapes by adjusting the positioning of shape points through template matching of the image texture around each point, and then conforming the tentative shapes to a global shape model until convergence occurs. In some 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.

[0075] 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, computation time, and power consumption. Complex image manipulations can include size and shape changes, emotion conversions (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.

[0076] In some examples, a computer animation model for transforming image data may be used by a system in which a user may capture an image or video stream of the user (e.g., a selfie) using a client device 102 having a neural network operating as part of a messaging client 104 operating on the client device 102. A transformation system operating within the messaging client 104 determines the presence of a face within the image or video stream and provides a modification icon associated with the computer animation model to transform the data image, or the computer animation model may exist in association with an interface described herein. The modification icon includes a change that may be a 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 a 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 may be presented in a graphical user interface displayed on the client device 102. The transformation system may 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. Machine-taught neural networks can be used to implement such modifications.

[0077] 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 examples, the modifications can be persistent after the initial selection of the modification icon. The user can switch to turn the modification on or off by tapping or otherwise selecting the face being modified by the transformation system, and store it for later viewing or browsing to other areas of the imaging application. In the case of modifying multiple faces by the transformation system, the user can globally switch to turn the modification on or off by tapping or selecting a single face modified and displayed in the graphical user interface. In some examples, each face in a group of multiple faces can be modified individually, or such modifications can be individually switched by tapping or selecting each face or a series of each face displayed in the graphical user interface.

[0078] In one or more implementations, the augmentation table 310 stores a corresponding visual code for each augmented reality content item (or overlay, image transformation, AR image, etc.) that can be applied to the image data. For example, the visual code for a particular augmented reality content item can be scannable in order to access (e.g., activate, unlock) the augmented reality content item.

[0079] 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 for whom a record is maintained in the entity table 308). A user can create a "personal story" in the form of a collection of content that has been created and sent / broadcasted by the user. To this end, the user interface of the messaging client 104 may include a user-selectable icon to enable the sending user to add specific content to his or her personal story.

[0080] 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 messaging client 104. Live stories may be identified to the user by the messaging client 104 based on his or her location. The end result is a "live story" told from a group perspective.

[0081] 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).

[0082] As mentioned above, the video table 314 stores video data, which in one example is associated with a message whose record is maintained within the message table 306. Similarly, the image table 316 stores image data associated with a message whose message data is stored in the entity table 308. The entity table 308 may 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.

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

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

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

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

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

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

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

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

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

[0092] Message 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 content item in message image payload 406 of message 400. For example, multiple images within message image payload 406 may each be associated with multiple content collections using an identifier value.

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

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

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

[0096] The content (e.g., value) of each component of message 400 may be a pointer to a location in a table in which the content data value is stored. For example, the image value in message image payload 406 may be a pointer to a location in image table 316 (or the address of a location in image table 316). Similarly, the value in message video payload 408 may point to data stored in video table 314, the value stored in message enhancement 412 may point to data stored in enhancement table 310, the value stored in message story identifier 418 may point to data stored in story table 312, and the values ​​stored in message sender identifier 422 and message recipient identifier 424 may point to user records stored in entity table 308.

[0097] Figure 5is an interaction diagram illustrating a process 500 for interacting with a visual code to access features within a messaging system according to some examples. Figure 1 The message transceiving client 104 and the message transceiving server system 108 are used to describe the process 500. However, one or more frames (or operations) of the process 500 can be performed by one or more other components and / or performed by other suitable devices. Further for the purpose of illustration, the frames (or operations) of the process 500 are described in this article as occurring in series or linearly. However, multiple frames (or operations) of the process 500 can occur in parallel or simultaneously. In addition, the frames (or operations) of the process 500 do not need to be performed in the order shown, and / or one or more frames (or operations) of the process 500 do not need to be performed and / or can be replaced by other operations. The process 500 can terminate when its operation is completed. In addition, the process 500 can correspond to a method, a program, an algorithm, etc.

[0098] In one or more embodiments, the messaging client 104 is executed on a client device 102 associated with a user of the messaging server system 108. The user is associated with a user account of the messaging server system 108. For example, the user is identified by the messaging server system 108 based on one or more unique identifiers (e.g., a messaging system identifier, an email address, and / or a device identifier) ​​associated with the user account of the user. In some embodiments, the messaging server system 108 implements and / or works in conjunction with a social network server 124 that is configured to identify other users (e.g., friends) with whom the user of the messaging client 104 has a relationship.

[0099] As described above, each of the visual code scanner system 214 and the enhancement system 208 may correspond to a respective subsystem of the messaging system 100 and may be supported on the client side by the messaging client 104 and / or on the server side by the application server 114. Thus, the operations described herein with respect to the visual code scanner system 214 and the enhancement system 208 may be implemented on the client side, the server side, and / or a combination of the client side and the server side.

[0100] As described herein, the messaging system 100 enables a user to interact with a visual code to access features of the messaging system 100. In response to a user selection of a visual code in a captured image, the messaging client 104 enables updating of a custom graphic within the visual code. The messaging client 104 animates the movement of the custom graphic from the visual code to a carousel interface having user-selectable icons for corresponding augmented reality content, and also updates the carousel interface having icons corresponding to the visual code. Code (e.g., assets) for implementing the corresponding augmented reality content item may be automatically downloaded and / or activated, thereby reducing the amount of interaction required from the user.

[0101] At box 502, the messaging client 104 running on the messaging client 104 displays the captured image data, which includes a visual code with a custom graphic and mark. As described above, the messaging client 104 is configured to access image data (e.g., still images, videos) including the visual code. The image data can be captured in real time by the client device 102 (e.g., a real-time image feed from a camera sensor of the client device 102). For example, the messaging client 104 can activate the camera when the messaging client 104 is initiated. The messaging client 104 can also include an interface element for activating the camera and for switching between the front camera and the rear camera.

[0102] As an alternative to capturing image data in real time, the image data may correspond to a previous image captured by the client device 102 or by another device. For example, the previous image may have been sent as a message to the user of the messaging client 104, or the user may have chosen to view / download the previous image via the messaging client 104.

[0103] The captured image data may correspond to an object, such as a poster, a computer display, clothing, or printed paper. The visual code may be printed on the object or otherwise appear on the object. In one or more embodiments, the visual code is a square shape with rounded edges.

[0104] In one or more embodiments, the visual code includes custom graphics and markings. The custom graphics can be used as a search pattern for identifying and recognizing the visual code, or as an alignment pattern for facilitating decoding. Figure 6 to Figure 1 0, the custom graphic is depicted as a ghost icon. However, other example custom graphics may be used, and may include designs having multiple paths, multiple polygons, multiple aesthetic elements, or other design features.

[0105] Therefore, the messaging client 104 identifies the custom graphic (e.g., ghost icon) in the image data in conjunction with the visual code scanner system 214, and uses the custom graphic as an alignment pattern for decoding the data included in the visual code. As described above, the visual code scanner system 214 extracts candidate shape features from the image data, applies rules and criteria to filter out irrelevant shape features, and performs a comparison with reference shape features based on a match score exceeding a threshold. The visual code scanner system 214 also uses the custom graphic as an alignment pattern for decoding, and generates a transformed image of the image data based on the alignment.

[0106] As described above, the visual code also includes indicia (e.g., dots) arranged in a unique configuration that is decodable to access specific features of the messaging system 100. Figure 5 In the example of , the feature corresponds to an augmented reality content item. However, the features as described herein are not limited to augmented reality content items, but may relate to other features, such as adding friends, linking to a website, connecting to specific content, etc.

[0107] Thus, at box 502, the messaging client 104 displays the visual code included within the captured image data. The visual code includes a custom graphic (e.g., which can be transformed for display based on alignment) and a marker. At box 504, the user of the client device 102 selects the visual code as displayed on the messaging client 104 (e.g., via a tap or press gesture). In response to such a user selection, the visual code scanner system 214 decodes the marker of the visual code. As a non-limiting example, the marker (e.g., dot) of the visual code is decoded into data shown as 1 for dots and 0 for non-dots to identify a specific feature (e.g., an augmented reality content item).

[0108] At block 506, the messaging client 104 displays the updated custom graphic. For example, the messaging client 104 causes the custom graphic to be modified to indicate the user selection received at block 504. As a non-limiting example, and as described below with respect to Figures 7 and 8 As discussed, the original custom graphic of the ghost icon with two open eyes is updated to blink. Updating the custom graphic may correspond to replacing the original custom graphic (e.g., a non-blinking ghost icon) with a static image (e.g., a blinking ghost icon). Alternatively, updating the custom graphic may correspond to animating the custom graphic (e.g., animating the ghost icon to blink or perform another predefined action).

[0109] In one example, the updated custom graphic is a default graphic (e.g., a default static image or a default animation) predefined (e.g., by a system administrator). In another example, the updated custom graphic can be set based on a code (e.g., an asset) for the corresponding augmented reality content item. As described herein, a visual code corresponds to an augmented reality content item having a code associated therewith. The code includes stored assets for implementing an augmented reality (e.g., a visual and / or audio effect) corresponding to the augmented reality content item. In addition, the code can include a specific icon for the augmented reality content item, wherein the specific icon can be used within the carousel interface.

[0110] In this regard, as follows Fig. 9 Further discussed, at box 508, the messaging client 104 enables the custom graphics to be animated to move from the display area of ​​the visual code to the carousel interface. In one or more embodiments, the carousel interface provided by the messaging client 104 allows the user to cycle through and / or select different augmented reality content items (e.g., lenses) to apply with respect to captured image data. Each of the available augmented reality content items is represented by a specific icon (e.g., a circular icon), which is user-selectable to switch to the corresponding augmented reality content item. As described above, each of the augmented reality content items has a corresponding code that implements an effect (e.g., video and / or audio effect) for the augmented reality content item and a specific icon.

[0111] The icon corresponding to the currently active augmented reality content item can be displayed in a different manner relative to the remaining icons. For example, the icon of the active augmented reality content item is displayed as centered, larger, and / or highlighted relative to the remaining icons in the carousel interface. In one or more embodiments, the remaining icons are displayed in a ranking order, for example, based on a predefined ranking (e.g., one or more of popularity, personal history, promotion, etc.).

[0112] In addition, at block 510, the messaging client 104 updates the carousel interface to include an additional icon of the augmented reality content item corresponding to the visual code. For example, the messaging client 104 provides an animation depicting the additional icon as being inserted between two existing icons of the carousel interface.

[0113] In one or more embodiments, the messaging client 104 can enable updating of custom graphics (e.g., box 506), moving the visual code toward the carousel interface (e.g., box 508), and inserting additional icons into the carousel interface (e.g., box 510) to be a smooth animated transition. For example, the messaging client 104 moves the custom graphics toward the carousel interface and transforms (e.g., scales, rotates, etc.) while moving. In addition, the messaging client 104 enables animating existing icons in the carousel interface to make room for additional icons, and enables smooth changes of custom graphics from graphics visible on the code (e.g., original ghost icons) to specific icons created for augmented reality content items.

[0114] At operation 512, the messaging client 104 sends a request for the code of the augmented reality content item corresponding to the visual code to the messaging server system 108. In response, the messaging server system 108 sends the code of the augmented reality content item corresponding to the visual code to the messaging client 104 (operation 514).

[0115] As described above, the code may include assets for implementing / realizing the augmented reality content item. In one or more implementations, the code is stored in the augmented table 310 of the database 126. The request of operation 512 may include an identifier of the augmented reality content item, where the identifier is based on decoding the tag as described above.

[0116] In response to receiving the code, the messaging client 104 enables activation of the augmented reality content item with respect to the captured image data (block 516). As described above, activating the augmented reality content item includes presenting visual and / or audio effects associated with the augmented reality content item in conjunction with the captured image data.

[0117] As follows about FIG. 10A to FIG. 10C As discussed further, the messaging client 104 may implement different options for downloading code for an augmented reality content item and / or for activating an augmented reality content item. The selection of an option may be determined by a user or system administrator based on an appropriate interface provided by the messaging system 100.

[0118] In a first option, the messaging client 104 requests a code corresponding to the augmented reality content item in response to the user input selecting the visual code at block 504 (e.g., per operation 512), and downloads the code (e.g., per operation 514). In addition, the messaging client 104 requests a code corresponding to the augmented reality content item in response to the user input selecting the visual code at block 504 (e.g., per operation 514). Figure 5 ), the second user input selects an additional icon to be inserted into the carousel interface (eg, as per box 510).

[0119] In the second option, the messaging client 104 requests a code corresponding to the augmented reality content item (e.g., per operation 512), downloads the code (e.g., per operation 514), and activates the augmented reality content item (e.g., per block 516), all in response to the user input selecting the code at block 504. Thus, the second option differs from the first option in that the second option does not require a second user input to activate the augmented reality content item.

[0120] In a third option, messaging client 104 responds to a second user input (eg, per block 510) selecting an additional icon to be inserted into the carousel interface. Figure 5 512), and downloads the code (e.g., according to operation 514). For example, the additional icon is initially grayed out when inserted into the carousel interface. User selection of the grayed-out icon causes the messaging client 104 to request and download the code corresponding to the augmented reality content item. The messaging client 104 may provide an animation showing the progress of the download. For example, the animation may gradually remove the gray mask of the icon to indicate download progress and completion.

[0121] Although Figure 5 The example of relates to interactions with visual codes for augmented reality content items, but the messaging system 100 is not limited thereto. The messaging system 100 may enable similar interactions with visual codes for other features provided by the messaging system 100. Examples of other such features include, but are not limited to: adding friends, linking to a website, connecting to specific content, etc.

[0122] Therefore, the messaging system 100 as described herein can interact with the visual code to access the features of the messaging system 100. In other systems, after selecting the visual code, a separate message box (e.g., superposition) is presented to the user, which prompts the user to download and / or activate the feature. This prompt may be distracting because it diverts the user's attention from the current interface related to the feature. The messaging system 100 can perform a more seamless transition when downloading and / or activating the feature. In the case where the visual code interaction as described herein cannot be performed, additional prompts that may distract and interfere with the user interface flow can be provided to the end user. Therefore, the messaging system 100 saves time for the user, and / or reduces the computing resources / processing power associated with the additional prompts and the associated delays. In addition, the visual code interaction as described herein may be more attractive to the users of the messaging system 100.

[0123] Figure 6A user interface 602 is shown in which a visual code is displayed within captured image data according to some example embodiments. Figure 6 As shown in the example of , user interface 602 includes visual code 604 , mark 606 , custom graphic 608 , captured image data 610 , and carousel interface 612 .

[0124] In one or more implementations, user interface 602 is provided by messaging client 104. User interface 602 enables display of augmented reality content in association with captured image data 610. As described above, captured image data 610 may correspond to image data captured by a front-facing camera or a rear-facing camera of client device 102. Alternatively, the image data may correspond to a previous image captured via client device 102 or another device.

[0125] The augmented reality content displayed in association with the captured image data 610 is based on the currently selected augmented reality content item (e.g., lens). In this regard, the carousel interface 612 includes a set of icons, each of which is user-selectable (e.g., via a tap / press gesture) to select / activate a corresponding augmented reality content item. The carousel interface 612 allows the user to cycle through the icons (e.g., via a swipe gesture) and select a specific augmented reality content item to apply with respect to the captured image data 610.

[0126] Although in Figure 6 , but each icon can have a corresponding graphic to indicate its corresponding augmented reality content item (e.g., a hair graphic to indicate a hair effect, a smile graphic to indicate a smile effect, etc.). The icon of the active augmented reality content item can be centered, larger, and / or highlighted relative to the rest of the icons in the carousel interface 612.

[0127] exist Figure 6 In the example of , captured image data 610 includes visual code 604. For example, captured image data 610 may correspond to an object (e.g., a poster, a computer display, clothing, or printed paper), and visual code 604 may appear on the object. Visual code includes custom graphics 608 and indicia 606.

[0128] As described above, a custom graphic 608 may be used as a lookup pattern for identifying and recognizing the visual code 604. Figure 6 In the example of , custom graphics 608 are depicted as ghost icons. However, other custom graphics may be used.

[0129] The indicia 606 of the visual code 604 are arranged in a unique configuration that is decodable to access specific features of the messaging system 100. Figure 6In the example of , the feature corresponds to an augmented reality content item. User selection of visual code 604 provides the user with access to the corresponding augmented reality content item.

[0130] Figure 7 The user interface 602 is shown with a user selecting a visual code 604 to activate an augmented reality content item according to some example embodiments. Figure 7 In the example of FIG. 6 , the user selects touch input 702 (e.g., a tap or press gesture) depicted as being performed with respect to the visual code 604. In response to the touch input 702, the visual code scanner system 214 decodes the indicia of the visual code (e.g., to identify the corresponding augmented reality content item) and proceeds to present the following information about the Figure 8 , Fig. 9 and FIG. 10A to FIG. 10C Animation for discussion.

[0131] Figure 8 6 shows a user interface 602 in which a custom graphic 608 of a visual code 604 is updated in response to a user selection (e.g., touch input 702) according to some example embodiments. The update of the custom graphic 608 visually indicates the receipt of the touch input 702 to the user of the client device 102. Figure 8 As shown in the example of , the original custom graphic 608 of the ghost icon is updated to blink. Updating the custom graphic 608 can correspond to replacing the original custom graphic (e.g., a non-blinking ghost icon) with a predefined static image (e.g., a blinking ghost icon). In one or more embodiments, updating the custom graphic 608 corresponds to animating the custom graphic (e.g., animating the ghost icon to blink or perform another predefined action).

[0132] Fig. 9 According to some example embodiments, Figure 8 The updated custom graphic 608 is animated to move toward the carousel interface 612 and is inserted into the user interface 602 within the carousel interface 612. Fig. 9 In the example of , animation 902 represents the movement of the updated custom graphic 608 from the display area of ​​the visual code 604 to the display area of ​​the carousel interface 612. The arrows of the animation 902 are depicted for illustrative purposes to indicate such movement.

[0133] about Fig. 10A, the messaging client 104 updates the carousel interface 612 to include an additional icon 1002 for the augmented reality content item corresponding to the visual code 604. For example, the messaging client 104 provides an animation depicting the additional icon 1002 as being inserted between two existing icons in the carousel interface 612. As described above, the carousel interface 612 allows the user to cycle through the augmented reality content items based on predefined user gestures. Fig. 10A The example of shows four icons, but the messaging client 104 is configured to present additional icons in response to a predefined user gesture (e.g., a slide gesture). For example, in response to a slide gesture, the carousel interface 612 presents icons that are not currently displayed, where the icons are ranked as described above.

[0134] FIG. 10A to FIG. 10C Different ways to download and / or activate an augmented reality content item corresponding to a visual code 604 are shown according to some example implementations. As described above, the messaging client 104 may implement different options for downloading a code (e.g., an asset) for an augmented reality content item and / or for activating an augmented reality content item.

[0135] Fig. 10A As shown above, Figure 5 Both the first and second options discussed. In the first option, the messaging client 104 responds to a first user input of a selection code (e.g., Figure 5 504) and request the code (e.g., asset) for the augmented reality content item, and download the code. In addition, the messaging client 104 activates the augmented reality content item in response to a second user input selecting the icon 1002 inserted into the carousel interface 612.

[0136] In a second option, the messaging client 104 requests a code (e.g., an asset) for the augmented reality content item in response to the first user input selecting the code, downloads the code, and in response to the first user input selecting the code (e.g., Figure 5 Therefore, the second option is different from the first option in that the second option does not require a second user input to select icon 1002.

[0137] Fig. 10B As shown above, Figure 5 After inserting the icon 1002 into the carousel interface 612, the messaging client 104 receives a second user input selecting the icon 1002. In response to receiving the second user input, the messaging client 104 requests the code (e.g., asset) corresponding to the augmented reality content item and downloads the code.

[0138] like Fig. 10BAs shown in the example of , icon 1002 is initially grayed out when inserted into carousel interface 612. User selection of the grayed out icon causes messaging client 104 to request and download code corresponding to the augmented reality content item.

[0139] Fig. 10C An expanded view of icon 1002 is depicted to show that messaging client 104 provides an animation showing the download progress of the augmented reality content item. For example, the animation gradually removes the gray mask of icon 1002 to indicate download progress and completion.

[0140] Fig.11 1 is a flow chart illustrating a process 1100 for interacting with a visual code to access features within a messaging system according to some examples. Figure 1 The messaging client 104 of process 1100 is used to describe process 1100. However, one or more frames (or operations) of process 1100 can be performed by one or more other components and / or performed by other suitable devices. Further for the purpose of illustration, the frames (or operations) of process 1100 are described in this article as occurring serially or linearly. However, multiple frames (or operations) of process 1100 can occur in parallel or simultaneously. In addition, the frames (or operations) of process 1100 do not need to be performed in the order shown, and / or one or more frames (or operations) of process 1100 do not need to be performed and / or can be replaced by other operations. Process 1100 can terminate when its operation is completed. In addition, process 1100 can correspond to method, program, algorithm, etc.

[0141] The messaging client 104 displays captured image data including a visual code, the visual code including a custom graphic and being decodable to access a first feature of a messaging application (block 1102). The visual code may include a unique configuration of indicia that is decodable to access the first feature. The messaging client 104 receives user input selecting the visual code (block 1104).

[0142] The messaging client 104 displays the updated version of the custom graphic (block 1106). The updated version of the custom graphic may correspond to a predefined static image. Alternatively, the updated version of the custom graphic may correspond to a predefined animation.

[0143] The messaging client 104 provides an animation depicting the updated version of the custom graphic as moving from the visual code to an interface element comprising a set of icons, each icon within the set of icons being selectable by the user to access a respective second feature of the messaging application (block 1108).

[0144] The interface element may be a carousel interface for navigating a set of icons. Each of the respective second features and the first feature may correspond to a respective augmented reality content item for application to the captured image data.

[0145] The messaging client 104 may download code for a first augmented reality content item corresponding to the first feature from the messaging server system 108. The messaging client 104 may activate the first augmented reality content item with respect to the captured image data based on the downloaded code.

[0146] Downloading the code may be in response to a second user input selecting an additional icon within a set of icons. Alternatively, downloading the code may be in response to receiving a user input (as per block 1104), and activating the first augmented reality content item may be in response to receiving a second user input selecting an additional icon within a set of icons.

[0147] The messaging client 104 updates the set of icons to include an additional icon that is selectable by the user to access a first feature of the messaging application (block 1110).

[0148] Fig.12 is a schematic diagram illustrating an access restriction process 1200, according to which access to content (e.g., ephemeral message 1202 and associated multimedia data payload) or a collection of content (e.g., ephemeral message group 1204) can be time-restricted (e.g., made ephemeral).

[0149] The ephemeral message 1202 is shown to be associated with a message duration parameter 1206, the value of which determines the amount of time that the messaging client 104 will display the ephemeral message 1202 to the receiving user of the ephemeral message 1202. In one example, depending on the amount of time specified by the sending user using the message duration parameter 1206, the receiving user can view the ephemeral message 1202 for up to 10 seconds.

[0150] The message duration parameter 1206 and the message recipient identifier 424 are shown as inputs to a message timer 1210, which is responsible for determining the amount of time that the transient message 1202 is shown to a particular receiving user identified by the message recipient identifier 424. In particular, the transient message 1202 is shown to the associated receiving user only for the period of time determined by the value of the message duration parameter 1206. The message timer 1210 is shown as providing an output to a more general transient timer system 202, which is responsible for the overall timing of displaying content (e.g., the transient message 1202) to the receiving user.

[0151] Short message 1202 Fig.121204 (e.g., a collection of messages in a personal story or an event story). The ephemeral message group 1204 has an associated group duration parameter 1208, the value of which determines the duration for which the ephemeral message group 1204 is presented and accessible to users of the messaging system 100. For example, the group duration parameter 1208 may be the duration of a concert, where the ephemeral message group 1204 is a collection of content about the concert. Alternatively, a user (an owning user or a curator user) may specify a value for the group duration parameter 1208 when performing setup and creation of the ephemeral message group 1204.

[0152] In addition, each ephemeral message 1202 within the ephemeral message group 1204 has an associated group participation parameter 1212, the value of which determines the duration for which the ephemeral message 1202 is accessible within the context of the ephemeral message group 1204. Thus, a particular ephemeral message group 1204 may "expire" and become inaccessible within the context of the ephemeral message group 1204 before the ephemeral message group 1204 itself expires according to the group duration parameter 1208. The group duration parameter 1208, the group participation parameter 1212, and the message recipient identifier 424 each provide inputs to a group timer 1214, which is operable to first determine whether a particular ephemeral message 1202 in the ephemeral message group 1204 is to be displayed to a particular receiving user, and if so, how long to display it. Note that the identity of the particular receiving user is also known to the ephemeral message group 1204 due to the message recipient identifier 424.

[0153] Thus, the group timer 1214 is operable to control the total lifespan of the associated ephemeral message group 1204 and the individual ephemeral messages 1202 included in the ephemeral message group 1204. In one example, each ephemeral message 1202 within the ephemeral message group 1204 remains viewable and accessible for a period of time specified by the group duration parameter 1208. In another example, within the context of the ephemeral message group 1204, a particular ephemeral message 1202 may expire based on the group participation parameter 1212. Note that even within the context of the ephemeral message group 1204, the message duration parameter 1206 may still determine the duration for which a particular ephemeral message 1202 is displayed to a receiving user. Thus, the message duration parameter 1206 determines the duration for which a particular ephemeral message 1202 is displayed to a receiving user, regardless of whether the receiving user is viewing the ephemeral message 1202 within or outside the context of the ephemeral message group 1204.

[0154] The transient timer system 202 may also be operable to remove a particular transient message 1202 from a transient message group 1204 based on a determination that an associated group participation parameter 1212 has been exceeded. For example, where a sending user has established a group participation parameter 1212 of 24 hours from posting, the transient timer system 202 will remove the associated transient message 1202 from the transient message group 1204 after the designated 24 hours. The transient timer system 202 is also operable to remove a transient message group 1204 when the group participation parameter 1212 for each transient message 1202 within the transient message group 1204 has expired, or when the transient message group 1204 itself has expired according to the group duration parameter 1208.

[0155] In some use cases, the creator of a particular ephemeral message group 1204 may specify an indefinite group duration parameter 1208. In this case, the expiration of the group participation parameter 1212 for the last remaining ephemeral message 1202 within the ephemeral message group 1204 will determine when the ephemeral message group 1204 itself expires. In this case, a new ephemeral message 1202 with a new group participation parameter 1212 added to the ephemeral message group 1204 effectively extends the life of the ephemeral message group 1204 to a value equal to the group participation parameter 1212.

[0156] In response to the transient timer system 202 determining that the ephemeral message group 1204 has expired (e.g., is no longer accessible), the transient timer system 202 communicates with the messaging system 100 (and, for example, in particular, the messaging client 104) to cause the indicia (e.g., icon) associated with the relevant ephemeral message group 1204 to no longer be displayed within the user interface of the messaging client 104. Similarly, when the transient timer system 202 determines that the message duration parameter 1206 for a particular ephemeral message 1202 has expired, the transient timer system 202 causes the messaging client 104 to no longer display the indicia (e.g., icon or text identification) associated with the ephemeral message 1202.

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

[0158] The machine 1300 may include a processor 1304, a memory 1306, and an input / output I / O component 1302 that may be configured to communicate with each other via a bus 1340. In an example, the processor 1304 (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 1308 that executes instructions 1310 and a processor 1312. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions simultaneously. Although Fig.13 Multiple processors 1304 are shown, but the machine 1300 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

[0159] The memory 1306 includes a main memory 1314, a static memory 1316, and a storage unit 1318, all of which are accessible by the processor 1304 via a bus 1340. The main memory 1306, the static memory 1316, and the storage unit 1318 store instructions 1310 that implement any one or more of the methods or functions described herein. The instructions 1310 may also reside, completely or partially, within the main memory 1314, within the static memory 1316, within the machine-readable medium 1320 within the storage unit 1318, within at least one of the processors 1304 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 1300.

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

[0161] In other examples, the I / O component 1302 may include a biometric component 1330, a motion component 1332, an environment component 1334, or a position component 1336, as well as various other components. For example, the biometric component 1330 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1332 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

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

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

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

[0165] The location component 1336 includes a positioning 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 obtained), an orientation sensor component (e.g., a magnetometer), and the like.

[0166] Various technologies may be used to implement communications. I / O components 1302 also include communications components 1338 that are operable to couple machine 1300 to network 1322 or device 1324 via corresponding couplings or connections. For example, communications components 1338 may include a network interface component or another suitable device that interfaces with network 1322. In other examples, communications components 1338 may include wired communications components, wireless communications components, cellular communications components, near field communications (NFC) components, Parts (e.g. Low energy consumption), Device 1324 may be another machine or any of a variety of peripherals (eg, a peripheral coupled via USB).

[0167] In addition, the communication component 1338 can detect the identifier, or include a component that is operable to detect the identifier. For example, the communication component 1338 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 an audio signal of a tag). In addition, various information can be obtained via the communication component 1338, such as obtaining positioning via Internet Protocol (IP) geolocation, ... Positioning is obtained by signal triangulation, positioning is obtained via detection of NFC beacon signals that can indicate a specific position, etc.

[0168] Various memories (e.g., main memory 1314, static memory 1316, and memory of processor 1304) and storage unit 1318 may store one or more sets of instructions and data structures (e.g., software) implemented or used by any one or more of the methods or functions described herein. These instructions (e.g., instructions 1310) when executed by processor 1304 cause various operations to implement the disclosed examples.

[0169] The instructions 1310 may be sent or received via a network interface device (e.g., a network interface component included in the communication component 1338) using a transmission medium and using any of several well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)) over the network 1322. Similarly, the instructions 1310 may be sent or received via a coupling (e.g., a peer-to-peer coupling) with the device 1324 using a transmission medium.

[0170] Fig.14 1400 is a block diagram illustrating a software architecture 1404 that may be installed on any one or more of the devices described herein. The software architecture 1404 is supported by hardware such as a machine 1402 including a processor 1420, a memory 1426, and an I / O component 1438. In this example, the software architecture 1404 may be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1404 includes layers such as an operating system 1412, a library 1410, a framework 1408, and an application 1406. In operation, the application 1406 invokes an API call 1450 through the software stack and receives a message 1452 in response to the API call 1450.

[0171] The operating system 1412 manages hardware resources and provides public services. The operating system 1412 includes, for example, a kernel 1414, services 1416, and drivers 1422. The kernel 1414 acts as an abstraction layer between the hardware layer and other software layers. For example, the kernel 1414 provides memory management, processor management (e.g., scheduling), component management, networking and security settings, and other functions. Services 1416 can provide other public services to other software layers. Drivers 1422 are responsible for controlling or interfacing with the underlying hardware. For example, drivers 1422 may include display drivers, camera drivers, or Low-power drivers, Flash drivers, Serial communication drivers (e.g., USB drivers), Drivers, audio drivers, power management drivers, etc.

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

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

[0174] In an example, applications 1406 may include a home application 1436, a contacts application 1430, a browser application 1432, a book reader application 1434, a positioning application 1442, a media application 1444, a messaging application 1446, a game application 1448, and a variety of other applications such as third-party applications 1440. Application 1406 is a program that executes the functions defined in the program. Various programming languages ​​can be used to create one or more of the applications 1406 constructed in various ways, such as an object-oriented programming language (e.g., Objective-C, Java, or C++) or a procedural programming language (e.g., C language or assembly language). In a specific example, third-party applications 1440 (e.g., those used by entities other than the vendor of a particular platform using ANDROID TM or IOS TM Software Development Kit (SDK) can be used to develop applications on platforms such as IOS TM ANDROID TM , Mobile software running on the mobile operating system of the phone or another mobile operating system. In this example, third-party applications 1440 can activate API calls 1450 provided by the operating system 1412 to facilitate the functions described herein.

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

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

[0177] "Communications network" means one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a 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, The coupling may be a network, another type of network, or a combination of two or more such networks. For example, the network 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 system for mobile communications (GSM) connection, or other type 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 rate 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) standards, other data transmission technologies defined by various standard setting organizations, other long distance protocols, or other data transmission technologies.

[0178] "Component" refers to a device, physical entity or logic with the following boundaries: the boundaries are 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 specific functions in related functions. 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 examples, 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 can also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component may include a dedicated circuit system or logic that is permanently configured to perform certain operations. The hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The hardware component may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, the hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of a machine) that is uniquely customized to perform the configured function and is no longer a general-purpose processor. It will be recognized that it can be determined for cost and time considerations whether to mechanically implement the hardware component in a dedicated and permanently configured circuit system or in a temporarily configured (e.g., configured by software) circuit system to implement the hardware component. 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. Considering an example where a hardware component is temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each hardware component in the hardware component at any one time. For example, where a hardware component includes a general purpose processor that is configured by software to be a special purpose processor, the general purpose processor may be configured as different special purpose processors (e.g., including different hardware components) at different times. The software configures a specific one or more processors accordingly, for example, to constitute a specific hardware component at one time and to constitute different hardware components at different times. Hardware components may provide information to other hardware components and receive information from other hardware components. Therefore, the described hardware components may be considered to be communicatively coupled.In the case of multiple hardware components being present at the same time, communication can be realized by (for example, by appropriate circuits and buses) transmitting signals between or among two or more hardware components in these hardware components. In examples where 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 accessible to 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 to it in communication. Then, other hardware components can access the memory device at a subsequent time to retrieve the stored output and process it. The hardware component can also initiate communication with an input device or an output device, and can operate on resources (for example, a collection of information). The various operations of the example methods described in this article can be performed at least in part by one or more processors that are temporarily configured (for example, by software) or permanently configured to perform related operations. Whether it is temporarily configured or permanently configured, such a processor 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. Similarly, the method described in this article can be implemented at least in part by a processor, wherein one or more specific processors are examples of hardware. For example, at least some of the operation of the method can be performed by one or more processors or the components implemented by the processor. In addition, one or more processors 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 of the operations in the operation can be performed by a computer group (as an example of a machine including a processor), wherein these operations can be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). The execution of certain operations can be distributed between processors, not only resident in a single machine, but also deployed across multiple machines. In some examples, a processor or a component implemented by a processor can be located in a single geographic location (e.g., in a home environment, an office environment, or a server cluster). In other examples, a processor or a component implemented by a processor can be distributed across multiple geographic locations.

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

[0180] "Ephemeral messages" are messages that can be accessed for a limited duration of time. Ephemeral messages can be text, images, videos, etc. The access time of an ephemeral 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 ephemeral.

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

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

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

Claims

1. A method comprising: displaying, by a messaging application executing on a client device, the captured image data including a visual code, the visual code including a custom graphic and being decodable to access a first feature of the messaging application; receiving, by the messaging application, user input selecting the visual code; as well as In response to receiving the user input, displays an updated version of said custom graphic, providing an animation depicting an updated version of the custom graphic as moving from the visual code to an interface element comprising a set of icons, each icon within the set of icons being selectable by a user to access a corresponding second feature of the messaging application, and The set of icons is updated to include additional icons that are user-selectable to access the first feature of the messaging application.

2. The method according to claim 1, wherein: The visual code also includes a unique configuration of indicia that is decodable to access the first feature.

3. The method according to claim 1, wherein: Each of the respective second features and the first feature corresponds to a respective augmented reality content item for application to the captured image data.

4. The method according to claim 3, further comprising: downloading, by the client device, from a server, code for a first augmented reality content item corresponding to the first feature; as well as Based on downloading the code, the first augmented reality content item is activated with respect to the captured image data.

5. The method according to claim 4, wherein: Downloading the code is in response to a second user input selecting the additional icon within the set of icons.

6. The method according to claim 4, wherein: Downloading the code is in response to receiving the user input, and Wherein activating the first augmented reality content item is in response to receiving a second user input selecting the additional icon within the group of icons.

7. The method according to claim 1, wherein: The interface element is a carousel interface for navigating the set of icons.

8. The method according to claim 1, wherein: The updated version of the custom graphic corresponds to a predefined static image.

9. The method according to claim 1, wherein: The updated version of the custom graphic corresponds to the predefined animation.

10. A device comprising: processor; as well as a memory storing instructions that, when executed by the processor, configure the processor to perform operations comprising: displaying, by a messaging application running on the device, the captured image data including a visual code, the visual code including a custom graphic and being decodable to access a first feature of the messaging application; receiving, by the messaging application, user input selecting the visual code; and In response to receiving the user input, displays an updated version of said custom graphic, providing an animation depicting an updated version of the custom graphic as moving from the visual code to an interface element comprising a set of icons, each icon within the set of icons being selectable by a user to access a corresponding second feature of the messaging application, and The set of icons is updated to include additional icons that are user-selectable to access the first feature of the messaging application.

11. The device according to claim 10, wherein: The visual code also includes a unique configuration of indicia that is decodable to access the first feature.

12. The device according to claim 10, wherein: Each of the respective second features and the first feature corresponds to a respective augmented reality content item for application to the captured image data.

13. The apparatus of claim 12, the operations further comprising: downloading from a server a code for a first augmented reality content item corresponding to the first feature; as well as Based on downloading the code, the first augmented reality content item is activated with respect to the captured image data.

14. The device according to claim 13, wherein: Downloading the code is in response to a second user input selecting the additional icon within the set of icons.

15. The apparatus according to claim 13, wherein: Downloading the code is in response to receiving the user input, and Wherein activating the first augmented reality content item is in response to receiving a second user input selecting the additional icon within the group of icons.

16. The apparatus according to claim 10, wherein: The interface element is a carousel interface for navigating the set of icons.

17. The apparatus according to claim 10, wherein: The updated version of the custom graphic corresponds to a predefined static image.

18. The apparatus according to claim 10, wherein: The updated version of the custom graphic corresponds to the predefined animation.

19. A non-transitory computer-readable storage medium comprising instructions, which, when executed by a computer, cause the computer to perform operations comprising: displaying, by a messaging application executing on a client device, the captured image data including a visual code, the visual code including a custom graphic and being decodable to access a first feature of the messaging application; receiving, by the messaging application, user input selecting the visual code; as well as In response to receiving the user input, displays an updated version of said custom graphic, providing an animation depicting an updated version of the custom graphic as moving from the visual code to an interface element comprising a set of icons, each icon within the set of icons being selectable by a user to access a corresponding second feature of the messaging application, and The set of icons is updated to include additional icons that are user-selectable to access the first feature of the messaging application.

20. The computer-readable medium of claim 19, wherein: The visual code also includes a unique configuration of indicia that is decodable to access the first feature.

Images