CN116648895A - Image pickup apparatus mode for capturing a plurality of video clips - Google Patents

Abstract

Aspects of the present disclosure relate to systems including computer-readable storage media storing programs and methods for providing different camera modes. The program and method cause the following operations to be performed: displaying, by the messaging application, a capture user interface for capturing video according to a first camera mode for capturing a single video clip to generate a media content item; providing, by the messaging application, a camera mode selection element within the capture user interface, the camera mode selection element selectable to switch from a first camera mode to a second camera mode for capturing a plurality of video clips for combining to generate a media content item; receiving, via a capture user interface, a user input selecting a camera mode selection element; and updating, by the messaging application, a capture user interface for video capture according to the second camera mode in response to receiving the user input.

Description

Image pickup apparatus mode for capturing a plurality of video clips

Cross Reference to Related Applications

This patent application claims the benefit of U.S. patent application Ser. No. 17/556,713, filed on day 2021, 12, and 30, which claims the benefit of U.S. provisional patent application Ser. No. 63/132,149, entitled "CAMERA MODE FOR CAPTURING MULTIPLE VIDEO CLIPS WITHIN AMESSAGING SYSTEM," filed on day 2020, the entire contents of which are incorporated herein by reference.

Technical Field

The present disclosure relates generally to messaging systems, including camera modes for capturing multiple video clips within the messaging system.

Background

Messaging systems provide for the exchange of message content between users. For example, messaging systems allow users to exchange message content (e.g., text, images) with one or more other users.

Drawings

In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. For ease of identifying a discussion of any particular element or act, the highest digit or digits in a reference number refer to the figure number in which that element is first introduced. Some non-limiting examples are shown in the figures of the accompanying drawings, in which:

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

Fig. 2 is a diagrammatic representation of a messaging system having both client-side and server-side functions in accordance with some examples.

FIG. 3 is a diagrammatic representation of a data structure as maintained in a database in accordance with some examples.

Fig. 4 is a diagrammatic representation of a message according to some examples.

Fig. 5 is a diagram illustrating a user interface arrangement configured to capture, combine, and preview multiple video clips, according to some example embodiments.

Fig. 6A-6E illustrate a user interface configured to capture a plurality of video clips for inclusion into a media content item according to some example embodiments.

FIG. 7 illustrates a user interface for previewing multiple video clips for assembly into a media content item according to some example embodiments.

Fig. 8 is a flowchart illustrating a process for providing a camera mode for capturing and combining multiple video clips according to some example embodiments.

Fig. 9 is a flow diagram of an access restriction process according to some examples.

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

Fig. 11 is a block diagram illustrating a software architecture in which an example may be implemented.

Detailed Description

Messaging systems typically allow users to exchange content items (e.g., messages, images, and/or videos) with each other in a message thread. The messaging system may implement one or more content feeds to present the media content to the end user.

The disclosed embodiments provide a messaging system with user interface elements to select between a first camera mode and a second camera mode. Each camera mode provides a different way for capturing video for inclusion in a media content item (e.g., for transmission to friends, broadcast to others, etc.). The first camera mode corresponds to capturing a single video clip that may be used to generate the media content item. The second camera mode corresponds to capturing a plurality of video clips that can be combined to generate the media content item. The user interface for capturing video includes a camera mode selection element (e.g., a button) for switching between a first camera mode and a second camera mode.

The behavior of the user interface changes based on the selected camera mode. For example, a capture button (e.g., for starting and stopping video capture) is responsive to different types of inputs depending on the camera mode selected. In the first camera mode, a press and hold gesture is used to capture a video clip and a tap gesture is used to capture a picture. In the second camera mode, video clips are captured by pressing and holding a gesture and/or by a first tap gesture (e.g., for starting video capture) followed by a second tap gesture (e.g., for ending video capture).

In another example, the second camera mode includes a timeline progress bar depicting a video clip (e.g., depicted as a segment) when the video clip is captured. In addition, the preview button in the second camera mode is selectable to redirect to a preview interface for previewing and editing the media content item. The media content item may be generated by combining one or more of the plurality of video clips (e.g., each clip having a corresponding edit) and/or may be transmitted, saved, or broadcast via a preview interface.

Fig. 1 is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of client devices 102, each hosting several applications including a messaging client 104 and other applications 106. Each messaging client 104 is communicatively coupled to other instances of messaging clients 104 (e.g., hosted on respective other client devices 102), messaging server systems 108, and third party servers 110 via a network 112 (e.g., the internet). The messaging client 104 may also communicate with locally hosted applications 106 using an Application Program Interface (API).

The messaging client 104 is capable of communicating and exchanging data with other messaging clients 104 and with the messaging server system 108 via the network 112. The data exchanged between the messaging clients 104 and the messaging server system 108 includes functions (e.g., commands to activate the functions) as well as payload data (e.g., text, audio, video, or other multimedia data).

The messaging server system 108 provides server-side functionality to particular 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 positioning of certain functions within the messaging client 104 or within the messaging server system 108 may be a design choice. For example, it may be technically preferable that: certain techniques and functions are initially deployed within the messaging server system 108, but later migrated to the messaging client 104 where the client device 102 has sufficient processing power.

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

Turning now specifically to messaging server system 108, an Application Program Interface (API) server 116 is coupled to application server 114 and provides a programming interface to application server 114. The application server 114 is communicatively coupled to a database server 120, the database server 120 facilitating access to a database 126, the database 126 storing data associated with messages processed by the application server 114. Similarly, web server 128 is coupled to application server 114 and provides a web-based interface to application server 114. To this end, web server 128 processes incoming network requests via the hypertext transfer protocol (HTTP) and several other related protocols.

An Application Program Interface (API) server 116 receives and transmits message data (e.g., command and message payloads) between the client device 102 and the application server 114. In particular, an Application Program Interface (API) server 116 provides a set of interfaces (e.g., routines and protocols) that may be invoked or queried by the messaging client 104 to activate functions of the application server 114. An Application Program Interface (API) server 116 exposes various functions supported by the application server 114, including: registering an account; a login function; sending a message from a particular messaging client 104 to another messaging client 104 via the application server 114; transmitting a media file (e.g., image or video) from the messaging client 104 to the messaging server 118 and for possible access by another messaging client 104; a setting of a media data collection (e.g., story); retrieving a friends list of the user of the client device 102; retrieving such a collection; retrieving the message and the content; adding and deleting entities (e.g., friends) in an entity graph (e.g., social graph); locating friends in the social graph; and open application events (e.g., associated with messaging client 104).

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 networking 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 may be aggregated into a collection of content (e.g., referred to as a story or gallery). These sets are then made available to the messaging client 104. Such processing may also be performed by the messaging server 118 on the server side in view of hardware requirements for other processors and memory intensive processing of data.

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 video within the payload of messages sent from the messaging server 118 or received at the messaging server 118.

The social networking server 124 supports various social networking functions and services and makes these functions and services available to the messaging server 118. To this end, social networking server 124 maintains and accesses entity graph 304 (shown in FIG. 3) within database 126. Examples of functions and services supported by the social networking server 124 include identifying other users in the messaging system 100 that have a relationship with or are "focused on" by a particular user, as well as identifying other entities and interests of the particular user.

