CONTENT-BASED SNAP POINT

[0001] Conventional content interfaces permit users to pan through content, such as a news article or a list of files. These interfaces typically operate in one of two ways. A first way pans based on the amount of content displayable to the user—for each user selection, the interface presents a next display worth of content. This can be thought of as a page-by-page progression, though the page is often based on the amount of content displayable to the user at the time rather than the content having been organized into pages independent of the presentation size. Thus, content presented on a small screen, in a small window, or with a low resolution may require many pages to fully represent. Likewise, large bodies of content may require many pages, even for large screens, large windows, or high resolutions. Not surprisingly, panning through content page-by-page is often slow and annoying for users.

[0002] A second way enables a user to vary how far the interface pans through the content based on some factor of the user's selection, such as how fast a user flicks her finger across a touch screen, touch pad, or mouse scroller. This second way permits users to move slowly or quickly through content but may stop at inconvenient points in the content, overshoot important parts of the content, or be difficult to use.

[0003] This document describes content-based snap points and techniques that use these snap points. In some embodiments, multiple content-based snap points are used to stop at points in content that are convenient, prevent overshooting of important parts in the content, and aid user's in manipulating and consuming the content.

[0004] This summary is provided to introduce simplified concepts for a content-based snap point that are further described below in the Detailed Description. This summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

[0017] This document describes content-based snap points. A content-based snap point can permit users to stop at points in content that are convenient, prevent overshooting of important parts in the content, and aid user's in manipulating and consuming the content.

[0018] Consider a case where a user wishes to find a particular part of a news article about the United Kingdom's coldest winter in 100 years, namely the part of the article concerning a severe freeze to the Lake District of England. Assume that this article needs 14 pages to fully present based on a presentation size and resolution and that it includes four subtitled sections, one of which is “Lake District Frozen Solid.” As is often the case, the user in this example does not know exactly where in the article the desired portion begins.

[0019] In one of the conventional ways to move through content noted above, the user can select to advance through the article page-by-page. Note that this conventional way will not necessarily present a page that begins with the desired Lake District section (the Lake District section will eventually come up, but may begin at the middle or end of a page). Assume that the Lake District section will be displayed starting in the middle of the seventh page. Therefore, to pan through the article page-by-page to find the Lake District section, a user will see the first page and then select to move to a next page, see that page displayed, look for content about the Lake District throughout the page rather than just the top of the page, select to move to a next page, look for content about the Lake District throughout that page, and so forth six times. Thus, following this first conventional way the user selects to move through the article six times, searches visually through seven pages, and then finds the section about the Lake District at the middle of that seventh page. As is readily apparent even with this relatively short news article, this conventional way in which to move through content can be slow and annoying.

[0020] Consider the same case for the second conventional way. Here the user again does not know where in the article the Lake District section begins. Assume that the user makes a low-movement input to begin moving through the article (e.g., a small or slow gesture) in response to which the conventional interface presents part of a next page of content. The user looks over the content, does not see anything on the Lake District in the displayed page, and then selects again with another low-movement selection. In response, the conventional interface presents more content but not quite a full page of content. The user again looks through the presented content without finding the Lake District section. Assume that the user then makes a moderate-movement selection, in response to which the conventional interface moves forward about two pages, thereby skipping roughly a page worth of content. At this point the user may be concerned that she has missed the Lake District section and go backwards, or may carefully study the content to see if it is about the Lake District because, even if she is expecting a subtitle, she does not know if she missed it. Following either of these cases, assume the user now makes a large-movement selection in response to which the conventional interface moves forward five pages, skipping the beginning of the Lake District section. At this point the user can back up, carefully study the content to see if she is somewhere in the Lake District section, or move forward again (likely to the end of the article). Or perhaps the user, now frustrated, searches for a search box, enters text of “Lake District,” see multiple options, select on one or more of these, and eventually find the Lake District section. Or the user could decide to use low-movement selections, possibly taking five, ten, or even fifteen selections and accompanying reviews of these pages to finally find the section. As is readily apparent, this second conventional way can be difficult to use, overshoot or undershoot a desired portion, or be quite slow.

