Animated snapshots

Current embodiments relate to generation/sharing of a snapshot of content that the user is viewing. Upon generation of a request for a snapshot of currently viewed content, the snapshot may be generated based at least in part upon one or more parameters and/or criteria included in the request and/or service generating the snapshot. Upon completion of the snapshot, a response that provides the snapshot or a location where the snapshot may be viewed is provided, such that the snapshot may be provided to particular sharing targets, such as social media platforms, electronic devices, email, etc.

BACKGROUND

The present disclosure relates generally to digital content consumption, and, more particularly, to streamlined generation and sharing of snapshots of digital content (e.g., via the Internet).

The world is becoming increasingly connected via digital networks and infrastructure. The Internet has given rise to many social media platforms that enable users to provide comments on particular products, “like” particular products, and/or suggest products that one or more friends might like. Accordingly, these social media platforms are becoming an increasingly useful avenue for advertisement and driving traffic to particular products and/or digital content. Unfortunately, the viewing experience associated with broadcast content (e.g., over-the-air, cable, video on demand service, and/or satellite television) has traditionally been a closed ecosystem that makes it difficult to share content to these social media platforms. Traditional broadcast tuning hardware does not provide effective and/or efficient way to share content on digital networks.

BRIEF DESCRIPTION

Generally speaking, the current embodiments relate to systems where a user may indicate a desire to generate and share a snapshot of content that the user is viewing. For example, a user may provide an indication by selecting an option on a remote control that is associated with a set top box that is rendering content on a television. Upon receiving this indication, the electronic device may provide a request for generation of a snapshot to one or more snapshot generation servers. The snapshot servers may generate the snapshot based at least in part upon one or more parameters and/or criteria included in the request and/or stored at the snapshot servers. Upon completion of the snapshot, the snapshot servers may provide a response that provides the snapshot or a location where the snapshot may be viewed. The electronic device may provide one or more user prompts for sharing the snapshot and/or submit a post of the snapshot to one or more social media platforms. Accordingly, users may quickly and easily generate and share snapshots of digital content to one or more social media platforms, resulting in increased awareness of those connected to the user's social media pages.

DETAILED DESCRIPTION

When introducing elements of various embodiments of the present disclosure, the articles “a,” “an,” “the,” and “said” are intended to mean that there are one or more of the elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements. It should be noted that the term “entity” refers to a user of one or more technology resources, such as: an employee, customer, contractor, or partner, or a computer system, web service, or the like. In some scenarios, “entity” may refer to a group or subset of users of one or more technology resources. Also, the term “technology resources” refers to technology related systems (e.g., software applications, databases, networks, file directories, feeds, and so forth). Provisioning refers to providing entities (e.g., users, clients, and/or customers) with access to data and/or technology resources and de-provisioning refers to removing and/or disabling entity (e.g., user, client, and/or customer) access to data and/or technology resources.

As previously mentioned, there exists an opportunity to more easily and/or efficiently create and share snapshots of content sourced from closed ecosystems (e.g., broadcast television systems) on social media platforms. By reducing the complexity in providing these snapshot sharing services, users may be encouraged to promote broadcasters and/or other vendors' products and/or content. Accordingly, traffic may be driven to these products and/or content, resulting in increased revenues for the broadcasters and/or other vendors.

Turning now to a more detailed discussion of the snapshot sharing system,FIG. 1is a schematic view of a snapshot provision and sharing system10, in accordance with certain embodiments. As mentioned above, a content provider12(e.g., broadcaster14and/or video-on-demand provider16) may provide primary content (e.g., digital content) to a user via content tuning/receiving hardware18(e.g., a set-top box). Upon receipt (or in a time-lapse (e.g., facilitated by digital video recording (DVR) hardware)), the content may be presented to the user (e.g., via a television and/or display20or other content playback device). In some embodiments, the content provider12may provide the primary content via one or more cloud computing services.

In some embodiments, the tuning/receiving hardware18may include the playback hardware (e.g., display20). For example, the tuning/receiving hardware18may be a smart television that has network communication capabilities or may be a computer system, tablet computer, or other processing device that incorporates a display20.

