Thumbnail of the recorded sound

Abstract

Aspects of the present disclosure relate to systems and methods for performing operations, the operations comprising: displaying, by a messaging application, a sound capture screen that enables a user to record sound; generating, by the messaging application, a visual element associated with the sound after recording the sound using the sound capture screen; receiving, by the messaging application, a selection of a visual element from a displayed list of visual elements representing different sounds; in response to receiving the selection of the visual element, conditionally adding one or more graphics representing the sound to one or more images at a user-selected location based on a privacy status of the sound; and playing, by the messaging application, the sound associated with the visual element along with displaying the one or more images.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of priority to U.S. Provisional Application Serial No. 62 / 706,872, filed on September 15, 2020, and U.S. Patent Application Serial No. 16 / 948,451, filed on September 18, 2020, each of which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure generally relates to recording sound using a messaging application. Background Art

[0004] The popularity of users interacting with other users online continues to grow. There are many ways for users to interact with other users online. Users can communicate with their friends using messaging applications, and can play multiplayer video games online with other users, or use a variety of other applications to perform other actions. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] In the drawings, which are not necessarily drawn to scale, like numbers may describe similar parts 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 networked 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 maintained in a database according to some examples.

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

[0010] Figures 5 to 9 is a diagrammatic representation of a graphical user interface according to some examples.

[0011] Fig.10 is a flow diagram illustrating example operation of a messaging application according to an example implementation.

[0012] Fig.11is 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.

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

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

[0015] Typically, users exchange messages with each other using messaging applications. Such applications allow users to select from a predefined list of images and avatars to send to each other. Users are increasingly using such images and avatars to communicate their ideas with each other. However, finding an appropriate image or avatar to convey a particular idea can be tedious and time-consuming. Specifically, users must manually search for a particular image or avatar that conveys a given message using keywords. This requires viewing multiple pages of information until the desired image or avatar is found. Given the complexity of finding an appropriate image or avatar and the amount of time it takes, users become discouraged from using images or avatars to communicate, which results in a waste of resources or a lack of use.

[0016] Even if an image or avatar of interest is eventually found, the images or avatars available through the messaging application are often generic and may not accurately reflect the user's thoughts. Such images or avatars can sometimes be enhanced with pre-recorded audio content. However, such audio content is also generic and may not accurately convey the user's message.

[0017] The disclosed embodiment improves the efficiency of using electronic devices by providing the following system, which allows users to create custom sounds or audio clips and associate the sounds or audio clips with images shared with other users. When the receiving user accesses one or more images associated with the sound, these images are presented to the recipient while the associated sound is played back. In some cases, the user who created the custom sound can specify the privacy status of the sound to control whether the recipient user can share the sound they received with other users and whether additional information about the sound can be viewed. Based on the privacy status of the sound, one or more graphic elements representing the sound (e.g., as stickers) can be conditionally added to the image or picture associated with the sound. If the sound is publicly available based on the privacy status, one or more images including one or more graphic elements are presented to the recipient of the image associated with the sound while the sound is played back.

[0018] Specifically, according to the disclosed embodiment, a message application implemented by one or more processors of a user device displays a sound capture screen that enables a user to record sound. After recording sound using the sound capture screen, the message application generates a visual element associated with the sound, and receives a selection of the visual element from a displayed list of visual elements representing different sounds. In response to receiving a selection of the visual element, the message application conditionally adds one or more graphics representing the sound to one or more images at a position selected by the user based on the privacy status of the sound. The message application plays the sound associated with the visual element together with displaying one or more images.

[0019] In this way, the disclosed embodiments improve the efficiency of using electronic devices by reducing the number of screens and interfaces that a user must view to find graphical elements to be shared with other users and sounds to be played with the graphical elements. This is achieved by allowing the user to record the desired sounds and presenting a graphical user interface from which the user can quickly and efficiently select the recorded sounds to be combined with one or more images (videos) captured or to be captured by the user using a client device. This reduces the device resources (e.g., processor cycles, memory, and power usage) required to complete tasks using the device.

[0020] Networked computing environment

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

[0022] The message clients 104 are capable of communicating and exchanging data with other message clients 104 and message server systems 108 via the network 112. The data exchanged between the message clients 104 and between the message clients 104 and the message server systems 108 include functions (e.g., commands for invoking functions) and payload data (e.g., text, audio, video, or other multimedia data).

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

[0024] The message server system 108 supports various services and operations provided to the message clients 104. Such operations include sending data to the message clients 104, receiving data from the message clients 104, and processing data generated by the message clients 104. 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 as examples. The data exchange within the message system 100 is initiated and controlled by functions available via the user interface (UI) of the message client 104.

[0025] Turning now specifically to the message 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 processes incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0026] 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. In particular, the application program interface (API) server 116 provides a set of interfaces (e.g., routines and protocols) that the message client 104 can call or query to invoke the functions of the application server 114. The application program interface (API) server 116 exposes various functions supported by the application server 114, including: account registration; login functionality; sending messages from a particular messaging client 104 to another messaging client 104 via the application server 114; sending media files (e.g., images or videos) from the messaging client 104 to the messaging server 118; and setting up collections of media data (e.g., stories) for access by another messaging client 104, retrieving a friend list of a user of the client device 102, retrieving such collections, retrieving messages and content, adding and removing entities (e.g., friends) from an entity graph (e.g., a social graph), locating friends in a social graph, and opening application events (e.g., related to a messaging client 104).

[0027] The application server 114 hosts several server applications and subsystems, including, for example, a message server 118, an image processing server 122, and a social network server 124. The message server 118 implements several message processing techniques and functions, which are particularly related to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the message client 104. As will be described in further detail, text and media content from multiple sources can be aggregated into content collections (e.g., called stories or galleries). These collections are then made available to the message 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 message server 118.

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

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

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

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

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