Returning to the messaging client 104, features and functions of external resources (e.g., applications 106 or applets)) 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 external to the messaging client 104. The 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 initiate or access a feature of such an external resource. The external resource may be an application 106 (e.g., a "local app") installed on the client device 102, or a small-scale version (e.g., an "applet") of an application hosted on the client device 102 or located remotely from the client device 102 (e.g., on the third-party server 110). The small-scale version of the application includes a subset of the features and functions of the application (e.g., full-scale, raw version of the application) and is implemented using a markup language document. In one example, a small-scale version of an application (e.g., an "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., a..ml file), applets may also include scripting languages (e.g., a..js file or a. Json file) and style sheets (e.g., a..ss file).

In response to receiving a user selection of an option to initiate 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, the application 106 locally installed on the client device 102 may be launched independent of the messaging client 104 and separately from the messaging client 104, for example, by selecting an icon corresponding to the application 106 on the home screen of the client device 102. A small version of such an application may be launched or accessed via the messaging client 104, and in some examples, no portion of the small application may be (or limited to be) accessed 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 the third-party server 110 and processing such document.

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 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 communicates with, for example, 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 render the web-based external resource within the user interface of the messaging client 104.

The messaging client 104 may notify the user of the client device 102 or other users (e.g., "friends") associated with such users of the activity occurring in one or more external resources. For example, the messaging client 104 may provide notifications to participants in a conversation (e.g., chat session) in the messaging client 104 regarding the current or recent use of external resources by one or more members of a group of users. One or more users may be invited to join an active external resource or to initiate a recently used but currently inactive external resource (among the set of friends). The external resources may provide participants in the conversation each using a respective messaging client 104 with the ability to share items, states, conditions, or locations in the external resources with one or more members of a group of users into a chat session. The shared items may be interactive chat cards with which members of the chat may interact, for example, to initiate a corresponding external resource, to view specific information within the external resource, or to bring members of the chat to a specific location or state within the external resource. Within a given external resource, a response message may be sent to the user on the messaging client 104. The external resource may selectively include different media items in the response based on the current context of the external resource.

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 dependent menu. For example, icons representing different ones of the applications 106 (or applets) may vary based on how the user launches the menu (e.g., from a conversational interface or from a non-conversational interface).

Fig. 2 is a block diagram illustrating additional details regarding the messaging system 100 according to some examples. In particular, the messaging system 100 is shown to include a messaging client 104 and an application server 114. The messaging system 100 contains a number of subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a transient timer system 202, a collection management system 204, an enhancement system 208, a map system 210, an external resource system 212, and a camera mode system 214.

The ephemeral 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 ephemeral timer system 202 contains a plurality of timers that selectively enable access to messages and associated content (e.g., for presentation and display) via the messaging client 104 based on a duration and display parameters associated with the message or collection of messages (e.g., story). Additional details regarding the operation of the transient timer system 202 are provided below.

The collection management system 204 is responsible for managing a collection or collection of media (e.g., a collection of text, image video, and audio data). The collection of content (e.g., messages, including images, video, text, and audio) may be organized into an "event gallery" or "event story. Such a collection may be made available for a specified period of time (e.g., the duration of the event to which the content relates). For example, content related to a concert may be made available as a "story" for the duration of the concert. The collection management system 204 may also be responsible for publishing icons that provide notifications to the user interface of the messaging client 104 regarding the presence of particular collections.

In addition, the collection management system 204 includes a curation interface 206 that enables the collection manager to manage and curate specific collections of content. For example, curation interface 206 enables an event organizer to curate a collection of content related to a particular event (e.g., delete inappropriate content or redundant messages). In addition, the collection management system 204 employs machine vision (or image recognition techniques) and content rules to automatically curate the collection of content. In some examples, the user may be paid the compensation for including the user-generated content into the collection. In such cases, the collection management system 204 operates to automatically pay such users to use their content.

Enhancement system 208 provides various functionality that enables a user to enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the enhancement system 208 provides functionality 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 overlay or enhancement (e.g., image filters) to the messaging client 104 based on the geolocation 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 may include audio and visual content and visual effects. Examples of audio and visual content include pictures, text, logos, animations and sound effects. Examples of visual effects include color overlays. Audio and visual content or visual effects may be applied to media content items (e.g., photos) at the client device 102. For example, the media overlay may include text or images that may be overlaid on top of a photograph taken by the client device 102. In another example, the media overlay includes a location identification overlay (e.g., a Venice beach), a name of a live event, or a merchant name overlay (e.g., a beach cafe). 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 merchant at the geolocation of the client device 102. The media overlay may include other indicia associated with the merchant. The media overlay may be stored in database 126 and accessed through database server 120.

In some examples, the enhancement system 208 provides a user-based distribution platform that enables a user to select a geographic location on a map and upload content associated with the selected geographic location. The user may also specify the case where a particular media overlay should be provided to other users. Enhancement system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geographic location.

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

In other examples, as discussed below with respect to fig. 3, the augmentation system 208 causes the augmented reality content to be presented in association with an image or video captured by the camera of the client device 102. The augment system 208 may implement or otherwise access augmented reality content items (e.g., corresponding to application shots (lens) or augmented reality experiences) to provide real-time special effects and/or sounds that may be added to an image or video. To facilitate presentation of augmented reality content, the augmentation system 208 may implement or otherwise access an object recognition algorithm (e.g., including a machine learning algorithm) configured to scan an image or video and detect/track movement of objects within the image or video.

The map 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 map system 210 enables display of user icons or avatars (e.g., stored in the profile data 302) on a map to indicate the current or past positioning of the user's "friends" within the context of the map, as well as media content (e.g., a collection of messages including photos and videos) generated by those friends. For example, on the map interface of the messaging client 104, a message posted to the messaging system 100 by a user from a particular geographic location may be displayed to a "friend" of the particular user within the context of the particular location of the map. The user may also share his or her location and status information with other users of the messaging system 100 via the messaging client 104 (e.g., using an appropriate status avatar), where the location and status information is similarly displayed to the selected user within the context of the map interface of the messaging client 104.

The external resource system 212 provides an interface for the messaging client 104 to communicate with a remote server (e.g., the third party server 110) to launch or access external resources (i.e., applications or applets). Each third party server 110 hosts an application or small-scale version of an application (e.g., a gaming application, a utility application, a payment application, or a ride share application), such as a markup language-based (e.g., HTML 5). The messaging client 104 may launch a web-based resource (e.g., an application) by accessing an HTML5 file from a third party server 110 associated with the web-based resource. In some examples, the application hosted by the third party server 110 is programmed in JavaScript with a Software Development Kit (SDK) provided by the messaging server 118. The SDK includes an Application Program Interface (API) having functions that can be invoked or activated by web-based applications. In some examples, the messaging server 118 includes a javascript library that provides given external resource access to certain user data of the messaging client 104. HTML5 is used as an example technique for programming games, but applications and resources programmed based on other techniques may be used.

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

The SDK stored on the messaging server 118 effectively provides bridging between external resources (e.g., applications 106 or applets) and the messaging client 104. This provides a seamless experience for a user to communicate with other users on the messaging client 104 while also preserving the look and feel of the messaging client 104. To bridge communications between external resources and the messaging client 104, in some examples, the SDK facilitates communications between the third party server 110 and the messaging client 104. In some examples, webviewjavascript bridge running on the client device 102 establishes two unidirectional communication channels between the external resource 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 callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with the callback identifier.

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 to share based on the needs of external resources. In some examples, each third party server 110 provides an HTML5 file corresponding to the web-based external resource to the messaging server 118. The messaging server 118 may add a visual representation (e.g., a box design or other graphic) of the web-based external resource in the messaging client 104. Once the user selects a visual representation or instructs the messaging client 104, through the GUI of the messaging client 104, to access the features of the web-based external resource, the messaging client 104 obtains the HTML5 file and instantiates the resources needed to access the features of the web-based external resource.

The messaging client 104 presents a graphical user interface (e.g., a landing page or a banner screen) for the external resource. During, before, or after presentation of the landing page or the banner screen, the messaging client 104 determines whether the initiated external resource has been previously authorized to access the user data of the messaging client 104. In response to determining that the initiated external resource has been previously authorized to access the user data of the messaging client 104, the messaging client 104 presents another graphical user interface of the external resource that includes functionality and features of the external resource. In response to determining that the initiated external resource was not previously authorized to access the user data of messaging client 104, messaging client 104 slides up a menu (e.g., animates the menu to appear from the bottom of the screen to the middle or other portion of the screen) after a threshold period of time (e.g., 3 seconds) of displaying a login page or title screen of the external resource for authorizing the external resource to access the user data. The menu identifies the type of user data that the external resource is to be authorized to use. In response to receiving a user selection of the receipt option, the messaging client 104 adds the external resource to the list of authorized external resources and allows the external resource to access 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 in accordance with the OAuth 2 framework.

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, external resources including full-scale applications (e.g., application 106) are provided access to a first type of user data (e.g., a two-dimensional-only avatar of a user with or without different body characteristics). As another example, access to a second type of user data (e.g., payment information, a two-dimensional avatar of the user, a three-dimensional avatar of the user, and avatars having various avatar characteristics) is provided to an external resource that includes a small scale version of the application (e.g., a web-based version of the application). Avatar characteristics include different ways of customizing the look and feel (e.g., different gestures, facial features, clothing, etc.) of the avatar.

The camera mode system 214 implements various functions to provide different camera modes within the context of the messaging system 100. For example, the camera mode system 214 provides a first camera mode and a second camera mode, and provides the user with the option of selecting between the first camera mode and the second camera mode. The first camera mode corresponds to capturing a single video clip to generate a media content item. The camera mode system 214 provides a second camera mode to capture multiple videos for combining to generate a media content item. In addition, camera mode system 214 is configured to adjust a user interface (e.g., a capture user interface for capturing video clips and/or a preview user interface for previewing captured video clips) based on which camera mode is enabled.

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

Database 126 includes message data stored within message table 306. For any particular one of the messages, the message data includes at least message sender data, message receiver (or receiver) data, and a payload. Additional details regarding information that may be included in a message and in message data stored in message table 306 are described below with reference to fig. 4.

The entity table 308 stores entity data and links (e.g., by way of reference) to the entity graph 304 and profile data 302. The entities whose records are maintained in entity table 308 may include individuals, corporate entities, organizations, objects, sites, events, and the like. 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).

Entity map 304 stores information about relationships and associations between entities. By way of example only, such relationships may be social, professional (e.g., working at a common company or organization), interest-based, or activity-based.

The profile data 302 stores a plurality of types of profile data regarding a particular entity. The profile data 302 may be selectively used and presented to other users of the messaging system 100 based on privacy settings specified by a particular entity. In the case where the entity is a person, the profile data 302 includes, for example, a user name, a telephone number, an address, settings (e.g., notification and privacy settings), and a user-selected avatar representation (or a collection of such avatar representations). A particular user may then selectively include one or more of these avatar representations in the content of messages communicated via the messaging system 100 and on map interfaces displayed to other users by the messaging client 104. The set of avatar representations may include a "status avatar" that presents a graphical representation of status or activity that the user may select to communicate at a particular time.

In the case where the entity is a community, the profile data 302 for the community may similarly include one or more avatar representations associated with the community in addition to the community name, the member, and various settings (e.g., notifications) for the relevant community.

