Web page accelerations for web application hosted in native mobile application

Aspects of the present disclosure relate to systems and methods for accelerating loading, parsing, and rendering of a web page hosted by a native mobile application. In one aspect, a manifest file including at least resources for rendering the webpage hosted by the native mobile application may be stored in a local web cache. A request may be sent, via the native mobile application, to a website associated with the native mobile application for the webpage. While initial content of the webpage is loading, the resources stored in the local web cache may be loaded into a browser document object model (DOM). The webpage may be rendered within the native mobile application in a user interface.

BACKGROUND

Both native mobile applications and websites may provide content for the benefit of a user of the native mobile applications and/or websites. Entities that develop applications may develop both a native application and a website application. For example, a user may download the native application to a client device and access the application content via the native application. In another example, a user may access the application content via a website. Generally, native applications access application content using Application Programming Interface (API) technology while website applications access application content using website technology (e.g., browsers, html, parsing, rendering). In some cases, native applications may host webpages that come from remote web servers. However, in these cases, download time, parse time, and rendering speed of the hosted webpages may be slow and inefficient. In turn, a user's experience of viewing and/or interacting with webpages hosted by native mobile applications may be dissatisfying.

SUMMARY

In summary, the disclosure generally relates to systems and methods for accelerating loading, parsing, and rendering of a web page hosted by a native mobile application. In one aspect, a manifest file including at least resources for rendering the webpage hosted by the native mobile application may be stored in a local web cache. A request may be sent, via the native mobile application, to a website associated with the native mobile application for the webpage. While initial content of the webpage is loading, the resources stored in the local web cache may be loaded into a browser document object model (DOM). The webpage may be rendered within the native mobile application in a user interface.

In another aspect, a method for pre-loading webpage data by a native mobile application is presented. A request may be sent from the native mobile application to a service for a latest version of a manifest file. The manifest file may include at least resources for rendering a webpage hosted by the native mobile application. When the service has the latest version of the manifest file, the latest version of the manifest file may be downloaded from the service. The latest version of the manifest file may be stored in a local web cache.

In further aspects, in response to receiving a selection of a native mobile application icon, a native mobile application associated with the native mobile application icon may be launched. A request may be sent to a service for a manifest file. The manifest file may include at least resources for rendering a web page hosted by the native mobile application. The manifest file may be downloaded from the service and stored in a local web cache.

DETAILED DESCRIPTION

Aspects of the disclosure are generally directed to accelerating loading, parsing, and rendering of a webpage hosted by a native mobile application. For example, a first phase for accelerating loading, parsing, and rendering of a webpage hosted by a native mobile application may include pre-loading webpage data using the native mobile application. For example, the webpage data may be pre-loaded by downloading and storing resources associated with a webpage/website that are required for rendering the webpage in the native mobile application. The resources may be stored in a local web cache. In one example, the resources may be included in a manifest file that is retrieved from a service (e.g., in the cloud). For example, the native mobile application may send a request to the service for a latest version of the manifest file. In one example, when the native mobile application already has the latest version of the manifest file including the manifest file contents (e.g., resources), retrieving the manifest file isn't necessary. When the service has a later version of the manifest file than the version of the manifest file currently stored at the local web cache, the native mobile application may download and store the latest version of the manifest file. In one example, the resources included in the manifest file include Javascript and Cascading Style Sheet (CSS) frameworks needed for rendering the webpage. In this regard, when a request is made through the native mobile application for a webpage hosted by the native mobile application, the resources that are already stored in the local web cache for that webpage do not have to be downloaded from the service/website. In turn, the webpage is rendered within the native mobile application in the user interface quickly, efficiently, and in less time than a webpage using current webpage technology takes to be rendered in the user interface. As such, a technical effect that may be appreciated is that by storing the resources needed for rendering a webpage in the local web cache network roundtrip costs may be reduced.

