Round-based collaborative playlist

Abstract

Systems and methods herein describe generating a shared list of media elements. The system detects selection of application icons within the chat interface and generates an application interface. The application interface includes a media library. The system initiates a first user time limit and detects a selection of a media element from a media library. The system adds media elements to a shared list of media elements. When the first user time limit expires, the system initiates a second user time limit and detects a selection of a second media element from the media library. The system adds the second media element to a shared list of media elements. Upon expiration of the second user time limit, the system stores a shared list of media elements.

Description

[0001] This application is a divisional application of invention patent application No. 202180066281.9, with the application date of September 30, 2021, international application number PCT / US2021 / 071663, and entered the Chinese national phase on March 28, 2023, with the invention name being “Round-based Collaborative Playlist”.

[0002] Priority claim

[0003] This application claims the benefit of priority to U.S. Provisional Application No. 63 / 198,144, filed on September 30, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0004] Embodiments of the present disclosure generally relate to shareable media items. More specifically, but not by way of limitation, the present disclosure is directed to systems and methods for generating turn-based collaborative playlists. Background Art

[0005] Creating shared playlists allows people to share music and videos among a group of friends. Summary of the invention

[0006] According to one aspect of the concept described herein, a method includes: selecting, by a processor, a first user from a group of users as a first referee of a first shared list of media elements; receiving a prompt for the first shared list of media elements from a first device of the first user; providing the prompt to a second device of a second user of the group of users and a third device of a third user of the group of users; receiving a first media element submission from the second device; receiving a second media element submission from the third device; receiving a selection of the first media element submission from the first device; and including the first media element submission in the first shared list of media elements based on the selection of the first media element submission.

[0007] According to another aspect of the concept described herein, a system comprises: one or more processors; and a memory storing instructions, which, when executed by the one or more processors, cause the one or more processors to perform operations, the operations comprising: selecting a first user from a group of users as a first referee for a first shared list of media elements; receiving a prompt for the first shared list of media elements from a first device of the first user; providing the prompt to a second device of a second user of the group of users and a third device of a third user of the group of users; receiving a first media element submission from the second device; receiving a second media element submission from the third device; receiving a selection of the first media element submission from the first device; and including the first media element submission in the first shared list of media elements based on the selection of the first media element submission.

[0008] According to another aspect of the concept described herein, a non-transitory computer-readable storage medium includes instructions, which, when processed by a computer, cause the computer to perform operations, the operations including: selecting a first user from a group of users as a first referee for a first shared list of media elements; receiving a prompt for the first shared list of media elements from a first device of the first user; providing the prompt to a second device of a second user of the group of users and a third device of a third user of the group of users; receiving a first media element submission from the second device; receiving a second media element submission from the third device; receiving a selection of the first media element submission from the first device; and including the first media element submission in the first shared list of media elements based on the selection of the first media element submission. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

[0014] Figure 5 is a flow chart of an access restriction process according to some examples.

[0015] Figure 6 A method for generating a turn-based collaborative playlist according to one embodiment is shown.

[0016] Figure 7 A user interface of a collaborative media listing system is shown according to one embodiment.

[0017] Figure 8 A user interface of a collaborative media listing system is shown according to one embodiment.

[0018] Fig. 9 A user interface of a collaborative media listing system is shown according to one embodiment.

[0019] Fig.10 A user interface of a collaborative media listing system is shown according to one embodiment.

[0020] Fig.11 A user interface of a media streaming service application according to one embodiment is shown.

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

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

[0023] Creating a shared playlist among friends can be a challenge if everyone's contribution is not equal. Incentivizing friends to add media items (e.g., video and audio files) to a shared playlist can result in a higher quality shared playlist.

[0024] Embodiments herein describe a collaborative media list system. A user can launch an application with a friend and log in using a music streaming service account. A user can use the application to create a shared playlist. The shared playlist can be synchronized with each user's music streaming service account. To generate a playlist, users are placed in a turn order and are asked to add songs (or any other suitable media content items) to the shared playlist when it is their turn. Deep links allow users to listen to individual songs and entire playlists in their respective music streaming service accounts. Deep links introduce users to specific pages in an application by using a uniform resource identifier (URI).

[0025] The collaborative media list system may allow users to add songs asynchronously or synchronously. In some examples, the collaborative media list system allows users to react to other users' media selections. For example, users may send messages to each other within the application interface (e.g., text messages, avatar icons, etc.). Thus, the collaborative media list system allows users to create an experience that provides entertainment while also addressing the frustrations of successfully creating a high-quality shared playlist.

[0026] In some examples, the collaborative media list system can provide various modes of operation for users. In one example, a rally mode allows each user to be allocated a certain amount of time to add songs to a shared playlist. Each user takes a turn adding songs to the playlist, and once each user skips their turn in succession, the game ends.

[0027] In one example, the competitive mode allows one user in the group to act as a referee. The remaining users in the group submit songs to the referee. The referee selects a winner, and the winner can receive a score. The collaborative media list system tracks the number of points accumulated by each user. In some examples, the referee can give a prompt to the remaining users. For example, the referee can ask the remaining users to submit the best rap songs of the 1990s. The user who submits the best song receives a score. In some examples, the referee's prompt can be a text prompt. In another example, the referee's prompt can be a graphic or image. The collaborative media list system can verify the minimum number of people required to participate in order to enable the competitive mode. In some examples, the minimum number is three people. The first user to win the predefined number of points wins the game, and the game ends. In some examples, after one user wins the game, a second user can be selected as a referee and the game starts over.