Database 126 also stores enhancement data, such as overlays or filters, in enhancement table 310. Enhancement data is associated with and applied to video (the data of which is stored in video table 314) and images (the data of which is stored in image table 316).

In one example, the filter is an overlay that is displayed as an overlay over the image or video during presentation to the recipient user. The filters may be of various types, including user-selected filters from a set of filters presented to the sending user by the messaging client 104 when the sending user is composing a message. Other types of filters include geolocation filters (also referred to as geo-filters) that may be presented to a sending user based on geolocation. For example, a nearby or special location-specific geolocation filter may be presented by the messaging client 104 within the user interface based on geolocation information determined by the Global Positioning System (GPS) unit of the client device 102.

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

Other augmented data that may be stored within the image table 316 includes augmented reality content items (e.g., corresponding to application shots or augmented reality experiences). The augmented reality content item may provide real-time special effects and/or sound that may be added to an image or video.

As described above, the augmentation data includes augmented reality content items, overlays, image transforms, AR images, and similar terms that relate to modifications that may be applied to image data (e.g., video or images). This includes real-time modifications that modify the image as it is captured using the device sensor (e.g., one or more cameras) of the client device 102 and then displayed on the screen of the client device 102 in the case of modifications. This also includes modifications to the stored content, such as video clips in a gallery that may be modified. For example, in a client device 102 accessing multiple augmented reality content items, a user may use a single video clip with multiple augmented reality content items to see how different augmented reality content items will modify the stored clip. For example, multiple augmented reality content items to which different pseudo-random motion models are applied may be applied to the same content by selecting different augmented reality content items for the same content. Similarly, real-time video capture may be used with the illustrated modifications to illustrate how the video image currently captured by the sensor of the client device 102 will modify the captured data. Such data may be displayed on the screen only and not stored in memory, or content captured by the device sensor may be recorded and stored in memory with or without modification (or both). In some systems, the preview feature may display how different augmented reality content items appear in different windows of the display at the same time. For example, this may enable multiple windows with different pseudo-random animations to be viewed simultaneously on a display.

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

Real-time video processing may 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 may load a video file and save it in the memory of the device, or may generate a video stream using a sensor of the device. In addition, computer animation models may be used to process any object, such as parts of a human face and body, animals or inanimate objects such as chairs, automobiles, or other objects.

In some examples, when a particular modification is selected along with the content to be transformed, the elements to be transformed are identified by the computing device and then detected and tracked if they exist in the video frame. Elements of the object are modified according to the modification request, thereby transforming frames of the video stream. The transformation of frames of the video stream may be performed by different methods for different types of transformations. For example, for transformations of frames that primarily refer to changing the form of an element of an object, characteristic points of each element of the object are computed (e.g., using an Active Shape Model (ASM) or other known methods). Then, a grid based on the characteristic points is generated for each of the at least one element of the object. The grid is used for tracking subsequent stages of 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. Additional points are then 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. The frames of the video stream may then be transformed by modifying the elements of the object based on the set of first points and the set of second points and the grid. In such a method, the background of the modified object may also be changed or distorted by tracking and modifying the background.

In some examples, transforming some regions of the object using elements of the object may be performed by calculating characteristic points for each element of the object and generating a grid based on the calculated characteristic points. Points are generated on the grid, and then various regions are generated based on the points. The elements of the object are then tracked by aligning the region of each element with the position of each of the at least one element, and the nature of the region may be modified based on the modification request, thereby transforming the frames of the video stream. The nature of the mentioned areas may be transformed in different ways depending on the specific modification request. Such modifications may involve: changing the color of the region; removing at least some portions of the region from frames of the video stream; including one or more new objects in the modification request-based region; and modifying or distorting elements of the region or object. In various examples, any combination of such modifications or other similar modifications may be used. For some models to be animated, some characteristic points may be selected as control points for the entire state space to be used to determine options for model animation.

In some examples of computer-animated models that use face detection to transform image data, a particular face detection algorithm (e.g., viola-Jones) is used to detect faces on the image. An Active Shape Model (ASM) algorithm is then applied to the facial regions of the image to detect facial feature reference points.

Other methods and algorithms suitable for face detection may be used. For example, in some examples, landmarks are used to locate features, which represent distinguishable points present in most of the images considered. For example, for facial landmarks, the localization of the left eye pupil may be used. In the case where the initial landmark is unidentifiable (e.g., if the person has eye-masks), a secondary landmark may be used. Such landmark identification procedure may be used for any such object. In some examples, the collection of landmarks forms a shape. The coordinates of points in the shape may be used to represent the shape as a vector. One shape is aligned with another shape using a similar transformation (allowing translation, scaling, and rotation) that minimizes the average euclidean distance between shape points. The average shape is the average of the aligned training shapes.

In some examples, the landmarks are searched starting from an average shape aligned with the position and size of the face determined by the global face detector. Such a search then repeats the following steps until convergence occurs: the tentative shape is suggested by adjusting the positioning of the shape points by template matching of the image texture around each point, and then conforming the tentative shape to the global shape model. In some systems, individual template matching is unreliable, and shape models pool the results of weak template matching to form a stronger overall classifier. The entire search is repeated at each level in the image pyramid, from coarse resolution to fine resolution.

The transformation system may capture images or video streams on a client device (e.g., client device 102) and perform complex image manipulation locally on the client device 102 while maintaining a suitable user experience, computation time, and power consumption. Complex image manipulation may include size and shape changes, mood migration (e.g., changing a face from frowning to smiling), state migration (e.g., aging a subject, reducing apparent age, changing gender), style migration, graphic element application, and any other suitable image or video manipulation implemented by a convolutional neural network that has been configured to be effectively performed on the client device 102.

In some examples, a computer animation model for transforming image data may be used by a system in which a user may capture an image or video stream (e.g., a self-portrait) of the user 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 faces within an image or video stream and provides a modification icon associated with a computer animation model to transform the data image, or the computer animation model may be present in association with the interface described herein. The modification icon includes a change, which may be the basis for modifying the face of the user within the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates a process of converting the image of the user to reflect the selected modification icon (e.g., generating a smiley face on the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream may be presented in a graphical user interface displayed on the client device 102. The transformation system may implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modifications. That is, the user may capture an image or video stream and, once the modification icon is selected, the modified result may be presented in real-time or near real-time. Further, the modification may be persistent while the video stream is being captured, and the selected modification icon remains switched. Machine-learned neural networks may be used to implement such modifications.

Presenting a modified graphical user interface performed by the transformation system may provide the user with additional interaction options. Such options may be based on an interface (e.g., initiated from a content creator user interface) for initiating content capture and selection of a particular computer animation model. In various examples, the modification may be persistent after an initial selection of the modification icon. The user may turn the modification on or off 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 may globally turn the modification on or off by tapping or selecting a single face modified and displayed within the graphical user interface. In some examples, each face in a set of multiple faces may be modified individually, or such modification may be switched individually by tapping or selecting each face or a series of each faces displayed within the graphical user interface.

Story table 312 stores data regarding a collection of messages and associated image, video, or audio data that are compiled into a collection (e.g., a story or gallery). Creation of a particular collection may be initiated by a particular user (e.g., each user for which records are maintained in entity table 308). A user may create a "personal story" in the form of a collection of content that has been created and transmitted/broadcast 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 particular content to his or her personal story.

The collection may also constitute a "live story" which is a collection of content from multiple users created manually, automatically, or using a combination of manual and automatic techniques. For example, a "live story" may constitute a curation stream of user submitted content from different locations and events. A user whose client device enables a positioning service and at a particular time is at a co-location event may be presented with an option, e.g., via a user interface of messaging client 104, to contribute content to a particular live story. The live story may be identified to the user by the messaging client 104 based on his or her positioning. The end result is a "live story" told from a community perspective.

Another type of collection of content is referred to as a "positioning story" that enables users whose client devices 102 are located within a particular geographic location (e.g., at a college or university campus) to contribute to the particular collection. In some examples, the contribution to the positioning story may require a second degree of authentication to verify that the end user belongs to a particular organization or other entity (e.g., is a student in a university campus).

As mentioned above, the video table 314 stores video data, which in one example is associated with messages whose records remain within the message table 306. Similarly, image table 316 stores image data associated with messages whose message data is stored in entity table 308. Entity table 308 may associate various enhancements from enhancement table 310 with various images and videos stored in image table 316 and video table 314.

Fig. 4 is a schematic diagram illustrating the structure of a message 400, the message 400 generated by a messaging client 104 for communication to another messaging client 104 or messaging server 118, according to some examples. The contents of a particular message 400 are used to populate a message table 306 stored within the database 126, the message table 306 being accessible by the messaging server 118. Similarly, the content of message 400 is stored in memory of client device 102 or application server 114 as "in-flight" or "in-flight" data. Message 400 is shown as including the following example components:

message identifier 402: a unique identifier that identifies the message 400.

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

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

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

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.

Message enhancement data 412: enhancement data (e.g., filters, labels, or other annotations or enhancements) representing enhancements to the message image payload 406, the message video payload 408, or the message audio payload 410 to be applied to the message 400. Enhancement data for a transmitted or received message 400 may be stored in the enhancement table 310.

Message duration parameter 414: the parameter values that indicate, in units of seconds, the content of the message (e.g., message image payload 406, message video payload 408, message audio payload 410) to be presented to or made accessible to the user via the messaging client 104.

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

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

Message tag 420: each message 400 may be tagged with a plurality of tags, each of which indicates the subject matter 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), the tag value may be included within the message tag 420 indicating the relevant animal. The tag value may be generated manually based on user input or may be generated automatically using, for example, image recognition.