[0021] In contrast, consider an example of techniques that use content-based snap points to move through content. As noted above, the news article has four sections each of which has a subtitle. Here the techniques assign four content-based snap points—one for each of the four sections. The article begins with a section about London, then a second section about Wales, a third about the Lake District, and a fourth about Scotland. Here assume that the user makes a moderate- or fast-movement selection in response to which the techniques present the section on Wales, the presented page beginning with the section and having a subtitle stating “Wales Expects Poor Crop Due to Prolonged Winter.” The user quickly ascertains that this is not the Lake District section, knowing that the section subtitle indicates otherwise, and also needing only to look at the top portion of the displayed content. The user then selects again and is presented with the Lake District section, entitled at the top of the portion displayed. The user quickly and easily found the desired portion of the content, here with two selections and two relatively short analyses of displayed content.

[0022] This is but one example of techniques using content-based snap points—others are described below including those that skip some content-based snap points, have subordinate content-based snap points, use static and dynamic threshold ranges for snap points, and numerous other aspects of the techniques.

[0023] FIG. 1 illustrates an example system 100 in which techniques using a content-based snap point can be embodied. System 100 includes a computing device 102, which is illustrated with six examples: a laptop computer 104, a tablet computer 106, a smart phone 108, a set-top box 110, a desktop computer 112, and a gaming device 114, though other computing devices and systems, such as servers and netbooks, may also be used.

[0024] Computing device 102 includes computer processor(s) 116 and computer-readable storage media 118 (media 118). Media 118 includes an operating system 120, windows-based mode module 122, immersive mode module 124, application-launching module 126, content handler 128, and one or more content 130, each having one or more content-based snap points 132. Computing device 102 also includes or has access to one or more displays 134, four examples of which are illustrated in FIG. 1.

[0025] Windows-based mode module 122, immersive mode module 124, and application-launching module 126 may present and use content 130 in different ways and through various content interfaces. Content handler 128, however, can use content-based snap points 132 in one or a combination of these three interfaces to aid in handling content 130, as well as other interfaces that present content. These three modules are described in greater detail below.

[0026] Windows-based mode module 122 presents at least some of content 130 through windows having frames. These frames may provide controls through which to interact with an application and/or controls enabling a user to move and size the window.

[0027] Immersive mode module 124 provides an environment by which a user may view and interact with content 130. In some embodiments, this environment presents content of, and enables interaction with, applications with little or no window frame and/or without a need for a user to manage a window frame's layout or primacy relative to other windows (e.g., which window is active or up front) or manually size or position content. This environment can be, but is not required to be, hosted and/or surfaced without use of a windows-based desktop environment. Thus, in some cases immersive mode module 124 presents an environment that is not a window (even one without a substantial frame) and precludes usage of desktop-like displays (e.g., a taskbar). Further still, in some embodiments this immersive environment is similar to an operating system in that it is not closeable or capable of being un-installed. While not required, in some cases this immersive mode module 124 enables use of all or nearly all of the pixels of a display for presentation of content 130.

[0028] Application-launching module 126 provides an application-launching interface having selectable labels associated with various applications. These labels are one example of content 130. In this context, content-based snap points 132 may reside between groups of these labels, for example.

[0029] Content-based snap points 132 are associated with various points in each respective content 130. These snap points 132 can be determined by content handler 128, received from the provider of each content 130, and/or received or determined based on information from one or more of operating system 120, windows-based mode module 122, immersive mode module 124, or application-launching module 126.

[0030] These snap points 132 are based on the content 130 to which they are associated, such as to logical breaks or dividers in content (e.g., the four sections having subtitles in the Winter article noted above), ways in which the content is displayed (e.g., a snap point set to prevent displaying half of a still image), an organization of content (e.g., labels or files organized into groups), or an expected use of content (e.g., a snap point based on expectation that a user zooming to see the State of Hawaii likely wants to zoom quickly past a screen of blue ocean). Ways in which snap points 132 are received or determined are set forth in greater detail below.

[0031] As noted, content 130 can be presented in at least these three ways, though other modes are also permitted. Operating system 120, modules 122, 124, and 126, as well as content handler 128 can be separate from each other or combined or integrated in some form.

[0032] FIG. 2 depicts a method 200 using a content-based snap point. This method is shown as a set of blocks that specify operations performed but is not necessarily limited to the order shown for performing the operations by the respective blocks. In portions of the following discussion reference may be made to system 100 of FIG. 1, reference to which is made for example only.