[0033] The message 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 message client 104 may provide a notification to a participant in a conversation (e.g., a chat session) in the message client 104 about the current or recent use of an external resource by one or more members of a user group. One or more users may be invited to join an active external resource or to start an external resource that was recently used but is currently inactive (in a friend group). The external resource may provide the participants in the conversation (each participant using a corresponding message client 104) with the ability to share items, conditions, states, or locations in the external resource with one or more members of the user group entering the chat session. The shared item may be an interactive chat card that members of the chat may interact with, for example, to start a corresponding external resource, view specific information within an external resource, or bring members of the chat to a specific location or state within an external resource. Within a given external resource, a response message may be sent to the user on the message client 104. The external resource may selectively include different media items in the response based on the current context of the external resource.

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

[0035] System Architecture

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

[0037] The transient timer system 202 is responsible for implementing temporary or time-limited access to content by the message client 104 and the message server 118. The transient timer system 202 includes a number of timers that selectively enable access (e.g., for presentation and display) of messages and associated content via the message 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.

[0038] The collection management system 204 is responsible for managing groups 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.

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

[0040] The enhancement system 208 provides various functions that enable a user to enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the enhancement system 208 provides functions related to generating and publishing media overlays for messages processed by the messaging system 100. The enhancement system 208 is operable to supply 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 supply 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 may 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 may be applied to media content items (e.g., photos) at the client device 102. For example, the media overlay may include text or images that may be overlaid on a photo 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 the name of a business at the geolocation of the client device 102. The media overlay may include other indicia associated with the business. The media overlay may be stored in the database 126 and accessed through the database server 120.

[0041] 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 an environment 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.

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

[0043] 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 316) on a map to indicate the current or past locations of the user's "friends" in the context of the map, as well as media content (e.g., a collection of messages including photos and videos) generated by such friends. For example, a message posted to the messaging system 100 by a user from a particular geolocation can be displayed to the particular user's "friends" at the particular location in the context of the map on the mapping interface of the messaging client 104. The user can also share his or her location and status information with other users of the messaging system 100 (e.g., using an appropriate status avatar) via the messaging client 104, where the location and status information is similarly displayed to selected users in the context of the mapping interface of the messaging client 104.

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

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

[0046] To integrate the functionality of the SDK into the web-based resource, the SDK is downloaded from the message server 118 by the external resource (app) server 110 or received in other ways by the external resource (app) server 110. 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 message client 104 into the web-based resource.

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

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

[0049] Message client 104 presents the graphical user interface (e.g., login page or title screen) of external resources. During, before or after presenting the login page or title screen, message client 104 determines whether the external resource started has been previously authorized to access the user data of message client 104. In response to determining that the external resource started has been previously authorized to access the user data of message client 104, message client 104 presents another graphical user interface including the functions and features of the external resource of the external resource. In response to determining that the external resource started has not been previously authorized to access the user data of message client 104, after the threshold time period (e.g., 3 seconds) of the login page or title screen of the external resource is displayed, message client 104 slides up the menu (e.g., menu is animated to reveal from the bottom of the screen to the middle of the screen or other parts) for authorizing the external resource to access the user data. The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving the user selection of the option accepted, message client 104 adds the external resource to the list of authorized external resources, and allows the external resource to access the user data from message client 104. In some examples, external resources are authorized by messaging client 104 to access user data according to the OAuth 2 framework.

[0050] 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 external application (e.g., a third party or external application 109) is provided with access rights 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 external application (e.g., a web-based version of a third-party application) is provided with access rights 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, such as different poses, facial features, clothing, etc.

[0051] In some embodiments, the messaging client 104 presents an interface that allows the user to create a custom sound clip, for example, by recording up to 60 seconds of sound. Figure 5 As shown, the messaging client 104 presents a graphical user interface 500 with a sound menu 530 in response to the user selecting the music icon 520. In some cases, the music icon 520 is initially presented as an overlay menu on top of the real-time video feed 510 or previously captured video or image content. The overlay menu allows the user to select from a variety of augmented reality items and customizations to modify the real-time video feed or previously captured video or image content.

[0052] In response to receiving a user selection of the music icon 520, the menu 530 slides the display upward to cover at least half of the screen from the bottom. The menu 530 includes one or more sound clips provided by various artists or third parties, and the user can select from these sound clips. Selecting any of the displayed sound clips will cause the sound clip of the artist corresponding to the selected sound clip to be played. The user can drag the thumbnail image representing the selected sound clip to the real-time video feed 510 or the previously captured video or image content to incorporate the selected sound clip into the real-time video feed 510 or the previously captured video or image content. In this way, when the user views the real-time video feed 510 or the previously captured video or image content, the sound is automatically played. Moreover, if the user shares the real-time video feed 510 or the previously captured video or image content incorporated with the thumbnail image with a second user (e.g., a friend), the selected sound is automatically played back to the second user when the second user views the shared real-time video feed 510 or the previously captured video or image content.

[0053] In some embodiments, menu 530 includes a create sound option 532. Create sound option 532 allows the user to record a custom sound. In response to receiving a user selection to create sound option 532, messaging client 104 navigates the user to another user interface 600 ( Figure 6 ). Specifically, the messaging client 104 activates the image capture device (e.g., camera) of the client device 102 and begins receiving a real-time video feed from the image capture device. The messaging client 104 blurs or dims the received real-time video feed and presents the blurred or dimmed video feed as the image content 610. The messaging client 104 presents the sound recording option 640 as an overlay icon on top of the image content 610.

[0054] To start recording a given sound, the messaging client 104 receives a user selection (first input) of a sound recording option 640. In response to receiving the user selection of the sound recording option 640, the messaging client 104 adjusts the properties of the screen to indicate to the user that the sound is being recorded based on the audio content captured by the microphone of the client device 102. For example, the messaging client 104 displays a border 620 around all or a specified portion of the screen. As another example, the messaging client 104 begins to slowly increase and decrease the brightness of the screen to indicate that the sound is being recorded.