Message sender identifier 422: an identifier (e.g., a messaging system identifier, an email address, or a device identifier) indicating the user of the client device 102 on which the message 400 was generated and from which the message 400 was sent.

Message recipient identifier 424: an identifier (e.g., a messaging system identifier, an email address, or a device identifier) indicating the user of the client device 102 to which the message 400 is addressed.

The contents (e.g., values) 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 the message-image payload 406 may be a pointer to a location within the image table 316 (or an address of a location within the image table 316). Similarly, values within message video payload 408 may point to data stored within video table 314, values stored within message enhancement 412 may point to data stored within enhancement table 310, values stored within message story identifier 418 may point to data stored within story table 312, and values stored within message sender identifier 422 and message receiver identifier 424 may point to user records stored within entity table 308.

Fig. 5 is a diagram illustrating a user interface arrangement 500 configured to capture, combine, and preview a plurality of video clips, according to some example embodiments. For purposes of illustration, the user interface arrangement 500 is described herein primarily with reference to the messaging client 104 of fig. 1 and the camera mode system 214 of fig. 2. Not all of the interfaces/components depicted and described may be used in all implementations, and one or more embodiments may include additional or different interfaces/components than those shown or described with respect to the figures. Changes may be made in the arrangement and type of interfaces/components without departing from the spirit or scope of the claims set forth herein.

The user interface arrangement 500 may be implemented at least in part by the camera mode system 214. As described above, the camera mode system 214 may correspond to a subsystem of the messaging system 100 and may be supported on the client side by the messaging client 104 and/or on the server side by the application server 114. In one or more embodiments, capturing, combining, and previewing of video clips as described herein may be implemented on the client side, the server side, and/or in a combination of the client side and the server side.

As shown in fig. 5, the capture user interface 502 includes a camera selection button 506, which camera selection button 506 is user selectable for switching between the rear camera and the front camera of the client device 102. The capture user interface 502 also includes a flash button 508 for activating or deactivating a flash with respect to the captured image data 512 (or captured image). The capture user interface 502 also includes a camera mode selection button 510. In addition, capture user interface 502 includes a carousel start button 522 for starting a carousel interface as discussed below with respect to fig. 6D.

Further, the capture user interface 502 includes a capture button 520 that a user can select to capture video (e.g., video clips) and/or images (e.g., pictures). As described herein, a "video clip" corresponds to a series of video frames that run for an uninterrupted period of time. For example, a video clip corresponds to a video captured from the time when the image pickup device starts recording until the time when the image pickup device stops recording.

In one or more implementations, the messaging client 104 in combination with the camera mode system 214 enables a user to select between a first camera mode and a second camera mode for video capture. For example, the first camera mode corresponds to capturing a single video clip that may be used to generate the media content item. The second camera mode corresponds to capturing a plurality of video clips that may be combined to generate the media content item.

In this regard, the camera mode selection button 510 is user selectable for switching between a first camera mode and a second camera mode. In one or more embodiments, the messaging client 104 defaults to the first camera mode. For example, upon startup of the messaging client 104, the messaging client 104 activates the camera of the client device 102 to display the captured image data 512 in real-time and defaults to the first camera mode with respect to the capture user interface 502.

In response to a user selection of the camera mode selection button 510, the messaging client 104 in combination with the camera mode system 214 causes a switch from the first camera mode to the second camera mode to be effected. Switching to the second camera mode may also be accomplished via a predefined touch gesture (e.g., a left drag gesture starting from capture button 520 while in the first camera mode). In one or more embodiments, a tutorial (e.g., modality or overlay) may be presented upon first initiation of the second camera mode to teach the user the features associated with the second camera mode.

In the first camera mode, capture button 520 may be selected to capture a single video clip via a predefined gesture (e.g., a press and hold gesture, where video is recorded for a hold duration). Additionally, capture button 520 may be selected to capture a picture via another predefined gesture (e.g., a tap gesture).

In the second camera mode, the behavior of the capture button 520 may be different from the behavior of the first camera mode to facilitate capturing multiple video clips. In one or more embodiments, capture button 520 is responsive to different types of touch inputs for capturing video clips. In a first example, capture button 520 may be selected to capture a video clip via a press and hold gesture (e.g., record a video during a hold duration). In another example, capture button 520 may be selected to capture a video clip via a first tap gesture and a second tap gesture, where for the video clip the first tap gesture initiates video capture and the second tap gesture ends video capture (e.g., corresponding to hands-free recording).

In one or more embodiments, the predefined touch area of capture button 520 for the second tap gesture may be smaller than the predefined touch area of capture button 520 for the first tap gesture (e.g., to reduce the likelihood of a user inadvertently stopping video capture). For example, the touch area may correspond to a predefined area within the center of the displayed capture button 520.

In the second camera mode, the camera mode system 214 causes a plurality of video clips to be captured in a sequential manner such that a first video clip is followed by a second video clip, the second video clip is followed by a third video clip, and so on. Each of the video clips may have been captured in response to a respective touch input (e.g., a press and hold gesture, a first/second tap, or a combination thereof) via capture button 520.

In one or more embodiments, the camera mode system 214 causes the update of the timeline bar 514 to be displayed in real-time to depict the video clip as it is captured. As shown in the example of fig. 5, the display of the timeline progress bar 514 may be accompanied by the display of a dismissal button 516 and a preview button 518. In one or more embodiments, the camera mode system 214 causes the undo button 516, timeline progress bar 514, and preview button 518 to be displayed only in the second camera mode. Thus, the cancel button 516, the timeline bar 514, and the preview button 518 are not displayed when the first camera mode is active.

As shown in the example of fig. 5, timeline progress bar 514 depicts video segments as respective segments, each segment having a length proportional to the duration of the respective video segment. Segments may be added and/or updated in real-time. As each respective video segment is captured, the length of each segment may appear to increase in real-time. For purposes of illustration, the expanded view 524 (which need not be shown by the capture user interface 502) depicts example video clips 1-5.

In one or more embodiments, timeline progress bar 514 is configured to update in real-time based on the combined duration for all currently captured video clips exceeding a preset time threshold. For example, the initial timeline length of the timeline progress bar 514 can be preset to a first time threshold (e.g., 10 seconds) such that the timeline progress bar 514 is depicted as being filled when the first time threshold is reached. Once the combined duration of the currently captured video segments reaches the first time threshold, the timeline length is adjusted to a second time threshold (e.g., 30 seconds), where the current progress (e.g., segmentation) is depicted as folded relative to the adjusted timeline length. Once the combined duration of the currently captured video segments reaches the second time threshold, the timeline length is adjusted to a third time threshold (e.g., 60 seconds), where the current progress (e.g., segmentation) is depicted as folded over with respect to the adjusted timeline length.

In one or more embodiments, the camera mode system 214 causes the combined duration of all currently captured video clips to be limited or suppressed. For example, the camera mode system 214 may set the maximum duration to 60 seconds (e.g., corresponding to the third time threshold mentioned above). If the total recording time reaches a maximum duration, capture user interface 502 may display a notification to prevent recording of subsequent video clips to be included in the media content item.

The capture user interface 502 also includes a cancel button 516. As described above, the deactivate button 516 may be presented when the second camera mode is active (and not when the first camera mode is active). The undo button 516 may be selected to delete the most recent video segment (e.g., the last or right-most segment corresponding to the timeline progress bar 514). In the event that there is no video clip in the timeline progress bar 514, the undo button 516 may be replaced with a close button (depicted as "x" and discussed further below with respect to FIG. 7) that is selectable to exit the second camera mode and revert to the first camera mode.

The restoration from the second camera mode to the first camera mode may also be accomplished by user selection of the camera mode selection button 510. In response to a user selection of camera mode selection button 510 while in the second camera mode, messaging client 104 may prompt the user to confirm that any captured video clips will be deleted.

The capture user interface 502 also includes a preview button 518. The preview button 518 is selectable to switch from the capture user interface 502 to the preview user interface 504. On the other hand, the first camera mode in the example embodiment may not include the preview button 518, and instead, the preview interface may be automatically presented after a single video clip (or picture) is captured.

In the second camera mode, the preview user interface 504 causes the captured video clips (e.g., clips 1-6) to be previewed at the time of capture. In addition, the preview user interface 504 provides user selectable elements for generating media content items based on the captured video clips.

In one or more implementations, the preview user interface 504 includes a user selectable button ("+" button, which is further depicted and discussed below with respect to fig. 7) for adding a video clip to a captured video clip. Selecting the button may cause the camera mode system 214 to switch from the preview user interface 504 back to the capture user interface 502, where all video clips and edits remain.