As discussed above, native applications access application content using Application Programming Interface (API) technology while website applications access application content using website technology (e.g., browsers, html, parsing, rendering). In some cases, native applications may host webpages that come from remote web servers. In this case, the native application retrieves application data using the API technology (in some cases the application data may be pre-loaded) and webpage data using the website technology. However, in these cases, download time, parse time, and rendering speed of the hosted webpages may be slow and inefficient. In turn, a user's experience of viewing and/or interacting with webpages hosted by native mobile applications may be dissatisfying. Accordingly, aspects described herein include accelerating loading, parsing, and rendering of a webpage hosted by a native mobile application. As discussed above, a first phase for accelerating loading, parsing, and rendering of a webpage hosted by a native mobile application may include pre-loading webpage data using the native mobile application. In this regard, the native mobile application of the present disclosure is pre-loading webpage/website data that may be accessed and/or used at a later time (e.g., not native mobile application data that is used in the application itself). In contrast, native mobile applications described in the prior art herein may pre-load data that is being used in the native mobile application itself (i.e., mobile application data).

In aspects, a second phase for accelerating loading, parsing, and rendering of a webpage hosted by a native mobile application may include loading the resources stored in the local web cache into a browser Document Object Model (DOM) while an initial payload of a webpage is loading. For example, at some point in time after the resources have been retrieved and stored in the local web cache, a user of the native mobile application may access a webpage hosted by the native mobile application. In one example, a user may select an icon associated with a website and/or webpage hosted by the native mobile application. In one example, the icon may include a link (e.g., a URL) to the website and/or webpage. In response to receiving the selection of the icon associated with the website and/or webpage hosted by the native mobile application, the native mobile application may send a request to the corresponding website for the webpage. While the initial payload of the webpage (e.g., the root Hyper Text Markup Language (HTML) page) is loading, the resources stored in the local web cache may be loaded into the browser DOM. When the initial payload of the webpage is returned, additional resources may need to be obtained to render the webpage. The additional resources include only those resources that were not pre-loaded/stored in the local web cache. For example, instead of requiring all the resources needed for the webpage be downloaded (which is typical for current webpage technology), only a small portion of the resources needed for the webpage may need to be obtained. In this regard, the resources may be downloaded for the webpage in less time than it takes to download resources using current webpage technology. In one example, storing the resources in the local web cache, as discussed above herein in the first phase, may save approximately three seconds of download time.

Furthermore, loading the resources stored in the local web cache into the browser DOM while the initial payload of the webpage is loading may facilitate rendering the webpage in less time than it takes for current webpage technology. For example, in current webpage technology, while the initial payload of the webpage is loading, the client is idle and all the resources needed for rendering the webpage are requested and downloaded before they are loaded into the browser DOM. In the technology of the present disclosure, as described herein, many of the resources are loaded into the browser DOM while the initial payload of the webpage is loading before the initial payload is returned and any additional resources are requested. In one example, loading the resources stored in the local web cache into the browser DOM while the initial payload of the webpage is loading may save approximately two seconds of loading resources into the browser DOM. As such, a total of approximately five seconds may be saved for loading, parsing, and rendering of a webpage hosted by a native mobile application using the technology of the present disclosure. In one example, approximately 30% of time is saved from when a user selects an icon associated with a website within the native mobile application to when a webpage and/or website is rendered within the native mobile application. In this regard, another technical effect that may be appreciated is that rendering of webpages hosted by native mobile applications fast and efficiently facilitates a compelling visual and functional experience to allow users to efficiently view and interact with a user interface to quickly, easily, and efficiently view webpages hosted by a native mobile application. Another technical effect that may be appreciated is that by reducing downloads when a user visits a website by pre-loading website/webpage resources/data, processor load may be reduced, memory may be conserved, and network bandwidth usage may be reduced.