[0033] Block 202 receives, during presentation of content, a content-manipulation input having a projected stopping point in the content. This content-manipulation input can be intended to zoom in or out of content to increase or decrease resolution (e.g., a map or photo), pan forward or back through content (e.g., an article or list), and rotate content (e.g., an image) for example.

[0034] A content-manipulation input can be one of a set of multiple possible inputs, such as a set of five hot keys. Another possibility is an input that can vary, such as a gesture having a variable velocity or inertia, a press-hold-and-release control or button (which varies based on how long the user holds), a flick of a mouse scroller or movement of a mouse selector (either varying based on velocity and/or orientation), to name just a few. These inputs can be received in many ways, such as through a touch screen, touch pad, mouse ball, and mouse scroller to name just a few.

[0035] Consider, by way of example, FIG. 3, which illustrates display 300 and immersive interface 302 presenting content 304. Display 300 is one example of display 134, immersive interface 302 is provided by immersive mode module 124, and content 304 is an example of content 130, all of FIG. 1. A fast-movement flick (a gesture having a high velocity) is received at 306. A factor of this gesture 306 is used in calculating a projected stopping point in content 304, here the magnitude of its velocity. Some interfaces behave differently in response to various inputs, such as by using different friction values for gestures, having different hot keys, or moving through content at different speeds during a hold of a press-hold-and-release, to name a few. In each of these cases, however, a projected stopping point in the content can be calculated. Here immersive mode module 124 receives gesture 306 through a touch screen, calculates a projected stopping point, and provides this to content handler 128.

[0036] Block 204 determines whether the projected stopping point in the content is within a threshold range of a content-based snap point. Each content-based snap point 132 of content 130 includes a threshold range. This threshold range can be centered around the snap point or not centered, and can be received or determined by content handler 128. In some cases the ranges vary based on various factors, including a current or prior content-manipulation input, to name just two. In the ongoing example, however, a relatively simple case of fixed threshold ranges is contemplated. Other examples consider variable thresholds below.

[0037] Continuing the ongoing example, consider FIG. 4, which illustrates a full representation of content 402 of which content 304 of FIG. 3 is only a part. The full content 402 includes four content-based snap points 404, 406, 408, and 410, which are assumed here to have been received from the provider of the news article, here a “News” website. Here assume that snap point 404 is at a first subtitle in the article, snap point 406 is at an advertisement within the article, snap point 408 is at a second subtitle, and snap point 410 at a conclusion section. This example also assumes that the threshold ranges shown 412, 414, 416, and 418 are also received by content handler 128 from the News website and do not vary.

[0038] If block 204 determines that the projected stopping point is within a threshold range for a content-based snap point, method 200 proceeds along a “Yes” path to block 206. If not, method 200 proceeds along a “No” path to block 208.

[0039] In this example, block 204, through content handler 128, determines that gesture 306 has a projected stopping point within a threshold range of a snap point, here more than halfway through the content, shown at projected stopping point 420 in FIG. 4 and within threshold range 416 associated with content-based snap point 408.

[0040] Note here that content handler 128 skips over threshold ranges 412 and 414 for snap points 404 and 406, respectively. In some other cases, however, a threshold range can be used that effectively hard-stops movement at a snap point, such as by setting the range to include all of the content that is past the snap point.

[0041] Block 206, responsive to determining that the projected stopping point in the content is within the threshold range of the snap point, causes the content to be presented at the snap point. In this example content handler 128 causes presentation of content of the news article at the snap point by passing snap point 408 as input to immersive mode module 124 of FIG. 1, responsive to which immersive mode module 124 moves through the “Satellite May Crash to Earth” article to a second subtitled section in immersive interface 302 (not shown).

[0042] Thus, instead of presenting content based on projected stopping point 420 of FIG. 4, content is presented based on content-based snap point 408. Similarly to the United Kingdom winter weather article noted above, these techniques permit a user to more quickly and easily move through content using these snap points, here to skip a first subtitled section and an advertisement to start at a second subtitled section. If the user did not desire this section, however, a fast or moderate-speed gesture will likely result in presentation of one of the other sections or the advertisement. As is readily apparent, the techniques permit the user to quickly find the various content-based sections of this news article.

