May.04, 2010 by Chris Chodnicki
Mobile: WAP vs. Native Application Development Matrix
Categories: Advances in technology, Business Development, Mobile, Thought Leadership
There are development platform options to consider when building a mobile application. Here is a comparison of WAP vs. Native platform solutions. This includes areas to consider not only upon initial deployment but post launch.
WAP vs. Native Application Decision Matrix
|
Native
|
WAP
|
Advantages
|
- Library update
- Direct technical support
- User has more control
- App store and device portal solution
- Can apply existing User Interface (UI) standard for mobile users
- Better UI design result, can take full advantage of each platform
- Data persistent – data could be available even with no network connection; more option on data cached
|
- Open Source solution
- One programming language or solution could be applied for different browsers
- Centralized – more control – easy to update
- UI design takes less time and code to implement
- Fast development
- No code size and memory limitations
- Better integrated tracking
|
Disadvantage
|
- Frequent library updates – Fluid technology
- Not all are Open Source solution
- Different programming languages
- Different UI design pattern
- Slow development time
- Code size and memory limitation
- Update depends on the app store or user to update
|
- Library update could be slow from time to time
- Limited direct technical support
- Library is still limited to utilize the native features
- Browser rending issue for different version and browsers
- Data persistent – limited option and fewer data space can be cached
|
Tags: Chris Chodnicki, Mobile, Native Platform, WAP
August 2nd, 2010 on 2:52 pm
I have been looking around for this kind of information and i think that i have found it on your site. Bookmarked!
November 6th, 2011 on 7:59 am
I always was interested in this subject and nonetheless am, thankyou for posting .