[0028] Networked computing environment

[0029] 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 hosting a number of applications including a messaging client 104 and other applications 106. Each messaging client 104 is communicatively coupled to other instances of the messaging client 104 (e.g., hosted on respective other client devices 102), a messaging server system 108, and a third-party server 116 via a network 112 (e.g., the Internet). The messaging client 104 may also communicate with the local host application 106 using an application program interface (API).

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

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

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

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

[0034] The application program interface (API) server 116 receives and sends message data (e.g., commands and message payloads) between the client device 102 and the application server 114. Specifically, the application program interface (API) server 116 provides a set of interfaces (e.g., routines and protocols) that the messaging client 104 can call or query to activate the functions of the application server 114. An 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 a messaging client 104 to a messaging server 118 and for possible access by another messaging client 104; setting up a collection of media data (e.g., a story); retrieving a friend list of a user of a client device 102; retrieving such a collection; retrieving messages and content; adding and removing entities (e.g., friends) from an entity graph (e.g., a social graph); locating friends in a social graph; and opening application events (e.g., related to a messaging client 104).

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

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

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

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

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

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

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

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

[0043] System Architecture

[0044] 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, an external resource system 214, and a collaborative media list system 216.

[0045] The transient timer system 202 is responsible for enforcing temporary or time-limited access to content by the messaging client 104 and the messaging 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 messaging client 104 based on duration and display parameters associated with a message or collection of messages (e.g., a story). Additional details regarding the operation of the transient timer system 202 are provided below.

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

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

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

[0049] 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 situations where a particular media overlay should be provided to other users. The enhancement system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.

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

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

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

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

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

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

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