For example, the camera mode system 214 may facilitate retention of clips in local memory associated with the collection management system 204 and may facilitate retention of edits in local memory associated with the enhancement system 208. In addition to retaining video clips and/or edits regarding user-selectable buttons ("+" buttons), camera mode system 214 may retain and re-present video clips and/or edits regarding user switching between other interfaces and/or applications. For example, when returning to the camera selection button 506 or preview user interface 504 from one or more of the following, the video clip and/or editing is retained: another interface (e.g., chat interface, reply interface) within the messaging client 104; applications other than messaging client 104 (e.g., wherein the selected camera mode and/or timeline progress is also preserved, as facilitated by camera mode system 214); and/or shut down the messaging client 104 (e.g., wherein the selected camera mode and/or timeline progress is also preserved).

Referring back to fig. 5, the preview user interface 504 includes an editing tool 526 for modifying/annotating (e.g., drawing on, adding text to, adding a decal to, cropping, etc.) the captured video clip. Although not shown in fig. 5, the preview user interface 504 may also include interface elements (e.g., buttons) for one or more of the following: saving the captured video clip (e.g., with modifications/annotations) as a media content item; creating or updating a story based on the captured video clips (e.g., with modifications/annotations); modifying an audio signal associated with the captured video clip; transmitting media content items including the captured video clips (e.g., with modifications/annotations) to contacts/friends; and/or broadcast media content items associated with a feed interface (e.g., for viewing by other users that are not necessarily contacts/friends).

As described, the preview user interface 504 enables generation of media content items based on a plurality of video clips. In one or more implementations, the messaging client 104 (e.g., in conjunction with the messaging server system 108) is configured to combine the plurality of video segments along with the modifications or annotations to generate the media content item based on the combined video segments. The media content item may correspond to a single entity (e.g., video, message) that includes all of the clips (with modifications/annotations). In one or more implementations, the media content items are configured to be played continuously (e.g., relative to a viewing user) in order to loop back to the first video clip after the last video clip is played.

Fig. 6A-6E illustrate a user interface (e.g., capture user interface 602) configured to capture a plurality of video clips for inclusion into a media content item according to some example embodiments. Fig. 6A-6E depict an example scenario in which a user selects the second camera mode mentioned above (fig. 6A), captures a first video clip (fig. 6B-6C), initiates an on-air interface (e.g., fig. 6D), and continues to capture the video clip (fig. 6E).

Similar to the capture user interface 502 of fig. 5, the capture user interface 602 of fig. 6A-6E includes one or more of the following: camera selection button 604 (e.g., for switching between a rear camera and a front camera), flash button 606 (e.g., for activating and deactivating a flash), camera mode selection button 608 (e.g., for switching between a first camera mode and a second camera mode), capture button 610, carousel start button 612 (e.g., for starting a carousel interface 624), timeline progress bar 616 (e.g., for displaying a progress of capturing a video clip), close button 614 (e.g., for switching back from the second camera mode to the first camera mode), preview button 618 (e.g., for previewing, editing, and generating a media content item based on the captured video clip), and/or undo button 622 (e.g., for deleting the most recent video clip).

In the example of fig. 6A, the user selects the image pickup device mode selection button 608. In one or more embodiments, the capture user interface 602 may default to a first camera mode for capturing a single video clip. In response to selection of the camera mode selection button 608, the messaging client 104 in combination with the camera mode system 214 causes a switch from the first camera mode to the second camera mode. As described above, such a handover may include: the capture button 520 is adjusted to respond to different types of touch inputs for capturing video and/or a cancel button 516, a timeline progress bar 514, and a preview button 518 are added to the capture user interface 502.

The close button 614 is a user selectable button for closing the second image pickup device mode. In response to a user selection of the close button 614, the camera mode system 214 causes the second camera mode to be exited and the first camera mode to be restored. In one or more embodiments, the close button 614 is presented when no video clips are captured (e.g., no video clips are captured, or all captured video clips have been deleted via the undo button 516).

The capture user interface 602 also includes a preview button 618, which preview button 618 is selectable to preview, edit, and/or generate a media content item that includes the captured video clip. In one or more implementations, the preview button 618 is enabled after the first video clip has been captured. Alternatively or additionally, the camera mode system 214 may implement a minimum video duration (e.g., 5 seconds) in order to enable the preview button 618. In the example of fig. 6A, preview button 618 is disabled because no video clip has been captured (e.g., timeline progress bar 616 is empty). In one or more implementations, the display of preview button 618 changes when switching from disabled (e.g., gray tick mark) to enabled (e.g., yellow tick mark). A tool-tip (e.g., a message indicating "preview your media content item") may direct the user's attention to the enabled preview button 618. The tool-tip may be displayed only once (e.g., the first time) to inform the user that selection of preview button 618 points to preview user interface 504.

Fig. 6B illustrates an example when a user initiates capture of a first video clip. For example, the user initiates capture of the first video clip based on touch input 620 via capture button 610 (e.g., a press and hold gesture or a first tap gesture as described above). As shown in the example of fig. 6B, the timeline progress bar 616 is updated in real-time to display a first segment that corresponds to a first video segment. The length of the first segment may appear to increase in real time as each respective video segment is captured.

Fig. 6C illustrates when the user has completed capturing the first video clip (e.g., release the press and hold gesture, or the second tap gesture as described above). In one or more embodiments, after capturing the first video clip is completed, camera mode system 214 causes capture user interface 602 to be updated by replacing shutdown button 614 with undo button 622 (e.g., undo button 622 may be selected to delete the first video clip from timeline progress bar 616) and/or by enabling preview button 618.

As described above, the carousel initiation button 612 is user selectable to initiate the carousel interface 624. In response to selection of preview button 618, capture user interface 602 (e.g., via camera mode system 214) is updated to display carousel interface 624 as shown in fig. 6D. In one or more implementations, the carousel interface 624 enables a user to cycle through and/or select different augmented reality content items (e.g., shots) to apply/display images with respect to images currently captured by a device camera and displayed on a device screen. Each of the available augmented reality content items is represented by an icon that is user selectable for switching to the corresponding augmented reality content item.

In one or more implementations, icons corresponding to active augmented reality content items (e.g., active AR icons 626) are displayed differently (e.g., larger than) relative to the remaining icons. The behavior of the AR icon 626 active in the second camera mode is similar to the behavior of the capture button 610. For example, the user may select the active AR icon 626 to capture a subsequent video clip via a corresponding press and hold gesture and/or first and second tap gestures. The corresponding augmented reality content item (e.g., shot) is applied to the subsequently captured video clip. In addition, the user may choose to apply different augmented reality content items to different video clips as they are captured. In one or more implementations, a viewing user of media content items including augmented reality content may be presented with an interface for applying (e.g., unlocking) corresponding augmented reality content items to modify captured images/videos from their ends.

In the example of fig. 6E, the user has captured four video clips, as depicted by the individual segments in timeline progress bar 616. As described above, the undo button 622 may be selected to delete video clips from the timeline progress bar 616 (e.g., where each flick gesture is used to delete the most recent video clip). The capture user interface 602 also includes a preview button 618 that is selectable to preview, edit, and/or generate media content items based on the captured video clip via the preview user interface 702, as discussed below with respect to fig. 7.

FIG. 7 illustrates a preview user interface 702 for previewing multiple video clips for assembly into a media content item according to some example embodiments. For example, fig. 7 depicts an example scenario in which a user selects to preview a plurality of video clips (e.g., 4 video clips) captured in association with fig. 6D.

Similar to the preview user interface 504 of fig. 5, the preview user interface 702 of fig. 7 includes an editing tool 704. For example, editing tool 704 includes user selectable icons (e.g., buttons) for modifying/annotating (e.g., drawing on, adding text to, adding a decal to, cropping, etc.) captured video clips. The user-selectable icons may include options for selecting between cycling, bouncing (e.g., switching between forward playback and reverse playback), and/or single playback with respect to the resulting media content item.

In addition, the preview user interface 702 includes: a save button 714 selectable to save the captured video clip (e.g., with modification/annotation) as a media content item; a story button 716 selectable to create a story based on the captured video clips (e.g., with modifications/annotations); an audio button 712 selectable to modify an audio signal associated with the captured video clip; and/or a send button 718 that may be selected to send media content items that combine the captured video clips (e.g., including any modifications/annotations) to a recipient (e.g., contacts/friends) and/or to broadcast media content items to other users of the messaging system 100.

Further, the preview user interface 702 (e.g., for preview purposes) causes loop playback of the captured video clip, as shown by loop playback 722. The preview user interface 702 also includes a video preview 708 in which each video clip is represented as a respective thumbnail and in which the position indicator 720 indicates the current playback position of the loop playback 722. The thumbnails are depicted as being grouped together (e.g., as a combined video clip). In one or more embodiments, the thumbnails can be individually selected for editing/deleting (e.g., in conjunction with one or more of the editing tools 704).

In addition, the preview user interface 702 includes an add video button 710 for adding video clips to captured video clips (e.g., viewable via video preview 708). In response to a user selection of add video button 710 (e.g., or alternatively, a predefined gesture, such as a swipe down gesture within a predefined area of preview user interface 702), camera mode system 214 causes a switch back from preview user interface 702 to capture user interface 502, wherein all video clips and edits are preserved. A tool-tip (e.g., a message indicating "return camera to add more") may direct the user's attention to add video button 710. The tool-tip may be displayed only once (e.g., the first time) to inform the user that selection of add video button 710 points to capture user interface 502.