[0055] The message client 104 begins storing the audio content captured by the microphone in response to receiving the first input selecting the sound recording option 640. When the audio content is stored, a progress bar 642 is presented in or associated with the sound recording option 640. The progress bar 642 is continuously performed and increases in size to fill the displayed portion of the sound recording option 640. For example, the sound recording option 640 can be a circle, and the progress bar 642 can slowly fill the circle with a certain color or a set of random colors. The progress bar 642 can be any suitable shape and size to fill the sound recording option 640. In some cases, the amount of time required for the progress bar 642 to completely fill the sound recording option 640 can depend on and vary based on the maximum allowed length or duration of the sound being recorded. For example, the message client 104 can set a 60-second limit for recording a single sound clip. In this case, the progress bar 642 begins to slowly fill the sound recording option 640 in response to receiving the first input selecting the sound recording option 640, and can complete filling the sound recording option 640 after 60 seconds. In some cases, the progress bar 642 may be a circular line that starts at one location inside or outside the sound recording option 640 and ends at another location inside or outside the sound recording option 640 after advancing around the circular sound recording option 640. In some cases, the end location may be the same as the start location, in which case the circular line forms a complete loop around the outside or inside of the sound recording option 640 after a specified maximum time allowed to record sound (e.g., 60 seconds). The color or pattern of the circular line may be different from the sound recording option 640. Once the progress bar 642 reaches the end location or end location (e.g., when the progress bar 642 completely fills the sound recording option 640 or when a complete loop is formed around or inside the sound recording option 640), the audio content stops being captured and recorded, and the sound clip including the last 60 seconds of audio captured is automatically stored.

[0056] The message client 104 presents a waveform 630 that visually represents the sound or audio content captured by the microphone. In one example, the message client 104 begins animating the waveform 630 after receiving the first input selecting the sound recording option 640. This visually notifies the user that the audio content is currently being received and captured by the microphone of the client device 102. The color characteristics and attributes of the waveform 630 may be the same or different from the color characteristics and attributes of the progress bar 642. The color characteristics and attributes of the waveform 630 and the progress bar 642 may be the same or different from the color characteristics and attributes of the border 620.

[0057] The message client 104 may receive a second input for selecting the sound recording option 640 again while recording the audio content captured by the microphone. In one example, the first input may be provided by the user's finger pressing and holding the sound recording option 640, and the second input may be the finger releasing from the sound recording option 640. In response to receiving the second input, the message client 104 terminates recording the audio content captured by the microphone. The second input may be received before the progress bar 642 reaches the end position (e.g., before the progress bar 642 completely fills up the sound recording option 640).

[0058] After the messaging client 104 finishes capturing the sound clip (e.g., automatically when the progress bar 642 reaches the end position or when a second input selecting the sound recording option 640 is received), the messaging client 104 presents a screen 700 ( Figure 7 ). These options include a sound name option 710, a sound privacy state selection option 720, an attribute information option 740, and a sound clip adjustment option 730. While the screen 700 with various options is presented, the sound clip is continuously looped in the background. When the user interacts with the sound clip adjustment option 730 to trim the start and end positions of the sound clip, the sound clip that is continuously looping in the background can be changed to a shorter duration.

[0059] The sound name option 710 may be a text box that allows the user to specify a name or title for the recorded sound. In some embodiments, the sound name option 710 allows the user to upload or select a thumbnail image to represent the recorded sound. The messaging client 104 determines whether the name entered by the user violates one or more restrictions (e.g., whether the name includes abusive or offensive language). In this case, the messaging client 104 prompts the user to specify an alternative name in the sound name option 710.

[0060] The sound privacy state selection option 720 can be a toggle switch that allows the user to switch on / off whether the sound is private or public. In response to setting option 720 to indicate that the recorded sound is public, the attribute information option 740 is presented. The attribute information option 740 can be a text box that allows the user to specify the name of the creator of the sound. In some examples, the attribute information option 740 allows the user to select an avatar representing the creator of the recorded sound. If the sound privacy state selection option 720 is set to a private state, the attribute information option 740 can remain hidden. By default, the sound privacy state selection option 720 is set to a private setting.

[0061] In some embodiments, the message client 104 determines whether the user has previously created a public sound. Specifically, the message client 104 determines whether the user has ever set option 720 to a public setting for any previous sound recorded by the user. If the user has not set option 720 to a public setting for any previous sound recorded by the user, and in response to determining that the user has set option 720 to a public setting for the first time, the message client 104 presents a dialog box. The dialog box informs the user that the public setting allows other users of the message client 104 to use the sound clip for the image or video content captured by their client device 102. Once the user cancels the dialog box, the attribute information option 740 is presented, and the privacy setting of the sound clip is set to public.

[0062] As described in more detail below, the private sound setting allows the user who created the sound to incorporate the sound into an image or video (e.g., by dragging a thumbnail (one or more graphics) representing the sound into the image or video). Fig. 9 A set of illustrative thumbnails representing sound clips are discussed. The incorporated sound replaces the soundtrack of the image or video. Once the user selects the option to share an image or video associated with a private sound, the image or video is sent to one or more other users. When the recipient user views the image or video, the associated sound clip is presented with the image or video. The thumbnail that is dragged into the image or video to associate the sound clip with the image or video is not presented to the recipient user. The recipient user is prevented from sharing the sound clip or the image or video including the sound clip with other users (e.g., a friend of a friend). In some examples, the recipient user can select the option to share the image or video including the associated private sound clip with another friend. In response to selecting the option to share the image or video with another friend, only the image or video content is sent to the other friend without sending the private sound clip. When other friends view the image or video, the sound is not presented or played back because the sound clip was initially set to a private state.

