124 may physically include an arrangement of one or more of the processors 308 (e.g., a subset of or among the one or more processors of the machine) configured to perform the operations described herein for that module. As another example, any module of the content suggestion system 124 may include software, hardware, or both, that configure an arrangement of one or more processors 310 (e.g., among the one or more processors of the machine) to perform the operations described herein for that module. Accordingly, different modules of the content suggestion system 124 may include and configure different arrangements of such processors 310 or a single arrangement of such processors 310 at different points in time. Moreover, any two or more modules of the content suggestion system 124 may be combined into a single module, and the functions described herein for a single module may be subdivided among multiple modules. Furthermore, according to various example embodiments, modules described herein as being implemented within a single machine, database, or device may be distributed across multiple machines, databases, or devices.

FIG. 4 is a flowchart illustrating a method 400 for presenting a content suggestion in a messaging interface, according to certain example embodiments. Operations of the method 400 may be performed by the modules described above with respect to FIG. 3. As shown in FIG. 4, the method 400 includes one or more operations 402, 404, 406, and 408.

At operation 402, the input module 302 receives an input into a messaging interface presented at a client device (e.g., the client device 102). The input may for example include message content that comprises a text string, as well as graphical icons such as emoji, numbers, and punctuation characters.

At operation 404, the keyword module 304 identifies a keyword based on the text string of the message content. For example, the keyword module 304 may parse the message content to identify one or more keywords in response to receiving the input into the messaging interface. The keywords may comprise text strings as well as other index terms based on combinations of letters, numbers, emoji, or punctuation characters.

At operation 406, the content module 306 identifies and retrieves a media item based on the keyword. The media items may for example include audio data, video data, images, as well as interactive media content such as augmented reality lenses and filters. For example, the content module 306 may access a media repository (e.g., the database 120) in response to the keyword module 304 identifies one or more keywords within the message content. The media repository may comprises a collection of media items tagged with index terms, such that reference to the index terms may identify a memory location of a media item. The content module 306 accesses the media repository and retrieves one or more media items based on the keyword.

At operation 408, the presentation module 308 generates and causes display of a chat suggestion within the messaging interface, wherein the chat suggestion includes a media item from among the one or more media items retrieved from the media repository. In some embodiments, the chat suggestion may comprise presentation of a graphical icon, wherein the graphical icon is based on the media item. In further embodiments, the chat suggestion may be presented as a curated selection of a collection of media items, wherein each media item among the collection of media items is retrieved based on the keyword. A sort order of the collection may be based on a ranking of the media items, wherein the ranking may be based on overall usage metrics (e.g., popularity), or based on relevance to the keyword (e.g., based on index term similarity).

FIG. 5 is a flowchart illustrating a method 500 for presenting a content suggestion in a messaging interface, according to certain example embodiments. Operations of the method 500 may be performed by the modules described above with respect to FIG. 3. As shown in FIG. 5, the method 500 includes one or more operations 502 and 504.

At operation 502, in response to receiving the input into the messaging interface as discussed in operation 402 of the method 400, the presentation module 308 causes display of a presentation of the text string from the message content at a position within the messaging interface. The presentation of the message content may for example comprise a display of a text string in a predefined font, color, size, or display format.

At operation 504, in response to the keyword module 304 identifying the keyword based on the text string, as in operation 404 of the method 400, the presentation module 308 emphasizes a display of the keyword within the presentation of the text string. For example, the presentation module 308 may display the keyword among the presentation of the text string in an emphasized font, color, or display format.

FIG. 6 is a flowchart illustrating a method 600 for generating a message based on a content suggestion, according to certain example embodiments. Operations of the method 600 may be performed by the modules described above with respect to FIG. 3. As shown in FIG. 6, the method 600 includes one or more operations 602 and 604.

At operation 602, the input module 302 receives an input through the messaging interface, wherein the input comprises a selection of a content suggestion (i.e., a media item) presented to the user. For example, a user of the client device 102 may be presented with a content suggestion, as in operation 408 of the method 400. Upon reviewing the content suggestion, in order to select the content suggestion, the user may provide an input through the messaging interface that includes a selection of the media item represented by the content suggestion.