Regarding preserving video clips and editing, the camera mode system 214 can facilitate preserving clips in local memory associated with the collection management system 204 and can facilitate preserving editing (e.g., via editing tool 704) in local memory associated with the enhancement system 208. In one or more embodiments, the preview user interface 702 further includes a close button 706 that is selectable to exit the preview user interface 702 and return to the capture user interface 502 without retaining video clips and/or edits. In one or more embodiments, user selection of the close button 706 may prompt the user to confirm deletion of the video clip and/or editing.

Fig. 8 is a flowchart illustrating a process 800 for providing a camera mode for capturing and combining multiple video clips, according to some example embodiments. For purposes of illustration, the process 800 is described herein primarily with reference to the messaging client 104 of fig. 1. However, one or more blocks (or operations) of process 800 may be performed by one or more other components and/or other suitable devices. Further for purposes of illustration, the blocks (or operations) of process 800 are described herein as occurring serially or linearly. However, multiple blocks (or operations) of process 800 may occur in parallel or concurrently. Additionally, the blocks (or operations) of process 800 need not be performed in the order shown, and/or one or more blocks (or operations) of process 800 need not be performed and/or may be replaced by other operations. When the operations of process 800 are complete, process 800 may terminate. In addition, process 800 may correspond to a method, a program, an algorithm, etc.

The messaging client 104 displays (e.g., with the camera mode system 214) a capture user interface for capturing video according to a first camera mode for capturing a single video clip to generate a media content item (block 802). The messaging client 104 provides a camera mode selection element within the capture user interface that is selectable to switch from a first camera mode to a second camera mode for capturing a plurality of video clips for combining to generate a media content item (block 804).

The capture user interface may include a capture button selectable to capture video. In the first camera mode, the capture button may be selected to capture a single video clip via a press and hold gesture. In the first camera mode, the capture button may also be selected to capture a picture via a flick gesture.

In the second camera mode, the capture button may be selected to capture at least one of the plurality of video clips via a corresponding press and hold gesture. Alternatively or additionally, in the second camera mode, the capture button may be selected to capture at least one of the plurality of video clips via a respective first tap gesture for starting video capture and a respective second tap gesture for ending video capture.

The messaging client 104 receives user input selecting the camera mode selection element via the capture user interface (block 806). The messaging client 104 updates the capture user interface for video capture according to the second camera mode in response to receiving the user input (block 808).

The updated capture user interface may include a preview button selectable to navigate to a preview user interface for previewing the captured plurality of video clips to generate the media content item. The updated capture user interface may include a timeline progress bar configured to be updated in real-time based on the number of captured video clips and the length of each captured video clip. The timeline progress bar may also be configured to update in real-time based on the total length of all captured video clips exceeding a preset threshold.

Fig. 9 is a schematic diagram illustrating an access restriction process 9000 according to which access to content (e.g., multimedia payloads of ephemeral messages 902 and associated data) or a collection of content (e.g., ephemeral message groups 904) may be time-limited (e.g., such that it is ephemeral).

The ephemeral message 902 is shown as being associated with a message duration parameter 906, the value of which determines the amount of time that the messaging client 104 will display the ephemeral message 902 to the receiving user of the ephemeral message 902. In one example, a receiving user may view the ephemeral message 902 for up to 10 seconds depending on the amount of time the sending user has specified using the message duration parameter 906.

The message duration parameter 906 and the message recipient identifier 424 are shown as inputs to a message timer 910, the message timer 910 being responsible for determining the amount of time that the ephemeral message 902 is shown to a particular receiving user identified by the message recipient identifier 424. In particular, the ephemeral message 902 is shown to the relevant receiving user only for a period of time determined by the value of the message duration parameter 906. The message timer 910 is shown to provide output to a more generalized ephemeral timer system 202, which ephemeral timer system 202 is responsible for overall timing of the display of content (e.g., ephemeral message 902) to a receiving user.

Transient message 902 is shown in fig. 9 as being included within a transient message group 904 (e.g., a collection of messages in a personal story or an event story). The ephemeral message group 904 has an associated group duration parameter 908, the value of the group duration parameter 908 determining the duration that the ephemeral message group 904 is presented and accessible to a user of the messaging system 100. For example, the group duration parameter 908 may be a duration of a concert, where the ephemeral message group 904 is a collection of content related to the concert. Alternatively, the user (owning user or curator user) may specify the value of the group duration parameter 908 when performing the setting and creation of the ephemeral message group 904.

In addition, each ephemeral message 902 within the ephemeral message group 904 has an associated group participation parameter 912, the value of the group participation parameter 912 determining the duration that the ephemeral message 902 will be accessible within the context of the ephemeral message group 904. Thus, before the ephemeral message group 904 itself expires according to the group duration parameter 908, a particular ephemeral message group 904 may "expire" and become inaccessible in the context of the ephemeral message group 904. The group duration parameter 908, the group participation parameter 912, and the message recipient identifier 424 each provide input to the group timer 914, and the group timer 914 is operable to first determine whether a particular ephemeral message 902 of the ephemeral message group 904 is to be displayed to a particular receiving user, and if so, how long to display. Note that due to the message recipient identifier 424, the ephemeral message group 904 also knows the identity of the particular recipient user.

Thus, the group timer 914 is operable to control the total lifetime of the associated ephemeral message group 904 and the individual ephemeral messages 902 included in the ephemeral message group 904. In one example, each ephemeral message 902 within the ephemeral message group 904 remains viewable and accessible for a period of time specified by the group duration parameter 908. In another example, within the context of the ephemeral message group 904, a certain ephemeral message 902 may expire based on the group participation parameter 912. Note that even within the context of the ephemeral message group 904, the message duration parameter 906 may still determine the duration of displaying the particular ephemeral message 902 to the receiving user. Thus, the message duration parameter 906 determines the duration for which a particular ephemeral message 902 is displayed to a receiving user, regardless of whether the receiving user views the ephemeral message 902 within or outside the context of the ephemeral message group 904.

The ephemeral timer system 202 may also be operable to delete a particular ephemeral message 902 from the ephemeral message group 904 based on determining that the particular ephemeral message 902 has exceeded the associated group participation parameter 912. For example, in the event that the sending user has established a group participation parameter 912 of 24 hours from release, the ephemeral timer system 202 will delete the relevant ephemeral message 902 from the ephemeral message group 904 after the specified 24 hours. The ephemeral timer system 202 also operates to delete the ephemeral message group 904 when the group participation parameter 912 for each ephemeral message 902 within the ephemeral message group 904 has expired, or when the ephemeral message group 904 itself has expired according to the group duration parameter 908.

In some use cases, the creator of a particular ephemeral message group 904 may specify an deadline group duration parameter 908. In this case, the expiration of the group participation parameter 912 for the last remaining ephemeral message 902 within the ephemeral message group 904 will determine when the ephemeral message group 904 itself has expired. In this case, the new ephemeral message 902 with the new group participation parameter 912 added to the ephemeral message group 904 effectively extends the lifetime of the ephemeral message group 904 to a value equal to the group participation parameter 912.

In response to the ephemeral timer system 202 determining that the ephemeral message group 904 has expired (e.g., is no longer accessible), the ephemeral timer system 202 communicates with the messaging system 100 (and, in particular, the messaging client 104, for example) such that the indicia (e.g., icon) associated with the relevant ephemeral message group 904 is no longer displayed within the user interface of the messaging client 104. Similarly, when the ephemeral timer system 202 determines that the message duration parameter 906 for a particular ephemeral message 902 has expired, the ephemeral timer system 202 causes the messaging client 104 to no longer display a flag (e.g., an icon or text identification) associated with the ephemeral message 902.

Fig. 10 is a diagrammatic representation of a machine 1000 within which instructions 1010 (e.g., software, programs, applications, applets, apps, or other executable code) for causing the machine 1000 to perform any one or more of the methods discussed herein may be executed. For example, the instructions 1010 may cause the machine 1000 to perform any one or more of the methods described herein. The instructions 1010 transform a generic, un-programmed machine 1000 into a specific machine 1000 that is programmed to perform the functions described and illustrated in the manner described. The machine 1000 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1000 may operate in the capacity of a server machine or a client machine in server-client network environments, or as a peer machine in peer-to-peer (or distributed) network environments. Machine 1000 may include, but is not limited to: a server computer, a client computer, a Personal Computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a Personal Digital Assistant (PDA), an entertainment media system, a cellular telephone, 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 device, a network router, a network switch, a network bridge, or any machine capable of executing instructions 1010 that specify actions to be taken by machine 1000, sequentially or otherwise. Furthermore, while only a single machine 1000 is illustrated, the term "machine" shall also be taken to include a collection of machines that individually or jointly execute instructions 1010 to perform any one or more of the methodologies discussed herein. For example, the machine 1000 may include the client device 102 or any one of a number of server devices forming part of the messaging server system 108. In some examples, machine 1000 may also include both a client and a server system, where some operations of a particular method or algorithm are performed on the server side, and where some operations of a particular method or algorithm are performed on the client side.

