# Patent

## Title
Navigating through augmented reality content

## Abstract

Aspects of the present disclosure involve a system comprising a computer-readable storage medium storing a program and method for displaying augmented reality content. The program and method provide for displaying a carousel interface comprising multiple icons, each icon corresponding to a respective one of a plurality of augmented reality content items for displaying with an image captured by a device camera; receiving user input to navigate through display of the plurality of augmented reality content items while displaying the image; and in a case where the user input corresponds to a predefined type of gesture, navigating through display of the plurality of augmented reality content items while displaying the image, and omitting display of the carousel interface.

## Background
CLAIM OF PRIORITY
This application is a continuation of U.S. application Ser. No. 17/199,808, filed Mar. 12, 2021, which application claims the benefit of priority to U.S. Provisional Application Ser. No. 63/000,060, filed on Mar. 26, 2020, which is incorporated herein by reference in its entirety.


TECHNICAL FIELD
The present disclosure relates generally to messaging applications, including providing display of augmented reality content within a messaging application.
BACKGROUND
Messaging systems provide for the exchange of message content between users. For example, a messaging system allows a user to exchange message content (e.g., text, images) with one or more other users.



BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.
FIG. 1 is a diagrammatic representation of a networked environment in which the present disclosure may be deployed, in accordance with some example embodiments.
FIG. 2 is a diagrammatic representation of a messaging client application, in accordance with some example embodiments.
FIG. 3 is a diagrammatic representation of a data structure as maintained in a database, in accordance with some example embodiments.
FIG. 4 is a diagrammatic representation of a message, in accordance with some example embodiments.
FIG. 5 is a flowchart for an access-limiting process, in accordance with some example embodiments.
FIG. 6 is an interaction diagram illustrating a process for navigating through the display of augmented reality content items, in accordance with some example embodiments.
FIGS. 7A-7C illustrate user interface for navigating through the display of augmented reality content items based on user input corresponding to a first gesture type, in accordance with some example embodiments.
FIGS. 8A-8B illustrate a user interface for navigating through the display of augmented reality content items based on user input corresponding to a second gesture type, in accordance with some example embodiments.
FIG. 9 is a flowchart illustrating a process for navigating through the display of augmented reality content items, in accordance with some example embodiments.
FIG. 10 is block diagram showing a software architecture within which the present disclosure may be implemented, in accordance with some example embodiments.
FIG. 11 is a diagrammatic representation of a machine, in the form of a computer system within which a set of instructions may be executed for causing the machine to perform any one or more of the methodologies discussed, in accordance with some example embodiments.