[0043] In some embodiments, content handler 128 visually indicates that the content is being presented at a snap point and/or that snap points have been passed over. Content handler 128, for example, may indicate this through a temporary slow-down in a scan of content shown in immersive interface 302 at content of snap points 404 and 406 on the way to stopping at snap point 408 or projected stopping point 420. Content handler 128 may also or instead indicate information when stopping at content-based snap point 420, such as with a visual “bounce,” which temporarily shows some content (e.g., a ¼ of a page) that follows the snap point before bouncing back to settle at the content of snap point 408 or shows that there is no content (e.g., a ½ of a page of white space) before bouncing back. Other visual indicators can optionally be used, such as to show that a user is at an end of the content with a hard stop (a visual rattle or shake of the content presented, etc.). These are but a few of the possible indicators that may further enable users to move through content more easily by providing information to the user.

[0044] Also in some embodiments, content handler 128 may alter an input to change the projected stopping point so that it equals the snap point. Consider the case where the projected stopping point is within a threshold range and thus, content handler 128 will cause the content to be presented at the snap point instead of the projected stopping point. Content handler 128 may alter the content-manipulation input or how the stopping point is calculated so that presenting the content at the snap point appears natural or expected. One way to do so is to calculate a new factor for an input that would result in a new projected stopping point equaling the snap point. Thus, a new velocity for a received gesture is calculated and passed back to one of operating system 120 or modules 122, 124, or 126 effective to cause the new projected stopping point to equal the desired stopping point—namely the snap point. Another way is to alter an algorithm used to calculate the projected stopping point, such as to alter a friction of a velocity-based gesture, which can also be passed to one of operating system 120 or modules 122, 124, or 126. By so doing, the presentation of content at the snap point appears more natural or expected, rather than looking like an artificial additional movement or jarring stop.

[0045] Block 208, responsive to determining that the projected stopping point in the content is not within the threshold range of the snap point, causes the content to be presented at the projected stopping point. Assume, for example, that projected stopping point 420 is instead just outside threshold range 416. In such a case, content handler 128 causes the content to be presented at the projected stopping point. Here assume that content handler 128 does so either by passing back the projected stopping point 420 to immersive mode module 124 or by indicating that no change in presentation is to be made.

[0046] The examples described above in relation to method 200 assume threshold ranges that are received from a content provider and do not change. Numerous alternatives are contemplated by the techniques, some examples of which are described below.

Determining a Content-Based Snap Point and/or Threshold Ranges

[0047] FIG. 5 depicts a method 500 for determining content-based snap points and/or threshold ranges associated with these content-based snap points. This method is shown as a set of blocks that specify operations performed, but is not necessarily limited to the order shown for performing the operations by the respective blocks. Method 500 may be used with, instead of, or in addition to one or more of the blocks of method 200. In portions of the following discussion reference may be made to system 100 of FIG. 1, reference to which is made for example only.

[0048] Block 502 receives or determines information about content. This information can include an organization of or logical breaks or discontinuities in the content, such as white space, subtitles, or images in text-based content, organizational changes in a file list, such as groupings, file types, or names changes, low-value and high-value content, such as ocean around an island for map content, to name just a few.

[0049] Block 504 determines a content-based snap point based on the information about the content. Thus, content handler 128 can set content-based snap points at an island-size resolution to extend or stop a zooming input from a world-sized resolution or at each new first-later alphabetical change to a long list of files (e.g., at “A”, “B”, and so forth to “Z”), to name just a few.

[0050] This information received may also be used to determine threshold ranges, even in cases where the snap points are received rather than determined. Block 506, which optionally proceeds from either of block 502 or block 504, determines a threshold range for a content-based snap point based on information about the content. The information received may also include information about the snap points as well as the other information noted above, such as the distance (in content) between adjacent snap points. Here content handler 128 determines threshold ranges for each snap point based at least in part on the size of the content and the distance between the snap points.

[0051] Consider again the example of FIG. 4, which illustrates four snap points 404, 406, 408, and 410, a distance between the snap points, and a total size of the content. As shown, threshold range 416 is large and has a wider threshold range relative to snap point 406 than snap point 410 because snap point 406 is further away. Whether or not threshold ranges are received or determined, content handler 128 may alter these threshold ranges based on received input(s), which is described below.

[0052] FIG. 6 illustrates a method 600 for dynamically altering threshold ranges associated with content-based snap points. This method is shown as a set of blocks that specify operations performed, but is not necessarily limited to the order shown for performing the operations by the respective blocks. Method 600 may be used with, instead of, or in addition to one or more of the blocks of method 200 and/or 500. In portions of the following discussion reference may be made to system 100 of FIG. 1, reference to which is made for example only.

