This document discusses different types of mobile app development approaches including native, cross-platform, web-based, and hybrid. It outlines the pros and cons of each approach in developing apps for various mobile operating systems such as iOS, Android, and others. Native apps are easiest to develop for a single platform but have low code reusability, while cross-platform and hybrid apps have higher code reusability but limited access to native device APIs.

1. 13390265 - Akash Kubavat

2. • Native
• Cross-Platform
• Web-based
• Hybrid

3. Scenario with leading mobile operating systems
* IBM, Native, web or hybrid mobile app development, 2012. IBM Software Thought Leadership
White Paper

8. Cloud service
generates app, which
can be distributed to…
Java based
core coding

9. • iOS
• Android
• BlackBerry
• Windows
• Symbian
• Palm
• Samsung Bada

11. • Binary executable per device  easy to recognize
• Easy access to API’s available by OS  faster performance
• SDK’s are platform-specific  easy to develop

12. • Code Reusability  Low
• Development & maintenance  Time-consuming & expensive.
• Designers are required to be familiar with different UI components of
each OS  more complexity and confusion for single developer
• Upgrade flexibility  Low

13. • Single source codebase  easy to develop and maintain
• Works with different target platforms  in-budget and in-time
• Extension of ‘known’ background  no additional languages

14. • Limited native API access, ultimately ‘a library’ is using library
• Doesn’t generate source code  no further tweaking, like LongPress
event of TextField
• If web-based  run on browser, which ‘it self’ is an application
• UI mapping is the biggest issue , like...