At operation 604, in response to receiving the selection of the content suggestion, the presentation module 308 generates a message based on at least the message content received from the user of the client device in operation 402 of the method 400, and the content suggestion selected by the user. The presentation module 308 generates and causes display of a presentation of the message within the messaging interface.

FIG. 7 is a flowchart illustrating a method 700 presenting a content suggestion in a messaging interface, according to certain example embodiments. Operations of the method 700 may be performed by the modules described above with respect to FIG. 3. As shown in FIG. 7, the method 700 includes one or more operations 702 and 704.

At operation 702, in response to the keyword module 304 parsing the message content received from the user as in operation 404 of the method 400, the content module 306 accesses a media repository (e.g., the database 120), wherein the media repository comprises a collection of media items, wherein each media item is indexed and tagged with one or more index terms. For example, the media may be organized in the media repository into one or more collections of media items, wherein each collection is itself tagged with one or more index terms.

At operation 704, the content module 306 identifies media items to be presented to the user as message content. The content module 306 accesses the media repository and identifies media content based on the keyword (e.g., the index terms).

FIG. 8 is a flowchart illustrating a method 800 for generating a media index, according to certain example embodiments. Operations of the method 800 may be performed by the modules described above with respect to FIG. 3. As shown in FIG. 8, the method 800 includes one or more operations 802 and 804.

The media index comprises associations between media items with various index terms that include keywords. The media index may be hosted within a media repository, such as the database 120, as well as at a memory location of a client device 102. Reference to an index term within the media index therefore identifies a memory location of one or more media items, which may be organized in collections. For example, the index term that comprises the text string “LOVE” may reference a memory location that comprises a plurality of media items which have been tagged with the index term.

At operation 802, the input module 302 receives a request to generate a message from the client device 102. In some embodiments, the request to generate the message may occur before the method 400. The request to generate the message may for example include the message content that includes a text string or other index term, and a selection of a chat suggestion that includes the media item.

At operation 804, in response to the request to generate the message that includes the message content and the selection of the chat suggestion, the keyword module 304 generates a media index that includes a linking of the index term from the message content with the media item, such that reference to the index term identifies a memory location of the media item. In some embodiments, the media index may correspond with a user profile associated with the client device 102, such that the media index is “personalized” to a user of the client device 102. In further embodiments, the media index may be located within the database 120, and may be updated and maintained based on requests to generate messages from a plurality of devices that include the client device 102.

FIG. 9 is an interface diagram 900 depicting a messaging interface 905, according to certain example embodiments. As seen in FIG. 9, the messaging interface 905 comprises a presentation of a set of messages received from one or more users, message content 910 into the messaging interface 905, the message content 910 comprising a text string, and a chat suggestion 915, generated based on the message content 910. The messaging interface 905 may be presented at a client device 102.

As discussed in the method 400 of FIG. 4, a user may provide the message content 910 into the messaging interface 905. In response to receiving the message content 910, the various modules of the content suggestion system 240 parses the message content 910 to identify one or more keywords, and identify one or more media items to present to the user within the messaging interface 905 as the chat suggestion 915.

As seen in FIG. 9, the chat suggestion 915 in this example embodiment comprises a display of a graphical icon, wherein the particular shape and/or appearance of the graphical icon is based on the message content retrieved based on the keyword parsed from the message content 910.

In some embodiments, a user may generate a message, such as the message 920, based on the message content 910 and a selection of the chat suggestion 915. For example, the chat suggestion 915 may be presented within an icon that comprises a representation of the media item 925, wherein the media item 925 includes an augmented reality filter element that corresponds to a keyword parsed from the message content 910.

In further embodiments, the content suggestion system 240 may generate and display a collection 930, wherein the collection 930 comprises a presentation of a set of media items that correspond with the keyword parsed from the message content 910. For example, as discussed in operation 408 of the method 400, a chat suggestion may comprise a curated collection of media items, such as the collection 930. A user may scroll through the collection 930 to identify and select one or more media items, such as the media item 925, from among the collection 930.