[0063] The public setting of the sound clip allows the recipient user to continue to share the sound clip with other users. As an example, the first user drags a thumbnail image representing the sound clip onto an image or video. The first user can place the thumbnail image anywhere on the image or video, or at one or more predetermined locations. Once the thumbnail image is added to the image or video, the sound clip associated with the thumbnail image replaces the audio of the video, or automatically plays for the duration of the sound clip while presenting a single image including the thumbnail image. The image or video including the thumbnail image is shared by the first user with the second user. The second user selects the option to view the image or video, and in response, the image or video with the thumbnail image at the location selected by the first user is presented to the second user, while the sound clip is played back. The second user can select the option to save the sound clip associated with the thumbnail image. The second user can then add the thumbnail image to another video or image captured by the second user's client device 102 so that the sound clip associated with the thumbnail image is played when the image or video is accessed or displayed. The second user can then share the image or video captured by the second user with the thumbnail added with a third user. The third user may be a friend of the second user, and may or may not be a friend of the first user.

[0064] The sound clip adjustment option 730 allows the user to trim the recorded sound clip. For example, the length of the sound clip can be 60 seconds. The user can move the vertical bars 731 and 732 of the sound clip adjustment option 730 to adjust the start time and end time of the sound clip to reduce the length of the sound clip. For example, the user can move the left bar 731 to the right by 10 seconds so that the first 10 seconds of the sound clip are deleted and the sound clip starts at 10 seconds of the original start time. Similarly, the user can move the right bar 732 to the left by 5 seconds so that the last 5 seconds of the sound clip are deleted and the sound clip ends 5 seconds in advance. Therefore, a total of 15 seconds are trimmed from the 60-second sound clip. The trimmed sound clip is stored and associated with options 710, 720 and 740.

[0065] The messaging client 104 receives a user selection of a save option (not shown) from screen 700. In response, the messaging client 104 saves the sound clip along with the various options selected and set by the user. In some embodiments, the messaging client 104 navigates the user to screen 800 ( Figure 8), in screen 800, the sound menu is presented as superimposed on the displayed real-time video feed or previously captured image. Sound menu 810 includes a new tab labeled "My Sounds" that lists one or more sounds created by the user or sounds saved by the user from other sounds that the user received from other users' images or video content. The tab labeled "My Sounds" can only be added to menu 530 (after the user has created or saved at least one sound clip. Figure 5 ) is presented in .

[0066] The list of sounds displayed in the sound menu 810 includes a visual element (e.g., an icon or thumbnail) representing each sound. The visual element includes a designated name or title for the sound, an avatar representing the creator of the sound, or one or more graphics representing the sound. In some cases, the visual elements include small waveforms that become animated when the user selects the play option to preview the sound clip associated with each visual element. The sound menu 810 includes a create sound option 820. Selecting the create sound option 820 navigates the user to the screen 600 to allow the user to create a new custom sound clip.

[0067] In some embodiments, the sound menu 810 visually distinguishes between private sounds and public sounds. For example, in response to the message client 104 determining that the sound clip associated with the first visual element 830 is a public sound, the first visual element 830 can be displayed in a first display format (e.g., a first visual attribute, such as in color and a globe icon). In response to the message client 104 determining that the sound clip associated with the second visual element 840 is a private sound, the second visual element 840 can be displayed in a second display format (e.g., a second visual attribute, such as in a grayed-out manner and a lock icon). In some embodiments, the message client 104 determines that a given sound clip violates copyright protection (e.g., by running a background music scan on the sound clip to determine whether the sound clip matches music from other artists). The background music scan is performed by uploading the sound clip to the server from the client device 102. The server runs the sound clip through a process that generates a fingerprint for the sound clip. The fingerprint is provided to another server, which determines whether the fingerprint matches a copyrighted track. If it matches, the other server returns an indication that the fingerprint of the sound clip violates copyright protection. In this case, the messaging client 104 presents a visual element 850 indicating that the sound clip has been deleted, and prevents selection of the visual element 850 to combine the sound clip with the image or video.

[0068] The messaging client 104 may receive input from the user clicking or selecting one of the given visual elements from the sound menu 810. In response, the messaging client 104 retrieves a thumbnail or one or more graphics representing the selected sound clip. The messaging client 104 determines whether the selected sound clip is public or private. In response to determining that the sound clip is a public sound clip, the messaging client 104 allows the user to selectively place the retrieved thumbnail or one or more graphics on the image or video 510 to associate the sound clip with the image or video 510. The user can then share the image or video 510 with other users of the messaging client 104, along with the associated sound clip and the thumbnail or one or more graphics.

[0069] For example, Fig. 9 As shown, various thumbnails or one or more graphics 900 are presented as stickers that a user can position on an image or video 510. The first graphic 910 may be a sticker including an album cover representing a sound clip and a title of the sound clip. The shape of the first graphic 910 may be rectangular and have a black or dark background. The second graphic 920 may be a sticker placed on a video 950, which includes an album cover representing a sound clip, an animated waveform, and a title of the sound clip. The shape of the second graphic 920 may be rectangular and have a light or white background. The animated waveform is animated continuously after being placed on the video 950 to indicate that the sound comes from the sound clip rather than the audio of the video 950. The third graphic 930 may be a sticker including an album cover representing a sound clip, an animated waveform, and a title of the sound clip. The third graphic 930 may be an elliptical or circular shape. The fourth graphic 940 may be a sticker including a name or title 944 of the sound clip; attribute information 946, such as an avatar of the creator of the sound clip or the name of the creator; an animated waveform 942; and the title of the sound clip. The shape of the fourth figure 940 may be an ellipse or a circle.

