Tersus: Native iPhone Applications vs. iPhone Web Applications

Native iPhone Applications vs. iPhone Web ApplicationsDate: Oct 31, 2012Tags:iPhone,Native vs. WebComparison of Native and Web iPhone Applications

Native iPhone Application

iPhone Web Application

Running

Over the iPhone's operating system (OS X iPhone)

Inside the Safari browser on the iPhone

Development

Unless using Tersus, is similar to developing Mac OS X applications (iPhone SDK, Objective-C)

Is similar to developing desktop web applications

Testing

Can be tested in the iPhone simulator, but full testing requires an iPhone device

Can be tested with the iPhone simulator and a Safari browser on the desktop, but full testing requires an iPhone device

Access to device capabilities

Full access (camera, accelerometer, etc.)

Cannot access all device capabilities

Access to device resources

Can access device resources (file system, contacts, calendar, etc.), but there are restrictions

Cannot access all device resources

Distribution

Typically through Apple's App Store (Wikipedia: "loading an application onto the devices is only possible after paying a Apple Developer Connection membership fee").

Needs no special distribution mechanism (simply go to the application's URL)

Deciding What Type of Application to Develop - Pros and ConsiPhone Web applications are simpler to develop and deploy, while native iPhone applications can have much richer functionality.You would generally prefer a native application when you need rich functionality and access to the device capabilities and resources, and also if you plan a mass distribution of the application through Apple's App Store.On the other hand, if you don't have a Mac, you don't know Objective-C, or you need a cross-device application, you would probably go for a web application.

Native iPhone Application

iPhone Web Application

Prerequisites

Download the iPhone SDK
Enroll to Apple's developer program (a few days + $100

download and install the Safari browser

Required Skills

Learn Objective-C (takes at least a few weeks)

Learn some set of technologies for developing

Limitations

Cannot use device capabilities and resources

Cross Device

Basically yes (can run on non-iPhone devices), but not always trivial

Offline Work

Almost always connected to the internet, but application can work offline as well

Unless specifically designed for offline work (which is not common), only works when an internet connection is available

Development

Not simple (mastering the iPhone SDK takes time even for Mac developers)

Not simple if you are not experienced with developing web applications, but not much more complex than developing desktop web applications if you are

Testing

Easy with the iPhone simulator

Easy with a Safari browse

Distribution

Unless limited to a small number of devices, Only through Apple's App Store, and requires Apple's approval

Easy and not restricted

How Using Tersus Changes the PictureTersus allows you to overcome most of the disadvantages of both native and web iPhone applications:

Developing with Tersus is simpler than developing with the iPhone SDK (for native applications) or with the standard web technologies (for web applications).

For the most parts of the application, you can develop the application once and then deploy it as either a native iPhone application or as an iPhone web application.

Specifically, you can start with a web application, work with it for some time, and then deploy the application as a native iPhone application.

This means you don't have enroll to Apple's developer program nor pay any fee to Apple until you have a working web application that people can use on their iPhones.

Furthermore, you don't need a server of your own to expose your application through the internet. You can host the application on one of the Tersus servers.

Note that Tersus also allows web application to use a client side database and work offline - you don't need to switch to a native application for this.

See this page for details regarding access to specific device capabilities, in native and web applications.

See Also: server access in native vs. web mobile applicationsSee Also:

To use the full functionality of this web site, JavaScript needs to be turned on.

For best results, use the Firefox browser..

Loading ...