[0053] Block 602 receives one or more content-manipulation inputs. Block 602 may do so similarly to block 202 of FIG. 2, though block 602 may receive numerous inputs some or all of which may be received prior to presentation of the content, such as when the method uses, at least in part, previously received inputs representing a user's history.

[0054] Block 604 alters, based on one or more received content-manipulation inputs, a threshold range associated with a content-based snap point.

[0055] Consider again the example of FIG. 4. Here assume that threshold ranges 412, 414, 416, and 418 are received from a content provider. Assume also that the current content-manipulation input is gesture 306 of FIG. 3, which has a high velocity. As such, it likely indicates a user's desire to move quickly to find major content-based breaks in the content rather than a desire to move to a particular line or paragraph. Here content handler 128 alters the four threshold ranges by increasing their size based on gesture 306 having a high velocity. By so doing, the current input is more likely to result in stopping at a snap point.

[0056] Here content handler 128 expands the thresholds as shown in FIG. 7, thereby requiring the current input to result in snapping to a snap point or hitting an end of the article but not stopping at a projected stopping point (unless it happens to stop at exactly one of those points). The threshold ranges 414, 414, 416, and 418 are shown as contrast to altered threshold ranges 702, 704, 706, and 708. Note that these altered threshold ranges now cover all of the full representation of content 402.

[0057] Continuing this example, assume that the altered thresholds resulted in the content being presented at snap point 406 according to blocks 204 and 206 of method 200. Following presentation of the content of snap point 406 (the advertisement mentioned above), assume that another input is received at block 602, here a low-velocity gesture (or some other high-resolution input). In response, content handler 128 at block 604 reduces the thresholds to reflect that the user is likely wishing to move more slowly or precisely through the news article. These reduced threshold ranges are also shown in FIG. 7, at 710, 712, 714, and 716. Note that with these reduced threshold ranges the new input received will likely not land on a snap point, which is sometimes desirable when a user wishes to slowly or carefully manipulate content. Even for larger threshold ranges, a user's input may not cause the content to be snapped to a snap point (e.g., in many cases a projected stopping point will not fall within one of the threshold ranges 414, 414, 416, and 418 illustrated in FIG. 4 for content 402).

[0058] In some embodiments threshold ranges for various snap points may overlap. In such a case the techniques determine which snap point to use. Consider, for example, image content 800 illustrated in FIG. 8, which has over 100 images (represented by small squares) and four primary content-based snap points 802, 804, 806, and 808 each corresponding to organizational breaks in image content 800, and having primary threshold ranges 810, 812, 814, and 816, respectively. Other, secondary content-based snap points are shown with dashed lines (collectively snap points 818) each having same secondary threshold ranges 820. These secondary threshold ranges 820 are effective to prevent portions of images to be “chopped” off or only partially presented. As noted above, any of these snap points or their threshold ranges can received or determined, including dynamically based on one or more inputs.

[0059] Consider the case where content presented is shown in window 822 by windows-based mode module 122 of FIG. 1. Assume also that a content-manipulation input is received having a projected stopping point of 824. Content movement progresses horizontally and shown at projected progress arrow 826 with window 822 shown in dashed lines represented the projected stopping point 824 (shown repeated and separate from image content 800 for visual clarity). At this point content handler 128 determines that projected stopping point 824 lands within two threshold ranges, here primary threshold range 814 and secondary threshold range 820-1, respectively associated with primary content-based snap point 806 and secondary content-based snap point 818-1. Content handler 128 determines, based on a hierarchy of threshold ranges, to present window 822 at snap point 806. This difference from the projected stopping point 824 and the actual presentation point of content-based snap point 806 is shown with reverse progress arrow 828. Note that content handler 128 may optionally show content for the projected stopping point 824 temporarily and then show a visual reversal (a “snap back”) to content-based snap point 806.

[0060] While not shown, the techniques may determine between numerous hierarchies of content-based snap points, though in this example only primary and secondary snap points are illustrated.

[0061] If, however, a projected stopping point is not within one of primary threshold ranges 810, 812, 814, and 816 but is within one of secondary threshold ranges 820 (which is necessarily the case for content 800 due to complete coverage by these secondary threshold ranges), content handler 128 causes presentation at the appropriate secondary content-based snap point.

