Browser-based Discovery and Application Switching

Abstract

Various embodiments enable a web browser to promote the availability of an installable application that is associated with a website to which the web browser has been navigated. The web browser is configured to discover the availability of these applications and, responsively, provide a user experience through which the user can acquire and install such applications, as well as switch to applications that have previously been installed. Thus, through the various embodiments, a user is relieved of the burden of having to navigate to a particular application store and periodically search for applications associated with sites to which they browse.

Description

RELATED APPLICATION

This application is a continuation of and claims priority under 35 U.S.C. §120 to U.S. patent application Ser. No. 13/229,386, filed on Sep. 9, 2011, the disclosure of which is incorporated by reference herein in its entirety.

BACKGROUND

In some online scenarios, website content can be consumed by both a web browser and by an installable application that has been developed for the website content by a web developer. The installable application typically operates outside the browser context. Such installable applications can, in some instances, be designed by a developer to provide a tailored user experience that is somewhat different than the user experience provided by the web browser. Yet, challenges exist in so far as making users aware of the fact that such applications exist and are available for consumption.

SUMMARY

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

Various embodiments enable a web browser to promote the availability of an installable application that is associated with a web site to which the web browser has been navigated. The web browser is configured to discover the availability of these applications and, responsively, provide a user experience through which the user can acquire and install such applications, as well as switch to applications that have previously been installed. Thus, through the various embodiments, a user is relieved of the burden of having to navigate to a particular application store and periodically search for applications associated with sites to which they browse.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items.

FIG. 1 is an illustration of an environment in an example implementation in accordance with one or more embodiments.

FIG. 2 is an illustration of a system in an example implementation showing FIG. 1 in greater detail.

FIG. 3 illustrates an example computing device with a web browser user interface.

FIG. 4 illustrates an example computing device with a web browser user interface in accordance with one or more embodiments.

FIG. 5 illustrates an example computing device with a web browser user interface in accordance with one or more embodiments.

FIG. 6 illustrates an example computing device with a web browser user interface in accordance with one or more embodiments.

FIG. 7 illustrates an example computing device with a web browser user interface in accordance with one or more embodiments.

FIG. 8 illustrates an example computing device with a web browser user interface in accordance with one or more embodiments.

FIG. 9 illustrates an example computing device with a web browser user interface in accordance with one or more embodiments.

FIG. 10 illustrates an example computing device with a web browser user interface in accordance with one or more embodiments.

FIG. 11 is a flow diagram that describes steps in a method in accordance with one or more embodiments.

FIG. 12 illustrates an example computing device that can be utilized to implement various embodiments described herein.

DETAILED DESCRIPTION

Overview

Various embodiments enable a web browser to promote the availability of an installable application that is associated with a web site to which the web browser has been navigated. The web browser is configured to discover the availability of these applications and, responsively, provide a user experience through which the user can acquire and install such applications, as well as switch to applications that have previously been installed. Thus, through the various embodiments, a user is relieved of the burden of having to navigate to a particular application store and periodically search for applications associated with sites to which they browse.

In the following discussion, an example environment is first described that is operable to employ the techniques described herein. Example illustrations of the various embodiments are then described, which may be employed in the example environment, as well as in other environments. Accordingly, the example environment is not limited to performing the described embodiments and the described embodiments are not limited to implementation in the example environment.

Example Environment

FIG. 1 is an illustration of an environment 100 in an example implementation that is operable to employ the animation techniques described in this document. The illustrated environment 100 includes an example of a computing device 102 that may be configured in a variety of ways. For example, the computing device 102 may be configured as a traditional computer (e.g., a desktop personal computer, laptop computer, and so on), a mobile station, an entertainment appliance, a set-top box communicatively coupled to a television, a wireless phone, a netbook, a game console, a handheld device, and so forth as further described in relation to FIG. 2. Thus, the computing device 102 may range from full resource devices with substantial memory and processor resources (e.g., personal computers, game consoles) to a low-resource device with limited memory and/or processing resources (e.g., traditional set-top boxes, hand-held game consoles). The computing device 102 also includes software that causes the computing device 102 to perform one or more operations as described below.