From time to time, the user may desire to share a snapshot of the digital content to one or more others. For example, the user may find a particular clip (e.g., segment, skit, monologue, etc.) to be entertaining and may want to share the clip with others that may find the clip entertaining Using the system10, the user may easily generate and/or share a snapshot of a portion of the content with others via one or more social media platforms. To do this, the user may initiate a function of the content tuning/receiving hardware18(or an independent snapshot capture and/or sharing device) by using one or more user input devices22(e.g., a remote control). For example, one or more inputs on the user input device22may provide an indication24that the user desires to capture and/or share a snapshot of the currently playing content.

Based upon this indication24, the content tuning/receiving hardware18(or an independent snapshot capture and/or sharing device) may provide a snapshot request26to one or more snapshot servers and/or services28. For example, in one embodiment, the snapshot servers and/or services28may host an application programming interface (API) and the snapshot request26may include an API call30to the API of the snapshot servers and/or services28. For example, the API call30may include a start time, end time, content path, and/or other information useful for generating and/or sharing snapshots. For example, in some embodiments, the snapshot request26and/or API call30may include one or more constraints that should be followed when generating and/or sharing the snapshot.

The snapshot servers and/or services28may receive the snapshot request26and may access the content. For example, the snapshot servers and/or services28may include a local content library32that includes the primary content34and/or may access one or more external content libraries36and/or broadcasts to obtain the primary content34. In some embodiments, the primary content34may be accessed directly from the content provider12. For example, the primary content34may be accessed from the content provider12in parallel with the tuning/receiving hardware18. Further, in some embodiments, the tuning/receiving hardware18may provide the primary content34to the snapshot servers and/or services28.

Once the primary content34is accessed, a snapshot generator service38may generate a snapshot40of the primary content34. For example, when dealing with video, the snapshot generator service38may segment the video into portable network graphics (PNG) files42and combine the PNG files into an animated graphics interchange format (GIF) file44. Many other methods of generating a snapshot40may be used. Further, the primary content may be audio or other non-video content.

Once the snapshot40has been generated, the snapshot servers and/or services28may optionally store the snapshot40in internal and/or external data storage46. In such embodiments, a universal resource locator (URL) or other location identifier48may be provided in a snapshot response message50to enable the content tuning/receiving hardware18(or an independent snapshot capture and/or sharing device) to access the snapshot40. In some embodiments, the snapshot40may be directly provided to the content tuning/receiving hardware18(or an independent snapshot capture and/or sharing device) in the response message50.

Upon receiving the snapshot40or the location identifier48the content tuning/receiving hardware18(or an independent snapshot capture and/or sharing device) may update52playback of the content with one or more sharing prompts. The sharing prompts may prompt the user for additional information useful for facilitating sharing of the snapshot. In certain embodiments, the prompts may include sharing confirmation, snapshot editing inputs, sharing destination prompts, etc. Further, in certain embodiments, a preview of the snapshot may be presented prior to actually sharing the snapshot.

Once the user provides sufficient inputs to the sharing prompts (e.g., confirms that the snapshot should be shared), the content tuning/receiving hardware18(or an independent snapshot capture and/or sharing device) may provide a POST command54to one or more social media platforms56and the content tuning/receiving hardware18(or an independent snapshot capture and/or sharing device) may update58playback to normal content presentation without the sharing prompts. Thus, users engaged with posts from the user's registered social media platforms56may become aware of the snapshot40that the user wished to share. Accordingly, additional traffic may be provided to the broadcaster12's content and/or products associated with the content40.

Snapshot Generation Request

Turning now to particular functionalities of an electronic device that may initiate snapshot generation requests,FIG. 2is a flowchart illustrating a process90for generating a snapshot request using the system ofFIG. 1, in accordance with certain embodiments. The process90(and the other processes described herein) may be implemented by a hardware-based processor and may be machine-readable instructions stored on a tangible, non-transitory, machine-readable medium. In one embodiment, process90may be implemented by the content tuning/receiving hardware18. In alternative embodiments, an independent snapshot capture and/or sharing device may be used to perform certain steps, while the content tuning/receiving hardware18may be used to perform other steps of the process90.