[0057] The messaging client 104 presents a graphical user interface (e.g., a login page or title screen) for an external resource. During, before, or after presenting the login page or title screen, the messaging client 104 determines whether the external resource launched has been previously authorized to access the user data of the messaging client 104. In response to determining that the external resource launched has previously been authorized to access the user data of the messaging client 104, the messaging client 104 presents another graphical user interface of the external resource including the functions and features of the external resource. In response to determining that the external resource launched has not previously been authorized to access the user data of the messaging client 104, after a threshold time period (e.g., 3 seconds) of displaying the login page or title screen of the external resource, the messaging client 104 slides up a menu (e.g., animating the menu to emerge 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 accept option, the messaging client 104 adds the external resource to the list of authorized external resources and allows the external resource to access the user data from the messaging client 104. In some examples, the external resource is authorized by the messaging client 104 to access the user data according to the OAuth 2 framework.

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

[0059] The collaborative media list system 216 provides an application interface for generating collaborative media lists. The collaborative media list system 216 allows users to add media items (eg, songs) to a shared media list.

[0060] Data Architecture

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

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

[0063] 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 messaging server system 108 stores data may be an identified entity. Each entity is provided with a unique identifier as well as an entity type identifier (not shown).

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

[0065] The profile data 316 stores multiple types of profile data about a particular entity. Based on the privacy settings specified by the particular entity, the 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, the profile data 316 includes, for example, a user name, phone number, address, settings (e.g., notification and privacy settings), and an avatar representation (or a collection of such avatar representations) selected by the user. The particular user can then selectively include one or more of these avatar representations 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 the state or activity that the user may choose to communicate at a particular time.

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

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

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

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

[0070] Other augmented data that may 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 may be real-time special effects and sounds that may be added to an image or video.

[0071] As described above, augmented data includes augmented reality content items, overlays, image transformations, AR images, and similar terms 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 the device sensor (e.g., one or more cameras) of the client device 102 and then display the image on the screen of the client device 102 with the modification. This also includes modifications to stored content, such as modifications to video clips in a gallery that can be modified. For example, in a client device 102 that can access multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to see how different augmented reality content items will modify the stored clips. For example, by selecting different augmented reality content items for the content, multiple augmented reality content items that apply different pseudo-random 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 function may simultaneously display how different augmented reality content items will look in different windows of the display. For example, this may enable viewing multiple windows with different pseudo-random animations on the display at the same time.

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

[0073] Real-time video processing can be performed using any type of video data (e.g., video streams, video files, etc.) stored in the memory of any type of computerized system. For example, a user can load a video file and save it in the memory of the device, or a video stream can be generated using the device's sensors. In addition, any object, such as a human face and parts of a human body, an animal, or a non-living thing (such as a chair, a car, or other objects) can be processed using computer animation models.

[0074] 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, it 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 the transformation of the frame that mainly refers to the form of the elements of the object to be changed, the feature points of each element of the object are calculated (for example, using the 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 grid of each element mentioned is aligned with the position of each element. Then, additional points are generated on the grid. A first set of first points is generated for each element based on the modification request, and a set of second points is generated for each element based on the set of first points and the modification request. Then, the frame of the video stream can be transformed by modifying the elements of the object based on the set of first points and the set of second points and the grid. In this method, the background of the modified object can also be changed or deformed by tracking and modifying the background.

[0075] In some examples, a transformation that changes some areas of an object using elements of an object can be performed by calculating feature points of each element of the object and generating a grid based on the calculated feature points. Points are generated on the grid, and then various areas are generated based on these points. Then, the elements of the object are tracked by aligning the area of ​​each element with the position of each of at least one element, and the properties of the area can be modified based on the request for modification, thereby converting the frame of the video stream. Depending on the specific modification request, the properties of the mentioned area can be transformed in different ways. Such modifications may involve: changing the color of the area; removing at least some parts of the area from the frame of the video stream; including one or more new objects in the area based on the modification request; and modifying or deforming 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.

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

[0077] 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 recognition process may be used for any such object. In some examples, a set of landmarks forms a shape. The shape may be represented as a vector using the coordinates of the points in the shape. One shape is aligned 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.

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

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

[0080] In some examples, a computer animation model for transforming image data can be used by a system in which a user can capture an image or video stream of the user (e.g., a selfie) using a client device 102 having a neural network that operates as part of a messaging client 104 operating on the client device 102. A transformation system operating within the messaging client 104 determines the presence of a face in 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 user's face in the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates a process of transforming the user's image to reflect the selected modification icon (e.g., generating a smiley face on the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream can be presented in a graphical user interface displayed on the client device 102. The transformation system can implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, once a modification icon is selected, the user can capture an image or video stream and be presented with the modification results in real time or near real time. In addition, when the video stream is being captured, the modification can be persistent and the selected modification icon remains toggled. Machine-taught neural networks can be used to implement such modifications.

[0081] The graphical user interface presenting the modifications performed by the transformation system can provide 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 by tapping or selecting an individual face or a series of faces displayed in the graphical user interface, or such modifications can be switched individually.

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

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

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

[0085] As mentioned above, the video table 304 stores video data, which in one example is associated with a message whose record is stored in the message table 302. Similarly, the image table 312 stores image data, which is associated with a message whose message data is stored in the entity table 306. The entity table 306 can 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.

[0086] Data communication architecture

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

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

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

[0090] 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 of the message 400 sent or received may be stored in the image table 312 .

[0091] 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 of the message 400 sent or received may be stored in the video table 304 .

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

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

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

[0095] 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 within a message image payload 406 or a specific video in a message video payload 408).

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

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

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

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

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

[0101] Time-based access restriction architecture

[0102] Figure 5 is a schematic diagram illustrating an access restriction process 500, according to which access to content (e.g., a multimedia payload of an ephemeral message 502 and associated data) or a collection of content (e.g., an ephemeral message group 504) can be time-restricted (e.g., made ephemeral).

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

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

[0105] Figure 5 502 is included in a transient message group 504 (e.g., a collection of messages in a personal story or an event story). The transient message group 504 has an associated group duration parameter 508, the value of which determines the duration for which the transient message group 504 is presented and accessible to users of the messaging system 100. For example, the group duration parameter 508 may be the duration of a concert, wherein the transient message group 504 is a collection of content related to the concert. Alternatively, a user (an owning user or a curator user) may specify a value for the group duration parameter 508 when performing setup and creation of the transient message group 504.

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

[0107] Thus, the group timer 514 is operable to control the total life span of the associated ephemeral message group 504 and the individual ephemeral messages 502 included in the ephemeral message group 504. In one example, each ephemeral message 502 within the ephemeral message group 504 remains viewable and accessible for a period of time specified by the group duration parameter 508. In another example, within the context of the ephemeral message group 504, a particular ephemeral message 502 may expire based on the group participation parameter 512. Note that even within the context of the ephemeral message group 504, the message duration parameter 506 may still determine the duration for which a particular ephemeral message 502 is displayed to a receiving user. Thus, the message duration parameter 506 determines the duration for which a particular ephemeral message 502 is displayed to a receiving user, regardless of whether the receiving user is viewing the ephemeral message 502 within or outside the context of the ephemeral message group 504.

[0108] The transient timer system 202 may also be operable to remove a particular transient message 502 from the transient message group 504 based on determining that the particular transient message 502 has exceeded the associated group participation parameter 512. For example, when the sending user has established a group participation parameter 512 of 24 hours from posting, the transient timer system 202 will remove the associated transient message 502 from the transient message group 504 after the specified 24 hours. The transient timer system 202 is also operable to remove a transient message group 504 when the group participation parameter 512 for each transient message 502 within the transient message group 504 has expired, or when the transient message group 504 itself has expired according to the group duration parameter 508.

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

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

[0111] Figure 6 600 for generating a shared media list according to some example implementations. Although the described flowchart may show the operations as sequential processing, many of the operations may be performed in parallel or simultaneously. In addition, the order of the operations may be rearranged. A process terminates when its operations are completed. A process may correspond to a method, procedure, algorithm, etc. The operations of a method may be performed in whole or in part, may be performed in combination with some or all of the operations in other methods, and may be performed by any number of different systems (such as the systems described herein) or any portion thereof (such as a processor included in any system).

[0112] In operation 602, the collaborative media list system 216 detects, via a processor, a first selection of an application icon in a chat interface of a first device by a first user. In some examples, the collaborative media list system 216 may generate and cause a message to be displayed within a chat interface of the first device or the second device, the message including an indication that the application icon has been selected. In some examples, the first user also selects an operating mode of the collaborative media list system 216 (e.g., a call-up mode or a competition mode).

[0113] In operation 604, the collaborative media list system 216 generates an application interface associated with the application icon, the application interface including a plurality of selectable media elements associated with the media library. The media library may include audio files and video files. In some examples, the first user may provide login credentials to access the media library. For example, the first user may provide login credentials associated with a media streaming service. The collaborative media list system 216 may verify the login credentials before proceeding to perform operation 606.

[0114] In operation 606, the collaborative media list system 216 causes the application interface to be displayed on a first device of a first user and a second device of a second user. In operation 608, the collaborative media list system 216 initiates a first user time limit that is a time period associated with the first user. In operation 610, the collaborative media list system 216 detects a second selection by the first user of a first selectable media element from a plurality of selectable media elements displayed on the first device. In operation 612, the collaborative media list system 216 generates a shared list of media elements, the shared list of media elements including the first selectable media element. In operation 614, the collaborative media list system 216 detects an expiration of the first user time limit. In operation 616, the collaborative media list system 216 initiates a second user time limit in response to detecting that the first user time limit has expired, the second user time limit being a time period associated with the second user. In some examples, the collaborative media list system 216 causes a message prompt to be displayed on the first device and the second device. For example, the message prompt may indicate the expiration of the first user time limit.

[0115] In operation 618, the collaborative media list system 216 detects a third selection of a second selectable media element from the plurality of selectable media elements displayed on the second device by the second user. In operation 620, the collaborative media list system 216 adds the second media element to a shared list of media elements. In operation 622, the collaborative media list system 216 detects that the second user time limit has expired. In operation 624, the collaborative media list system 216 stores the shared list of media elements in response to detecting that the second user time limit has expired. The one or more processors of the collaborative media list system 216 may cause the shared list of media elements to be stored in an application associated with the application interface.

[0116] In some examples, prior to operation 610, collaborative media listing system 216 detects a first input of a first text query by a first user from a first device and causes display of a first set of selectable media elements associated with the first text query, wherein the first selectable media element is associated with the first text query. Collaborative media listing system 216 may detect a second selection of a first selectable media element in the first set of selectable media elements associated with the first text query.

[0117] In some examples, prior to operation 618, collaborative media listing system 216 detects a second input of a second text query by a second user from a second device and causes display of a second set of selectable media elements associated with the second text query, wherein the second selectable media element is associated with the second text query. Collaborative media listing system 216 can detect a third selection by the second user of a second media element in the second set of selectable media elements associated with the second text query.

[0118] In some examples, operations 608 to 624 are repeated until both users skip their turns consecutively. For example, if neither user contributes a song during their assigned time slots, the collaborative media listing system 216 can detect that the game has ended and close the application interface. For example, after operation 624, the collaborative media listing system 216 can initiate a subsequent first user time limit. The collaborative media listing system 216 can detect a subsequent expiration of a subsequent first user time limit. The collaborative media listing system 216 can initiate a subsequent second user time limit. The collaborative media listing system 216 can detect a subsequent expiration of a subsequent second user time limit. In response to detecting a subsequent expiration of a subsequent first user time limit and a subsequent expiration of a subsequent second user time limit, the collaborative media listing system 216 can close the application interface associated with the chat interface.

[0119] In some examples, the shared media list is generated by the first user after operation 602. The first user can select preferences and other predefined settings for the shared media list, such as a title for the shared media list. In some examples, the user can preview the track within the application interface before adding the track to the shared media list.

[0120] In some examples, when in the call mode, the user's turn is determined in alphabetical order. In another example, the user's turn is determined in the order in which the collaborative media list system 216 is launched.

[0121] In some examples, the shared media list can be modified within a predetermined time period. For example, any user can add to the shared media list within 24 hours of creating the shared media list. However, after 24 hours, the shared media list may expire and will not be accessible through the application interface.

[0122] Figures 7 to 10A user interface of the collaborative media list system 216 is shown according to some example embodiments. Item 702 shows a portion of an application interface. For example, upon receiving a selection of an application icon in operation 602, the collaborative media list system 216 causes presentation of the application interface as depicted in item 702. Item 704 is an example selectable user interface element for logging into a media streaming service account. The collaborative media list system 216 can be communicatively coupled to a media streaming service account. The user may be prompted to log into the media streaming service account to access the media library. Item 706 is an example selectable user interface element for initiating a messaging session via the messaging client 104.

[0123] Figure 8 An example graphical user interface of a collaborative media list system 216 that can be on a first device. Item 802 shows a portion of an application interface that prompts a user to take his or her turn. For example, the application indicates a name or user name associated with the user. The application interface also includes an item 804 indicating the amount of time remaining for the game. In some examples, item 804 may indicate the amount of time remaining for the user to complete his or her turn. Item 806 shows a portion of the application interface from which a user can add optional media elements to a shared media list. For example, the collaborative media list system 216 may cause the presentation of a media library using an API associated with a media streaming service. The user may be able to access the media library by performing one or more gestures (e.g., an upward swipe action). Item 808 shows a portion of an application interface with a shared media list. In one example, the shared media list is a playlist of songs. The shared media list may include a title. The collaborative media list system 216 may cause one or more users to be presented as contributors to the shared media list. In some examples, the collaborative media list system 216 causes user avatars 810 of one or more contributors to the shared media list to be presented.

[0124] Fig. 9 904. An example graphical user interface of collaborative media list system 216 may be on a second device. Collaborative media list system 216 may have multiple active sessions (e.g., on a first device, and on a second device). Each active session may be associated with a user account of a social media application. Item 902 illustrates a user interface element for adding a media element (e.g., a song) to a shared media playlist. Item 902 may further include an avatar representing a user who is adding a media element. In some examples, collaborative media list system 216 receives a selection of a button indicating that the user wants to add a song to a playlist. After selecting the button presented in item 902, collaborative media list system 216 presents search interface 904, from which collaborative media list system 216 receives a text search query. The text search query is used to identify media elements from a media library.

[0125] Item 1002 shows an updated shared media playlist. After the user adds a song to the shared media playlist, the collaborative media list system 216 can cause the updated shared media playlist to be displayed. Item 1004 shows a message prompt indicating that the song has been successfully added to the playlist. In some examples, the collaborative media list system 216 causes the message prompt to be presented across all computing devices that are being used to contribute to the collaborative media list system 216. In some examples, the collaborative media list system 216 causes the message prompt to be presented only on the computing device to which the song was added.

[0126] Fig.11 1104. The graphical user interface of the media streaming service application also includes a title 1104 for the shared playlist. The graphical user interface of the media streaming service application also includes a list of songs 1106 added by the user.

[0127] Machine Architecture

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

[0129] The machine 1200 may include a processor 1204, a memory 1206, and an input / output (I / O) component 1202 that may be configured to communicate with each other via a bus 1240. In an example, the processor 1204 (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 1208 that executes instructions 1210 and a processor 1212. 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.12 Multiple processors 1204 are shown, but the machine 1200 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.

[0130] The memory 1206 includes a main memory 1214, a static memory 1216, and a storage unit 1218 that can be accessed by the processor 1204 via the bus 1240. The main memory 1206, the static memory 1216, and the storage unit 1218 store instructions 1210 that implement any one or more of the methods or functions described herein. The instructions 1210 may also reside, completely or partially, within the main memory 1214, within the static memory 1216, within the machine-readable medium 1220 within the storage unit 1218, within at least one of the processors 1204 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 1200.

[0131] I / O components 1202 may include a variety of components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurements, etc. The specific I / O components 1202 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, while a headless server machine will be less likely to include such a touch input device. It will be appreciated that I / O components 1202 may include Fig.121202. In various examples, the I / O components 1202 may include a user output component 1226 and a user input component 1228. The user output component 1226 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 1228 may include an alphanumeric input component (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input component), a point-based input component (e.g., a mouse, a touch pad, a trackball, a joystick, a motion sensor, or other pointing instrument), a tactile input component (e.g., a physical button, a touch screen that provides the location and force of a touch or touch gesture, or other tactile input component), an audio input component (e.g., a microphone), etc.

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

[0133] Environmental components 1234 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.

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

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

[0136] The positioning component 1236 includes a position sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or a barometer that detects air pressure that can obtain the altitude), an orientation sensor component (e.g., a magnetometer), and the like.

[0137] A variety of technologies may be used to implement communications. The I / O components 1202 also include a communication component 1238 that is operable to couple the machine 1200 to the network 1222 or device 1224 via a corresponding coupling or connection. For example, the communication component 1238 may include a network interface component or another suitable device to interface with the network 1222. In other examples, the communication component 1238 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 1224 may be any peripheral device (eg, a peripheral device coupled via USB) from another machine or a variety of peripheral devices.

[0138] In addition, the communication component 1238 can detect an identifier or include a component operable to detect an identifier. For example, the communication component 1238 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, UltraCode, UCC RSS-2D bar codes, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying an audio signal of a tag). In addition, various information can be derived via the communication component 1238, such as a location via Internet Protocol (IP) geolocation, a location via Internet Protocol (IP), ... The location of signal triangulation, the location of an NFC beacon signal via detection that can indicate a specific location, etc.

[0139] Various memories (e.g., main memory 1214, static memory 1216, and memory of processor 1204) and storage unit 1218 may store one or more sets of instructions and data structures (e.g., software) implemented or used by any one or more of the methods or functions described herein. These instructions (e.g., instructions 1210) when executed by processor 1204 cause various operations to implement the disclosed examples.

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

[0141] Software Architecture

[0142] Fig.131300 is a block diagram illustrating a software architecture 1304 that can be installed on any one or more of the devices described herein. The software architecture 1304 is supported by hardware, such as a machine 1302, including a processor 1320, a memory 1326, and an I / O component 1338. In this example, the software architecture 1304 can be conceptualized as a stack of layers in which each layer provides specific functionality. The software architecture 1304 includes layers such as an operating system 1312, a library 1310, a framework 1308, and an application 1306. In operation, the application 1306 invokes an API call 1350 through the software stack and receives a message 1352 in response to the API call 1350.

[0143] The operating system 1312 manages hardware resources and provides public services. The operating system 1312 includes, for example, a kernel 1314, a service 1316, and a driver 1322. The kernel 1314 acts as an abstraction layer between the hardware layer and other software layers. For example, the kernel 1314 provides memory management, processor management (e.g., scheduling), component management, network and security settings, and other functions. The service 1316 can provide other public services to other software layers. The driver 1322 is responsible for controlling or interfacing with the underlying hardware. For example, the driver 1322 may include a display driver, a camera driver, or Low-power drivers, Flash drivers, Serial communication drivers (e.g., USB drivers), Drivers, audio drivers, power management drivers, etc.

[0144] The libraries 1310 provide a common low-level infrastructure used by the applications 1306. The libraries 1310 may include system libraries 1318 (e.g., C standard libraries) that provide functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the libraries 1310 may include API libraries 1324, 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 1310 may also include a variety of other libraries 1328 to provide many other APIs to the application 1306 .

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

[0146] In an example, applications 1306 may include a home application 1336, a contacts application 1330, a browser application 1332, a book reader application 1334, a positioning application 1342, a media application 1344, a messaging application 1346, a game application 1348, and a variety of other applications such as third-party applications 1340. Applications 1306 are programs that execute functions defined in the program. Various programming languages ​​may be used to create one or more of the applications 1306 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 or assembly language). In a specific example, third-party applications 1340 (e.g., applications created by an entity other than the vendor of a particular platform using ANDROID TM or IOS TM Software Development Kit (SDK) can be used to develop applications on platforms such as IOS TM ANDROID TM , Mobile software running on the mobile operating system of the phone or other mobile operating systems. In this example, third-party applications 1340 can activate API calls 1350 provided by the operating system 1312 to facilitate the functions described herein.

[0147] Glossary

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

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

[0150] "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, A network, other type of network, or a combination of two or more such networks. For example, the network or a portion of the network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a global system for mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rate for GSM evolution (EDGE) technology, including the third generation partnership project (3GPP) of 3G, fourth generation wireless (4G) network, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standard, other data transmission technologies defined by various standard setting organizations, other long distance protocols, or other data transmission technologies.

[0151] "Component" refers to a device, physical entity or logic with the following boundaries, which is defined by function or subroutine calls, branch points, APIs or other technologies that provide partitioning or modularization for specific processing or control functions. Components can be combined with other components via their interfaces to perform machine processing. Components can be packaged functional hardware units designed for use with other components, and can be part of a program that generally performs specific functions in related functions. Components can constitute software components (e.g., codes implemented on machine-readable media) or hardware components. "Hardware components" are tangible units that can perform certain operations and can be configured or arranged in a certain physical manner. In various examples, one or more computer systems (e.g., independent computer systems, client computer systems, or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured as hardware components for performing certain operations described herein by software (e.g., applications or application parts). Hardware components can also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component may include a dedicated circuit system or logic that is permanently configured to perform certain operations. The hardware component may be a dedicated processor such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The hardware component may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, the hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of a machine) that is uniquely customized to perform the configured function, and is no longer a general-purpose processor. It will be understood that it can be decided to implement the hardware component mechanically, in a dedicated and permanently configured circuit or in a temporarily configured (e.g., configured by software) circuit for cost and time considerations. Accordingly, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, that is, an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in some way or perform certain operations described herein. Considering an example where a hardware component is temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each hardware component in the hardware component at any one time. For example, in the case where a hardware component includes a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be configured as different special-purpose processors (e.g., including different hardware components) at different times. The software configures one or more specific processors accordingly to constitute a specific hardware component, for example, at one time, and to constitute different hardware components at different times. 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 being present at the same time, communication can be achieved by signal transmission between or among two or more hardware components (e.g., through appropriate circuits and buses). In examples where multiple hardware components are configured or instantiated at different times, communication between such hardware components can be achieved, for example, by storing information in a memory structure accessed by multiple hardware components and retrieving information in the memory structure. For example, a hardware component can perform an operation, and the output of the operation is stored in a memory device to which it is communicatively coupled. Then, other hardware components can access the memory device at a subsequent time to retrieve the stored output and process the stored output. The hardware component can also initiate communication with an input device or an output device, and can operate on resources (e.g., the collection of information). The various operations of the example methods described herein can be performed at least in part by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether temporarily configured or permanently configured, such a processor can constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refer to hardware components implemented using one or more processors. Similarly, the method described herein can be implemented at least in part by a processor, wherein specific one or more processors are examples of hardware. For example, at least some operations of the method can be performed by one or more processors or the parts implemented by the processor. In addition, the one or more processors can also be operated to support the execution of the related operations in the "cloud computing" environment or operate as "software as a service" (SaaS). For example, at least some operations in the operation can be performed by a computer group (as an example of a machine including a processor), wherein these operations can be accessed via a network (for example, the Internet) and via one or more appropriate interfaces (for example, API). The execution of some operations can be distributed between processors, not only resident in a single machine, but deployed across multiple machines. In some examples, a processor or the parts implemented by a processor can be located in a single geographic location (for example, in a home environment, an office environment or a server group). In other examples, a processor or the parts implemented by a processor can be distributed across several geographic locations.

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

[0153] "Ephemeral messages" are messages that are accessible for a limited duration in time. Ephemeral messages can be text, images, videos, etc. The access time for ephemeral messages can be set by the message sender. 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.

[0154] “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 / or 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), FPGAs, 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.”

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