Computing device 102 includes a web browser 104 to provide functionality as described in this document. The web browser can be implemented in connection with any suitable type of hardware, software, firmware or combination thereof. In at least some embodiments, the web browser is implemented in software that resides on some type of tangible, computer-readable storage medium examples of which are provided below.

Web browser 104 is representative of functionality that enables the user to browse to different websites and consume content associated with those websites. As will be described below in detail, the web browser is configured to promote the availability of an installable application that is associated with a website to which the web browser has been navigated.

The web browser 104 is configured to discover the availability of these applications and, responsively, provide a user experience through which the user can acquire and install such applications, as well as switch to applications that have previously been installed. Thus, through the various embodiments, a user is relieved of the burden of having to navigate to a particular application store and periodically search for applications associated with sites to which they browse. Through the techniques described below, the web browser can enable the user to naturally and easily discover and install applications associated with their browsing habits.

Computing device 102 also includes a gesture module 105 that recognizes gestures that can be performed by one or more fingers, and causes operations to be performed that correspond to the gestures. The gestures may be recognized by module 105 in a variety of different ways. For example, the gesture module 105 may be configured to recognize a touch input, such as a finger of a user's hand 106a as proximal to display device 108 of the computing device 102 using touchscreen functionality. Module 105 can be utilized to recognize single-finger gestures and bezel gestures, multiple-finger/same-hand gestures and bezel gestures, and/or multiple-finger/different-hand gestures and bezel gestures.