The process90beings with receiving content (block92). For example, as discussed above, the content may be provided by a content provider12, such as a broadcaster14and/or a video-on-demand provider16. The content may include video, audio, etc. and may be content that is live streamed or previously created.

Upon receiving the content, the content may be presented to the user (block94). In some embodiments, the content may be presented after a particular time lapse. For example, digital video recording hardware and/or software may be used to record the content for playback at a later date.

Content tuning/receiving hardware18(or an independent snapshot capture and/or sharing device) may monitor for an indication that data capture (e.g., snapshotting) is desired by the user (decision block96). For example, a particular infrared command code may be used to provide an indication that snapshotting is requested.

If no such indication is received, normal content playback (block94) continues. However, in some embodiments, when such an indication is provided, the content tuning/receiving hardware18(or an independent snapshot capture and/or sharing device) may discern whether or not a snapshot timing indication has been provided (decision block98). For example, certain inputs may indicate a duration of snapshot to capture. For example, in some embodiments, a user may hold down a button for the duration of time to capture. The amount of time the button is held down for may be used as the duration.

In situations where no timing indication is provided, a request for snapshot capture may be generated that uses a default duration (e.g., 6 seconds) (block100). Otherwise, when a duration indication is provided, the snapshot capture request may include the indicated duration (block102). In some embodiments, rather than providing a duration, a start and end time relative to the content playback may be used to capture the snapshot. Accordingly, these times may be presented in the snapshot capture request.

Additionally, a data constraint analysis may be completed. For example, constraints may limit attributes of the snapshot generation and/or sharing. For example, as will be discussed in more detail below, constraints may be placed on the snapshot generation, such as: a minimum snapshot duration, maximum snapshot duration, particular restricted portions of the content that may not be captured, particular data frames that should be added to the snapshot (e.g., a spoiler alert banner), etc. Further constraints may be placed on the sharing of particular snapshots, such as: restricted targets (e.g., social media sites where the snapshot cannot be posted), exclusive targets (e.g., a listing of social media sites where the snapshot can be posted), particular activities/functionalities to be invoked upon a share (e.g., provide reward points, track sharing, etc.), etc. A more detailed discussion of potential constraints will be discussed with regard toFIGS. 5-11below.

The system may determine whether or not any data capture constraints are applicable to the current snapshot generation and/or sharing request (decision block104). If no data capture and/or sharing constraints exist, the snapshot request may be provided without additional constraint (block106). Otherwise, when constraints exist, the request may be provided in accordance with the data constraints (block108). For example, the data constraints may be included in the provided request in some embodiments. Alternatively and/or additionally, the request parameters (e.g. start time, end time, duration, etc.) may be adjusted to accommodate the constraints. For example, if a constraint defines a maximum duration to be 5 seconds, but the requested duration is 10 seconds, the request may automatically be adjusted to the maximum duration of 5 seconds.

As mentioned above, the request is provided to one or more snapshot servers and/or services28. Once the request is sent, normal operation may continue (e.g., block94).

Snapshot Generation

Turning now to the snapshot generation process, the actual generation of the snapshots may occur independently from the electronic device where a request for creation of the snapshot is made.FIG. 3is a flowchart illustrating a process120for generating a snapshot and snapshot response from a received snapshot request, in accordance with certain embodiments. Upon receiving a data capture request (e.g. as provided via process90ofFIG. 2) (block122), the primary content may be accessed (block124). For example, as discussed above, the snapshot servers and/or services28may access the primary content34from internal and/or external content libraries32and/or36. The received data capture request may include a content identifier and/or a content location identifier that may guide the snapshot server and/or services28to access the primary content.

Based upon the request, the snapshot servers and/or services28may know the snapshot generation parameters. For example, the start time, duration, and/or end time for the snapshot may be provided. Further, the constraints for snapshot generation may be included. Accordingly, the snapshot may be generated (block126). In some embodiments, a subset of the primary content (e.g. from the start time for the duration provided in the data capture request and/or from the start time to the end time provided in the data capture request) may be broken up into separate PNG image files. These PNG image files may be combined into one animated GIF file. Alternatively, the subset of primary content may be stored as a compressed video, etc.