DETAILED DESCRIPTION
A messaging system typically allow users to exchange content items (e.g., messages, images and/or video) with one another in a message thread. A messaging system may implement or otherwise work in conjunction with an augmented reality system to display augmented reality content with respect to messaging. For example, the augmented reality content is combined with image data captured by a device camera in creating message content. However, a user may wish for facilitated selection of augmented reality content with respect to messaging.
The disclosed embodiments provide for a messaging application running on a device to navigate through augmented reality content items (e.g., corresponding to applying Lenses or augmented reality experiences) while displaying image data captured by a device camera. For example, the messaging application displays a carousel interface with icons for selecting among available augmented reality content items. The messaging application is configured to receive user input of a first type (e.g., a drag gesture), indicating to quickly navigate between the augmented reality content items. In response, the messaging application discontinues displaying the carousel interface (e.g., by replacing it with a sliding interface), and provides for more quickly navigating through the augmented reality content items while continuing to display the image data captured by the device camera.
Alternatively or in addition, the messaging application is configured to receive user input of a second type (e.g., a swipe gesture) indicating to more slowly navigate between the augmented reality content items. In response, the messaging application provides for more slowly (e.g., iteratively) navigating through the augmented reality content items while continuing to display the captured image data and continuing to display the carousel interface.
FIG. 1 is a block diagram showing an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network 106. The messaging system 100 includes instances of a client device 102, each of which hosts a number of applications, including a messaging client application 104. Each messaging client application 104 is communicatively coupled to other instances of the messaging client application 104 and a messaging server system 110 via a network 106 (e.g., the Internet).
A messaging client application 104 is able to communicate and exchange data with another messaging client application 104 and with the messaging server system 110 via the network 106. The data exchanged between the messaging client application 104, and between the other messaging client application 104 and the messaging server system 110, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video or other multimedia data).
In some embodiments, the messaging client application 104 activates a camera of the client device 102 (e.g., upon startup of the messaging client application 104). The messaging client application 104 allows a user to request to scan one or more items in a camera feed captured by the camera. For example, the messaging client application 104 may receive a user selection of a dedicated scan option (e.g., a button) presented together with the camera feed. In an alternative embodiment, the messaging client application 104 may detect physical contact between a finger of the user's hand and a region of the touch screen for a threshold period of time. For example, the messaging client application 104 determines that the user touched and held their finger on the screen for more than three seconds. In response, the messaging client application 104 captures an image being displayed on the screen and processes the image to identify one or more objects in the image. In some embodiments, the messaging client application 104 uses one or more trained classifiers and/or environmental factors to identify the objects in the image.
The messaging server system 110 provides server-side functionality via the network 106 to a particular messaging client application 104. While certain functions of the messaging system 100 are described herein as being performed by either the messaging client application 104 or by the messaging server system 110, it will be appreciated that the location of certain functionality either within the messaging client application 104 or the messaging server system 110 is a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the messaging server system 110, but to later migrate this technology and functionality to the messaging client application 104 where a client device 102 has a sufficient processing capacity.
The messaging server system 110 supports various services and operations that are provided to the messaging client application 104. Such operations include transmitting data to, receiving data from, and processing data generated by the messaging client application 104. This data may include message content, client device information, graphical elements, geolocation information, media annotation and overlays, virtual objects, message content persistence conditions, social network information, and live event information, as examples. Data exchanges within the messaging system 100 are invoked and controlled through functions available via user interfaces (UIs) (e.g., graphical user interfaces) of the messaging client application 104.
Turning now specifically to the messaging server system 110, an API server 108 (application programming interface server) is coupled to, and provides a programmatic interface to, an application server 112. The application server 112 is communicatively coupled to a database server 116, which facilitates access to a database 122 in which is stored data associated with messages processed by the application server 112.
Dealing specifically with the API server 108, this server receives and transmits message data (e.g., commands and message payloads) between the client device 102 and the application server 112. Specifically, the API server 108 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client application 104 in order to invoke functionality of the application server 112. The API server 108 exposes various functions supported by the application server 112, including account registration: login functionality; the sending of messages, via the application server 112, from a particular messaging client application 104 to another messaging client application 104: the sending of media files (e.g., graphical elements, images or video) from the messaging client application 104 to the messaging server application 114, and for possible access by another messaging client application 104; a graphical element list; the setting of a collection of media data (e.g., a Story); the retrieval of such collections; the retrieval of a list of friends of a user of a client device 102; maintaining augmented reality content items; the retrieval of messages and content; the adding and deleting of friends to a social graph; the location of friends within a social graph; access to user conversation data; access to avatar information stored on messaging server system 110; and opening an application event (e.g., relating to the messaging client application 104).
The application server 112 hosts a number of applications and subsystems, including a messaging server application 114, an image processing system 118, a social network system 120, and an augmented reality system 124. The messaging server application 114 implements a number of message processing technologies and functions, particularly related to the aggregation and other processing of content (e.g., textual and multimedia content) included in messages received from multiple instances of the messaging client application 104. As will be described in further detail, the text and media content from multiple sources may be aggregated into collections of content (e.g., called Stories or galleries). These collections are then made available, by the messaging server application 114, to the messaging client application 104. Other processor- and memory-intensive processing of data may also be performed server-side by the messaging server application 114, in view of the hardware requirements for such processing.
The application server 112 also includes an image processing system 118 that is dedicated to performing various image processing operations, typically with respect to images or video received within the payload of a message at the messaging server application 114. In one or more implementations, a portion of the image processing system 118 may also be implemented by the augmented reality system 124.
The social network system 120 supports various social networking functions and services and makes these functions and services available to the messaging server application 114. To this end, the social network system 120 maintains and accesses an entity graph within the database 122. Examples of functions and services supported by the social network system 120 include the identification of other users of the messaging system 100 with which a particular user has relationships or is “following” and also the identification of other entities and interests of a particular user. Such other users may be referred to as the user's friends. The social network system 120 may access location information associated with each of the user's friends to determine where they live or are currently located geographically. The social network system 120 may maintain a location profile for each of the user's friends indicating the geographical location where the user's friends live.
The messaging client application 104 includes a set of functions that allows the client device 102 to access the augmented reality system 124. The augmented reality system 124 generates and maintains a list of augmented reality content items. The augmented reality content items may correspond to augmented reality experiences for supplementing captured image data with augmented reality content.
In one or more embodiments, the augmented reality system 124 provides for determining (e.g., receives) one or more attributes (e.g., a name) of an object. The augmented reality system 124 provides for searching for one or more augmented reality content items (e.g., virtual objects) that are associated with the one or more attributes of the object, and for ranking the virtual objects (e.g., based on the associations and weights assigned to each of the attributes). The augmented reality system 124 causes one or more virtual objects or graphical elements of the highest ranked augmented reality content item to be presented on top of the captured image.
The application server 112 is communicatively coupled to a database server 116, which facilitates access to a database 122, in which is stored data associated with messages processed by the messaging server application 114. The database 122 may be a third-party database. For example, the application server 112 may be associated with a first entity, and the database 122 or a portion of the database 122 may be associated and hosted by a second different entity. In some embodiments, the database 122 stores user data that the first entity collects about various each of the users of a service provided by the first entity. For example, the user data includes user names, phone numbers, passwords, addresses, friends, activity information, preferences, videos or content consumed by the user, and so forth.
FIG. 2 is block diagram illustrating further details regarding the messaging system 100, according to example embodiments. Specifically, the messaging system 100 is shown to comprise the messaging client application 104 and the application server 112, which in turn embody a number of some subsystems, namely an ephemeral timer system 202, a collection management system 204 and an annotation system 206.
The ephemeral timer system 202 is responsible for enforcing the temporary access to content permitted by the messaging client application 104 and the messaging server application 114. To this end, the ephemeral timer system 202 incorporates a number of timers that, based on duration and display parameters associated with a message, or collection of messages (e.g., a Story), selectively display and enable access to messages and associated content via the messaging client application 104. Further details regarding the operation of the ephemeral timer system 202 are provided below.
The collection management system 204 is responsible for managing collections of media (e.g., collections of text, image video and audio data). In some examples, a collection of content (e.g., messages, including images, video, text and audio) may be organized into an “event gallery” or an “event Story.” Such a collection may be made available for a specified time period, such as the duration of an event to which the content relates. For example, content relating to a music concert may be made available as a “Story” for the duration of that music concert. The collection management system 204 may also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the messaging client application 104.
The collection management system 204 furthermore includes a curation interface 208 that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface 208 enables an event organizer to curate a collection of content relating to a specific event (e.g., delete inappropriate content or redundant messages). Additionally, the collection management system 204 employs machine vision (or image recognition technology) and content rules to automatically curate a content collection. In certain embodiments, compensation may be paid to a user for inclusion of user-generated content into a collection. In such cases, the curation interface 208 operates to automatically make payments to such users for the use of their content.
The annotation system 206 provides various functions that enable a user to annotate or otherwise modify or edit media content associated with a message. For example, the annotation system 206 provides functions related to the generation and publishing of media overlays for messages processed by the messaging system 100. The annotation system 206 operatively supplies a media overlay or supplementation (e.g., an image filter) to the messaging client application 104 based on a geolocation of the client device 102. In another example, the annotation system 206 operatively supplies a media overlay to the messaging client application 104 based on other information, such as social network information of the user of the client device 102. A media overlay may include audio and visual content and visual effects. Examples of audio and visual content include pictures, texts, logos, animations, and sound effects. An example of a visual effect includes color overlaying. The audio and visual content or the visual effects can be applied to a content item (e.g., a photo) at the client device 102. For example, the media overlay may include text that can be overlaid on top of a photograph taken by the client device 102. In another example, the media overlay includes an identification of a location overlay (e.g., Venice beach), a name of a live event, or a name of a merchant overlay (e.g., Beach Coffee House). In another example, the annotation system 206 uses the geolocation of the client device 102 to identify a media overlay that includes the name of a merchant at the geolocation of the client device 102. The media overlay may include other indicia associated with the merchant. The media overlays may be stored in the database 122 and accessed through the database server 116.
In one example embodiment, the annotation system 206 provides a user-based publication platform that enables users to select a geolocation on a map, and upload content associated with the selected geolocation. The user may also specify circumstances under which a particular media overlay should be offered to other users. The annotation system 206 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.
In another example embodiment, the annotation system 206 provides a merchant-based publication platform that enables merchants to select a particular media overlay associated with a geolocation via a bidding process. For example, the annotation system 206 associates the media overlay of a highest bidding merchant with a corresponding geolocation for a predefined amount of time.
FIG. 3 is a schematic diagram illustrating data structures 300 which may be stored in the database 122 of the messaging server system 110, according to certain example embodiments. While the content of the database 122 is shown to comprise a number of tables, it will be appreciated that the data could be stored in other types of data structures (e.g., as an object-oriented database).
The database 122 includes message data stored within a message table 314. An entity table 302 stores entity data, including an entity graph 304. Entities for which records are maintained within the entity table 302 may include individuals, corporate entities, organizations, objects, places, events, and so forth. Regardless of type, any entity regarding which the messaging server system 110 stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).
The entity graph 304 stores information regarding relationships and associations between entities. Such relationships may be social, professional (e.g., work at a common corporation or organization), interest-based, or activity-based, merely for example.
The message table 314 may store a collection of conversations between a user and one or more friends or entities. The message table 314 may include various attributes of each conversation, such as the list of participants, the size of the conversation (e.g., number of users and/or number of messages), the chat color of the conversation, a unique identifier for the conversation, and any other conversation related feature(s).
The database 122 also stores annotation data, in the example form of filters, in an annotation table 312. The database 122 also stores annotated content received in the annotation table 312. Filters for which data is stored within the annotation table 312 are associated with and applied to videos (for which data is stored in a video table 310) and/or images (for which data is stored in an image table 308). Filters, in one example, are overlays that are displayed as overlaid on an image or video during presentation to a recipient user. Filters may be of various types, including user-selected filters from a gallery of filters presented to a sending user by the messaging client application 104 when the sending user is composing a message. Other types of filters include geolocation filters (also known as geo-filters), which may be presented to a sending user based on geographic location. For example, geolocation filters specific to a neighborhood or special location may be presented within a UI by the messaging client application 104, based on geolocation information determined by a Global Positioning System (GPS) unit of the client device 102. Another type of filter is a data filter, which may be selectively presented to a sending user by the messaging client application 104, based on other inputs or information gathered by the client device 102 during the message creation process. Examples of data filters include current temperature at a specific location, a current speed at which a sending user is traveling, battery life for a client device 102, or the current time.
Other annotation data that may be stored within the image table 308 are augmented reality content items (e.g., corresponding to applying Lenses or augmented reality experiences). An augmented reality content item may be a real-time special effect and sound that may be added to an image or a video.
As described above, augmented reality content items, overlays, image transformations, AR images and similar terms refer to modifications that may be made to videos or images. This includes real-time modification which modifies an image as it is captured using a device sensor and then displayed on a screen of the device with the modifications. This also includes modifications to stored content, such as video clips in a gallery that may be modified. For example, in a device with access to multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to see how the different augmented reality content items will modify the stored clip. For example, multiple augmented reality content items that apply different pseudorandom movement models can be applied to the same content by selecting different augmented reality content items for the content. Similarly, real-time video capture may be used with an illustrated modification to show how video images currently being captured by sensors of a device would modify the captured data. Such data may simply be displayed on the screen and not stored in memory, or the content captured by the device sensors may be recorded and stored in memory with or without the modifications (or both). In some systems, a preview feature can show how different augmented reality content items will look within different windows in a display at the same time. This can, for example, enable multiple windows with different pseudorandom animations to be viewed on a display at the same time.
Data and various systems using augmented reality content items or other such transform systems to modify content using this data can thus involve detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.), tracking of such objects as they leave, enter, and move around the field of view in video frames, and the modification or transformation of such objects as they are tracked. In various embodiments, different methods for achieving such transformations may be used. For example, some embodiments may involve generating a three-dimensional mesh model of the object or objects, and using transformations and animated textures of the model within the video to achieve the transformation. In other embodiments, 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 position. In still further embodiments, neural network analysis of video frames may be used to place images, models, or textures in content (e.g., images or frames of video). An augmented reality content items thus refer both to the images, models, and textures used to create transformations in content, as well as to additional modeling and analysis information needed to achieve such transformations with object detection, tracking, and placement.
Real-time video processing can be performed with any kind of video data (e.g., video streams, video files, etc.) saved in a memory of a computerized system of any kind. For example, a user can load video files and save them in a memory of a device, or can generate a video stream using sensors of the device. Additionally, any objects can be processed using a computer animation model, such as a human's face and parts of a human body, animals, or non-living things such as chairs, cars, or other objects.
In some embodiments, when a particular modification is selected along with content to be transformed, elements to be transformed are identified by the computing device, and then detected and tracked if they are present in the frames of the video. The elements of the object are modified according to the request for modification, thus transforming the frames of the video stream. Transformation of frames of a video stream can be performed by different methods for different kinds of transformation. For example, for transformations of frames mostly referring to changing forms of object's elements characteristic points for each of element of an object are calculated (e.g., using an Active Shape Model (ASM) or other known methods). Then, a mesh based on the characteristic points is generated for each of the at least one element of the object. This mesh used in the following stage of tracking the elements of the object in the video stream. In the process of tracking, the mentioned mesh for each element is aligned with a position of each element. Then, additional points are generated on the mesh. A first set of first points is generated for each element based on a request for modification, and a set of second points is generated for each element based on the set of first points and the request for modification. Then, the frames of the video stream can be transformed by modifying the elements of the object on the basis of the sets of first and second points and the mesh. In such method, a background of the modified object can be changed or distorted as well by tracking and modifying the background.
In one or more embodiments, transformations changing some areas of an object using its elements can be performed by calculating of characteristic points for each element of an object and generating a mesh based on the calculated characteristic points. Points are generated on the mesh, and then various areas based on the points are generated. The elements of the object are then tracked by aligning the area for each element with a position for each of the at least one element, and properties of the areas can be modified based on the request for modification, thus transforming the frames of the video stream. Depending on the specific request for modification properties of the mentioned areas can be transformed in different ways. Such modifications may involve: changing color of areas; removing at least some part of areas from the frames of the video stream; including one or more new objects into areas which are based on a request for modification; and modifying or distorting the elements of an area or object. In various embodiments, any combination of such modifications or other similar modifications may be used. For certain models to be animated, some characteristic points can be selected as control points to be used in determining the entire state-space of options for the model animation.
In some embodiments of a computer animation model to transform image data using face detection, the face is detected on an image with use of a specific face detection (e.g., Viola-Jones). Then, an Active Shape Model (ASM) algorithm is applied to the face region of an image to detect facial feature reference points.
In other embodiments, other methods and algorithms suitable for face and/or object detection can be used. For example, in some embodiments, features are located using a landmark which represents a distinguishable point present in most of the images under consideration. For facial landmarks, for example, the location of the left eye pupil may be used. In an initial landmark is not identifiable (e.g., if a person has an eyepatch), secondary landmarks may be used. Such landmark identification procedures may be used for any such objects. In some embodiments, a set of landmarks forms a shape. Shapes can be represented as vectors using the coordinates of the points in the shape. One shape is aligned to another with a similarity transform (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between shape points. The mean shape is the mean of the aligned training shapes.
In some embodiments, a search for landmarks from the mean shape aligned to the position and size of the face determined by a global face detector is started. Such a search then repeats the steps of suggesting a tentative shape by adjusting the locations of shape points by template matching of the image texture around each point and then conforming the tentative shape to a global shape model until convergence occurs. In some systems, individual template matches are unreliable and the shape model pools the results of the weak template matchers to form a stronger overall classifier. The entire search is repeated at each level in an image pyramid, from coarse to fine resolution.
Embodiments of a transformation system can capture an image or video stream on a client device (e.g., the client device 102) and perform complex image manipulations locally on the client device 102 while maintaining a suitable user experience, computation time, and power consumption. The complex image manipulations may include size and shape changes, emotion transfers (e.g., changing a face from a frown to a smile), state transfers (e.g., aging a subject, reducing apparent age, changing gender), style transfers, graphical element application, and any other suitable image or video manipulation implemented by a convolutional neural network that has been configured to execute efficiently on the client device 102.
In some example embodiments, a computer animation model to transform image data can be used by a system where a user may capture an image or video stream of the user (e.g., a selfie) using a client device 102 having a neural network operating as part of a messaging client application 104 operating on the client device 102. The transform system operating within the messaging client application 104 determines the presence of an object (e.g., a face) within the image or video stream and provides modification icons associated with a computer animation model to transform image data, or the computer animation model can be present as associated with an interface described herein. The modification icons include changes which may be the basis for modifying the user's face within the image or video stream as part of the modification operation. Once a modification icon is selected, the transform system initiates a process to convert the image of the user to reflect the selected modification icon (e.g., generate a smiling face on the user). In some embodiments, a modified image or video stream may be presented in a graphical user interface displayed on the mobile client device as soon as the image or video stream is captured and a specified modification is selected. The transform system may implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, the user may capture the image or video stream and be presented with a modified result in real time or near real time once a modification icon has been selected. Further, the modification may be persistent while the video stream is being captured and the selected modification icon remains toggled. Machine taught neural networks may be used to enable such modifications.
In some embodiments, the graphical user interface, presenting the modification performed by the transform system, may supply the user with additional interaction options. Such options may be based on the interface used to initiate the content capture and selection of a particular computer animation model (e.g., initiation from a content creator user interface). In various embodiments, a modification may be persistent after an initial selection of a modification icon. The user may toggle the modification on or off by tapping or otherwise selecting the face being modified by the transformation system and store it for later viewing or browse to other areas of the imaging application. Where multiple faces are modified by the transformation system, the user may toggle the modification on or off globally by tapping or selecting a single face modified and displayed within a graphical user interface. In some embodiments, individual faces, among a group of multiple faces, may be individually modified or such modifications may be individually toggled by tapping or selecting the individual face or a series of individual faces displayed within the graphical user interface.
As mentioned above, the video table 310 stores video data which, in one embodiment, is associated with messages for which records are maintained within the message table 314. Similarly, the image table 308 stores image data associated with messages for which message data is stored in the entity table 302. The entity table 302 may associate various annotations from the annotation table 312 with various images and videos stored in the image table 308 and the video table 310.
The augmented reality content items table 316 stores an indication (e.g., a list) of augmented reality content items available for selection and activation by the messaging client application 104. In one or more embodiments, each augmented reality content item in the augmented reality content items table 316 is associated with one or more object attributes. Each augmented reality content item in the augmented reality content items table 316 may also be associated with one or more predefined words (e.g., using metadata labels, designations, and the like). In one or more embodiments, the messaging client application 104 searches the object attributes and/or predefined words stored in the augmented reality content items table 316 to identify one or more augmented reality content items associated with a scanned object or an object identified in a captured image. Each augmented reality content item stored in the augmented reality content items table 316 includes one or more graphical elements or virtual objects which may or may not be animated. Each augmented reality content item also includes instructions on where to position the graphical elements or virtual objects relative to other objects depicted in the captured image.
A story table 306 stores data regarding collections of messages and associated image, video, or audio data, which are compiled into a collection (e.g., a Story or a gallery). The creation of a particular collection may be initiated by a particular user (e.g., each user for which a record is maintained in the entity table 302). A user may create a “personal Story” in the form of a collection of content that has been created and sent/broadcast by that user. To this end, the UI of the messaging client application 104 may include an icon that is user-selectable to enable a sending user to add specific content to his or her personal Story.
A collection may also constitute a “live Story,” which is a collection of content from multiple users that is created manually, automatically, or using a combination of manual and automatic techniques. For example, a “live Story” may constitute a curated stream of user-submitted content from various locations and events. Users whose client devices have location services enabled and are at a common location event at a particular time may, for example, be presented with an option, via a UI of the messaging client application 104, to contribute content to a particular live Story. The live Story may be identified to the user by the messaging client application 104 based on his or her location. The end result is a “live Story” told from a community perspective.
A further type of content collection is known as a “location Story,” which enables a user whose client device 102 is located within a specific geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some embodiments, a contribution to a location Story may require a second degree of authentication to verify that the end user belongs to a specific organization or other entity (e.g., is a student on the university campus).
FIG. 4 is a schematic diagram illustrating a structure of a message 400, according to some embodiments, generated by a messaging client application 104 for communication to a further messaging client application 104 or the messaging server application 114. The content of a particular message 400 is used to populate the message table 314 stored within the database 122, accessible by the messaging server application 114. Similarly, the content of a message 400 is stored in memory as “in-transit” or “in-flight” data of the client device 102 or the application server 112. The message 400 is shown to include the following components:

    
    
        A message identifier 402: a unique identifier that identifies the message 400.
        A message text payload 404: text, to be generated by a user via a user interface of the client device 102 and that is included in the message 400.
        A message image payload 406: image data, captured by a camera component of a client device 102 or retrieved from a memory component of a client device 102, and that is included in the message 400.
        A message video payload 408: video data, captured by a camera component or retrieved from a memory component of the client device 102 and that is included in the message 400.
        A message audio payload 410: audio data, captured by a microphone or retrieved from a memory component of the client device 102, and that is included in the message 400.
        Message annotations 412: annotation data (e.g., filters, stickers or other enhancements) that represents annotations to be applied to message image payload 406, message video payload 408, or message audio payload 410 of the message 400.
        A message duration parameter 414: parameter value indicating, in seconds, the amount of time for which content of the message (e.g., the message image payload 406, message video payload 408, message audio payload 410) is to be presented or made accessible to a user via the messaging client application 104.
        A message geolocation parameter 416: geolocation data (e.g., latitudinal and longitudinal coordinates) associated with the content payload of the message. Multiple message geolocation parameter 416 values may be included in the payload, each of these parameter values being associated with respect to content items included in the content (e.g., a specific image within the message image payload 406, or a specific video in the message video payload 408).
        A message story identifier 418: identifier values identifying one or more content collections (e.g., “Stories”) with which a particular content item in the message image payload 406 of the message 400 is associated. For example, multiple images within the message image payload 406 may each be associated with multiple content collections using identifier values.
        A message tag 420: each message 400 may be tagged with multiple tags, each of which is indicative of the subject matter of content included in the message payload. For example, where a particular image included in the message image payload 406 depicts an animal (e.g., a lion), a tag value may be included within the message tag 420 that is indicative of the relevant animal. Tag values may be generated manually, based on user input, or may be automatically generated using, for example, image recognition.
        A message sender identifier 422: an identifier (e.g., a messaging system identifier, email address, or device identifier) indicative of a user of the client device 102 on which the message 400 was generated and from which the message 400 was sent.
        A message receiver identifier 424: an identifier (e.g., a messaging system identifier, email address, or device identifier) indicative of a 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 tables within which content data values are stored. For example, an image value in the message image payload 406 may be a pointer to (or address of) a location within an image table 308. Similarly, values within the message video payload 408 may point to data stored within a video table 310, values stored within the message annotations 412 may point to data stored in an annotation table 312, values stored within the message story identifier 418 may point to data stored in a story table 306, and values stored within the message sender identifier 422 and the message receiver identifier 424 may point to user records stored within an entity table 302.
FIG. 5 is a schematic diagram illustrating an access-limiting process 500, in terms of which access to content (e.g., an ephemeral message 502, and associated multimedia payload of data) or a content collection (e.g., an ephemeral message group 504) may be time-limited (e.g., made ephemeral).
An ephemeral message 502 is shown to be associated with a message duration parameter 506, the value of which determines an amount of time that the ephemeral message 502 will be displayed to a receiving user of the ephemeral message 502 by the messaging client application 104. In one embodiment, an ephemeral message 502 is viewable by a receiving user for up to a maximum of 10 seconds, depending on the amount of time that the sending user specifies using the message duration parameter 506.
The message duration parameter 506 and the message receiver identifier 424 are shown to be inputs to a message timer 512, which is responsible for determining the amount of time that the ephemeral message 502 is shown to a particular receiving user identified by the message receiver identifier 424. In particular, the ephemeral message 502 will only be shown to the relevant receiving user for a time period determined by the value of the message duration parameter 506. The message timer 512 is shown to provide output to a more generalized ephemeral timer system 202, which is responsible for the overall timing of display of content (e.g., an ephemeral message 502) to a receiving user.
The ephemeral message 502 is shown in FIG. 5 to be included within an ephemeral message group 504 (e.g., a collection of messages in a personal Story, or an event Story). The ephemeral message group 504 has an associated group duration parameter 508, a value of which determines a time-duration for which the ephemeral message group 504 is presented and accessible to users of the messaging system 100. The group duration parameter 508, for example, may be the duration of a music concert, where the ephemeral message group 504 is a collection of content pertaining to that concert. Alternatively, a user (either the owning user or a curator user) may specify the value for the group duration parameter 508 when performing the setup and creation of the ephemeral message group 504.
Additionally, each ephemeral message 502 within the ephemeral message group 504 has an associated group participation parameter 510, a value of which determines the duration of time for which the ephemeral message 502 will be accessible within the context of the ephemeral message group 504. Accordingly, a particular ephemeral message group 504 may “expire” and become inaccessible within the context of the ephemeral message group 504, prior to the ephemeral message group 504 itself expiring in terms of the group duration parameter 508. The group duration parameter 508, group participation parameter 510, and message receiver identifier 424 each provide input to a group timer 514 which operationally determines, firstly, whether a particular ephemeral message 502 of the ephemeral message group 504 will be displayed to a particular receiving user and, if so, for how long. Note that the ephemeral message group 504 is also aware of the identity of the particular receiving user as a result of the message receiver identifier 424.
Accordingly, the group timer 514 operationally controls the overall lifespan of an associated ephemeral message group 504, as well as an individual ephemeral message 502 included in the ephemeral message group 504. In one embodiment, each and every ephemeral message 502 within the ephemeral message group 504 remains viewable and accessible for a time-period specified by the group duration parameter 508. In a further embodiment, a certain ephemeral message 502 may expire, within the context of ephemeral message group 504, based on a group participation parameter 510. Note that a message duration parameter 506 may still determine the duration of time for which a particular ephemeral message 502 is displayed to a receiving user, even within the context of the ephemeral message group 504. Accordingly, the message duration parameter 506 determines the duration of time that a particular ephemeral message 502 is displayed to a receiving user, regardless of whether the receiving user is viewing that ephemeral message 502 inside or outside the context of an ephemeral message group 504.
The ephemeral timer system 202 may furthermore operationally remove a particular ephemeral message 502 from the ephemeral message group 504 based on a determination that it has exceeded an associated group participation parameter 510. For example, when a sending user has established a group participation parameter 510 of 24 hours from posting, the ephemeral timer system 202 will remove the relevant ephemeral message 502 from the ephemeral message group 504 after the specified 24 hours. The ephemeral timer system 202 also operates to remove an ephemeral message group 504 either when the group participation parameter 510 for each and every ephemeral message 502 within the ephemeral message group 504 has expired, or when the ephemeral message group 504 itself has expired in terms of the group duration parameter 508.
In certain use cases, a creator of a particular ephemeral message group 504 may specify an indefinite group duration parameter 508. In this case, the expiration of the group participation parameter 510 for the last remaining ephemeral message 502 within the ephemeral message group 504 will determine when the ephemeral message group 504 itself expires. In this case, a new ephemeral message 502, added to the ephemeral message group 504, with a new group participation parameter 510, effectively extends the life of an ephemeral message group 504 to equal the value of the group participation parameter 510.
Responsive to the ephemeral timer system 202 determining that an ephemeral message group 504 has expired (e.g., is no longer accessible), the ephemeral timer system 202 communicates with the messaging system 100 (and, for example, specifically the messaging client application 104) to cause an indicium (e.g., an icon) associated with the relevant ephemeral message group 504 to no longer be displayed within a user interface of the messaging client application 104. Similarly, when the ephemeral timer system 202 determines that the message duration parameter 506 for a particular ephemeral message 502 has expired, the ephemeral timer system 202 causes the messaging client application 104 to no longer display an indicium (e.g., an icon or textual identification) associated with the ephemeral message 502.
FIG. 6 is an interaction diagram illustrating a process 600 for navigating through the display of augmented reality content items (e.g., corresponding to augmented reality experiences), in accordance with some example embodiments. For explanatory purposes, the process 600 is primarily described herein with reference to the messaging client application 104 of the client device 102, and the messaging server system 110 of FIG. 1. However, one or more blocks (or operations) of the process 600 may be performed by one or more other components, and/or by other suitable devices. Further for explanatory purposes, the blocks of the process 600 are described herein as occurring in serial, or linearly. However, multiple blocks of the process 600 may occur in parallel. In addition, the blocks of the process 600 need not be performed in the order shown and/or one or more blocks of the process 600 need not be performed and/or can be replaced by other operations.
As described herein, the messaging client application 104 is configured to provide for navigating/scrolling through augmented reality content items (e.g., corresponding to augmented reality experiences). For example, the messaging client application 104 displays a carousel interface with icons for selecting from available augmented reality content items. The messaging client application 104 receives user input (e.g., a drag gesture) indicating to more quickly navigate between the augmented reality content items. In response, the messaging client application 104 discontinues displaying the carousel interface (e.g., by replacing it with a sliding interface), and provides for more quickly navigating through the augmented reality content items while continuing to display the image data captured by the device camera.
Thus, following start block 602, the messaging client application 104 displays image data captured by a camera of the client device 102 and a carousel interface (block 604). For example, the messaging client application 104 is configured to default to activating the camera when the messaging client application 104 is initialized. Alternatively or in addition, the messaging client application 104 automatically activates the camera for particular interfaces of the messaging client application 104, such as an interface for generating multimedia content (e.g., for including in a message). As noted, the carousel interface provides for selecting an augmented reality content item (e.g., or augmented reality experience) and/or switching between available augmented reality content items. The available augmented reality content items may be displayed in a ranked order within the carousel interface.
As noted above, the augmented reality system 124 included in the messaging server system 110 is configured to provide for ranking available augmented reality content items. For example, available augmented reality content items are ranked by comparing one or more attributes of object(s) detected in images with corresponding augmented reality content item attributes/words (e.g., as stored in the augmented reality content items table 316). Moreover, in case multiple augmented reality content items are available for a detected object (e.g., a user's face), augmented reality content items may be ranked based on one or more parameters such as preferences/history of augmented reality content items selected by the user, popularity of augmented reality content items among system users, newly-available augmented reality content items, and the like.
The messaging server system 110 may provide an indication of the ranking to the messaging client application 104. Based on the ranking, the messaging client application 104 may select a default augmented reality content item for applying to the captured image (e.g., to display augmented reality content with the image) and/or arrange the carousel interface icons (e.g., representing respective augmented reality content items) in ranked order.
The messaging client application 104 receives user input for navigating through available augmented reality content items (block 606). In one or more embodiments, the messaging client application 104 provides for a user to select to navigate through (e.g., scroll through) the available augmented reality content items of the carousel interface. As described herein, the user may select to navigate through augmented reality content items in different manners (e.g., at different speeds) based on different types of gestures.
In one or more implementations, the messaging client application 104 in conjunction with an operating system of the client device 102 (e.g., operating system 1012, discussed below) is configured to detect different types of user gestures with respect to user input. For example, the messaging client application 104 is configured to detect and distinguish between a swipe gesture and a drag gesture, each of which occurs when a finger is moved across the screen (e.g., in a horizontal or vertical direction).
In one or more implementations, the speed of finger movement across the screen is used to distinguish between a swipe gesture and a drag gesture. For example, a drag gesture is typically slower and more controlled than a swipe gesture. On the other hand, a swipe gesture is typically faster than a drag gesture. In one or more implementations, a drag gesture may continue to be detected/processed while the finger maintains contact with the screen, even when the user switches direction of finger movement across the screen (e.g., from the left-right direction to the right-left direction). On the other hand, the swipe gesture may simply be completed based a finger moving a threshold speed/distance on the screen.
Thus, at decision block 608, the messaging client application 104 determines whether the user input corresponds to a first type of gesture (e.g., the drag gesture). For example, the drag gesture (e.g., the more controlled and/or slow gesture) corresponds with user intent to more quickly navigate/scroll through the display of available augmented reality content items (e.g., while still displaying images captured by the device camera). Thus, the messaging client application 104 navigates through the augmented reality content items at a first speed (block 616), which is quicker than the second speed discussed below.
In one or more implementations, the quick navigation/scrolling through of augmented reality content items (e.g., augmented reality experiences) is effected by accessing representations of augmented reality content items in local memory of the client device 102, as opposed to remotely accessing augmented reality content item data from the messaging server system 110. For example, the local representations for augmented reality content items may correspond to one or more images for each augmented reality content item (e.g., and an order of the augmented reality content items), without necessarily including additional augmented reality content item data such as models, textures and/or other images for transforming image content. In one or more implementations, the locally-stored representations are accessed by the messaging client application 104 and locally stored prior to displaying the carousel interface (e.g., upon initialization of the messaging client application 104). By virtue of storing the local representations and order of the augmented reality content items, it is possible for the messaging client application 104 to more quickly navigate/scroll through the display of available augmented reality content items during the drag gesture. It is noted displaying the augmented reality content items in this manner may not correspond with fully applying the augmented reality content items, but instead with providing a quick preview of the augmented reality content item.
As noted above, a drag gesture continues to be detected when the user switches direction of finger movement across the screen. Thus, in one or more implementations, the messaging client application 104 provides for navigating/scrolling through the augmented reality content items in a manner that corresponds to the drag gesture movement. For example, the messaging client application 104 provides for adjusting the speed of navigating/scrolling through the augmented reality content items, to correlate with the speed of the finger movement across the device screen.
As discussed further below with respect to the example of FIGS. 7A-7B, the messaging client application 104 may be configured to omit display of the carousel interface during the drag gesture, and to display a sliding interface in lieu of the carousel interface. For example, the sliding interface may correspond to a line/bar element that indicates a position of a current augmented reality content item with respect to the ordered list of available augmented reality content items. The position may be indicated by an icon, presented on the line/bar element, that represents the current augmented reality content item. In this regard, the locally-stored representations of the augmented reality content items may further include the icon data for quick access by the messaging client application 104. Moreover, the locally-stored representations of the augmented reality content items may include a name for each augmented reality content item, for quick access and display by the messaging client application 104 during the drag operation. Thus, at block 618, the messaging client application 104 replaces the carousel interface with the sliding interface.
Upon detecting a release of the finger from the screen, the messaging client application 104 may request remaining augmented reality content item data (e.g., the entirety of the augmented reality content item data, including models/textures) from the messaging server system 110. In this manner, with respect to a current augmented reality content item of the sliding interface, the messaging client application 104 fully applies the augmented reality content item to transform the image captured by the device camera, and may revert to displaying the carousel interface instead of the sliding interface.
At decision block 610, in a case where the user input received at block 606 does not correspond to the first type of gesture (e.g., a drag gesture), the messaging client application 104 determines whether the user input corresponds to a second type of gesture (e.g., a swipe gesture, corresponding to quicker finger movement relative to the drag gesture). If the user input corresponds to the second type of gesture, the messaging client application 104 navigates through the available augmented reality content items at a second speed, which is slower than the first speed as discussed above (block 612).
In one or more implementations, the slower navigation/scrolling through of augmented reality content items corresponds with iterating through available augmented reality content items on a per-swipe basis. For example, each swipe gesture (e.g., in the left or right direction) may provide for the messaging client application 104 to iterate to the next augmented reality content item (e.g., in the respective left or right direction).
In one or more embodiments, the slower navigation/scrolling through of augmented reality content items corresponds with remotely accessing each augmented reality content item from the messaging server system 110 in response to a swipe gesture. For example, the messaging server system 110 requests the respective images, models and/or textures from the messaging server system 110, in order to transform the image captured by the device camera and fully apply the respective augmented reality content items. Moreover, as discussed further below with respect to FIGS. 8A-8B, the messaging client application 104 continues to display the carousel interface (block 614). The process ends at end block 620.
Thus, the process 600 provides for the messaging client application 104 to more quickly navigate through available augmented reality content items, for example, in response to a drag gesture. Alternatively or in addition, the process 600 provides for the messaging client application 104 to more slowly and iteratively navigate through available augmented reality content items, for example, in response to individual swipe gestures.
FIGS. 7A-7C illustrate a user interface 702 for navigating through the display of augmented reality content items (e.g., augmented reality experiences) based on user input corresponding to a first gesture type, in accordance with some example embodiments. The user interface 702 is displayed within the messaging client application 104. For example, FIG. 7A corresponds with receiving user input corresponding to the first gesture type (e.g., a drag gesture), FIG. 7B corresponds with quickly navigating through augmented reality content items during a drag motion from the left-right direction, and FIG. 7C corresponds with quickly navigating through augmented reality content items when the drag gesture switches to the right-left direction.
In the example of FIG. 7A, the user interface 702 includes captured image data 704 corresponding to image data captured by a front-facing camera of the client device 102. Alternatively, the image data may be captured by a rear-facing camera of the client device 102.
The user interface 702 includes a carousel interface 718 which allows the user to cycle through and/or select an augmented reality content item to apply with respect to the captured image data 704. Each of the available augmented reality content items is represented by an icon which is user-selectable for switching to the respective augmented reality content item. In one or more embodiments, the icon corresponding to the active augmented reality content item (e.g., selected augmented reality content item icon 720) is displayed in a different manner relative to (e.g., larger than) the remaining icons. As noted above, the active augmented reality content item may correspond to a default augmented reality content item selected by the messaging client application 104 based on augmented reality content item ranking data received from the messaging server system 110. In one or more embodiments, user selection of the selected augmented reality content item icon 720 provides for generating a message which includes an image (e.g., in response to a press/tap gesture of the selected augmented reality content item icon 720) and/or a video (e.g., in response to a press-and-hold gesture of the selected augmented reality content item icon 720) of the screen content, for example, to send to friends, include in a Story, and the like.
In the example of FIG. 7A, the user provides touch input 706 corresponding to a first gesture type (e.g., a drag gesture). For illustrative purposes, an arrow is depicted with respect to the touch input 706, indicating finger movement from the left-right direction. In response to the touch input 706, the messaging client application 104 navigates/scrolls through display of augmented reality content items during the drag gesture. For example, while FIG. 7A illustrates an augmented reality content item 708 corresponding to a first active augmented reality content item, FIG. 7B illustrates an augmented reality content item 710 corresponding to a second available augmented reality content item.
While not shown in FIGS. 7A-7C, it is noted that additional augmented reality content items may have been presented in between FIG. 7A and FIG. 7B in response to the touch input 706 (e.g., drag gesture). For example, at least the augmented reality content item corresponding to augmented reality content item 712 in FIG. 7C was presented during the navigating/scrolling through available augmented reality content items, as it appears in the ordered list of augmented reality content items before the augmented reality content item corresponding to augmented reality content item 710.
As noted above, the augmented reality content item 710 may correspond to a locally-stored representation of the augmented reality content item, for example, to quickly navigate/scroll through available augmented reality content items during the drag gesture. In addition, the locally-stored representation may include an augmented reality content item name 714.
As seen in FIG. 7B, the user interface 702 further includes a sliding interface 722 which replaces display of the carousel interface 718. The sliding interface indicates the position of a current augmented reality content item (e.g., depicted by the current augmented reality content item icon 724) relative to other available augmented reality content items.
As discussed above, the messaging client application 104 is configured to continually process the drag gesture while the finger maintains screen contact, even in case where finger movement across the screen changes direction. In the example of FIG. 7B, the touch input 706 changes from the left-right direction to the right-left direction, as depicted by the arrow corresponding to the touch input 706 in FIG. 7B. In response to the changed direction of the touch input 706, the messaging client application 104 provides for navigating/scrolling through the available augmented reality content items in the reverse order. As shown in the example of FIG. 7C, the messaging client application 104 navigates/scrolls back to the augmented reality content item corresponding to the augmented reality content item 712, and displays a corresponding augmented reality content item name 716 together with a current augmented reality content item icon 726.
FIGS. 8A-8B illustrates a user interface 802 for navigating through the display of augmented reality content items (e.g., augmented reality experiences) based on user input corresponding to a second gesture type, in accordance with some example embodiments. The user interface 802 is displayed within the messaging client application 104. For example, FIG. 8A corresponds with receiving user input corresponding to the second gesture type (e.g., a swipe gesture), and FIG. 8B corresponds with navigating through augmented reality content items in a more slow, iterative manner.
In the example of FIG. 8A, the user interface 802 includes captured image data 804 corresponding to image data captured by a front-facing camera of the client device 102. Alternatively, the image data may be captured by a rear-facing camera of the client device 102.
The user interface 802 includes a carousel interface 812 which allows the user to cycle through and/or select an augmented reality content item to apply with respect to the captured image data 804. Each of the available augmented reality content items is represented by an icon which is user-selectable for switching to the respective augmented reality content item. In one or more embodiments, the icon corresponding to the active augmented reality content item (e.g., selected augmented reality content item icon 814) is displayed in a different manner relative to (e.g., larger than) the remaining icons. As noted above, the active augmented reality content item may correspond to a default augmented reality content item selected by the messaging client application 104 based on augmented reality content item ranking data received from the messaging server system 110. In one or more embodiments, user selection of the selected augmented reality content item icon 814 provides for generating a message which includes an image (e.g., in response to a press/tap gesture of the selected augmented reality content item icon 814) and/or a video (e.g., in response to a press-and-hold gesture of the selected augmented reality content item icon 814) of the screen content, for example, to send to friends, include in a Story, and the like.
In the example of FIG. 8A, the user provides touch input 806 corresponding to the second gesture type (e.g., a swipe gesture). For illustrative purposes, an arrow is depicted with respect to the touch input 706, indicating finger movement from the right-left direction. In response to the touch input 706, the messaging client application 104 iteratively navigates/scrolls through available augmented reality content items. As noted above, a single swipe gesture may cause the messaging client application 104 to iterate to a single, next available augmented reality content item (e.g., corresponding to augmented reality content item 810 and selected augmented reality content item icon 816 in FIG. 8B), such that navigating through multiple augmented reality content items requires respective multiple swipe gestures. Moreover, as noted above, each of the augmented reality content item 808 and the augmented reality content item 810 may correspond with respective request by the messaging client application 104 to the messaging server system 110 to apply the respective augmented reality content item.
FIG. 9 is a flowchart illustrating a process for navigating through the display of augmented reality content items, in accordance with some example embodiments. For explanatory purposes, the process 900 is primarily described herein with reference to the messaging client application 104 and the messaging server system 110 of FIG. 1. However, one or more blocks (or operations) of the process 900 may be performed by one or more other components, and/or by other suitable devices. Further for explanatory purposes, the blocks of the process 900 are described herein as occurring in serial, or linearly. However, multiple blocks of the process 900 may occur in parallel. In addition, the blocks of the process 900 need not be performed in the order shown and/or one or more blocks of the process 900 need not be performed and/or can be replaced by other operations.
The messaging client application 104 running on the client device 102 displays a carousel interface comprising multiple icons, each icon corresponding to a respective one of a plurality of augmented reality content items (e.g., corresponding to selected augmented reality content item(s)) for displaying with an image captured by a device camera (block 902). Each icon of the carousel interface may be selectable by a user for displaying the respective one of the plurality of augmented reality content items with the image.
The messaging client application 104 receives user input to navigate through display of the plurality of augmented reality content items (e.g., augmented reality content items) while displaying the image (block 904). In a case where the user input corresponds to a predefined type of gesture, the messaging client application 104 navigates through display of the plurality of augmented reality content items while displaying the image (block 906), and omits display of the carousel interface (block 908).
The predefined type of gesture may be a drag gesture. In a case where the user input corresponds to a second predefined type of gesture (e.g., a swipe gesture), the messaging client application 104 navigates through display of the plurality of augmented reality content items while displaying both the image and the carousel interface. Navigating through display of the plurality of augmented reality content items with respect to the drag gesture may be performed at a first speed (e.g., faster or quicker speed), and the navigating through display of the plurality of augmented reality content items with respect to the swipe gesture may be performed at a second speed (e.g., a slower speed).
The messaging client application 104 may receive, from a messaging server system 110, representations of the plurality of augmented reality content items (e.g., augmented reality content items), and store the representations in local memory. Navigating through display of the plurality of augmented reality content items may include retrieving the representations from the local memory, and navigating through display of the representations while displaying the image.
The plurality of augmented reality content items may be arranged in order, where navigating through display of the plurality of augmented reality content items is based on the order. In a case where the user input corresponds to the predefined type of gesture (e.g., the drag gesture), the messaging client application 104 may display a sliding interface in lieu of the carousel interface, the sliding interface indicating a position of a currently-displayed augmented reality content based on the order.
FIG. 10 is a block diagram 1000 illustrating a software architecture 1004, which can be installed on any one or more of the devices described herein. The software architecture 1004 is supported by hardware such as a machine 1002 that includes processors 1020, memory 1026, and I/O components 1038. In this example, the software architecture 1004 can be conceptualized as a stack of layers, where each layer provides a particular functionality. The software architecture 1004 includes layers such as an operating system 1012, libraries 1010, frameworks 1008, and applications 1006. Operationally, the applications 1006 invoke API calls 1050 through the software stack and receive messages 1052 in response to the API calls 1050.
The operating system 1012 manages hardware resources and provides common services. The operating system 1012 includes, for example, a kernel 1014, services 1016, and drivers 1022. The kernel 1014 acts as an abstraction layer between the hardware and the other software layers. For example, the kernel 1014 provides memory management, processor management (e.g., scheduling), component management, networking, and security settings, among other functionality. The services 1016 can provide other common services for the other software layers. The drivers 1022 are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers 1022 can include display drivers, camera drivers, BLUETOOTH® or BLUETOOTH® Low Energy drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), WI-FI® drivers, audio drivers, power management drivers, and so forth.
The libraries 1010 provide a low-level common infrastructure used by the applications 1006. The libraries 1010 can include system libraries 1018 (e.g., C standard library) that provide functions such as memory allocation functions, string manipulation functions, mathematic functions, and the like. In addition, the libraries 1010 can include API libraries 1024 such as media libraries (e.g., libraries to support presentation and manipulation of various media formats such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), graphics libraries (e.g., an OpenGL framework used to render in two dimensions (2D) and three dimensions (3D) in a graphic content on a display), database libraries (e.g., SQLite to provide various relational database functions), web libraries (e.g., WebKit to provide web browsing functionality), and the like. The libraries 1010 can also include a wide variety of other libraries 1028 to provide many other APIs to the applications 1006.
The frameworks 1008 provide a high-level common infrastructure that is used by the applications 1006. For example, the frameworks 1008 provide various graphical user interface (GUI) functions, high-level resource management, and high-level location services. The frameworks 1008 can provide a broad spectrum of other APIs that can be used by the applications 1006, some of which may be specific to a particular operating system or platform.
In an example embodiment, the applications 1006 may include a home application 1036, a contacts application 1030, a browser application 1032, a book reader application 1034, a location application 1042, a media application 1044, a messaging application 1046 (e.g., corresponding to the messaging client application 104), a game application 1048, and a broad assortment of other applications such as third-party applications 1040. The applications 1006 are programs that execute functions defined in the programs. Various programming languages can be employed to create one or more of the applications 1006, structured in a variety of manners, such as object-oriented programming languages (e.g., Objective-C, Java, or C++) or procedural programming languages (e.g., C or assembly language). In a specific example, the third-party applications 1040 (e.g., applications developed using the ANDROIDTM or IOSTM software development kit (SDK) by an entity other than the vendor of the particular platform) may be mobile software running on a mobile operating system such as IOSTM, ANDROIDTM, WINDOWS® Phone, or another mobile operating system. In this example, the third-party applications 1040 can invoke the API calls 1050 provided by the operating system 1012 to facilitate functionality described herein.
FIG. 11 is a diagrammatic representation of a machine 1100 within which instructions 1108 (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine 1100 to perform any one or more of the methodologies discussed herein may be executed. For example, the instructions 1108 may cause the machine 1100 to execute any one or more of the methods described herein. The instructions 1108 transform the general, non-programmed machine 1100 into a particular machine 1100 programmed to carry out the described and illustrated functions in the manner described. The machine 1100 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1100 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1100 may comprise, but not be 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 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 devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions 1108, sequentially or otherwise, that specify actions to be taken by the machine 1100. Further, while only a single machine 1100 is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions 1108 to perform any one or more of the methodologies discussed herein.
The machine 1100 may include processors 1102, memory 1104, and I/O components 1144, which may be configured to communicate with each other via a bus 1142. In an example embodiment, the processors 1102 (e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an ASIC, a Radio-Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 1106 and a processor 1110 that execute the instructions 1108. The term “processor” is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. Although FIG. 11 shows multiple processors 1102, the machine 1100 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiples cores, or any combination thereof.
The memory 1104 includes a main memory 1112, a static memory 1114, and a storage unit 1116, both accessible to the processors 1102 via the bus 1142. The main memory 1104, the static memory 1114, and storage unit 1116 store the instructions 1108 embodying any one or more of the methodologies or functions described herein. The instructions 1108 may also reside, completely or partially, within the main memory 1112, within the static memory 1114, within machine-readable medium 1118 within the storage unit 1116, within at least one of the processors 1102 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 1100.
The I/O components 1144 may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components 1144 that are included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones may include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components 1144 may include many other components that are not shown in FIG. 11. In various example embodiments, the I/O components 1144 may include output components 1128 and input components 1130. The output components 1128 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., a vibratory motor, resistance mechanisms), other signal generators, and so forth. The input components 1130 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or another pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), optical sensor components (e.g., a camera) and the like.
In further example embodiments, the I/O components 1144 may include biometric components 1132, motion components 1134, environmental components 1136, or position components 1138, among a wide array of other components. For example, the biometric components 1132 include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram-based identification), and the like. The motion components 1134 include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environmental components 1136 include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detection concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components 1138 include location sensor components (e.g., a GPS receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.
Communication may be implemented using a wide variety of technologies. The I/O components 1144 further include communication components 1140 operable to couple the machine 1100 to a network 1120 or devices 1122 via a coupling 1126 and a coupling 1124, respectively. For example, the communication components 1140 may include a network interface component or another suitable device to interface with the network 1120. In further examples, the communication components 1140 may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices 1122 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).
Moreover, the communication components 1140 may detect identifiers or include components operable to detect identifiers. For example, the communication components 1140 may include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components 1140, such as location via Internet Protocol (IP) geolocation, location via Wi-Fi® signal triangulation, location via detecting an NFC beacon signal that may indicate a particular location, and so forth.
The various memories (e.g., memory 1104, main memory 1112, static memory 1114, and/or memory of the processors 1102) and/or storage unit 1116 may store one or more sets of instructions and data structures (e.g., software) embodying or used by any one or more of the methodologies or functions described herein. These instructions (e.g., the instructions 1108), when executed by processors 1102, cause various operations to implement the disclosed embodiments.
The instructions 1108 may be transmitted or received over the network 1120, using a transmission medium, via a network interface device (e.g., a network interface component included in the communication components 1140) and using any one of a number of well-known transfer protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions 1108 may be transmitted or received using a transmission medium via the coupling 1124 (e.g., a peer-to-peer coupling) to the devices 1122.
A “client device” refers to any machine that interfaces to a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, desktop computer, laptop, portable digital assistants (PDAs), smartphones, tablets, ultrabooks, netbooks, laptops, multi-processor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user may use to access a network.
A “communication network” refers to one or more portions of a network that may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, a network or a portion of a network may include a wireless 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 types of cellular or wireless coupling. In this example, the coupling may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) 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) standard, others defined by various standard-setting organizations, other long-range protocols, or other data transfer technology.
A “component” refers to a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other technologies that provide for the partitioning or modularization of particular processing or control functions. Components may be combined via their interfaces with other components to carry out a machine process. A component may be a packaged functional hardware unit designed for use with other components and a part of a program that usually performs a particular function of related functions. Components may constitute either 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 a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware components of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware component that operates to perform certain operations as described herein. A hardware component may also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include dedicated circuitry or logic that is permanently configured to perform certain operations. A hardware component may be a special-purpose processor, such as a field-programmable gate array (FPGA) or an application specific integrated circuit (ASIC). A hardware component may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, hardware components become specific machines (or specific components of a machine) uniquely tailored to perform the configured functions and are no longer general-purpose processors. It will be appreciated that the decision to implement a hardware component mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software), may be driven by cost and time considerations. Accordingly, the phrase “hardware component” (or “hardware-implemented component”) should be understood to encompass a tangible entity, be that 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 embodiments in which hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one instance in time. For example, where a hardware component comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware components) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware component at one instance of time and to constitute a different hardware component at a different instance of time. Hardware components can provide information to, and receive information from, other hardware components. Accordingly, the described hardware components may be regarded as being communicatively coupled. Where multiple hardware components exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware components. In embodiments in which multiple hardware components are configured or instantiated at different times, communications between such hardware components may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware components have access. For example, one hardware component may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware component may then, at a later time, access the memory device to retrieve and process the stored output. Hardware components may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information). The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented component” refers to a hardware component implemented using one or more processors. Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented components. Moreover, the one or more processors may also operate to support performance of the relevant 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 group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an API). The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processors 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 example embodiments, the processors or processor-implemented components may be distributed across a number of geographic locations.
A “computer-readable medium” refers to both machine-storage media and transmission media. Thus, the terms include both storage devices/media and carrier waves/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.
An “ephemeral message” refers to a message that is accessible for a time-limited duration. An ephemeral message may be a text, an image, a video and the like. 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 setting technique, the message is transitory.
A “machine-storage medium” refers to a single or multiple storage devices and/or media (e.g., a centralized or distributed database, and/or associated caches and servers) that store executable instructions, routines and/or data. The term shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, including memory internal or external to processors. Specific examples of machine-storage media, computer-storage media and/or device-storage media include non-volatile memory, including by way of example semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks The terms “machine-storage medium,” “device-storage medium,” “computer-storage medium” mean the same thing and may be used interchangeably in this disclosure. The terms “machine-storage media,” “computer-storage media,” and “device-storage media” specifically exclude carrier waves, modulated data signals, and other such media, at least some of which are covered under the term “signal medium.”
A “processor” refers to any circuit or virtual circuit (a physical circuit emulated by logic executing on an actual processor) that manipulates data values according to control signals (e.g., “commands”, “op codes”, “machine code”, etc.) and which produces corresponding output signals that are applied to operate a machine. A processor may, for example, be 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) or any combination thereof. A processor may further be a multi-core processor having two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously.
A “signal medium” refers to any intangible medium that is capable of storing, encoding, or carrying the instructions for execution by a machine and includes digital or analog communications signals or other intangible media to facilitate communication of software or data. The term “signal medium” shall be taken to include any form of a modulated data signal, carrier wave, and so forth. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a matter as to encode information in the signal. The terms “transmission medium” and “signal medium” mean the same thing and may be used interchangeably in this disclosure.
Changes and modifications may be made to the disclosed embodiments without departing from the scope of the present disclosure. These and other changes or modifications are intended to be included within the scope of the present disclosure, as expressed in the following claims.

