html5.pdf

Worklight® - Extend Your Business White Paper HTML5, Hybrid or Native Mobile App Development Contents Intro 3 Introducing the Approaches 3 Native Applications3 Mobile Web Applications6 Hybrid Applications 7 Comparing the Different Approaches 8 Choosing the Right Approach 10 Scenarios for the Native Approach 10 Scenarios for the Web Approach 11 Scenarios for the Hybrid Approach 11 Summary 12 About Worklight13 2 Intro Many organizations taking their first steps to implement a mobile strategy are facing an important decision that will influence the results of this initiative. The process of choosing a development approach for a mobile application, namely native, web or hybrid, entails many parameters such as budget, project timeframe, target audience and application functionality to name a few. Each approach carries inherent benefits and limitations, and finding the one that best addresses the organization’s needs could be a challenging task. The purpose of this whitepaper is not to identify the best development approach, as such does not exist, but rather to list the pros and cons each carries and describe the different scenarios, or enterprise requirements, that best fit one or the other. Introducing the Approaches Native Applications Native applications have binary executable files that are downloaded directly to the device and stored locally. The installation process can be initiated by the user, or in some cases, by the IT department of the organization. The most popular way to download a native app is by visiting an application store such as Apple’s App Store, Android’s Marketplace, or BlackBerry’s App World, but other methods exist and are sometimes provided by the mobile vendor. Once the app has been installed on the device, the user l