[0062] FIG. 9 depicts a method 900 using a content-based snap point in an application-launching interface. This method is shown as a set of blocks that specify operations performed but is not necessarily limited to the order shown for performing the operations by the respective blocks. In portions of the following discussion reference may be made to system 100 of FIG. 1, reference to which is made for example only. Method 900 may be used with, instead of, or in addition to one or more of the methods 200, 500, or 600 or blocks thereof In portions of the following discussion reference may be made to system 100 of FIG. 1, reference to which is made for example only.

[0063] Block 902 presents, in an application-launching interface, selectable labels associated with applications, the presented selectable labels a subset of a full set of selectable labels available through the application-launching interface. These selectable labels are another example of content capable of being handled with content-based snap points.

[0064] Consider FIG. 10, which illustrates an example application-launching interface 1000 presented by application-launching module 126 of FIG. 1. Interface 1000 presents eight selectable labels 1002 associated with eight applications. These eight labels 1002 are a subset of a full set of selectable labels shown at 1004.

[0065] Block 904 receives, through the application-launching interface, a content-manipulation input to present additional selectable labels of the full set of selectable labels, the content-manipulation input having a projected stopping point.

[0066] Here assume that the content-manipulation input has a projected stopping point 1006 shown within the full set of selectable labels 1004. As shown, one content-based snap point 1008 is illustrated, here having a threshold range of 1010.

[0067] Block 906 determines whether the projected stopping point for the content-manipulation input in the full set of selectable labels is within a threshold range of a content-based snap point. If block 906 determines that the projected stopping point is within the threshold range, method 900 proceeds along a “Yes” path to block 908. If not, method 900 proceeds along a “No” path to block 910.

[0068] Block 908 presents additional, selectable labels of the full set of selectable labels associated with and at the content-based snap point. As shown in the illustrated example, projected stopping point 1006 is within threshold range 1010. In response, content handler 128 passes the content-based snap point 1008 to application-launching interface 126, which presents the interface 1000 having six additional selectable labels, shown at 1012 (three small and three large selectable labels shown).

[0069] Block 910 presents additional, selectable labels at the projected stopping point if it is determined not to be within a threshold range (e.g., the end of the full set if the projected stopping point is farther than the threshold range 110).

[0070] As noted above, content-based snap points can be received or determined in numerous manners. For this example assume that a user selected, through application-launching interface 1000, to group selectable labels shown at 1002 and 1012 (the first 15 labels of the 21 total labels shown at 1004). Based on this grouping selection, content handler 128 and/or application-launching module 126 set content-based snap point 1008 at its location and having associated threshold range 1010. By so doing, a user can easily select to see the remainder of this group of labels on most content-manipulation inputs. A high velocity selection, however, would likely have a projected stopping point outside threshold range 1010, thereby causing content handler 128 to move to the end of the full set of labels 1004. Thus, a content-based snap point can enable a user to determine how an interface responds to content-manipulation inputs. In this example all but high velocity, low resolution, or otherwise large inputs result in seeing the remainder of the labels in the user's group.

[0071] A content-based snap point can be moved or adjusted by content handler 128 based on various factors, including changes to content or by user selection. Consider again application-launching interface 1000. Here assume a user installs two new applications. Selectable labels for these can be added to the full set 1004 by application-launching module 126 to the group that currently has fifteen selectable labels (say at the end of these labels but before the last six labels). Content handler 128 may adjust content-based snap point 1008 or it may be set for adjustment automatically based on the group size expanding. Thus, content-based snap points can change over time based on content changing. In this example the new selectable labels will also be shown (which likely pushes off all of the labels shown at 1002 responsive to the content-manipulation input).

[0072] The preceding discussion describes methods relating to content-based snap points. Aspects of these methods may be implemented in hardware (e.g., fixed logic circuitry), firmware, software, manual processing, or any combination thereof A software implementation represents program code that performs specified tasks when executed by a computer processor. The example methods may be described in the general context of computer-executable instructions, which can include software, applications, routines, programs, objects, components, data structures, procedures, modules, functions, and the like. The program code can be stored in one or more computer-readable memory devices, both local and/or remote to a computer processor. The methods may also be practiced in a distributed computing mode by multiple computing devices. Further, the features described herein are platform-independent and can be implemented on a variety of computing platforms having a variety of processors.

