Mobile Web vs. Native Apps: Deciding the Strategy for 2011

The Mobile Dilemma

As smartphone adoption scales, organizations must answer a fundamental question: Should we build a native mobile application (using Objective-C for iOS and Java for Android) or a web-based HTML5 mobile site?

Each path requires different skills, budgets, and distribution strategies.

Native Applications: Performance and Access

Native apps execute directly on the mobile OS:

• ◆Pros: Maximum performance, fluid 60fps animations, rich gestural interactions, and complete access to device hardware APIs (contacts, cameras, background tasks).
• ◆Cons: High development cost (requiring separate iOS and Android teams) and app store approval delays.

HTML5 Mobile Web: Universal Distribution

Mobile web apps run inside the mobile browser:

• ◆Pros: Write once, run anywhere. Immediate deployment without app store gatekeepers, and lower development costs.
• ◆Cons: Limited performance, no offline execution by default, and restricted access to local hardware APIs.

The Hybrid Bridge: PhoneGap

PhoneGap (Cordova) compiles web code (HTML, CSS, JS) inside a native container shell, allowing deployment to app stores while accessing local APIs:

// Accessing hardware features via PhoneGap API in 2011
document.addEventListener("deviceready", onDeviceReady, false);

function onDeviceReady() {
    navigator.notification.vibrate(500); // Trigger device vibration
}

Decision Matrix