Referring now to the drawings, in which like numerals represent like elements through the several figures, aspects of the present disclosure and the exemplary operating environment will be described. With reference toFIG. 1, one aspect of a native mobile application system100for accelerating loading, parsing, and rendering of a webpage hosted by a native mobile application is illustrated. In aspects, the native mobile application system100may be implemented on a client computing device104. In a basic configuration, the client computing device104is a handheld computer having both input elements and output elements. The client computing device104may be any suitable computing device for implementing the native mobile application system100for accelerating loading, parsing, and rendering of a webpage hosted by a native mobile application. For example, the client computing device104may be at least one of: a mobile telephone; a smart phone; a tablet; a phablet; a smart watch; a wearable computer; a personal computer; a desktop computer; a laptop computer; a gaming device/computer (e.g., Xbox); a television; and etc. This list is exemplary only and should not be considered as limiting. Any suitable client computing device104for native mobile application system100for accelerating loading, parsing, and rendering of a webpage hosted by a native mobile application may be utilized.

In aspects, the native mobile application system100may be implemented on a service106. The service106may provide data to and from the client computing device104through a network105. In aspects, the native mobile application system100may be implemented on more than one service106, such as a plurality of services106. In one example, the service106includes a cloud service. In another example, the service106includes a content delivery network (CDN) and/or an application service. In some examples, the service106includes a plurality of CDNs and/or a plurality of application services. In one case, the application service may include a service such as SharePoint. As discussed above, the service106may provide data to and from the client computing device104through the network105. The data may be communicated over any network suitable to transmit data. In some aspects, the network is a distributed computer network such as the Internet. In this regard, the network may include a Local Area Network (LAN), a Wide Area Network (WAN), the Internet, wireless and wired transmission mediums. In some aspects, the native mobile application system100may be implemented on both a client computing device104and a service106.

As illustrated inFIG. 1, the client computing device104may include a pre-loader framework110, a versioning tag112, a local web cache114, a web accelerator116, and a hosted web view118. The various components may be implemented using hardware, software, or a combination of hardware and software. In examples, the pre-loader framework110may be part of a native mobile application located at the client computing device104. The native mobile application may include any application that can be downloaded from an application store to the client computing device104. In one example, the native mobile application is a SharePoint mobile application. The native mobile application may be downloaded to any platform running on the client computing device104(e.g., any operating system). The pre-loader framework110may be configured to send a request for a manifest file from the native mobile application to the service106. For example, when the native mobile application is launched (step (1)), the native mobile application may start the pre-loader framework110. When the pre-loader framework110is started, the pre-loader framework may send a request to the service106for a manifest file. In one example, the request may be sent to a CDN network. The manifest file may include resources for rendering a webpage hosted by the native mobile application. In one example, the resources may include at least Javascript and Cascading Style Sheet (CSS) frameworks associated with the native mobile application.

In aspects, the versioning tag112may tag the manifest file with a version number. For example, the request for the manifest file sent to the service106may indicate which version of the manifest file is currently stored in the local web cache114. In this regard, when the request for the manifest file is sent to the service106, the service may determine whether it has a later version of the manifest file (step (2)). When the service does not have a later version of the manifest file, a download of the manifest file (e.g., the framework resources) is not needed. In this regard, the manifest file is only downloaded when needed (e.g., when a later/newer version exists in the service106). When the service has a later version of the manifest file, the pre-loader framework110may download the manifest file and its contents (e.g., resources) (step (3)). In one example, up to 30 files and/or 1.5 MB of data may be downloaded.

When the manifest file is downloaded by the pre-loader framework110, the pre-loader framework110may store the manifest file in the local web cache114(step (4)). The local web cache may include any local web cache suitable for caching and/or storing a manifest file and/or the resources included in the manifest file. In aspects, the hosted web view118may include a browser experience for a user of the native mobile application. For example, a user may select an icon associated with a website in the native mobile application (step (5)). In response to receiving a selection of the icon associated with the website, the native mobile application may send a request to the service106(e.g., the website) for content (step(6)). In one example, the request is sent to an application service. In one example, the application service is associated with the native mobile application. In one case, the application service is SharePoint Online. In some examples, the content may include one or more webpages associated with the website. In some examples, the content may include initial content (e.g., a root/initial HTML page) While initial content is loading, the web accelerator116may retrieve the stored manifest file (e.g., resources) from the local web cache114and load the resources into memory (step (7)). For example, the web accelerator116may load the resources stored in the local web cache114into a browser DOM. A DOM is a cross-platform and language-independent convention for representing and interacting with objects in HTML, XHTML, and XML documents, and is well known to those skilled in the art. In another example, while initial content is loading, the resources may be pre-compiled into the browser DOM. (step (7)). When the initial content is done loading, the initial content may be sent to the native mobile application (step(8)). In some cases, additional resources may have to be obtained before the website and/or webpages may be rendered in the hosted web view118, which will be described in more detail relative toFIG. 3.