FIG. 10 is an interface diagram 1000 depicting a message 920 generated using the messaging interface 905, according to certain example embodiments. As seen in FIG. 10, the message 920 comprises a presentation of the message content 910 (i.e., a text string), and the media item 925 from the chat suggestion 915. As seen in the interface diagram 1000, the media item 925 may include an augmented reality filter element.

FIG. 11 is an interface diagram 1100 depicting a messaging interface 1105, according to certain example embodiments. As seen in FIG. 11, the messaging interface 1105 comprises a presentation of message content 1110, and a chat suggestion 1120, generated based on the message content 1110. The messaging interface 1105 may be presented at a client device 102.

As discussed in the method 500 of FIG. 5, the keyword 1115 within the input 1110 may be emphasized in response to the content suggestion module 240 parsing the message content 1110 to identify the keyword 1115.

FIG. 12 is an interface diagram 1200 depicting a message 1205 generated using the messaging interface 1105, according to certain example embodiments. As seen in FIG. 12, the message 1205 comprises a presentation of the message content 1110, and a media item 1210 from the chat suggestion 1120.

Software Architecture

FIG. 13 is a block diagram illustrating an example software architecture 1306, which may be used in conjunction with various hardware architectures herein described. FIG. 13 is a non-limiting example of a software architecture and it will be appreciated that many other architectures may be implemented to facilitate the functionality described herein. The software architecture 1306 may execute on hardware such as the machine 1400 of FIG. 14 that includes, among other things, processors 1404, memory 1414, and I/O components 1418. A representative hardware layer 1352 is illustrated and can represent, for example, the machine 1300 of FIG. 13. The representative hardware layer 1352 includes a processing unit 1354 having associated executable instructions 1304. Executable instructions 1304 represent the executable instructions of the software architecture 1306, including implementation of the methods, components and so forth described herein. The hardware layer 1352 also includes memory and/or storage modules memory/storage 1356, which also have executable instructions 1304. The hardware layer 1352 may also comprise other hardware 1358.

In the example architecture of FIG. 13, the software architecture 1306 may be conceptualized as a stack of layers where each layer provides particular functionality. For example, the software architecture 1306 may include layers such as an operating system 1302, libraries 1320, applications 1316 and a presentation layer 1314. Operationally, the applications 1316 and/or other components within the layers may invoke application programming interface (API) API calls 1308 through the software stack and receive a response as in response to the API calls 1308. The layers illustrated are representative in nature and not all software architectures have all layers. For example, some mobile or special purpose operating systems may not provide a frameworks/middleware 1318, while others may provide such a layer. Other software architectures may include additional or different layers.

The operating system 1302 may manage hardware resources and provide common services. The operating system 1302 may include, for example, a kernel 1322, services 1324 and drivers 1326. The kernel 1322 may act as an abstraction layer between the hardware and the other software layers. For example, the kernel 1322 may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. The services 1324 may provide other common services for the other software layers. The drivers 1326 are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers 1326 include display drivers, camera drivers, Bluetooth® 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 depending on the hardware configuration.

The libraries 1320 provide a common infrastructure that is used by the applications 1316 and/or other components and/or layers. The libraries 1320 provide functionality that allows other software components to perform tasks in an easier fashion than to interface directly with the underlying operating system 1302 functionality (e.g., kernel 1322, services 1324 and/or drivers 1326). The libraries 1320 may include system libraries 1344 (e.g., C standard library) that may provide functions such as memory allocation functions, string manipulation functions, mathematical functions, and the like. In addition, the libraries 1320 may include API libraries 1346 such as media libraries (e.g., libraries to support presentation and manipulation of various media format such as MPREG4, H.264, MP3, AAC, AMR, JPG, PNG), graphics libraries (e.g., an OpenGL framework that may be used to render 2D and 3D in a graphic content on a display), database libraries (e.g., SQLite that may provide various relational database functions), web libraries (e.g., WebKit that may provide web browsing functionality), and the like. The libraries 1320 may also include a wide variety of other libraries 1348 to provide many other APIs to the applications 1316 and other software components/modules.