[0070] In response to determining that the sound clip is a private sound clip, the messaging client 104 associates the sound clip with the image or video 510 and does not present a thumbnail or one or more graphics on the image or video 510. This allows the user to share the image or video 510 with other users without allowing other users to re-share or save the private sound clip. When other users view or access the image or video they received, the other users also cannot see the thumbnail or one or more graphics associated with the sound clip being played back.

[0071] The messaging client 104 may receive input from the user by pressing and holding a given visual element from the sound menu 810. In response, the messaging client 104 presents an options menu associated with the sound clip of the given visual element. The options menu may include an edit option that navigates the user to the screen 700 to modify the properties associated with the sound clip. In some embodiments, when the screen 700 is navigated to by selecting the edit option, the screen 700 does not include the sound clip adjustment option 730 because the sound clip cannot be trimmed after being saved.

[0072] The options menu may also include a delete option for deleting the sound clip. The options menu may include a share option. The share option allows the user to specify one or more recipients of the sound clip associated with the selected given visual element. The share option allows the user to share only the sound clip associated with the given visual element without adding the sound clip to the shared image or video. The recipient of the sound clip can then combine the received sound with the image or video content captured by the recipient's client device 102 using a thumbnail or one or more graphics associated with the sound clip. In some embodiments, the share option is only presented to the sound clip whose privacy is set to public.

[0073] Data Architecture

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

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

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

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

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

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

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

[0081] In one example, a filter is an overlay displayed as an overlay on an image or video during presentation to a receiving user. Filters can be of various types, including filters selected by a user from a set of filters presented to a sending user by a 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 a sending user based on geolocation. For example, a geolocation filter specific to a nearby or special location can be presented by a messaging client 104 within a user interface based on geolocation information determined by a global positioning system (GPS) unit of a client device 102.

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

[0083] Other augmented data that can be stored in the image table 312 include augmented reality content items (eg, corresponding to application lenses or augmented reality experiences). Augmented reality content items can be real-time special effects and sounds that can be added to images or videos.

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

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

[0086] 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, any object, such as human faces and parts of the human body, animals, or non-living things (e.g., chairs, cars, or other objects) can be processed using computer animation models.

[0087] In some examples, when a specific modification is selected together with the content to be transformed, the element to be transformed is identified by the computing device, and then if the element to be transformed is present in the frame of the video, the element to be transformed is detected and tracked. The elements of the object are modified according to the modification request, thereby transforming the frame of the video stream. For different kinds 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 refers to a variation of the elements of the object, the feature points of each element of the object are calculated (for example, using an active shape model (ASM) or other known methods). Then, a grid based on the feature points is generated for each of at least one element of the object. The grid is used for the subsequent stage of tracking the elements of the object in the video stream. During the tracking process, the mentioned grid of 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 the group of first points and the group of second points and the grid. In such a method, the background of the modified object can also be changed or distorted by tracking and modifying the background.

[0088] In some examples, a transformation that changes some areas of an object using the elements of an object can be performed by calculating feature points of each element of the object and generating a grid based on the calculated feature points. Points are generated on the grid, and then various areas 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 feature points can be selected as control points for determining the entire state space of options for model animation.

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

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

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

