Universal Access

jQuery Mobile applications are universally accessible to all devices with a browser. This is a favorable reach advantage to jQuery Mobile’s distribution model (see Figure 1–1). Nearly every mobile device ships with a browser. If your app is universally accessible to this broad spectrum it is a major competitive advantage. The following is a complete listing of supported devices in jQuery Mobile 1.0, which includes most phones, tablets, desktop browsers, and even e-readers.

Figure 1–1. jQuery 1.0 Mobile Browser Coverage

Supported Devices:

• Phones/Tablets
  • Android 1.6+
  • BlackBerry 5+
  • iOS 3+
  • Windows Phone 7
  • WebOS 1.4+
  • Symbian (Nokia S60)
  • Firefox Mobile Opera Mobile 11+
  • Opera Mini 5+
• Desktop browsers
  • Chrome 11+
  • Firefox 3.6+
  • Internet Explorer 7+
  • Safari
• e-readers
  • Kindle
  • Nook

NOTE: For an up-to-date listing of all supported platforms, refer to jQuery Mobile’s supported platforms page (see http://jquerymobile.com/gbs/).

Comparatively, native application development has a very restrictive distribution model (see Figure 1–2). Native applications are only available on their native operating system. For example, an iPhone app is only accessible from an iOS device. If your goal is to reach the most consumers possible this distribution model is limited. Fortunately, jQuery Mobile apps are not restricted by this distribution barrier.

Figure 1–2. Native OS Coverage

n addition to universal access, jQuery Mobile applications can take advantage of the instant deployment capabilities we have grown accustomed to on the Web. For jQuery Mobile apps, no barriers exist in regards to certification reviews that are required within the native app distribution model. Mobile Web apps can be updated and deployed instantly to your production users. For example, I was recently working on a native enterprise application that needed an update and it took a week for the re-certification process to approve the change. In all fairness, the native app stores have options to submit urgent updates but the point is you will be dependent upon a third party to push the update to their store. The instantaneous deployment model of the Mobile Web is very advantageous in this regard.CopycopyHighlighthighlightAdd NotenoteGet Linklink