[0156] "Signal medium" refers to any intangible medium that is capable of storing, encoding or carrying instructions executed by a machine, and includes digital or analog communication signals or other intangible media to facilitate the communication of software or data. The term "signal medium" should be deemed to include any form of modulated data signal, carrier wave, etc. The term "modulated data signal" means 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.

[0157] Additionally, the present technology may also be configured as follows.

[0158] (1) A method comprising:

[0159] Detecting, by the processor, a first selection by the first user of an application icon in the chat interface of the first device;

[0160] generating an application interface associated with the application icon, the application interface comprising a plurality of selectable media elements associated with a media library;

[0161] Displaying the application interface on the first device of the first user and the second device of the second user;

[0162] initiating a first user time limit as a time period associated with the first user;

[0163] detecting a second selection by the first user of a first selectable media element among the plurality of selectable media elements displayed on the first device;

[0164] generating a sharing list of media elements, wherein the sharing list of media elements includes the first selectable media element;

[0165] detecting expiration of the first user time limit;

[0166] in response to detecting that the first user time limit has expired, initiating a second user time limit that is a time period associated with the second user;

[0167] detecting a third selection by the second user of a second selectable media element among the plurality of selectable media elements displayed on the second device;

[0168] adding the second media element to a sharing list of the media elements;