[0092] The transformation system can capture an image or video stream on a client device (e.g., client device 102) and perform complex image manipulations locally on the client device 102 while maintaining an appropriate user experience, computational time, and power consumption. Complex image manipulations can include size and shape changes, emotion transfer (e.g., changing a face from a frown to a smile), state transfer (e.g., aging a subject, 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.

[0093] In some examples, a computer animation model for transforming image data can be used by a system in which a user can capture an image or video stream of the user (e.g., a selfie) using a client device 102 having a neural network 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 image data, or the computer animation model can be presented as associated with an interface described herein. The modification icon includes the following changes, which can be the basis for modifying the face of the user within the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates 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 can be presented in a graphical user interface displayed on the client device 102. The transformation system can implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, a user can capture an image or video stream and once a modification icon is selected, be presented with the results of the modification in real time or near real time. Furthermore, 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.

[0094] The graphical user interface presenting the modifications performed by the transformation system can supply additional interactive options for the user. Such options can be based on an interface for initiating content capture and selection of a specific computer animation model (e.g., initiated from a content creator user interface). In various examples, the modification can be persistent after the initial selection of the modification icon. The user can turn on or off the modification by tapping or otherwise selecting the face modified by the transformation system, and store it for later viewing or browsing to other areas of the imaging application. In the case of multiple faces modified by the transformation system, the user can globally turn on or off the modification 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 switched individually by tapping or selecting each face or a series of each face displayed in the graphical user interface.

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

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

[0097] 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 embodiments, contributions to location stories may require a second degree of authentication to verify that the end user belongs to a specific organization or other entity (e.g., is a student on a university campus).

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

[0099] The external resource authorization table stores a list of all third-party resources (e.g., external applications, small-scale versions of external applications, such as web-based external applications and web-based game applications) that have been authorized to access the user data of the message client 104. The external resource authorization table also stores a timer for each authorized external resource, which is reset or refreshed each time the corresponding external resource is used. In other words, the timer represents the frequency or recency of use of each external resource. Whenever a user of the message client 104 starts or accesses a function of an external resource, the timer of the external resource is reset or refreshed. In some cases, when the timer of a given external resource reaches a threshold (e.g., 90 days), the corresponding external resource is automatically deauthorized (e.g., the authorization of the external resource to access the user data is revoked until the user reauthorizes the external resource to access the user data of the message client 104). The external resource authorization table can also store the association between the user identifier provided by the message client 104 and the corresponding user account information generated using the independent version of the external application. The user identifier is used by the message client 104 to retrieve the user account information generated using one version of the external application to be incorporated into or merged into another version of the external application.

[0100] Data communication architecture

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

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

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

[0104] 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 . The image data for a sent or received message 400 may be stored in the image table 312 .

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

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

[0107] Message enhancement data 412: Enhancement data (e.g., 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.

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

[0109] 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, with each of these parameter values ​​being associated with a content item included in the content (e.g., a specific image in a message image payload 406, or a specific video in a message video payload 408).

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

[0111] Message tags 420: Each message 400 may be tagged with a plurality of tags, each of such plurality of tags indicating 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 values ​​may be manually generated based on user input, or may be automatically generated using, for example, image recognition.

[0112] • 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.

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

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

[0115] Fig.10 1 is a flow chart illustrating example operations of the message client 104 in performing the process 1000 according to an example implementation. The process 1000 may be implemented in computer-readable instructions for execution by one or more processors, such that the operations of the process 1000 may be performed in part or in whole by functional components of the client device 102; therefore, the process 1000 is described below by way of example with reference thereto. However, in other implementations, at least some of the operations of the process 1000 may be deployed on various other hardware configurations, such as on the application server 114. The operations in the process 1000 may be performed in parallel in any order, or may be skipped and omitted entirely.

[0116] At operation 1001, the client device 102 displays a sound capture screen through a message application, which enables the user to record sound. For example, the message client 104 presents the screen 600 to the user, which includes a sound recording option 640 that enables the user to record sound.

[0117] At operation 1002, the client device 102 generates a visual element associated with the sound. For example, after the sound is recorded, the messaging client 104 presents the sound menu 810 ( Figure 8 ), the sound menu 810 includes a visual element (such as a thumbnail or icon) representing the sound.

[0118] At operation 1003, client device 102 receives a selection of a visual element from a displayed list of visual elements representing different sounds. For example, messaging client 104 receives a user selection of visual element 830 from sound menu 810. In some cases, all stored or recorded sounds have the same visual elements, which are displayed to indicate that they are user-generated sounds. Visual elements may display different visual attributes based on whether the corresponding sound clip is private, public, or violates guidelines (e.g., copyright protection).

[0119] At operation 1004, the client device 102 conditionally adds one or more graphics representing the sound to one or more images at a user-selected location based on the privacy status of the sound. For example, the messaging client 104 determines whether the sound clip associated with the selected visual element is private or public. If the sound clip has a public privacy status, the messaging client 104 presents a graphic or thumbnail sticker representing the sound clip and allows the user to place the graphic or thumbnail in a user-selected portion of the image or video. If the sound clip has a private privacy status, the messaging client 104 associates the sound clip with the image or video and does not incorporate the graphic or thumbnail into the image or video. In this case, the sound clip replaces the sound of the video or is associated with the image so that when the image or video is displayed to a given user or a user with whom the image or video is shared, the sound clip is played.

[0120] At operation 1004 , the client device 102 plays the sound associated with the visual element along with displaying the one or more images.

[0121] Machine Architecture

[0122] Fig.11It is a diagrammatic representation of a machine 1100 in which instructions 1108 (e.g., software, programs, applications, applet, app, or other executable code) for causing the machine 1100 to perform any one or more of the methods discussed herein may be executed. For example, the instructions 1108 may cause the machine 1100 to perform any one or more of the methods described herein. The instructions 1108 convert a general-purpose, non-programmed machine 1100 into a specific machine 1100 that is programmed to perform the functions described and shown in the manner described. The machine 1100 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1100 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1100 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 network device, a network router, a network switch, a network bridge, or any machine capable of sequentially or otherwise executing instructions 1108 specifying actions to be taken by the machine 1100. In addition, although only a single machine 1100 is shown, the term "machine" should also be taken to include a collection of machines that individually or jointly execute instructions 1108 to perform any one or more of the methods discussed herein. For example, the machine 1100 may include any of the client device 102 or a number of server devices that form part of the message server system 108. In some examples, the machine 1100 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 wherein certain operations of a particular method or algorithm are performed on the client side.

[0123] The machine 1100 may include a processor 1102, a memory 1104, and an input / output (I / O) component 1138 that may be configured to communicate with each other via a bus 1140. In an example, the processor 1102 (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 1106 that executes instructions 1108 and a processor 1110. The term "processor" is intended to include a multi-core processor that may include two or more independent processors (sometimes referred to as "cores") that may execute instructions simultaneously. Although Fig.11 Multiple processors 1102 are shown, but the machine 1100 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.

[0124] The memory 1104 includes a main memory 1112, a static memory 1114, and a storage unit 1116, which are all accessible by the processor 1102 via the bus 1140. The main memory 1104, the static memory 1114, and the storage unit 1116 store instructions 1108 that implement any one or more of the methods or functions described herein. The instructions 1108 may also reside, completely or partially, within the main memory 1112, within the static memory 1114, within the machine-readable medium 1118 within the storage unit 1116, within at least one of the processors 1102 (e.g., within a cache memory of the processor), or within any suitable combination thereof during execution thereof by the machine 1100.

[0125] I / O components 1138 may include various components for receiving input, providing output, generating output, transmitting information, exchanging information, capturing measurements, etc. The specific I / O components 1138 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 may not include such a touch input device. It should be appreciated that I / O components 1138 may include Fig.1111 and 12. In various examples, the I / O components 1138 may include a user output component 1124 and a user input component 1126. The user output component 1124 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 1126 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 another pointing instrument), a tactile input component (e.g., a physical button, a touch screen or other tactile input component that provides positioning and / or force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.

[0126] In another example, the I / O component 1138 may include: a biometric component 1128, a motion component 1130, an environment component 1132, or a position component 1134, as well as a variety of other components. For example, the biometric component 1128 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body gestures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweat, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1130 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

[0127] Environmental components 1132 include, for example, one or more cameras (with still image / photo and video capabilities), an illumination sensor component (e.g., a photometer), a temperature sensor component (e.g., one or more thermometers that detect ambient temperature), a humidity sensor component, a pressure sensor component (e.g., a barometer), an acoustic sensor component (e.g., one or more microphones that detect background noise), a proximity sensor component (e.g., an infrared sensor that detects nearby objects), a gas sensor (e.g., a gas detection sensor that detects concentrations of hazardous gases for safety or measures pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

[0128] 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 of a user of client device 102 (e.g., a "selfie"), 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.

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

[0130] The location component 1134 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.

[0131] Various technologies may be used to implement communications. The I / O components 1138 also include a communication component 1136 that is operable to couple the machine 1100 to the network 1120 or device 1122 via a corresponding coupling or connection. For example, the communication component 1136 may include a network interface component or other suitable device that interfaces with the network 1120. In other examples, the communication component 1136 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, Components (e.g. Low power consumption), Device 1122 may be another machine or any of a variety of peripheral devices (eg, a peripheral device coupled via USB).

[0132] In addition, the communication component 1136 can detect the identifier, or include a component operable to detect the identifier. For example, the communication component 1136 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional bar codes such as Universal Product Code (UPC) bar codes, multi-dimensional bar codes such as Quick Response (QR) codes, Aztec codes, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar codes, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying tagged audio signals). In addition, various information can be obtained via the communication component 1136, such as positioning via Internet Protocol (IP) geolocation, location information ... Positioning by signal triangulation, positioning via detection of NFC beacon signals, etc., which may indicate a specific position.

[0133] Various memories (e.g., main memory 1112, static memory 1114, and memory of processor 1102) and storage unit 1116 may store one or more sets of instructions and data structures (e.g., software) implemented or used by any one or more of the methods or functions described herein. When executed by processor 1102, these instructions (e.g., instructions 1108) cause various operations to implement the disclosed examples.

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

[0135] Software Architecture

[0136] Fig.121200 is a block diagram illustrating a software architecture 1204 that may be installed on any one or more of the devices described herein. The software architecture 1204 is supported by hardware such as a machine 1202 including a processor 1220, a memory 1226, and an I / O component 1238. In this example, the software architecture 1204 may be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1204 includes layers such as an operating system 1212, a library 1210, a framework 1208, and an application 1206. In operation, the application 1206 invokes an API call 1250 through the software stack and receives a message 1252 in response to the API call 1250.

[0137] The operating system 1212 manages hardware resources and provides public services. The operating system 1212 includes, for example, a kernel 1214, services 1216, and drivers 1222. The kernel 1214 acts as an abstraction layer between the hardware layer and other software layers. For example, the kernel 1214 provides memory management, processor management (e.g., scheduling), component management, networking and security settings, and other functions. Services 1216 can provide other public services to other software layers. Drivers 1222 are responsible for controlling or interfacing with the underlying hardware. For example, drivers 1222 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.

[0138] The libraries 1210 provide a common low-level infrastructure used by the applications 1206. The libraries 1210 may include system libraries 1218 (e.g., C standard libraries) that provide functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the libraries 1210 may include API libraries 1224, such as media libraries (e.g., libraries 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)), graphics libraries (e.g., OpenGL framework for presentation in two dimensions (2D) and three dimensions (3D) in graphics content on a display), database libraries (e.g., SQLite providing various relational database functions), web libraries (e.g., WebKit providing web browsing functions), etc. The library 1210 may also include various other libraries 1228 to provide many other APIs to the application 1206 .

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

[0140] In an example, applications 1206 may include a home application 1236, a contacts application 1230, a browser application 1232, a book reader application 1234, a positioning application 1242, a media application 1244, a messaging application 1246, a game application 1248, and a variety of other applications such as external applications 1240. Applications 1206 are programs that execute functions defined in the program. Various programming languages ​​may be used to create one or more of the applications 1206 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, external applications 1240 (e.g., those created by an entity other than a 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, the external application 1240 can activate the API call 1250 provided by the operating system 1212 to facilitate the functions described herein.

[0141] Glossary

[0142] "Carrier signal" refers to any intangible medium that can store, encode or carry instructions for execution by the 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.

[0143] "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.

[0144] "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 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.

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

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

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

[0148] Considering embodiments where hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one time. For example, where the hardware components include a general-purpose processor that is configured by software to be a special-purpose processor, the general-purpose processor can be configured to be a different special-purpose processor (e.g., including different hardware components) at different times. Thus, the software configures a specific processor or processors accordingly, such as to constitute a specific hardware component at one time and to constitute a different hardware component at different times.

[0149] Hardware components can provide information to other hardware components and receive information from other hardware components. Therefore, the described hardware components can be considered to be communicatively coupled. In the case of multiple hardware components simultaneously, communication can be realized by (for example, by appropriate circuits and buses) signal transmission between or among two or more hardware components. In an embodiment in which 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 store the output of the operation in a memory device communicatively coupled thereto. 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, the collection of information).

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

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

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

[0153] “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 are used interchangeably in this disclosure. The terms “machine storage media,” “computer storage media,” and “device storage media” expressly exclude carrier waves, modulated data signals, and other such media, at least some of which are encompassed by the term “signal media.”

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

[0155] "Signal media" refers to any intangible medium that is capable of storing, encoding, or carrying instructions executed by a machine, and "signal media" 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" refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. The terms "transmission medium" and "signal medium" refer to the same thing and may be used interchangeably in this disclosure.

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

Claims

1. A method comprising: Displaying, by the messaging application, a sound capture screen, the sound capture screen enabling a user to record sound; After recording the sound using the sound capture screen, generating, by the messaging application, a visual element associated with the sound; receiving, by the messaging application, a selection of the visual element from a displayed list of visual elements representing different sounds; In response to receiving a selection of the visual element, conditionally adding one or more graphics representing the sound over a portion of the one or more images at a user-selected location based on a privacy status of the sound, the privacy status controlling whether a recipient of the one or more images and the sound is allowed to share the sound with one or more friends of the recipient; as well as A sound associated with the visual element is played by the messaging application in conjunction with displaying the one or more images, the visual element being displayed over the portion of the one or more images.

2. The method according to claim 1, further comprising: receiving a user selection of a sound icon superimposed on one or more images captured by a client device having the messaging application implemented thereon; as well as In response to receiving a user selection of the sound icon, a sound menu is presented, the menu including an option to create a sound.

3. The method according to any one of claims 1 to 2, wherein: In response to receiving a user selection of the sound icon, the sound capturing screen is displayed.

4. The method according to any one of claims 1 to 3, wherein: Displaying the sound capture screen includes: activating a video capture device of a client device on which the messaging application is implemented; blurring or darkening an image captured by the video capture device and displayed on the sound capture screen; Display borders around blurred or darkened images; and Sound recording options are displayed on the sound capture screen along with a waveform.

5. The method according to claim 4, further comprising: receiving a first input selecting the sound recording option; In response to the first input, begin recording audio content captured by a microphone of the client device; receiving a second input reselecting the sound recording option; In response to the second input, terminating recording of audio content captured by a microphone of the client device; as well as Audio content recorded between the first input and the second input is stored as the sound.

6. The method of claim 5, further comprising: while recording the audio content, animating the waveform based on the audio content; as well as While the audio content is being recorded, a progress bar associated with the sound recording option is filled.

7. The method according to claim 6, wherein: The progress bar indicates the maximum duration for recording the sound.

8. The method according to claim 6, wherein: The audio content is recorded without recording images captured by the video capture device.

9. The method according to any one of claims 1 to 8, further comprising: After recording the sound using the sound capture screen, a plurality of options are displayed, the options including a first option for associating a name with the sound and a second option for trimming beginning and ending portions of the sound.

10. The method according to claim 9, further comprising: The sound is played back in a loop while the plurality of options are displayed.

11. The method according to any one of claims 9 to 10, wherein: The options include a third option for making the sound publicly available, the method further comprising: receiving input selecting the third option to make the sound publicly available; determining that the third option has been selected by the user a first time; and In response to determining that the third option has been selected by the user for a first time, presenting a dialog box indicating that the sound will be available to other users of the messaging application for incorporation into images captured by the other users.

12. The method according to any one of claims 9 to 11, wherein: The options include a third option for making the sound publicly available, the method further comprising: receiving input selecting the third option to make the sound publicly available; and A properties option is presented that allows the user to specify the name of the creator of the sound in addition to the name of the sound.

13. The method according to any one of claims 1 to 12, further comprising: determining a privacy status of the sound; In response to determining that the privacy status of the sound indicates that the sound is a private sound, assigning a first visual attribute to a visual element in the list; as well as In response to determining that the privacy status of the sound indicates that the sound is a public sound, assigning a second visual attribute to the visual elements in the list.

14. The method according to claim 13, further comprising: determining that the privacy status of the sound indicates that the sound is a private sound; transmitting the one or more images and sounds associated with the visual elements to one or more other users; In response to determining that the privacy status of the sound indicates that the sound is a private sound, playing the sound associated with the visual element along with the one or more images on a client device associated with the one or more other users without presenting one or more graphics representing the sound; as well as The one or more other users are prevented from sharing the sound with respective friends of the one or more other users.

15. The method according to any one of claims 13-14, further comprising: determining that the privacy status of the sound indicates that the sound is a public sound; transmitting the one or more images and sounds associated with the visual elements to one or more other users; In response to determining that the privacy status of the sound indicates that the sound is a public sound, playing the sound associated with the visual element along with the one or more images including one or more graphics representing the sound on a client device associated with the one or more other users; as well as In response to receiving input from the one or more other users selecting one or more graphics representing the sound included in the one or more images, the one or more other users are enabled to share the sound with respective friends of the one or more other users.

16. The method according to any one of claims 1 to 15, wherein: The list of visual elements visually distinguishes private sounds from public sounds.

17. The method according to any one of claims 1 to 16, wherein: The one or more graphics representing the sound include the name of the sound, a visual representation of the creator of the sound, and an animated waveform.

18. The method according to claim 17, wherein: The name of the sound, a visual representation of the creator of the sound, and the animated waveform are presented in an oval sticker, a rectangular sticker, or a circular sticker.

19. A system comprising: A processor configured to perform operations comprising: Displaying, by the messaging application, a sound capture screen, the sound capture screen enabling a user to record sound; After recording the sound using the sound capture screen, generating, by the messaging application, a visual element associated with the sound; receiving, by the messaging application, a selection of the visual element from a displayed list of visual elements representing different sounds; In response to receiving a selection of the visual element, conditionally adding one or more graphics representing the sound over a portion of the one or more images at a user-selected location based on a privacy status of the sound, the privacy status controlling whether a recipient of the one or more images and the sound is allowed to share the sound with one or more friends of the recipient; and A sound associated with the visual element is played by the messaging application in conjunction with displaying the one or more images, the visual element being displayed over the portion of the one or more images.

20. A non-transitory machine-readable storage medium comprising instructions that, when executed by one or more processors of a machine, cause the machine to perform operations comprising: Displaying, by the messaging application, a sound capture screen, the sound capture screen enabling a user to record sound; After recording the sound using the sound capture screen, generating, by the messaging application, a visual element associated with the sound; receiving, by the messaging application, a selection of the visual element from a displayed list of visual elements representing different sounds; In response to receiving a selection of the visual element, conditionally adding one or more graphics representing the sound over a portion of the one or more images at a user-selected location based on a privacy status of the sound, the privacy status controlling whether a recipient of the one or more images and the sound is allowed to share the sound with one or more friends of the recipient; as well as A sound associated with the visual element is played by the messaging application in conjunction with displaying the one or more images, the visual element being displayed over the portion of the one or more images.

Images