Machine 1000 may include a processor 1004, a memory 1006, and input/output I/O components 1002, which may be configured to communicate with each other via a bus 1040. In an example, the processor 1004 (e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Radio Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, the processor 1008 and the processor 1012 to execute the instructions 1010. The term "processor" is intended to include multi-core processors, which may include two or more separate processors (sometimes referred to as "cores") that may concurrently execute instructions. Although fig. 10 shows multiple processors 1004, machine 1000 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

The memory 1006 includes a main memory 1014, a static memory 1016, and a storage unit 1018, all accessible by the processor 1004 via the bus 1040. Main memory 1006, static memory 1016, and storage unit 1018 store instructions 1010 that implement any one or more of the methods or functions described herein. The instructions 1010 may also reside, completely or partially, within the main memory 1014, within the static memory 1016, within the machine-readable medium 1020 within the storage unit 1018, within at least one of the processors 1004 (e.g., within the cache memory of the processor), or any suitable combination thereof during execution thereof by the machine 1000.

The I/O component 1002 can include various components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurement results, and the like. The particular I/O components 1002 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 would likely not include such a touch input device. It is to be understood that I/O component 1002 can include many other components not shown in FIG. 10. In various examples, I/O components 1002 can include a user output component 1026 and a user input component 1028. The user output component 1026 may include visual components (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)), acoustic components (e.g., speakers), haptic components (e.g., vibration motors, resistance mechanisms), other signal generators, and so forth. The user input component 1028 can 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 touchpad, a trackball, a joystick, a motion sensor, or another pointing instrument), a tactile input component (e.g., a physical button, a touch screen providing positioning and force of a touch or touch gesture, or other tactile input component), an audio input component (e.g., a microphone), and the like.

In another example, I/O component 1002 can include: biometric component 1030, motion component 1032, environmental component 1034, or location component 1036, as well as a wide variety of other components. For example, the biometric component 1030 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body gestures, or eye tracking), measuring biological signals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identifying a person (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or electroencephalogram-based recognition), and the like. The motion component 1032 includes an acceleration sensor component (e.g., accelerometer), a gravity sensor component, a rotation sensor component (e.g., gyroscope).

The environmental components 1034 include, for example: one or more camera devices (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 the concentration of hazardous gas or measures contaminants in the atmosphere for safety), or other components that may provide an indication, measurement, or signal corresponding to the surrounding physical environment.

Regarding the image pickup apparatuses, the client device 102 may have an image pickup apparatus system including, for example, a front-end image pickup apparatus on the front surface of the client device 102 and a rear-end image pickup apparatus on the rear surface of the client device 102. The front-facing camera may, for example, be used to capture still images and video (e.g., "self-timer") of the user of the client device 102, which may then be enhanced with the enhancement data (e.g., filters) described above. The rear camera may be used, for example, to capture still images and video in a more traditional camera mode, where the images are similarly enhanced with enhancement data. In addition to the front-end camera and the rear-end camera, the client device 102 may also include a 360 ° camera for capturing 360 ° photos and videos.

Further, the camera system of the client device 102 may include dual rear-facing cameras (e.g., a main camera and a depth sensing camera) or even a triple, quadruple or quintuple rear-facing camera configuration on the front and rear sides of the client device 102. For example, these multiple camera systems may include a wide-angle camera, an ultra-wide-angle camera, a tele camera, a macro camera, and a depth sensor.

The position part 1036 includes: a positioning sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects barometric pressure from which altitude may be derived), an orientation sensor component (e.g., a magnetometer), and so forth.

Communication may be implemented using a variety of techniques. The I/O component 1002 also includes a communication component 1038, the communication component 1038 being operable to couple the machine 1000 to the network 1022 or the device 1024 via a corresponding coupling or connection. For example, communication components 1038 may include a network interface component for interfacing with network 1022 or another suitable device. In a further example of this embodiment, the method comprises, the communication means 1038 may include wired communication means, wireless communication means cellular communication component, near Field Communication (NFC) component,Parts (e.g.)>Low energy consumption),>components, and other communication components that provide communication via other modalities. Device 1024 may be another machine or any of a variety of peripheral devices (e.g., a peripheral device coupled via USB).

Further, communication component 1038 can detect an identifier or include components operable to detect an identifier. For example, the communication component 1038 may include a Radio Frequency Identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., for detecting one-dimensional barcodes such as Universal Product Code (UPC) barcodes, one-dimensional barcodes such as Quick Response (QR) codes, aztec codes, data matrices, data symbols (Dataglyph), maximum codes (MaxiCode), PDF41 7. Ultra Code (Ultra Code), multi-dimensional bar codes of UCC RSS-2D bar codes and optical sensors of other optical codes) or acoustic detection means (e.g. a microphone for identifying the marked audio signal). In addition, various information may be obtained via the communication component 1038, such as a position fix obtained via Internet Protocol (IP) geolocation, viaSignal triangulation derived location, NFC beacon signal derived location via detection that may indicate a particular location, etc.

The various memories (e.g., main memory 1014, static memory 1016, and memory of processor 1004) and storage unit 1018 may store one or more sets of instructions and data structures (e.g., software) embodied or used by any one or more of the methods or functions described herein. These instructions (e.g., instructions 1010), when executed by the processor 1004, cause various operations to implement the disclosed examples.

The instructions 1010 may be transmitted or received over the network 1022 via a network interface device (e.g., a network interface component included in the communication component 1038) using a transmission medium and using any one of a number of well-known transmission protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions 1010 may be transmitted or received via a coupling (e.g., peer-to-peer coupling) to a device 1024 using a transmission medium.

Fig. 11 is a block diagram 1100 illustrating a software architecture 1104 that may be installed on any one or more of the devices described herein. The software architecture 1104 is supported by hardware such as a machine 1102 that includes a processor 1120, memory 1126 and I/O components 1138. In this example, the software architecture 1104 may be conceptualized as a stack of layers, with each layer providing a particular function. The software architecture 1104 includes layers such as an operating system 1112, libraries 1110, frameworks 1108, and applications 1106. In operation, the application 1106 activates an API call 1150 through the software stack and receives a message 1152 in response to the API call 1150.

Operating system 1112 manages hardware resources and provides common services. Operating system 1112 includes, for example: a kernel 1114, services 1116 and drivers 1122. The kernel 1114 acts as an abstraction layer between the hardware layer and other software layers. For example, the kernel 1114 provides memory management, processor management (e.g., scheduling), component management, networking, and security settings, among other functions. Service 1116 may provide other common services for other software layers. The driver 1122 is responsible for controlling or interfacing with the underlying hardware. For example, the driver 1122 may include a display driver, an imaging device driver, Or (b)Low power drives, flash drives, serial communication drives (e.g., USB driver),Drivers, audio drivers, power management drivers, etc.

Library 1110 provides a common low-level infrastructure used by applications 1106. The library 1110 may include a system library 1118 (e.g., a C-standard library), the system library 1118 providing functions such as memory allocation functions, string manipulation functions, mathematical functions, and the like. In addition, libraries 1110 may include API libraries 1124, such as media libraries (e.g., libraries for supporting presentation and manipulation of various media formats, such as moving Picture experts group 4 (MPEG 4), advanced video coding (H.264 or AVC), moving Picture experts group layer 3 (MP 3), advanced Audio Coding (AAC), adaptive Multi-Rate (AMR) audio codec, joint Picture experts group (JPEG or JPG) or Portable Network Graphics (PNG)), graphics libraries (e.g., openGL framework for presentation in two-dimensional (2D) and three-dimensional (3D) in graphical content on a display), database libraries (e.g., SQLite providing various relational database functions), web libraries (e.g., webKit providing Web browsing functions), and the like. The library 1110 may also include various other libraries 1128 to provide many other APIs to the application 1106.

Framework 1108 provides a common high-level infrastructure used by applications 1106. For example, framework 1108 provides various Graphical User Interface (GUI) functions, advanced resource management, and advanced location services. Framework 1108 can provide a wide range of other APIs that can be used by applications 1106, some of which can be specific to a particular operating system or platform.