As discussed above, once the snapshot is generated, the snapshot (or a reference to the snapshot) may be provided, via a response message, to the device that requested the snapshot (block128). In some embodiments, the snapshot will be stored in a data store and the response may contain a URL or other location indicator that points to the snapshot. In some embodiments, when multiple users request the same snapshot (or similar snapshots), the snapshot server and/or services28may generate one copy of the snapshot and provide a response to the multiple users with the same location identifier. Accordingly, each user may access the snapshot without generating multiple copies of the snapshot (or similar snapshots).

Snapshot Sharing

Once the snapshot is generated, the electronic device that initiated the snapshot request may proceed with sharing the snapshot.FIG. 4is a flowchart illustrating a process150for sharing generated snapshots, in accordance with certain embodiments. Upon receiving a snapshot response (e.g., from the snapshot server and/or services28as described inFIG. 3) (block152), the content tuning/receiving hardware18(or an independent snapshot capture and/or sharing device) may prompts one or more sharing prompts and/or sharing graphical user interfaces (block154). As will be discussed in more detail below, the sharing prompts may facilitate the sharing of the snapshot by enabling the user to provide additional information to facilitate sharing of the snapshot. For example, the user may view a preview of the snapshot, provide an indication of particular social media sites to share the snapshot to, confirm that the snapshot should be shared, etc.

In the current embodiment, the user may confirm sharing prior to any posts of the snapshot to social media sites. Accordingly, the system may determine whether or not the user has confirmed the sharing (decision block156). When the user does not confirm the sharing (e.g., “cancels” the sharing), normal playback may resume (block158). However, when the sharing is confirmed, the system (e.g., the content tuning/receiving hardware18(or an independent snapshot capture and/or sharing device)) may provide a post request to post the snapshot to specified social media platforms.

Further, while the current discussion primarily discusses social media platforms, it is important to note that the current techniques are not limited to posting to social media platforms. For example, the snapshot could be shared with other electronic devices (e.g., via short message service (SMS) text messages, electronic mail, etc.). Once the post request is sent, normal playback may resume (block158).

Snapshot Generation and Sharing Constraints

As mentioned above, in some embodiments, it may be beneficial to add certain constraints to what and/or how snapshots are generated and/or shared.FIG. 5is a schematic view of a tangible, non-transitory, machine-readable medium that includes one or more snapshot creation and/or sharing constraints, in accordance with certain embodiments. Additionally,FIG. 6is a schematic view of an example piece of primary content having associated constraints, in accordance with the constraints stored in the machine-readable medium ofFIG. 5. For clarity,FIGS. 5 and 6will be discussed jointly.

Broadcasters and/or vendors may desire to place constraints on snapshot generation and/or sharing of their content and/or content related to their products. Accordingly, one or more constraints data stores190(e.g., database) may hold one or more constraints192for one or more pieces of primary content34. In certain embodiments, the constraints192may include a content identifier194, a segment identifier196, and/or one or more constraint rules198. The content identifier194may include an identifier of the content that may be mapped to the content identifier sent in the snapshot request26(ofFIG. 1). Accordingly, the system10may determine constraints for a given piece of primary content by querying the content identifier194.

It may be beneficial to enable more granular constraints. Accordingly, a segment identifier196may specify particular portions of the content that the associated constraint rule(s)198apply to. In some embodiments, the segments may be may be categorically defined. In the current example, constraints192A,192B,192E,192F, and192G provide categorical segment definitions. For example, constraint192A holds constraint rules198associated with introductory segments210(e.g., first segments, first 5 minutes, first 10 minutes, etc.) of content194(e.g., content195) identified as “ONE.” Constraint192B holds constraint rules198associated with intermediate segments212(e.g., segments in between introductory segments210and spoiler segments214, middle segments, middle 50%, etc.) of content194(e.g. content195) identified as “ONE.” Constraints192E and192F hold constraint rules198associated with spoiler sections214of the content (e.g., particular portions that may give away key plot elements, the last 5 minutes of the content, etc.) of content194(e.g. content195) identified as “ONE.” Constraint192F holds constraint rules198associated with all segment breaks216(e.g., commercial blocks where primary content is not played, etc.) of content194identified as “ONE.” Finally, constraint192G holds constraint rules198associated with all of content194(e.g., content218) identified as “COMM. 1.”