FIG. 2illustrates a sequence diagram200for loading a website, according to an example of the prior art. The sequence diagram200includes a renderer202, a script DOM204, a cache206, a browser208, and a website210. When a user identifies a website210from the browser208, a request may be sent to the website210to load an initial webpage. When the initial webpage is done loading, the initial webpage may be returned to the browser208. A request may be sent from the browser208to the website210for a plurality of resources that are required for rendering the webpage. The plurality of resources are returned to the browser208one by one. When the initial webpage and all the resources needed to render the webpage are returned to the browser208, the browser208may load the resources into the script DOM204. When the scripts are loaded, the scripts may be processed at the rendered202, where the webpage may be rendered on a user interface. The sequence diagram200for loading a webpage illustrates how sequential the process is for loading a webpage using current (e.g., prior art) webpage technology.

FIG. 3illustrates a sequence diagram300for accelerating loading, parsing, and rendering of a web page hosted by a native mobile application, according to an example aspect. The sequence diagram300includes a renderer302, a browser DOM304, a local web cache306, a native mobile application308, a CDN310, and an application service312. In a first phase, upon launching the native mobile application308, the native mobile application308may send a request to the CDN310for a manifest file. The manifest file includes resources (e.g., webpage data) for rendering a webpage hosted by the native mobile application308. In some examples, the resources include Javascript and CSS frameworks associated with the native mobile application308. The native mobile application308may download the resources from the CDN310. When the resources are downloaded from the CDN310, the native mobile application308may store the resources in the local web cache306. As discussed above, the resources stored are associated with a webpage that may be rendered at a future time.

In a second phase, while a user of the native mobile application308is viewing and/or interacting with the native mobile application308, the user may access a website and/or webpage associated with the native mobile application308. In this regard, the user may select an icon within the native mobile application308associated with a website. In response to receiving a selection of the icon associated with the website, the renderer302may initiate a request to the application service312(e.g., an application service associated with the native mobile application308) to load the website. While an initial payload of the website is loading, a loading status indicator may be presented within the native mobile application308by the renderer302. In another example, while the initial payload of the website is loading, the native mobile application308loads the resources stored in the local web cache306into the browser DOM304. In addition to loading the resources stored in the local web cache306into the browser DOM304while the initial payload of the website is loading, the resources may be pre-compiled into the browser DOM304. When the initial payload is returned (e.g., downloaded from the application service312to the native mobile application308), the initial payload may be loaded into the browser DOM304. As discussed above, loading and pre-compiling the resources stored in the local web cache306into the browser DOM304while the initial payload of the website is loading may save approximately two seconds of load time into the browser DOM304. In other words, the native mobile application308is parallel processing while loading the website. In contrast, as illustrated inFIG. 2, the current technology for loading a website is sequentially processing while loading the website (e.g., the client is idle while the initial payload is loading).

In some cases, additional resources may be required for rendering the website and/or webpage. In this regard, the native mobile application308may send a request to the application service312for additional (e.g., tenant) resources. As discussed above, the additional resources may include only the resources that were not pre-loaded/stored in the local web cache306. In some cases, no additional resources may be required to render the website and/or webpage. In this case, the website and/or webpage may be rendered by the renderer302after the initial payload is downloaded at the native mobile application308and loaded into the browser DOM304. In turn, the resources may be downloaded for the webpage in less time than it takes for current webpage technology. For example, maybe only 10 scripts of 30 scripts may be downloaded when 20 scripts of the 30 scripts are stored at the local web cache306. In one example, storing the resources in the local web cache306may save approximately three seconds of download time. When any required additional resources are returned and downloaded at the native mobile application308, the additional resources may be loaded into the browser DOM304. In some examples, additional website and/or webpage related content/responses may be downloaded at the native mobile application308. The website and/or webpage may be rendered by the renderer302within the native mobile application308in a user interface.