The computing device 102 may also be configured to detect and differentiate between a touch input (e.g., provided by one or more fingers of the user's hand 106a) and a stylus input (e.g., provided by a stylus 116). The differentiation may be performed in a variety of ways, such as by detecting an amount of the display device 108 that is contacted by the finger of the user's hand 106 versus an amount of the display device 108 that is contacted by the stylus 116.

Thus, the gesture module 105 may support a variety of different gesture techniques through recognition and leverage of a division between stylus and touch inputs, as well as different types of touch inputs.

FIG. 2 illustrates an example system 200 showing the browser 104 and gesture module 105 as being implemented in an environment where multiple devices are interconnected through a central computing device. The central computing device may be local to the multiple devices or may be located remotely from the multiple devices. In one embodiment, the central computing device is a “cloud” server farm, which comprises one or more server computers that are connected to the multiple devices through a network or the Internet or other means.

In one embodiment, this interconnection architecture enables functionality to be delivered across multiple devices to provide a common and seamless experience to the user of the multiple devices. Each of the multiple devices may have different physical requirements and capabilities, and the central computing device uses a platform to enable the delivery of an experience to the device that is both tailored to the device and yet common to all devices. In one embodiment, a “class” of target device is created and experiences are tailored to the generic class of devices. A class of device may be defined by physical features or usage or other common characteristics of the devices. For example, as previously described the computing device 102 may be configured in a variety of different ways, such as for mobile 202, computer 204, and television 206 uses. Each of these configurations has a generally corresponding screen size and thus the computing device 102 may be configured as one of these device classes in this example system 200. For instance, the computing device 102 may assume the mobile 202 class of device which includes mobile telephones, music players, game devices, and so on. The computing device 102 may also assume a computer 204 class of device that includes personal computers, laptop computers, netbooks, and so on. The television 206 configuration includes configurations of device that involve display in a casual environment, e.g., televisions, set-top boxes, game consoles, and so on. Thus, the techniques described herein may be supported by these various configurations of the computing device 102 and are not limited to the specific examples described in the following sections.

Cloud 208 is illustrated as including a platform 210 for web services 212. The platform 210 abstracts underlying functionality of hardware (e.g., servers) and software resources of the cloud 208 and thus may act as a “cloud operating system.” For example, the platform 210 may abstract resources to connect the computing device 102 with other computing devices. The platform 210 may also serve to abstract scaling of resources to provide a corresponding level of scale to encountered demand for the web services 212 that are implemented via the platform 210. A variety of other examples are also contemplated, such as load balancing of servers in a server farm, protection against malicious parties (e.g., spam, viruses, and other malware), and so on.

Thus, the cloud 208 is included as a part of the strategy that pertains to software and hardware resources that are made available to the computing device 102 via the Internet or other networks.

The gesture techniques supported by the gesture module may be detected using touchscreen functionality in the mobile configuration 202, track pad functionality of the computer 204 configuration, detected by a camera as part of support of a natural user interface (NUI) that does not involve contact with a specific input device, and so on. Further, performance of the operations to detect and recognize the inputs to identify a particular gesture may be distributed throughout the system 200, such as by the computing device 102 and/or the web services 212 supported by the platform 210 of the cloud 208.

Generally, any of the functions described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or a combination of these implementations. The terms “module,” “functionality,” and “logic” as used herein generally represent software, firmware, hardware, or a combination thereof. In the case of a software implementation, the module, functionality, or logic represents program code that performs specified tasks when executed on or by a processor (e.g., CPU or CPUs). The program code can be stored in one or more computer readable memory devices. The features of the gesture techniques described below are platform-independent, meaning that the techniques may be implemented on a variety of commercial computing platforms having a variety of processors.

In the discussion that follows, various sections describe example embodiments. A section entitled “Browser-based Application Discovery” describes how a web browser can discover installable applications in accordance with one or more embodiments. Next, a section entitled “Example Method” describes an example method in accordance with one or more embodiments. Last, a section entitled “Example Device” describes aspects of an example device that can be utilized to implement one or more embodiments.

Having described example operating environments in which the browser can be utilized, consider now a discussion of an example browser in accordance with one or more embodiments.

Browser-Based Application Discovery

FIG. 3 illustrates an example computing device in accordance with one or more embodiments, generally at 300. Computing device 300 includes a web browser that is configured to present a web browser user interface 302. User interface 302 includes a content-rendering area 304 within which web content is rendered and a control area 306 within which navigation instrumentalities and other content is provided. The content rendering area 304 and control area 306 are provided on a display device 308 of the computing device 300.

Control area 306 includes various navigational instrumentalities including, by way of example and not limitation, a backward navigation button 310, a forward navigation button 312, an icon 314 associated with a website, and an address field within which a URL 316 can be displayed.

In operation, when a user navigates to a particular website, the web browser receives an HTML file, parses the HTML file and displays content described in the file in the web browser user interface 302. In one or more embodiments, the web developers can advertise the availability of a particular installable application in a couple of different ways such that the web browser can become knowledgeable of the availability. For example, in at least some embodiments, in-page markup can be utilized to advertise the availability of an application. Accordingly, this approach includes, in the HTML itself, markup indicating the availability of an application. Alternately or additionally, the availability of a particular application associated with the website can be included as part of the HTTP header that is received when the web browser navigates to a particular website.

Regardless of how the availability of an application is advertised, once the web browser becomes knowledgeable of the availability of an application, the web browser can take steps to inform the user of the availability of an application. As an example, consider FIG. 4, wherein like numerals from FIG. 3 are utilized.

There, computing device 300 includes a button 400 that has replaced icon 314 (FIG. 3). In this instance, the HTML file that was received from a Web server included information or data indicating the availability of an installable application. In this particular example, the user has navigated to a website called “MaxTV”. Responsive to learning of the availability of an application associated with the current webpage, button 400 is presented. The button is a user-selectable button that can be selected in any suitable way. In at least some embodiments, a user can touch-select button 400, as in FIG. 5, in order to initiate an acquisition process through which the user can acquire the associated installable application. As an example, consider FIG. 6.

There, selectable pop-up display 600 is presented responsive to the user touch-selecting button 400 (FIG. 5). Once the user touch-selects or otherwise selects pop-up display 600, the web browser can navigate to an associated application store to expose the user to an acquisition environment in which the user can acquire the associated application. In one or more embodiments, when the web browser navigates to the application store it includes a globally unique identifier associated with the application the user wishes to acquire. Any suitable type of globally unique identifier can be utilized. In at least some embodiments, the globally unique identifier can include an application ID as well as a product family name that forms a tuple that serves as the globally unique identifier. Using the globally unique identifier, the application store can present the user with an acquisition experience that is specific to the application of interest. As an example, consider FIG. 7.

There, content associated with the application store and, more particularly, the current application of interest, is displayed within the computing device's display device. Notice in this example that additional information is included such as a section 700 with an overview, details, and reviews. A user-selectable display 702 is presented to enable user to purchase or otherwise acquire the application of interest. In this example the display resides in the form of a “get” button. If the user selects this display, the user can acquire the application and have it installed locally on their computing device.

Subsequently, when the user navigates to the same website using their web browser, they can be exposed to a different user experience associated with enabling them to switch to the currently installed application. As an example, consider FIG. 8.

There, the user has again navigated to the website associated with “MaxTV” and has touch-selected button 400. Responsive to touch-selecting button 400, the user can be presented with a menu option that provides them the choice of switching to the application since it is currently installed. As an example, consider FIG. 9.

There, a display or button 900 is presented and provides the user with the choice to switch to the associated application. If the user opts to select the button 900, the web browser can enable switching to the associated application.

In one or more embodiments, when the web browser enables switching to the associated application, the web browser can provide contextual information associated with the state of the current navigation to the application so that the user experience is preserved during and after the transition. Any suitable way of providing contextual information to the application can be utilized. In at least some embodiments, contextual information can be passed to the application by passing the URL associated with the webpage the user was currently consuming. As an example, consider FIG. 10.

There, application content 1000 is displayed within the display device of computing device 300. Here, the application can provide a tailored user experience for the user. In this example, the web browser has been placed in the background and none of the instrumentalities within the control area are displayed. Rather, content of the application is rendered in the manner defined by the application developer. In this particular example, the user interface of the application is a “chromeless” user interface that is devoid of navigation instrumentalities typically associated with a web browser.

Having considered embodiments in which a web browser can facilitate acquisition of and switching to applications, consider now an example method in accordance with one or more embodiments.

Example Method

FIG. 11 is a flow diagram that describes steps in a method accordance with one or more embodiments. The method can be performed in connection with any suitable hardware, software, firmware, or combination thereof. In at least some embodiments, the method can be performed by software, e.g., a web browser, embodied on some type of computer-readable storage medium.

Step 1100 navigates to a website. This step can be performed in any suitable way. In the example above, this step is performed, in part, by receiving an HTML file, parsing through the file for file content, and rendering website content in a user interface. Step 1102 ascertains whether the website has any information associated with an installable application. Any suitable type of information can be utilized. In the example above, such information resides in the form of a globally unique identifier that can be provided in the HTML itself. Alternatively, such information can be included in the HTTP header. If there is no information associated with an installable application, step 1104 does not show an associated user interface. If, on the other hand, there is information associated with an installable application, step 1106 ascertains whether the application has been installed. If the application has not been installed, step 1108 displays an application store button sufficient to enable user to navigate to an application store to acquire the installable application. Step 1110 receives selection of the application store button, and step 1112 activates an application store page to expose the user to an acquisition experience in which they can acquire the installable application.

If, on the other hand, the application is installed, step 1114 ascertains whether the version of the installed application is acceptable. For example, a web developer may have modified the application and updated it. If the version is not acceptable by, for example, being out of date, the method branches to step 1108 as described above. If, on the other hand, the version of the installed application is acceptable, step 1116 displays a switching user interface. The switching user interface enables the user to opt to switch to the installed application. An example of such a user interface is described above. Step 1118 receives a switch selection associated with switching to the installed application. Step 1120 activates the installed application with contextual information associated with the user's current webpage. Using the installed application, the user can now have a tailored experience in which their webpage context is preserved.

Having described an example method in accordance with one or more embodiments, consider now a discussion of an example device that can be utilized to implement the embodiments described above.

Example Device

FIG. 12 illustrates various components of an example device 1200 that can be implemented as any type of portable and/or computer device as described with reference to FIGS. 1 and 2 to implement the embodiments described herein. Device 1200 includes communication devices 1202 that enable wired and/or wireless communication of device data 1204 (e.g., received data, data that is being received, data scheduled for broadcast, data packets of the data, etc.). The device data 1204 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 1200 can include any type of audio, video, and/or image data. Device 1200 includes one or more data inputs 906 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.

Device 1200 also includes communication interfaces 1208 that 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 1208 provide a connection and/or communication links between device 1200 and a communication network by which other electronic, computing, and communication devices communicate data with device 1200.

Device 1200 includes one or more processors 1210 (e.g., any of microprocessors, controllers, and the like) which process various computer-executable or readable instructions to control the operation of device 1200 and to implement the embodiments described above. Alternatively or in addition, device 1200 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 1212. Although not shown, device 1200 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.

Device 1200 also includes computer-readable media 1214, such as one or more memory components, 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 1200 can also include a mass storage media device 1216.

Computer-readable media 1214 provides data storage mechanisms to store the device data 1204, as well as various device applications 1218 and any other types of information and/or data related to operational aspects of device 1200. For example, an operating system 1220 can be maintained as a computer application with the computer-readable media 1214 and executed on processors 1210. The device applications 1218 can include a device manager (e.g., 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, etc.), as well as other applications that can include, web browsers, image processing applications, communication applications such as instant messaging applications, word processing applications and a variety of other different applications. The device applications 1218 also include any system components or modules to implement embodiments of the techniques described herein. In this example, the device applications 1218 include an interface application 1222 and a gesture-capture driver 1224 that are shown as software modules and/or computer applications. The gesture-capture driver 1224 is representative of software that is used to provide an interface with a device configured to capture a gesture, such as a touchscreen, track pad, camera, and so on. Alternatively or in addition, the interface application 1222 and the gesture-capture driver 1224 can be implemented as hardware, software, firmware, or any combination thereof. In addition, computer readable media 1214 can include a web browser 1225 that functions as described above.

Device 1200 also includes an audio and/or video input-output system 1226 that provides audio data to an audio system 1228 and/or provides video data to a display system 1230. The audio system 1228 and/or the display system 1230 can include any devices that process, display, and/or otherwise render audio, video, and image data. Video signals and audio signals can be communicated from device 1200 to an audio device and/or to a display device via an RF (radio frequency) link, S-video link, composite video link, component video link, DVI (digital video interface), analog audio connection, or other similar communication link. In an embodiment, the audio system 1228 and/or the display system 1230 are implemented as external components to device 1200. Alternatively, the audio system 1228 and/or the display system 1230 are implemented as integrated components of example device 1200.

CONCLUSION

Various embodiments enable a web browser to promote the availability of an installable application that is associated with a web site to which the web browser has been navigated. The web browser is configured to discover the availability of these applications and, responsively, provide a user experience through which the user can acquire and install such applications, as well as switch to applications that have previously been installed. Thus, through the various embodiments, a user is relieved of the burden of having to navigate to a particular application store and periodically search for applications associated with sites to which they browse.

Although the embodiments have been described in language specific to structural features and/or methodological acts, it is to be understood that the embodiments defined in the appended claims are not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed embodiments.

Claims

1. A method comprising:

navigating, via a web browser, to a website;

ascertaining, via the web browser, whether the web site has any information associated with an installable application;

responsive to ascertaining said information, ascertaining, via the web browser, whether the installable application has been installed;

responsive to the installable application not being installed, displaying, via the web browser, an application store button sufficient to enable a user to navigate to an application store to acquire the installable application; and

responsive to the installable application being installed, displaying, via the web browser, a switching user interface configured to enable the user to opt to switch to an installed application.

2. The method of claim 1, wherein said information comprises a unique identifier.

3. The method of claim 1, wherein said information comprises a unique identifier provided in HTML associated with the website.

4. The method of claim 1, wherein said information is included in an HTTP header.

5. The method of claim 1 further comprising responsive to the installable application being installed, ascertaining whether an installed version of the application is acceptable and, if so, performing said displaying a switching user interface.

6. The method of claim 1 further comprising responsive to the installable application being installed, ascertaining whether an installed version of the application is acceptable and, if not, performing said displaying an application store button.

7. The method of claim 1 further comprising, responsive to the application not being installed and after performing said displaying an application store button, receiving selection of the application store button and activating an application store page to expose the user to an acquisition experience in which they can acquire the installable application.

8. The method of claim 1 further comprising receiving a switch selection via the switching user interface and, responsively, activating the application with contextual information associated with the user's current context.

9. One or more computer readable storage media embodying computer readable instructions which, when executed, implement a web browser configured to:

ascertain whether a webpage to which the web browser has been navigated has an associated application; and

responsive to the webpage having an associated application, enable a user to switch from the web browser to the associated application using a switching user interface displayed by the web browser.

10. The one or more computer readable storage media of claim 9, wherein the web browser is configured to ascertain whether the webpage has an associated application by identifying a unique identifier associated with the application.

11. The one or more computer readable storage media of claim 9, wherein the web browser is configured to ascertain whether the webpage has an associated application by identifying, in HTML associated with the webpage, a unique identifier associated with the application.

12. The one or more computer readable storage media of claim 9, wherein the web browser is configured to ascertain, in an HTTP header associated with the webpage, whether the webpage has an associated application by identifying a unique identifier associated with the application.

13. The one or more computer readable storage media of claim 9, wherein the web browser is configured to enable a user to acquire a newer version of the associated application.

14. The one or more computer readable storage media of claim 9, wherein the web browser is configured to enable a user to acquire the associated application.

15. The one or more computer readable storage media of claim 9, wherein the web browser is configured to enable a user to acquire the associated application by navigating to an application store page.

16. A computing device comprising:

one or more processors;

one or more computer readable media;

a web browser embodied on the one or more computer readable media and executable under the influence of the one or more processors, the web browser being configured to: ascertain whether a webpage to which the web browser has been navigated has an associated application; responsive to the webpage having an associated application, enable a user to at least: acquire the application and switch from the web browser to the associated application in a manner that preserves the user's webpage context.

17. The computing device of claim 16, wherein the web browser is configured to ascertain whether the webpage has an associated application by identifying a unique identifier associated with the application and acquire the associated application by using the unique identifier.

18. The computing device of claim 16, wherein the web browser is configured to ascertain whether the webpage has an associated application by identifying, in HTML associated with the webpage, a unique identifier associated with the application and acquire the associated application by using the unique identifier.

19. The computing device of claim 16, wherein the web browser is configured to ascertain, in an HTTP header associated with the webpage, whether the webpage has an associated application by identifying a unique identifier associated with the application and acquire the associated application by using the unique identifier.

20. The computing device of claim 16, wherein the web browser is configured to enable a user to acquire a newer version of the associated application.

21. The one or more computer readable storage media of claim 9, wherein the web browser is configured to provide information to the associated application so that the application can tailor a user's experience to an experience associated with the web page to which the web browser was navigated.

22. The one or more computer readable storage media of claim 9, wherein the web browser is configured to provide information to the associated application in association with switching from the web browser to the associated application.

23. The one or more computer readable storage media of claim 9, wherein the web browser is configured to provide a URL to the associated application, the URL being associated with the web page to which the web browser was navigated.

24. One or more computer readable storage media embodying computer readable instructions which, when executed, implement a web browser configured to:

navigate to a website;

display a user interface that is configured to enable a user to acquire an installable application associated with the website; and

display a user interface that is configured to enable a user to switch to an acquired installable application.

25. The one or more computer-readable storage media of claim 24, wherein the web browser is configured to enable a user to acquire the installable application by, at least, causing a web browser navigation to an associated application store.

26. The one or more computer-readable storage media of claim 24, wherein the web browser is configured to enable acquisition of the installable application from an associated application store.

27. The one or more computer readable storage media of claim 24, wherein the web browser is configured to provide information to the acquired installable application so that the application can tailor a user's experience to an experience associated with the web site to which the web browser was navigated.

28. The one or more computer readable storage media of claim 24, wherein the web browser is configured to provide information to the acquired installable application in association with switching from the web browser to the acquired installable application.

29. The one or more computer readable storage media of claim 24, wherein the web browser is configured to provide a URL to the acquired installable application, the URL being associated with the web site to which the web browser was navigated.

30. The one or more computer readable storage media of claim 24, wherein the user interface that is configured to enable a user to acquire the installable application comprises:

a replaceable icon associated with the website; and

a user-selectable button configured to replace the replaceable icon, the user-selectable button being configured to initiate an acquisition process through which information associated with the installable application can be displayed and the installable application can be acquired.