Cross-Platform vs Native Mobile Application Development
Native applications are meant to run on a specific device platform. They are developed in a programming language Native to the device and the operating system and requires one specific app to be created for one target platform. Native apps are developed in iOS, Android and Windows phone.
Here we have listed the pros and cons of native mobile app development
|Pros of Native mobile app development||Cons of Native mobile app development|
|Access to all the features of the device and operating system.||Two or more apps are required to be developed|
|Utilising advanced features such as access to USB input, complex networking etc.||No code can be shared between the version of separate apps|
|No limitations in terms of app performance and speed||Slow development time|
|No limitation in terms of advanced user interface customisation||Testing time is affected as separate codebase needs to be tested.|
Pros and Cons of cross-platform mobile app development
|Code sharing functionality between versions of the app.||No code sharing facility|
|User interface is rendered using native controls||User interface customisation dependent on framework support|
Examples of Cross-platform includes:
- Adobe air
Main disadvantages of Adobe Air over other cross platforms
- Database access limited to SQLite or web services.
- No threading support.
- No model for commercial components
- Major security concerns
- Synchronization service depends on LiveCycle, the server side piece which runs on J2E application servers.
- Lack of UI standards leading to annoying inconsistencies between AIR applications.
The major drawback of Adobe air over native application development is that at time of up-gradation in adobe air code in each module needs to be altered while in case of native it is upgraded automatically.