Referring now toFIG. 4, an exemplary method400for accelerating loading, parsing, and rendering of a web page hosted by a native mobile application, according to an example aspect is shown. Method400may be implemented on a computing device or a similar electronic device capable of executing instructions through at least one processor. Method400may begin at operation402, where a manifest file is stored in a local web cache. In one example, the manifest file includes resources for rendering a webpage hosted by a native mobile application. In one example, the resources may include at least Javascript and Cascading Style Sheet (CSS) frameworks associated with the native mobile application. The native mobile application accesses and stores the resources in the local web cache before the webpage is accessed, hosted, and launched. In this regard, the native mobile application is storing resources associated with a specific website associated with the native mobile application. In some cases, the website may never be accessed (e.g., a user may never go to the website) even when the resources are stored in the local web cache.

After the manifest file (e.g., webpage resources) are stored in the local cache (e.g., upon launching the native mobile application), flow proceeds to operation404where a request is sent, via the native mobile application, to a website associated with the native mobile application for the webpage. In some examples, the request is sent to the website in response to receiving a selection of an icon within the native mobile application, where the icon is associated with the website. When the request is sent to the website, an initial payload of the website may be loaded. In one example, the initial payload may include initial content and/or initial/root HTML.

While the initial content/payload of the website is loading, flow proceeds to operation406, where the resources stored in the local web cache are loaded into a browser DOM. In one example, when the resources stored in the local web cache are loaded into the browser DOM, the resources may be pre-compiled into the browser DOM. In another example, a loading status indicator may be presented within the native mobile application while the initial content/payload of the website is loading. In one example, loading and pre-compiling the resources stored in the local web cache into the browser DOM while the initial content/payload of the website is loading may save approximately two seconds of load time into the browser DOM. In another example, the amount of load time saved may be based on the website (e.g., web application) and/or webpage hosted by the native mobile application. In some cases, more than two seconds of download time may be saved. In other cases, less than two seconds of download time may be saved.

When the initial content/payload of the website is done loading and downloaded to the native mobile application, flow proceeds to operation408where the website and/or webpage is rendered within the native mobile application in a user interface. In one example, the website and/or webpage is rendered in a user interface of a client computing device, as discussed herein. In some cases, additional resources may be downloaded after the initial content/payload of the website is downloaded and before the website and/or webpage is rendered. In this case, as discussed above, the additional resources may include only the resources that were not pre-loaded/stored in the local web cache. In turn, in one example, storing the resources in the local web cache may save approximately three seconds of download time. In other examples, the amount of download time saved may be based on the website, web application, and/or webpage hosted by the native mobile application and/or the number of resources that need to be/are downloaded. In one case, storing the resources in the local web cache may save more than three seconds of download time. In another case, storing the resources in the local web cache may save less than three seconds of download time.

Referring now toFIG. 5, an exemplary method500for pre-loading webpage data by a native mobile application, according to an example aspect is shown. Method500may be implemented on a computing device or a similar electronic device capable of executing instructions through at least one processor. Method500begins at operation502where a request is sent from a native mobile application to a service for a latest version of a manifest file. In one example, the manifest file includes resources for rendering a webpage and/or website hosted by the native mobile application. In one example, the resources for rendering the webpage and/or website may include at least Javascript and Cascading Style Sheet (CSS) frameworks associated with the native mobile application. The service may include at least a content delivery network and a native mobile application service. In one example, the request is sent to the content delivery network.

When the request is sent from the native mobile application to the service for a latest version of a manifest file, flow proceeds to decision operation504where it is determined whether the manifest file is a latest version. For example, the manifest file may be tagged with a version number. In this regard, the request for the manifest file sent to the service may indicate which version of the manifest file is currently stored in the local web cache. In this regard, when the request for the manifest file is sent to the service, the service may determine whether it has a later and/or latest version of the manifest file. When the service determines it does not have a later version of the manifest file, a download of the latest manifest file is not needed and flow proceeds back to operation502where a request is sent from a native mobile application to a service for a latest version of a manifest file (e.g., upon the next opening/launching of the native mobile application).