[0169] detecting that the second user time limit has expired;

[0170] In response to detecting that the second user time limit has expired, storing the shared list of media elements.

[0171] (2) The method according to (1), wherein detecting the second selection further comprises:

[0172] detecting a first input of a first text query by the first user from the first device; and

[0173] A first set of selectable media elements associated with the first text query is caused to be displayed, wherein the first selectable media elements are associated with the first text query.

[0174] (3) The method according to (1), wherein detecting the third selection further comprises:

[0175] detecting a second input of a second text query by the second user from the second device;

[0176] A second set of selectable media content elements associated with the second text query is caused to be displayed, wherein the second selectable media elements are associated with the second text query.

[0177] (4) The method according to (1), wherein the media library includes audio files and video files.

[0178] (5) The method according to (1), wherein detecting the expiration of the first time limit further comprises:

[0179] Displaying a message prompt on the first device and the second device.

[0180] (6) The method according to (1), further comprising:

[0181] Initiate subsequent first user time limit;

[0182] detecting a subsequent expiration of the subsequent first user time limit;

[0183] Initiate a subsequent second user time limit;

[0184] detecting a subsequent expiration of the subsequent second user time limit;

[0185] In response to detecting a subsequent expiration of the subsequent first user time limit and a subsequent expiration of the subsequent second user time limit, closing the application interface.

