This is because navigating between pages will require scripts, assets, etc., to be reloaded. This is easy to forget as your application gets larger.Įven if you choose not to use Cordova, creating a mobile application without using a single page architecture will have serious performance implications. If you do not use a SPA, and your user clicks to go from one page to another, you will have to wait for deviceready to fire again before you make use of a plugin. A Cordova application must wait for the deviceready event to fire before any plugins may be used.

Using a SPA can help you organize your application in a more efficient manner, but it also has specific benefits for Cordova applications. After you load Gmail, mail views, editing, and organization are all done by updating the DOM instead of actually leaving the current page to load a completely new one.

SPAs are commonly used for more complex client-side applications. The user loads an initial set of resources (HTML, CSS, and JavaScript) and further updates (showing a new view, loading data) is done via XHR requests. Loosely defined, a SPA is a client-side application that is run from one request of a web page. Also, if you see something that can be improved, please contribute! Best Practices for Cordova Apps 1) SPA Is Your Friendįirst and foremost - your Cordova applications should adopt the SPA (Single Page Application) design. Consider this your launching point for your growth as a Cordova developer.

The following document offers advice on various topics relating to best practices, testing, upgrades, and other topics, but is not meant to be prescriptive. For developers who have an understanding of how to use the Cordova CLI and make use of plugins, there are a few things you may want to consider researching next to build better, more performant Cordova applications.

Iphone safari inspector emulator mac