The frameworks/middleware 1318 (also sometimes referred to as middleware) provide a higher-level common infrastructure that may be used by the applications 1316 and/or other software components/modules. For example, the frameworks/middleware 1318 may provide various graphic user interface (GUI) functions, high-level resource management, high-level location services, and so forth. The frameworks/middleware 1318 may provide a broad spectrum of other APIs that may be utilized by the applications 1316 and/or other software components/modules, some of which may be specific to a particular operating system 1302 or platform.

The applications 1316 include built-in applications 1338 and/or third-party applications 1340. Examples of representative built-in applications 1338 may include, but are not limited to, a contacts application, a browser application, a book reader application, a location application, a media application, a messaging application, and/or a game application. Third-party applications 1340 may include an application developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform, and may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. The third-party applications 1340 may invoke the API calls 1308 provided by the mobile operating system (such as operating system 1302) to facilitate functionality described herein.

The applications 1316 may use built in operating system functions (e.g., kernel 1322, services 1324 and/or drivers 1326), libraries 1320, and frameworks/middleware 1318 to create user interfaces to interact with users of the system. Alternatively, or additionally, in some systems interactions with a user may occur through a presentation layer, such as presentation layer 1314. In these systems, the application/component “logic” can be separated from the aspects of the application/component that interact with a user.

FIG. 14 is a block diagram illustrating components of a machine 1400, according to some example embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 14 shows a diagrammatic representation of the machine 1400 in the example form of a computer system, within which instructions 1410 (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine 1400 to perform any one or more of the methodologies discussed herein may be executed. As such, the instructions 1410 may be used to implement modules or components described herein. The instructions 1410 transform the general, non-programmed machine 1400 into a particular machine 1400 programmed to carry out the described and illustrated functions in the manner described. In alternative embodiments, the machine 1400 operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1400 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 1400 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 personal digital assistant (PDA), an entertainment media system, a cellular telephone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions 1410, sequentially or otherwise, that specify actions to be taken by machine 1400. Further, while only a single machine 1400 is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions 1410 to perform any one or more of the methodologies discussed herein.

The machine 1400 may include processors 1404, memory memory/storage 1406, and I/O components 1418, which may be configured to communicate with each other such as via a bus 1402. The memory/storage 1406 may include a memory 1414, such as a main memory, or other memory storage, and a storage unit 1416, both accessible to the processors 1404 such as via the bus 1402. The storage unit 1416 and memory 1414 store the instructions 1410 embodying any one or more of the methodologies or functions described herein. The instructions 1410 may also reside, completely or partially, within the memory 1414, within the storage unit 1416, within at least one of the processors 1404 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 1400. Accordingly, the memory 1414, the storage unit 1416, and the memory of processors 1404 are examples of machine-readable media.

The I/O components 1418 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 1418 that are included in a particular machine 1400 will depend on the type of machine. For example, portable machines such as mobile phones will likely 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 1418 may include many other components that are not shown in FIG. 14. The I/O components 1418 are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting. In various example embodiments, the I/O components 1418 may include output components 1426 and input components 1428. The output components 1426 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 1428 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 other 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), and the like.

In further example embodiments, the I/O components 1418 may include biometric components 1430, motion components 1434, environmental environment components 1436, or position components 1438 among a wide array of other components. For example, the biometric components 1430 may 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 1434 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environment components 1436 may include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometer 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 1438 may include location sensor components (e.g., a Global Position system (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 1418 may include communication components 1440 operable to couple the machine 1400 to a network 1432 or devices 1420 via coupling 1422 and coupling 1424 respectively. For example, the communication components 1440 may include a network interface component or other suitable device to interface with the network 1432. In further examples, communication components 1440 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 1420 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a Universal Serial Bus (USB)).

Moreover, the communication components 1440 may detect identifiers or include components operable to detect identifiers. For example, the communication components 1440 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 1440, such as, location via Internet Protocol (IP) geo-location, location via Wi-Fi® signal triangulation, location via detecting a NFC beacon signal that may indicate a particular location, and so forth.

GLOSSARY

“CARRIER SIGNAL” in this context refers to any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such instructions. Instructions may be transmitted or received over the network using a transmission medium via a network interface device and using any one of a number of well-known transfer protocols.

“CLIENT DEVICE” in this context 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), smart phones, tablets, ultra books, 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.