[0186] (7) The method according to (1), wherein detecting the first selection of the application icon further comprises:

[0187] generating a message including an indication that the application icon has been selected; and

[0188] Enable the message to be displayed in the chat interface of the first device or the second device.

[0189] (8) A system comprising:

[0190] Processor; and

[0191] a memory storing instructions that, when executed by the processor, configure the system to perform operations comprising:

[0192] Detecting, by the processor, a first selection by the first user of an application icon in the chat interface of the first device;

[0193] generating an application interface associated with the application icon, the application interface comprising a plurality of selectable media elements associated with a media library;

[0194] Displaying the application interface on the first device of the first user and the second device of the second user;

[0195] initiating a first user time limit as a time period associated with the first user;

[0196] detecting a second selection by the first user of a first selectable media element among the plurality of selectable media elements displayed on the first device;

[0197] generating a sharing list of media elements, wherein the sharing list of media elements includes the first selectable media element;

[0198] detecting expiration of the first user time limit;

[0199] in response to detecting that the first user time limit has expired, initiating a second user time limit that is a time period associated with the second user;

[0200] detecting a third selection by the second user of a second selectable media element among the plurality of selectable media elements displayed on the second device;

[0201] adding the second media element to a sharing list of the media elements;

[0202] detecting that the second user time limit has expired;