Additionally and/or alternatively, the content segments196may be explicitly defined (e.g., by a segment identifier and/or timing identifier). Constraints192C and192H provide explicitly defined constraints192. For example, constraint192C holds constraint rules198associated with a segment220identified as “SECOND SEGMENT” of content194(e.g., content195) identified as “ONE.” Constraint192H holds constraint rules198associated with a segment222timed222from 0:00 to 1:00 of content194(e.g., content224) identified as “COMM.2.”

In some embodiments, certain segments may be un-constrained. For example, no constraint rules apply in the constraints192A and192F, as indicated by NULL constraint rules198A and198F.

Alternatively, any number of constraints may be associated with content. For example, minimum snapshot sizes, maximum snapshot sizes, and/or banned capture periods may be applied to particular segments196of content194. Constraint192B provides a constraint rule198B that indicates that the snapshot cannot exceed a maximum of 6 seconds. Constraint rule198E indicates that spoiler pre-frames should be invoked for constraint192E.

Additionally or alternatively, sharing constraints may be enforced in the system. Constraint rules198C and198D provide sharing constraints that constrain target sharing platforms. For example, constraint rule198C indicates that snapshots associated with constraint192C can only be shared to platforms SM1and SM3. Constraint rule198D indicates that snapshots associated with constraint192D cannot be shared to platform SM1. In other words, constraint192C provides an exclusive target constraint and constraint192D provides a banned target constraint.

Additional activities may be triggered using the constraints192. For example, constraints192G and192H trigger activities based upon sharing snapshots. For example, in constraint192G, the constraint rule198G provides a reward for sharing a snapshot associated with the constraint192G. Constraint192H includes a constraint rule198H that triggers tracking and recording when a user shares a snapshot associated with constraint192H.

In some embodiments, subject matter contained in particular segments may trigger certain constraints. For example, metadata of the primary content (e.g., information describing the content or adding supplemental information to the content) may indicate particular details that invoke certain constraints. For example, a watermark or other data marker may indicate when a copyright notification should occur based upon the particular portion of the primary content. In some embodiments, the metadata may indicate a particular logo or other trademark and/or copyrighted content. In some embodiments, the metadata may include a “point-to” location, such as a uniform resource locator (URL), which may provide a location for supplemental content related to the portion of primary content.

Upon detecting such metadata, constraints may be triggered. For example, in some embodiments, similar to the spoiler alert frames that are added to the introduction of a snapshot, copyright, trademark, and/or other notifications may be appended to the snapshot (e.g., append pre-frames). For example, a notification may be indicate that the clip is “Provided by” a particular content provider or vendor. Additionally and/or alternatively, when a point-to location is provided in the metadata, a link to the location may be presented to viewers of the snapshot. Thus, when the snapshot is a commercial for XYZ product, for example, a link to XYZ's website may be presented in the snapshot.

In some embodiments, certain default constraints may be provided regardless of the identity of the primary content. For example, in some embodiments, a default constraint may indicate that all snapshots, regardless of the identity of primary content, should credit the snapshot provided. For example, pre-frames may be appended to the snapshot to credit a particular provider of the snapshot. For example, the vendor of the vendor of the device18may be credited, by providing a notification that the snapshot is “Provided by [vendor].”

Each of the constraints192may be associated with the primary content.FIG. 6illustrates how these constraint rules198may be associated with the content194. As illustrated, constraint rule198A (e.g., no constraints) are associated with introductory segments210of content “ONE.” Further, constraint rule198G is associated with “ALL” of content “COMM. 1.” Intermediate segments212are associated with the constraint rule198B. Further, “SECOND SEGMENT”220is associated with constraint rule192C. Content “COMM. 2”224is associated with constraint rule198H. And lastly, the restricted spoiler section214is associated with constraint rules198D and198E.