## Claims

1. A method, comprising:
displaying a carousel interface comprising multiple icons, each icon corresponding to a respective one of a plurality of augmented reality content items for displaying with an image captured by a device camera;
receiving user input to navigate through display of the plurality of augmented reality content items while displaying the image;
in a case where the user input corresponds to a drag gesture,
navigating through display of the plurality of augmented reality content items while displaying the image, and
replacing display of the carousel interface with a sliding interface, the sliding interface being configured to display a respective icon, of the multiple icons, corresponding to a currently-displayed augmented reality content item; and

in a case where the user input corresponds to a swipe gesture,
navigating through display of the plurality of augmented reality content items while displaying both the image and the carousel interface.

2. The method of claim 1, receiving, from a server, representations of the plurality of augmented reality content items; and
storing the representations in local memory.

3. The method of claim 2, wherein navigating through display of the plurality of augmented reality content items comprises:
retrieving the representations from the local memory; and
navigating through display of the representations while displaying the image.

4. The method of claim 1, wherein the plurality of augmented reality content items is arranged in order, and wherein navigating through display of the plurality of augmented reality content items is based on the order.

5. The method of claim 4, wherein the sliding interface indicates a position of the currently-displayed augmented reality content item based on the order.

6. The method of claim 1, wherein each icon of the carousel interface is selectable by a user for displaying the respective one of the plurality of augmented reality content items with the image.