[0203] In response to detecting that the second user time limit has expired, storing the shared list of media elements.

[0204] (9) The system of (8), wherein detecting the second selection further comprises:

[0205] detecting a first input of a first text query by the first user from the first device; and

[0206] A first set of selectable media elements associated with the first text query is caused to be displayed, wherein the first selectable media elements are associated with the first text query.

[0207] (10) The system of (8), wherein detecting the third selection further comprises:

[0208] detecting a second input of a second text query by the second user from the second device;

[0209] A second set of selectable media content elements associated with the second text query is caused to be displayed, wherein the second selectable media elements are associated with the second text query.

[0210] (11) The system of (8), wherein the media library includes audio files and video files.

[0211] (12) The system of (8), wherein detecting expiration of the first time limit further comprises:

[0212] Displaying a message prompt on the first device and the second device.

[0213] (13) The system according to (8), wherein the operations further include:

[0214] Initiate subsequent first user time limit;

[0215] detecting a subsequent expiration of the subsequent first user time limit;

[0216] Initiate a subsequent second user time limit;

[0217] detecting a subsequent expiration of the subsequent second user time limit;

[0218] In response to detecting a subsequent expiration of the subsequent first user time limit and a subsequent expiration of the subsequent second user time limit, closing the application interface.

[0219] (14) The system of (8), wherein detecting the first selection of the application icon further comprises:

[0220] generating a message including an indication that the application icon has been selected; and

[0221] Enable the message to be displayed in the chat interface of the first device or the second device.

[0222] (15) A non-transitory computer-readable storage medium comprising instructions that, when processed by a computer, configure the computer to perform operations comprising:

[0223] Detecting, by the processor, a first selection by the first user of an application icon in the chat interface of the first device;

[0224] generating an application interface associated with the application icon, the application interface comprising a plurality of selectable media elements associated with a media library;

[0225] Displaying the application interface on the first device of the first user and the second device of the second user;

[0226] initiating a first user time limit as a time period associated with the first user;

[0227] detecting a second selection by the first user of a first selectable media element among the plurality of selectable media elements displayed on the first device;

[0228] generating a sharing list of media elements, wherein the sharing list of media elements includes the first selectable media element;

[0229] detecting expiration of the first user time limit;

[0230] in response to detecting that the first user time limit has expired, initiating a second user time limit that is a time period associated with the second user;

[0231] detecting a third selection by the second user of a second selectable media element among the plurality of selectable media elements displayed on the second device;

[0232] adding the second media element to a sharing list of the media elements;