When the service determines it has a later and/or latest version of the manifest file, flow proceeds to operation506where the latest version of the manifest file is downloaded from the service. In one example, up to 30 files/scripts and/or 1.5 MB of data may be downloaded from the service. In other examples, more than 30 files/scripts and/or 1.5 MB of data may be downloaded. In another example, less than 30 files/scripts and/or 1.5 MB of data may be downloaded. In one example, approximately 20 files/scripts may be downloaded. In one example, downloading the manifest file from the service takes approximately 3 seconds.

When the latest version of the manifest file is downloaded from the service, flow proceeds to operation508where the latest version of the manifest file is stored in a local web cache. The native mobile application may store the latest version of the manifest file in the local web cache before the webpage hosted by the native mobile application is accessed, hosted, and launched. In this regard, the native mobile application is storing resources associated with a specific website and/or web application associated with the native mobile application. In some cases, the website may never be accessed (e.g., a user may never go to the website) even when the resources are stored in the local web cache. In other cases, when a user accesses the website through the native mobile application, by pre-loading/storing the latest version of the manifest file in the local web cache, the website and/or webpage may be rendered quickly and efficiently, ultimately resulting in a satisfying user experience.

The term rendering as used herein generally refers to the various capabilities employed in various computing architectures to assemble information that can then be used by other capabilities to generate an image or images. Within the context of methods400and500, for example, rendering a webpage, for example, generally refers to assembling the information or data used to generate an image or images that together result in the rendered webpage/website. Animation or other dynamics may also be used to achieve certain effects.

However, it may be appreciated that other perspectives on rendering may be considered within the scope of the present disclosure. For example, rendering as used herein may also, in some scenarios, be considered to refer to the various capabilities employed by various computing architectures to generate an image or images from information assembled for that purpose. With respect to the methods400and500, rendering a webpage may refer to generating an image or images, from information assembled for that purpose, that together result in the webpage, which can then be displayed.

It may also be appreciated that rendering in some scenarios may refer to a combination of the aforementioned possibilities. For example, rendering in some scenarios may refer to both assembling the information used to generate an image or images for a webpage and then generating the image or images of the webpage. In addition, a wide variety of other steps, processes, and stages may occur within the context of presenting views of an application, all of which may be considered part of presenting a view. Thus, yet one other variation on methods400and500includes, but is not limited to, presenting a webpage and/or website.

FIG. 6illustrates computing system601that is representative of any system or collection of systems in which the various applications, services, scenarios, and processes disclosed herein may be implemented. Examples of computing system601include, but are not limited to, server computers, rack servers, web servers, cloud computing platforms, and data center equipment, as well as any other type of physical or virtual server machine, container, and any variation or combination thereof. Other examples may include smart phones, laptop computers, tablet computers, desktop computers, hybrid computers, gaming machines, virtual reality devices, smart televisions, smart watches and other wearable devices, as well as any variation or combination thereof.

Computing system601may be implemented as a single apparatus, system, or device or may be implemented in a distributed manner as multiple apparatuses, systems, or devices. Computing system601includes, but is not limited to, processing system602, storage system603, software605, communication interface system607, and user interface system609. Processing system602is operatively coupled with storage system603, communication interface system607, and user interface system609.

Processing system602loads and executes software605from storage system603. Software605includes native mobile application606, which is representative of the native mobile applications discussed with respect to the precedingFIGS. 1-5. When executed by processing system602to enhance rendering of hosted webpages, software605directs processing system602to operate as described herein for at least the various processes, operational scenarios, and sequences discussed in the foregoing implementations. Computing system601may optionally include additional devices, features, or functionality not discussed for purposes of brevity.

Referring still toFIG. 6, processing system602may comprise a micro-processor and other circuitry that retrieves and executes software605from storage system603. Processing system602may be implemented within a single processing device, but may also be distributed across multiple processing devices or sub-systems that cooperate in executing program instructions. Examples of processing system602include general purpose central processing units, application specific processors, and logic devices, as well as any other type of processing device, combinations, or variations thereof.