In an example, applications 1106 can include a home application 1136, a contacts application 1130, a browser application 1132, a book reader application 1134, a positioning application 1142, a media application 1144, a messaging application 1246, a gaming application 1248, and a variety of other applications such as a third party application 1140. The application 1106 is a program that performs the functions defined in the program. One or more of the applications 1106 that are variously structured may be created using a variety of programming languages, such as an object oriented programming language (e.g., objective-C, java or C++) or a procedural programming language (e.g., C-language or assembly language). In a particular example, third party application 1140 (e.g., using ANDROID by an entity other than the vendor of the particular platform ^TM Or IOS ^TM Applications developed in Software Development Kits (SDKs) may be, for example, in IOS ^TM 、ANDROID ^TM 、The Phone's mobile operating system or other mobile software running on the mobile operating system. In this example, third party application 1140 may activate an API call 1150 provided by operating system 1112 to facilitate the functionality described herein.

Glossary of terms

"carrier signal" refers to any intangible medium capable of storing, encoding or carrying instructions for execution by a machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such instructions. The instructions may be transmitted or received over a network using a transmission medium via a network interface device.

"client device" refers to any machine that interfaces with a communication network to obtain resources from one or more server systems or other client devices. The client device may be, but is not limited to, a mobile phone, desktop computer, laptop computer, portable Digital Assistant (PDA), smart phone, tablet computer, ultrabook, netbook, laptop computer, multiprocessor system, microprocessor-based or programmable consumer electronics, game console, set top box, or any other communication device that a user can use to access a network.

"communication network" refers to one or more portions of a network, the network 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 Virtual Private Network (VPN) Metropolitan Area Networks (MANs), the Internet, portions of the Public Switched Telephone Network (PSTN), plain Old Telephone Service (POTS) networks, cellular telephone networks, wireless networks, A network, another type of network, or a combination of two or more such networks. For example, the network or portion of the network may comprise a wireless network or 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 (1 xRTT), evolution data optimized (EVDO) technology, general Packet Radio Service (GPRS) technology, enhanced data rates for GSM evolution (EDGE) technology, third generation partnership project (3 GPP) including 3G, fourth generation wireless (4G) networks, universal Mobile Telecommunications System (UMTS), high Speed Packet Access (HSPA), worldwide Interoperability for Microwave Access (WiMAX), long Term Evolution (LTE) standards, other data transmission technologies defined by various standards setting organizations, other long distance protocols, or other data transmission technologies.

"component" refers to a device, physical entity, or logic having the following boundaries: the boundaries are defined by function or subroutine calls, branch points, APIs, or other techniques that provide for the partitioning or modularization of particular processing or control functions. The components may be combined with other components via their interfaces to perform machine processes. A component may be a packaged functional hardware unit designed for use with other components, as well as a portion of a program that typically performs a particular one of the relevant functions. The components may constitute software components (e.g., code embodied on a machine-readable medium) or hardware components. A "hardware component" is a tangible unit capable of performing certain operations and may be configured or arranged in some physical manner. In various examples, one or more computer systems (e.g., stand-alone computer systems, client computer systems, or server computer systems) or one or more hardware components of a computer system (e.g., processors or groups of processors) may be configured by software (e.g., an application or application part) as hardware components that operate to perform certain operations as described herein. The hardware components may also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component may include specialized circuitry or logic permanently configured to perform certain operations. The hardware component may be a special purpose processor such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). The hardware components may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, the hardware components may include software that is executed by a general purpose processor or other programmable processor. Once configured by such software, the hardware components become the specific machine (or specific component of a machine) that is uniquely customized to perform the configured functions, and are no longer general purpose processors. It will be appreciated that decisions for hardware components may be driven mechanically in dedicated and permanently configured circuitry or in circuitry that is temporarily configured (e.g., by software configuration) for cost and time considerations. Accordingly, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, i.e., an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering the example where hardware components are temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each of the hardware components at any one time. For example, where the hardware components include a general-purpose processor configured as a special-purpose processor by software, the general-purpose processor may be configured as different special-purpose processors (e.g., including different hardware components) at different times, respectively. The software configures one or more particular processors accordingly to constitute particular hardware components, for example, at one time, and to constitute different hardware components at different times. A hardware component may provide information to and receive information from other hardware components. Thus, the described hardware components may be considered to be communicatively coupled. Where multiple hardware components are present at the same time, communication may be achieved by signal transmission (e.g., through appropriate circuitry and buses) between or among two or more of the hardware components. In examples where multiple hardware components are configured or instantiated at different times, communication between such hardware components may be achieved, for example, by storing information in a memory structure accessible to the multiple hardware components and retrieving the information in the memory structure. For example, one hardware component may perform an operation and store the output of the operation in a memory device to which it is communicatively coupled. Additional hardware components may then access the memory device at a later time to retrieve and process the stored output. The hardware component may also initiate communication with an input device or an output device, and may operate on a resource (e.g., collection of information). Various operations of the example methods described herein may be performed, at least in part, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily configured or permanently configured, such a processor may constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refers to hardware components implemented using one or more processors. Similarly, the methods described herein may be implemented, at least in part, by processors, where a particular processor or processors are examples of hardware. For example, at least some of the operations of the method may be performed by one or more processors 1004 or processor-implemented components. In addition, one or more processors may also operate to support execution of related operations in a "cloud computing" environment or as a "software as a service" (SaaS). For example, at least some of the operations may be performed by a set of computers (as examples of machines including processors), where the operations are accessible via a network (e.g., the internet) and via one or more suitable interfaces (e.g., APIs). The performance of certain of the operations may be distributed among processors, not only residing within a single machine, but also deployed across multiple machines. In some examples, the processor or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other examples, the processor or processor-implemented components may be distributed across several geolocations.

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

"ephemeral message" refers to a message that can be accessed for a limited duration of time. The transient message may be text, images, video, etc. The access time for the ephemeral message may be set by the message sender. Alternatively, the access time may be a default setting or a setting specified by the recipient. Regardless of the setup technique, the message is temporary.

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

"non-transitory computer-readable storage medium" refers to a tangible medium capable of storing, encoding or carrying instructions for execution by a machine.

"signal medium" refers to any intangible medium capable of storing, encoding, or carrying instructions for execution by a machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of software or data. The term "signal medium" shall be taken to include any form of modulated data signal, carrier wave, and the like. 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" mean the same and may be used interchangeably throughout this disclosure.

Claims (20)

1. A method, comprising:

displaying, by a messaging application running on the device, a capture user interface for capturing video according to a first camera mode for capturing a single video clip to generate a media content item;

providing, by the messaging application, a camera mode selection element within the capture user interface, the camera mode selection element selectable to switch from the first camera mode to a second camera mode for capturing a plurality of video clips for combining to generate the media content item;

Receiving, via the capture user interface, a user input selecting the camera mode selection element; and

updating, by the messaging application, the capture user interface for video capture according to the second camera mode in response to receiving the user input.

2. The method of claim 1, wherein the capture user interface comprises a capture button selectable to capture video.

3. The method of claim 2, wherein in the first camera mode, the capture button is selectable to capture the single video clip via a press and hold gesture, and

wherein in the first camera mode, the capture button is selectable to capture a picture via a tap gesture.

4. The method of claim 2, wherein in the second camera mode, the capture button is selectable to capture at least one of the plurality of video clips via a respective press and hold gesture.

5. The method of claim 2, wherein in the second camera mode, the capture button is selectable to capture at least one of the plurality of video clips via a respective first tap gesture for starting video capture and a respective second tap gesture for ending video capture.

6. The method of claim 1, wherein the updated capture user interface includes a preview button selectable to navigate to a preview user interface for previewing the plurality of captured video clips to generate the media content item.

7. The method of claim 1, wherein the updated capture user interface comprises a timeline progress bar configured to be updated in real-time based on a number of captured video clips and a length of each captured video clip.

8. The method of claim 7, wherein the timeline progress bar is configured to update in real-time based on a total length of all captured video clips exceeding a preset threshold.

9. A system, comprising:

a processor; and

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

displaying, by a messaging application running on the system, a capture user interface for capturing video according to a first camera mode for capturing a single video clip to generate a media content item;

Providing, by the messaging application, a camera mode selection element within the capture user interface, the camera mode selection element selectable to switch from the first camera mode to a second camera mode for capturing a plurality of video clips for combining to generate the media content item;

receiving, via the capture user interface, a user input selecting the camera mode selection element; and

updating, by the messaging application, the capture user interface for video capture according to the second camera mode in response to receiving the user input.

10. The system of claim 9, wherein the capture user interface includes a capture button selectable to capture video.

11. The system of claim 10, wherein in the first camera mode, the capture button is selectable to capture the single video clip via a press and hold gesture, and

wherein in the first camera mode, the capture button is selectable to capture a picture via a tap gesture.

12. The system of claim 10, wherein in the second camera mode, the capture button is selectable to capture at least one of the plurality of video clips via a respective press and hold gesture.

13. The system of claim 10, wherein in the second camera mode, the capture button is selectable to capture at least one of the plurality of video clips via a respective first tap gesture for starting video capture and a respective second tap gesture for ending video capture.

14. The system of claim 9, wherein the updated capture user interface includes a preview button selectable to navigate to a preview user interface for previewing the plurality of captured video clips to generate the media content item.

15. The system of claim 9, wherein the updated capture user interface comprises a timeline progress bar configured to be updated in real-time based on a number of captured video clips and a length of each captured video clip.

16. The system of claim 15, wherein the timeline progress bar is configured to update in real-time based on a total length of all captured video clips exceeding a preset threshold.

17. A non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to perform operations comprising:

displaying, by a messaging application running on the device, a capture user interface for capturing video according to a first camera mode for capturing a single video clip to generate a media content item;

providing, by the messaging application, a camera mode selection element within the capture user interface, the camera mode selection element selectable to switch from the first camera mode to a second camera mode for capturing a plurality of video clips for combining to generate the media content item;

receiving, via the capture user interface, a user input selecting the camera mode selection element; and

updating, by the messaging application, the capture user interface for video capture according to the second camera mode in response to receiving the user input.

18. The computer-readable medium of claim 17, wherein the capture user interface comprises a capture button selectable to capture video.

19. The computer readable medium of claim 18, wherein in the first camera mode, the capture button is selectable to capture the single video clip via a press and hold gesture, and

wherein in the first camera mode, the capture button is selectable to capture a picture via a tap gesture.

20. The computer readable medium of claim 18, wherein in the second camera mode, the capture button is selectable to capture at least one of the plurality of video clips via a respective press and hold gesture.