In certain embodiments, when a snapshot duration causes a snapshot to enter a separate segment196, the most restrictive constraint rules198may be applied to the entire snapshot. Alternatively, the user may be informed that certain options are only available for a portion of the snapshot and allow the user to select between shortening the snapshot, applying the most restrictive constraint rules198or modifying relevant settings of the snapshot as new segments196are reached. For example, in one embodiment a user may attempt to record a snapshot of a portion of the third segment226(an intermediate segment212) that enters into the restricted spoiler segment214. Of these segments226and214, the only maximum set is 6 seconds in segment226. There is no maximum set in segment214. In some embodiments, because the most restrictive constraint rules198are selected between multiple segments, a 6 second maximum rule may be applied to segment214. Additionally, segment214includes a ban to SM1(constraint rule198D). This may be applied to segment226because it is the most restrictive target rule of the two segments.

Continuing with the current example constraint rules198,FIGS. 7-11are schematic views illustrating a sequence of generating and sharing content according to the constraints192described inFIGS. 5 and 6, in accordance with certain embodiments. For example,FIG. 7illustrates a basic flow250of snapshot generation and sharing, without associated constraints (e.g., of the introductory segments210).

As illustrated inFIG. 7, a user input device22(e.g., a remote control) may be used to provide an indication that a snapshot is desired. This indication may be triggered by a single button click252, a button click and hold254(e.g., where the hold may indicate the duration of the data capture), and/or a graphical user interface control input256.

In certain embodiments, an indication may be presented on the playback device20that indicates data capture (e.g., snapshotting) is occurring. For example, in progression251A, indicator258A may indicate that a default capture of 6 seconds is being captured when a 1 click252operation (or other non-time indicating request) is initiated. Indicator258B may indicate that a variable length data capture is occurring based upon a click and hold254operation (or other specified variable length data capture request) occurring. Indicator258C may be provided as a GUI based prompt to allow the user to indicate a particular data capture duration when a GUI based control operation256(or other explicitly defined duration data capture request) occurring.

As illustrated in progression251B, once the snapshot is generated and received (or a location indicator of the snapshot is received), one or more sharing prompts260may be presented. In the current embodiment, the sharing prompts260are provided in a sidebar that extends from the right of the screen.

