This is a simple PhoneGap application based on Twitter Bootstrap library. It should be ready for PhoneGap Build. Use or fork it, if you want to see, how Bootstrap framework works and looks inside a mobile application or if you need a base app for building PhoneGap applications using Bootstrap.

This demo contains or includes following things:

• Twitter Bootstrap itself and examples of using it,

• Font Awesome font library along with some cool examples,

• Some examples of using AJAX / JSON calls from PhoneGap application,

• Very cool and superb customizable digital display, purely in Javascript, from 3quarks.com.

• Simple theme (stylesheet switcher) allowing dynamic (client-side) look change plus all the free Bootstrap themes / styles from Bootswatch.com.

• Multi-language, application auto-translation system, based on i18next library. Some example locales (English, Polish, German and Chinese) included.

• Heavily modified version of Boostrap Slider. My modifications includes theming (slider will adapt to any Bootswatch style), adding some new features and fixing many small bugs.

As you can see, there are a lot of things here, which makes application big and slow. In most projects, however, you'll only need part of them, so don't worry. This is only an example.

Tested on five different devices and five Android versions:

• Sony Xperia E with Android 4.1.1,
• GSmart Rola G1317D with Android 2.2.2.
• Kiano Core 10.1 tablet with Android 4.1.1,
• LG GT540 with Android 2.3.3 and CyanogenMod 7,
• Samsung Galaxy Nexus with Android 4.3 (previously on 4.2.2).

Seems fine on all of them (see below notice for devices with Android 2.x on-board).

For clarity of quite large code (many Bootstrap, Javascript and PhoneGap examples), one large HTML file (index.html) is split into three tabs. Contents of each tab are loaded via AJAX upon app's startup. It was proven, that on some devices (mostly Android 2.x.x) this can fail, with a system-level error message and immediate application shutdown.

Don't be confused with this, as such solution is meant for this demo only. In real-life application, that you will be designing, if you decide to split content into separate files, these will be separate pages (like main app windows, configuration, log, etc.), accessible via normal links, not AJAX loads. This way, they won't be affected by above mentioned problem.

You may leave AJAX-based conent load only, if you decide to drop support for Android 2.x.x entirely.