Storage system603may comprise any computer readable storage media readable by processing system602and capable of storing software605. Storage system603may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. Examples of storage media include random access memory, read only memory, magnetic disks, optical disks, flash memory, virtual memory and non-virtual memory, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other suitable storage media. In no case is the computer readable storage media a propagated signal.

In addition to computer readable storage media, in some implementations storage system603may also include computer readable communication media over which at least some of software605may be communicated internally or externally. Storage system603may be implemented as a single storage device, but may also be implemented across multiple storage devices or sub-systems co-located or distributed relative to each other. Storage system603may comprise additional elements, such as a controller, capable of communicating with processing system602or possibly other systems.

Software605may be implemented in program instructions and among other functions may, when executed by processing system602, direct processing system602to operate as described with respect to the various operational scenarios, sequences, and processes illustrated herein. For example, software605may include program instructions for implementing enhanced rendering of hosted webpages.

In general, software605may, when loaded into processing system602and executed, transform a suitable apparatus, system, or device (of which computing system601is representative) overall from a general-purpose computing system into a special-purpose computing system customized to facilitate enhanced rendering of hosted webpages. Indeed, encoding software605on storage system603may transform the physical structure of storage system603. The specific transformation of the physical structure may depend on various factors in different implementations of this description. Examples of such factors may include, but are not limited to, the technology used to implement the storage media of storage system603and whether the computer-storage media are characterized as primary or secondary storage, as well as other factors.

User interface system609is optional and may include a keyboard, a mouse, a voice input device, a touch input device for receiving a touch gesture from a user, a motion input device for detecting non-touch gestures and other motions by a user, and other comparable input devices and associated processing elements capable of receiving user input from a user. Output devices such as a display, speakers, haptic devices, and other types of output devices may also be included in user interface system609. In some cases, the input and output devices may be combined in a single device, such as a display capable of displaying images and receiving touch gestures. The aforementioned user input and output devices are well known in the art and need not be discussed at length here.

User interface system609may also include associated user interface software executable by processing system602in support of the various user input and output devices discussed above. Separately or in conjunction with each other and other hardware and software elements, the user interface software and user interface devices may support a graphical user interface, a natural user interface, or any other type of user interface.

Communication between computing system601and other computing systems (not shown), may occur over a communication network or networks and in accordance with various communication protocols, combinations of protocols, or variations thereof. Examples include intranets, internets, the Internet, local area networks, wide area networks, wireless networks, wired networks, virtual networks, software defined networks, data center buses, computing backplanes, or any other type of network, combination of network, or variation thereof. The aforementioned communication networks and protocols are well known and need not be discussed at length here. However, some communication protocols that may be used include, but are not limited to, the Internet protocol (IP, IPv4, IPv6, etc.), the transfer control protocol (TCP), and the user datagram protocol (UDP), as well as any other suitable communication protocol, variation, or combination thereof.

In any of the aforementioned examples in which data, content, or any other type of information is exchanged, the exchange of information may occur in accordance with any of a variety of protocols, including FTP (file transfer protocol), HTTP (hypertext transfer protocol), REST (representational state transfer), WebSocket, DOM (Document Object Model), HTML (hypertext markup language), CSS (cascading style sheets), HTML5, XML (extensible markup language), JavaScript, JSON (JavaScript Object Notation), and AJAX (Asynchronous JavaScript and XML), as well as any other suitable protocol, variation, or combination thereof.

