Mobile: WAP vs. Native Application Development (Apps)

 

There are development platform options to consider when building a mobile application. Here is a comparison of WAP vs. Native platform solutions (Apps). This includes areas to consider not only upon initial deployment but post launch.

WAP vs. Native Application Decision (Apps)

Apps 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

WAP Advantages:

• 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

Apps 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

WAP Disadvantage:

• 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