7. The method of claim 1, wherein the navigating through display of the plurality of augmented reality content items with respect to the drag gesture is performed at a first speed,
and wherein the navigating through display of the plurality of augmented reality content items with respect to the swipe gesture is performed at a second speed which is slower than the first speed.

8. A device, comprising:
a processor; and
a memory storing instructions that, when executed by the processor, cause the processor to:
display a carousel interface comprising multiple icons, each icon corresponding to a respective one of a plurality of augmented reality content items for displaying with an image captured by a device camera;
receive user input to navigate through display of the plurality of augmented reality content items while displaying the image;
in a case where the user input corresponds to a drag gesture,
navigate through display of the plurality of augmented reality content items while displaying the image, and
replace display of the carousel interface with a sliding interface, the sliding interface being configured to display a respective icon, of the multiple icons, corresponding to a currently-displayed augmented reality content item; and

in a case where the user input corresponds to a swipe gesture,
navigate through display of the plurality of augmented reality content items while displaying both the image and the carousel interface.

9. The device of claim 8, wherein the navigating through display of the plurality of augmented reality content items with respect to the drag gesture is performed at a first speed,
and wherein the navigating through display of the plurality of augmented reality content items with respect to the swipe gesture is performed at a second speed which is slower than the first speed.

10. The device of claim 8, receive, from a server, representations of the plurality of augmented reality content items; and
store the representations in local memory.

11. The device of claim 10, wherein navigating through display of the plurality of augmented reality content items comprises:
retrieve the representations from the local memory; and
navigate through display of the representations while displaying the image.

12. The device of claim 8, wherein the plurality of augmented reality content items is arranged in order, and wherein navigating through display of the plurality of augmented reality content items is based on the order.

13. The device of claim 12, wherein the sliding interface indicates a position of the currently-displayed augmented reality content item based on the order.

14. The device of claim 8, wherein each icon of the carousel interface is selectable by a user for displaying the respective one of the plurality of augmented reality content items with the image.

15. A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a computer, cause the computer to:
display a carousel interface comprising multiple icons, each icon corresponding to a respective one of a plurality of augmented reality content items for displaying with an image captured by a device camera;
receive user input to navigate through display of the plurality of augmented reality content items while displaying the image;
in a case where the user input corresponds to a drag gesture,
navigate through display of the plurality of augmented reality content items while displaying the image, and
replace display of the carousel interface with a sliding interface, the sliding interface being configured to display a respective icon, of the multiple icons, corresponding to a currently-displayed augmented reality content item; and

in a case where the user input corresponds to a swipe gesture,
navigate through display of the plurality of augmented reality content items while displaying both the image and the carousel interface.