Among other examples, the present disclosure presents systems comprising: at least one processor; and memory encoding computer executable instructions that, when executed by the at least one processor, perform a method for accelerating loading, parsing, and rendering of a web page hosted by a native mobile application, the method comprising: storing a manifest file including at least resources for rendering the webpage hosted by the native mobile application in a local web cache; sending a request, via the native mobile application, to a website associated with the native mobile application for the webpage; while initial content of the webpage is loading, loading the resources stored in the local web cache into a browser document object model (DOM); and rendering the webpage within the native mobile application in a user interface. In further examples, the method further comprises sending a request to the website for additional resources for rendering the webpage, wherein the additional resources include resources not included in the manifest file. In further examples, the method further comprises downloading the additional resources. In further examples, the method further comprises loading the additional resources into the browser DOM. In further examples, the resources for rendering the web page hosted by the native mobile application include at least Javascript and Cascading Style Sheets (CSS) frameworks associated with the native mobile application. In further examples, the method further comprises while the initial content of the webpage is loading, pre-compiling the resources for rendering the webpage in response to loading the resources stored in the local web cache into the browser document object model (DOM). In further examples, the method further comprises while the initial content of the webpage is loading presenting a loading status indicator within the native mobile application.

Further aspects disclosed herein provide an exemplary computer-implemented method for pre-loading webpage data by a native mobile application, the computer-implemented method comprising: sending a request from the native mobile application to a service for a latest version of a manifest file, wherein the manifest file includes at least resources for rendering a webpage hosted by the native mobile application; when the service has the latest version of the manifest file, downloading the latest version of the manifest file from the service; and storing the latest version of the manifest file in a local web cache. In further examples, the computer-implemented method further comprises sending a request from the native mobile application to the service for a latest version of a manifest file in response to launching the native mobile application. In further examples, the resources for rendering the web page hosted by the native mobile application include at least Javascript and Cascading Style Sheets (CSS) frameworks associated with the native mobile application. In further examples, the computer-implemented method further comprises in response to receiving a selection of an icon associated with a website in the native mobile application, sending a request for the webpage to the website. In further examples, the computer-implemented method further comprises while an initial payload associated with the webpage hosted by the native mobile application is loading, loading the resources stored in the local web cache into a browser document object model (DOM). In further examples, the computer-implemented method further comprises receiving the initial payload associated with the webpage hosted by the native mobile application from the website. In further examples, the computer-implemented method further comprises sending a request to the website for additional resources for rendering the webpage hosted by the native mobile application, wherein the additional resources include resources not included in the manifest file. In further examples, the computer-implemented method further comprises downloading the additional resources for rendering the webpage hosted by the native mobile application. In further examples, the computer-implemented method further comprises rendering the webpage within the native mobile application in a user interface.

Additional aspects disclosed herein provide exemplary systems comprising one or more computer readable storage media; and program instructions stored on the one or more computer readable storage media that, when executed by at least one processor, cause the at least one processor to at least: in response to receiving a selection of a native mobile application icon, launch a native mobile application associated with the native mobile application icon; send a request to a service for a manifest file, wherein the manifest file includes at least resources for rendering a web page hosted by the native mobile application; download the manifest file from the service; and store the manifest file in a local web cache. In further examples, the service includes at least a content delivery network and a native mobile application service. In further examples, the manifest file is a latest version of the manifest file. In further examples, the resources for rendering the web page hosted by the native mobile application include at least Javascript and Cascading Style Sheets (CSS) frameworks associated with the native mobile application.

Techniques for accelerating loading, parsing and rendering of webpages hosted by a native mobile application are described. Although aspects are described in language specific to structural features and/or methodological acts, it is to be understood that the aspects defined in the appended claims are not necessarily limited to the specific features or acts described above. Rather, the specific features and acts are disclosed as example forms of implementing the claimed aspects.

A number of methods may be implemented to perform the techniques discussed herein. Aspects of the methods may be implemented in hardware, firmware, or software, or a combination thereof. The methods are shown as a set of blocks that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. Further, an operation shown with respect to a particular method may be combined and/or interchanged with an operation of a different method in accordance with one or more implementations. Aspects of the methods may be implemented via interaction between various entities discussed above with reference to the touchable user interface.

Additionally, while the aspects may be described in the general context of native mobile application systems that execute in conjunction with an application program that runs on an operating system on a computing device, those skilled in the art will recognize that aspects may also be implemented in combination with other program modules. In further aspects, the aspects disclosed herein may be implemented in hardware.

Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that aspects may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and comparable computing devices. Aspects may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.