{"id":579,"date":"2017-11-05T22:19:34","date_gmt":"2017-11-05T22:19:34","guid":{"rendered":"http:\/\/www.netexl.com\/blog\/?p=579"},"modified":"2026-04-02T10:17:42","modified_gmt":"2026-04-02T10:17:42","slug":"responsive-bootstrap-and-jquery-game-template-for-mobile","status":"publish","type":"post","link":"https:\/\/www.netexl.com\/blog\/responsive-bootstrap-and-jquery-game-template-for-mobile\/","title":{"rendered":"Responsive Bootstrap and JQuery Game Template for Mobile"},"content":{"rendered":"

For mobile web app templates, Jquery Mobile<\/a> has been a popular choice but it comes with its own set of issues when we have multiple pages in the game since it makes ajax calls to load the pages and if there are specific things which are required to be handled on each page then it becomes even more complex to handle those scenarios. The alternate is to have a simple Bootstrap and JQuery based template with multiple pages which is simple and works just like a website. The problem here is that the pages are loaded again and again whenever we navigate from one page to another. This is not an ideal scenario\u00a0for mobile web apps\u00a0since all external libraries are required to be initialized on all pages which\u00a0is not required\u00a0and unnecessary work for processor. For example,\u00a0if you compiled your web app using PhoneGap and\u00a0are using a plugin to play audio. You need to initialized the audio plugin on all pages wherever you\u00a0need to\u00a0use the plugin. In ideal scenario, the plugin should only be initialized once when app is first opened and should be available on all pages of your app\u00a0which is why the preferred approach on mobile is to have single HTML file.<\/p>\n