Mobile applications come in two distinct formats: native apps and web apps. Due to differences in their underlying technology,
Each approach has inherent advantages and drawbacks.
Mobile Web Apps:
A mobile web app is a web application formatted for smartphones and tablets, and accessed through the mobile device’s web browser. Like a traditional web application, a mobile web app is built with three core technologies: HTML (defines static text and images), CSS (defines style andpresentation), and JavaScript (defines interactions and animations). .Since web apps are browser-based, they’re intended to be platform and device independent, able to run on any web-enabled smartphone or tablet. A mobile web app is normally downloaded from a central web server each time it is run, although apps built using HTML5 (described below) can also run on the mobile device for offline use.
Advantages:
1) The key advantage of mobile web apps over native mobile apps is cross-platform compatibility, allowing them to reachthe broadest audience for the least effort. They’re relatively cheap, easy, and fast to build, although some device-specific customization is usually required. Mobile web browsers are fairly standardized, making it much easier to create a universal mobile web app than a native one.
2) Web apps are also cheaper and easier to maintain than native apps for the same reasons, using cross-platform applets rather than keeping up with changes across different devices.
3) Simple, ubiquitous access: Users don’t have to download an application, but simply access a URL via their mobile browser which instantly delivers the most up-to-date application to their device. They can then bookmark the URL for repeat use.
Disadvantages:
1) Although improvements are ongoing, mobile browsers have limited capabilities compared to traditional desktop browsers. Functionality is similar for the major players (Apple, Android, RIM, Windows), but falls off sharply on other platforms. Depending on what platforms need to be supported, the solution may be limited to the lowest common denominator, giving the app a clunky” look, or require time-consuming customization across browser versions.
2) Web apps generally1 cannot access the on-board hardware and software on a mobile device. Requirements such as camera control, direct GPS control (there is limited access to current location), PIM integration, or control of the phone app will rule out web apps right away. Heavy/complex custom graphics (gaming, etc.) also cannot be supported.
3) Web apps generally require a connection to function, with performance issues if the website is slow or unavailable. When users are on the go without Wi-Fi coverage, they have to pay for connection time to network operators. In some countries the cost is minimal, but in others can be a showstopper. (This changes with HTML5, which makes web app content available in offline mode so users can still access the app even if they do not have cell reception or connection to a Wi-Fi network.
Mobile Native Application:
A native mobile app is built specifically for a particular device and its operating system. Unlike a web app that is accessed over the internet, a native app is downloaded from a web store and installed on the device. Native apps are written in Java, Objective C, or some other programming language. Native apps have a major advantage over web apps—the ability to leverage device-specific hardware and software. This means that native apps can take advantage of the latest technology available on mobile devices and can integrate with on-board apps such as the calendar, contacts, and email. However, this is a double-edged sword: while mobile technology is wildly popular, it is also constantly changing and highly fragmented. This makes the task of keeping up with the pace of emerging technology onerous and costly, especially on multiple platforms.
Advantages:
A richer, more compelling user experience: Native apps can leverage the capabilities of the mobile device, including onboard hardware (such as GPS, camera, and graphics) and software (such as email, calendar, contacts, picture/video gallery, file manager, and home screen widget areas).
Ability to run offline: Since the application remains installed on the device from the original download, no internet connection is required. Users get peak performance at all times, with all grap
Disadvantages:
Content publishers have to share information about their subscribers with the app store, an arrangement that frustrates publishers (particularly media companies). + For a native app to work across multiple devices, separate versions of the app are required. The fragmented nature of the mobile industry means that developing, testing, and porting apps for different environments costs money—particularly with maintenance and promotion costs. Cross-platform frameworks can make things easier, but time and cost remain a fact of life when developing for rich functionality on multiple mobile platforms. (The next section explores development issues for mobile apps in more detail