In the current example, no constraints are associated with the current snapshot (e.g., because the snapshot occurred during the introductory segment210. Thus, all available prompts260may be presented. Some available prompts260may include: a snapshot preview262, one or more target social media platform prompts264that indicate particular social media platforms to share the snapshot to; other destination prompts266for sharing the snapshot to (e.g., email address prompt); editing prompts268, such as a request to add a particular duration (e.g. 4 seconds) and/or subtract a particular duration (e.g., 4 seconds), and/or confirmation270and/or cancellation272prompts.

As illustrated by progression251C, when the user confirms sharing by selecting the confirmation prompt270, the snapshot274may be shared to the social media platform56, such that the snapshot274becomes visible on the social media platform's graphical user interface276.

Turning now to other constraints,FIG. 8illustrates an embodiment where spoiler alert handling and banned target constraints have been applied. In the example ofFIG. 8, a snapshot request is initiated during the restricted spoiler214segment. Accordingly, the constraint rules198D (banning sharing to social media platform SM1) and198E (invoke spoiler pre-frames) are associated with the snapshot request. In progression301A, the snapshot request is created and provided to the snapshot server and/or services28. In the current embodiment, no indication of the screen capture request is provided. However, in alternative embodiments, indicators, such as256A-C, may be provided to the user.

As illustrated in progression301B, when the snapshot response is received, the sharing prompts260are presented. In the current embodiment, the user is provided a notice302that spoiler alert frames will be added to the snapshot because the user has captured spoiler segment214content. Further, because constraint rule198D bans sharing to SM1, the SM1is removed as a sharing option from the social media platform prompts264. In some embodiments, banned options may be disabled and greyed out (or otherwise indicated as unavailable). Upon confirming the share via confirmation prompt270, the altered snapshot304that includes the prepended spoiler alert frames306and the captured frames308is posted to the social media platform56and/or other target destinations (e.g. email, servers, and/or other electronic devices). Accordingly, the social media platform GUIs276may reflect the posted altered snapshot304.

Snapshots of supplemental content may also be generated and shared. For example,FIG. 9illustrates an embodiment330where a snapshot of a commercial may be generated and shared. Further,FIG. 9illustrates additional constraints and/or activities that may be associated with the shared snapshot. For example, in certain embodiments, rewards points or other incentives may be offered for a user generating and sharing a commercial via their social media accounts (e.g., as illustrated in constraint192G). Additionally and/or alternatively, tracking functionalities may be implemented (e.g., as illustrated in constraint192H).

In certain embodiments, this incentive may be provided by notifying the user via the primary content. For example, in progression331A, an indication332is presented in the content334, which happens to be a commercial for product XYZ. The manufacturer of XYZ and/or the broadcaster of the commercial (e.g., content334) may desire that users share the commercial on their social networking sites. Accordingly, the manufacturer of XYZ may provide the indication332as part of the content334and/or the broadcaster may provide the indication332as an overlay of the content332. In some embodiments, no indicator332may be presented.

The user may initiate a request to generate and share the content334(e.g., via the user input device22). Upon receiving a response that snapshot has been created and is ready for sharing, sharing prompts302may be presented to the user, as illustrated in progression331B. In the current embodiment, because constraint rule198G indicates that a reward should be provided for sharing the snapshot, the sharing prompts302may include Reward Information prompts336, such as an account name338and/or a password340. As discussed above, a snapshot preview262may also be provided. The primary content may continue to be shown (e.g., in a window342). Further, detailed rewards rules344may be presented as well as particular social media platform prompts264.

Upon confirming sharing (e.g., via the confirmation prompt270), the snapshot may be provided to the social media platforms56(and any other target destinations), such that the content is presented in the GUI276. Further, reward points (or other incentives) may be provided for the user. For example, in the current embodiment, the reward prompt information336is used to access an external reward points database346where the system may provide reward points for the user sharing the commercial content334. For example, here the user is awarded 16 points (8 points for each of the two social media platforms that the user shared the content334to).

In certain embodiments, it may be beneficial to track users that share snapshots. For example, this information may be useful to gather demographics and/or other information of an audience that is particularly receptive to particular content. For example, as discussed above, constraint192H triggers tracking of users that share the content “COMM. 2”. Accordingly, if content334where “COMM. 2”, the system could provide an user tracking data store348with an entry350that the particular user has shared the content334and/or a particular time and/or date of the sharing.

As previously discussed, some constraints relate to minimum and/or maximum timings allowed for a snapshot.FIG. 10illustrates an embodiment380where maximum timing constraints have been applied. For example, the embodiment ofFIG. 10may relate to one of the intermediate segments212that have an associated 6 second maximum constraint rule198B. During the progression381A, the user may provide a timing indication382of 30 seconds (e.g., via the user input device22to the device18).

Because the current snapshot is constrained by constraint rule198B, the snapshot is limited to a 6 second maximum. In some embodiments, the first six seconds, last six seconds, middle six seconds, and/or most commonly snapshotted six seconds may be used to automatically select six seconds from the 30 seconds requested by the user. However, in other embodiments, the user may be allowed to select a particular six second interval to share. For example, in progression381B, the user is presented sharing prompts260that provide an interface384for selecting a six second interval of the thirty seconds requested by the user. Upon selection of the interval and confirmation of the share (e.g., via the confirmation prompt270, the six second snapshot is posted to the applicable targets (e.g. social media platforms56), such that the social media platform GUIs276may present the six second snapshot386.

In some embodiments, it may be beneficial to provide exclusive posting rights to certain targets.FIG. 11illustrates an embodiment400where exclusive target constraints have been applied. In progression401A, the user may request a snapshot (e.g., via user input device22) during the “SECOND SEGMENT”220ofFIGS. 5 and 6. As previously discussed, this segment is associated with constraint rule198C, which provides an exclusive right to share content snapshots of this segment220with social media platforms SM1and SM3. Accordingly, as illustrated in progression401B, the sharing prompts260, which include a snapshot preview262, target social media platform prompts264, confirmation prompts270and/or cancellation272prompts, has a disabled social media platform prompt264′. Thus, the user is unable to select this option for sharing, because of the exclusivity constraint placed upon “SECOND SEGMENT” snapshots.

However, the user is able to share to the exclusive targets. For example, upon confirming the sharing via the confirmation prompt270, the snapshot402is posted to the selected exclusive targets (e.g., social media platform52SM1). Thus, the snapshot402may be presented by the target (e.g., the social media platform GUI276).