[0073] These techniques may be embodied on one or more of the entities shown in environment 100 of FIG. 1 and/or example device 1100 described below, which may be further divided, combined, and so on. Thus, environment 100 and/or device 1100 illustrate some of many possible systems or apparatuses capable of employing the described techniques. The entities of environment 100 and/or device 1100 generally represent software, firmware, hardware, whole devices or networks, or a combination thereof In the case of a software implementation, for instance, the entities (e.g., modules 122, 124, and 126 and content handler 128) represent program code that performs specified tasks when executed on a processor (e.g., processor(s) 116). The program code can be stored in one or more computer-readable memory devices, such as computer-readable storage media 118 or computer-readable media 1114 of FIG. 11. The features and techniques described herein are platform-independent, meaning that they may be implemented on a variety of commercial computing platforms having a variety of processors.

[0074] FIG. 11 illustrates various components of example device 1100 that can be implemented as any type of client, server, and/or computing device as described with reference to the previous FIGS. 1-10 to implement techniques that use a content-based snap point. In embodiments, device 1100 can be implemented as one or a combination of a wired and/or wireless device, as a form of television client device (e.g., television set-top box, digital video recorder (DVR), etc.), consumer device, computer device, server device, portable computer device, user device, communication device, video processing and/or rendering device, appliance device, gaming device, electronic device, and/or as another type of device. Device 1100 may also be associated with a user (e.g., a person) and/or an entity that operates the device such that a device describes logical devices that include users, software, firmware, and/or a combination of devices.

[0075] Device 1100 includes communication devices 1102 that enable wired and/or wireless communication of device data 1104 (e.g., received data, data that is being received, data scheduled for broadcast, data packets of the data, etc.). The device data 1104 or other device content can include configuration settings of the device, media content stored on the device, and/or information associated with a user of the device. Media content stored on device 1100 can include any type of audio, video, and/or image data. Device 1100 includes one or more data inputs 1106 via which any type of data, media content, and/or inputs can be received, such as user-selectable inputs, messages, music, television media content, recorded video content, and any other type of audio, video, and/or image data received from any content and/or data source.

[0076] Device 1100 also includes communication interfaces 1108, which can be implemented as any one or more of a serial and/or parallel interface, a wireless interface, any type of network interface, a modem, and as any other type of communication interface. The communication interfaces 1108 provide a connection and/or communication links between device 1100 and a communication network by which other electronic, computing, and communication devices communicate data with device 1100.

[0077] Device 1100 includes one or more processors 1110 (e.g., any of microprocessors, controllers, and the like), which process various computer-executable instructions to control the operation of device 1100 and to enable techniques enabling and/or using a content-based snap point. Alternatively or in addition, device 1100 can be implemented with any one or combination of hardware, firmware, or fixed logic circuitry that is implemented in connection with processing and control circuits which are generally identified at 1112. Although not shown, device 1100 can include a system bus or data transfer system that couples the various components within the device. A system bus can include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and/or a processor or local bus that utilizes any of a variety of bus architectures.

[0078] Device 1100 also includes computer-readable storage media 1114, such as one or more memory devices that enable persistent and/or non-transitory data storage (i.e., in contrast to mere signal transmission), examples of which include random access memory (RAM), non-volatile memory (e.g., any one or more of a read-only memory (ROM), flash memory, EPROM, EEPROM, etc.), and a disk storage device. A disk storage device may be implemented as any type of magnetic or optical storage device, such as a hard disk drive, a recordable and/or rewriteable compact disc (CD), any type of a digital versatile disc (DVD), and the like. Device 1100 can also include a mass storage media device 1116.

[0079] Computer-readable storage media 1114 provides data storage mechanisms to store the device data 1104, as well as various device applications 1118 and any other types of information and/or data related to operational aspects of device 1100. For example, an operating system 1120 can be maintained as a computer application with the computer-readable storage media 1114 and executed on processors 1110. The device applications 1118 may include a device manager, such as any form of a control application, software application, signal-processing and control module, code that is native to a particular device, a hardware abstraction layer for a particular device, and so on.

[0080] The device applications 1118 also include any system components or modules to implement techniques using or enabling a content-based snap point. In this example, the device applications 1118 can include windows-based mode module 122, immersive mode module 124, application-launching module 126, and content handler 128.

[0081] Although embodiments of techniques and apparatuses enabling and using a content-based snap point have been described in language specific to features and/or methods, it is to be understood that the subject of the appended claims is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as example implementations for a content-based snap point.