[0233] detecting that the second user time limit has expired;

[0234] In response to detecting that the second user time limit has expired, storing the shared list of media elements.

[0235] (16) The non-transitory computer-readable storage medium of (15), wherein detecting the second selection further comprises:

[0236] detecting a first input of a first text query by the first user from the first device; and

[0237] A first set of selectable media elements associated with the first text query is caused to be displayed, wherein the first selectable media elements are associated with the first text query.

[0238] (17) The non-transitory computer-readable storage medium of (15), wherein detecting the third selection further comprises:

[0239] detecting a second input of a second text query by the second user from the second device;

[0240] A second set of selectable media content elements associated with the second text query is caused to be displayed, wherein the second selectable media elements are associated with the second text query.

[0241] (18) The non-transitory computer-readable storage medium of (15), wherein the media library includes audio files and video files.

[0242] (19) The non-transitory computer-readable storage medium of (15), wherein detecting expiration of the first time limit further comprises:

[0243] Displaying a message prompt on the first device and the second device.

[0244] (20) The non-transitory computer-readable storage medium of (15), wherein detecting the first selection of the application icon further comprises:

[0245] generating a message including an indication that the application icon has been selected; and

[0246] Enable the message to be displayed in the chat interface of the first device or the second device.

Claims

1. A method comprising: selecting, by the processor, a first user from a group of users as a first referee for a first shared list of media elements; receiving a prompt for a first shared list of media elements from a first device of the first user; providing the prompt to a second device of a second user of the group of users and a third device of a third user of the group of users; receiving a first media element submission from the second device; receiving a second media element submission from the third device; receiving, from the first device, a selection of the first media element submission; as well as Based on selection of the first media element submission, the first media element submission is included in a first shared list of media elements.

2. The method according to claim 1, further comprising: increasing a first score associated with the second user based on the selection of the first media element submission; as well as Based on the first score reaching a predefined score, a first shared list of the media elements is stored.

3. The method according to claim 2, further comprising: Access to the first shared list of media elements is denied after a predefined period of time after storing the first shared list of media elements.

4. The method according to claim 2, further comprising: The second user is selected from the group of users as a second referee for a second shared list of media elements.

5. The method according to claim 4, further comprising: receiving, from the first device, a first title of a first shared list of media elements; as well as A second title of a second shared list of media elements is received from the second device.

6. The method according to claim 1, further comprising: verifying that the set of users satisfies a minimum number of users; as well as A gaming mode is enabled in which the first user from the group of users is the first referee for the first shared list of media elements.

7. The method according to claim 1, further comprising: receiving, from the third device, a response to the submission of the first media element; as well as The reaction to the first media element submission is provided to the second device.

8. The method according to claim 1, wherein: Selecting the first user from the group of users as the first referee is based on a selection of a game mode by the first user.

9. The method according to claim 1, wherein: The hint for the first shared list of media elements is an image.

10. A system comprising: one or more processors; as well as a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: selecting a first user from a group of users as a first referee for a first shared list of media elements; receiving a prompt for a first shared list of media elements from a first device of the first user; providing the prompt to a second device of a second user of the group of users and a third device of a third user of the group of users; receiving a first media element submission from the second device; receiving a second media element submission from the third device; receiving, from the first device, a selection of the first media element submission; and Based on selection of the first media element submission, the first media element submission is included in a first shared list of media elements.

11. The system of claim 10, wherein the operations further comprise: increasing a first score associated with the second user based on the selection of the first media element submission; as well as Based on the first score reaching a predefined score, a first shared list of the media elements is stored.

12. The system of claim 11, the operations further comprising: Access to the first shared list of media elements is denied after a predefined period of time after storing the first shared list of media elements.

13. The system of claim 11, the operations further comprising: The second user is selected from the group of users as a second referee for a second shared list of media elements.

14. The system of claim 13, wherein the operations further comprise: receiving, from the first device, a first title of a first shared list of media elements; as well as A second title of a second shared list of media elements is received from the second device.

15. The system of claim 10, the operations further comprising: verifying that the set of users satisfies a minimum number of users; as well as A gaming mode is enabled in which the first user from the group of users is the first referee for the first shared list of media elements.

16. The system of claim 10, the operations further comprising: receiving, from the third device, a response to the submission of the first media element; as well as The reaction to the first media element submission is provided to the second device.

17. A non-transitory computer-readable storage medium comprising instructions that, when processed by a computer, cause the computer to perform operations comprising: selecting a first user from a group of users as a first referee for a first shared list of media elements; receiving a prompt for a first shared list of media elements from a first device of the first user; providing the prompt to a second device of a second user of the group of users and a third device of a third user of the group of users; receiving a first media element submission from the second device; receiving a second media element submission from the third device; receiving, from the first device, a selection of the first media element submission; as well as Based on selection of the first media element submission, the first media element submission is included in a first shared list of media elements.

18. The non-transitory computer readable storage medium of claim 17, the operations further comprising: increasing a first score associated with the second user based on the selection of the first media element submission; as well as Based on the first score reaching a predefined score, a first shared list of the media elements is stored.

19. The non-transitory computer readable storage medium of claim 18, the operations further comprising: Access to the first shared list of media elements is denied after a predefined period of time after storing the first shared list of media elements.

20. The non-transitory computer readable storage medium of claim 18, the operations further comprising: The second user is selected from the group of users as a second referee for a second shared list of media elements.

Images