This document evaluates and compares four mobile application paradigms: native apps, mobile widgets, mobile web apps, and HTML5 mobile apps. It assesses each paradigm for developers, mobile users, and service/content providers. The evaluation finds that native apps provide the best user experience while HTML5 apps allow development for multiple platforms with one codebase. Developers prefer HTML5, but users prefer native apps. The document also experimentally verifies the paradigms by building sample apps of each type.

1. Evaluation Of Mobile App
Paradigms
Ngu Phuc Huy & Do vanThanh
2012

2. Outline :
• Introduction.
• The aim of paper.
• Related works.
• General terms.
• The mobile app paradigms:
- Mobile native applications.
- Mobile widget.
- Mobile web applications.
- HTML5 mobile application.
• Evaluation and result:
- For developers.
- For mobile users.
- For service/content provider.
• Verification.
• Conclusion.
• References.

3. which mobile application paradigm
fits better to what type of application
and usage ?
Introduction :
The development
cost
User experience
Sale revenues of
mobile apps

4. The aim of paper :

5. RELATED WORKS:
It provide both a formal evaluation
and practical verification of the four
mobile app paradigms.
It provide both a formal evaluation
and practical verification of the four
mobile app paradigms.
DifferentDifferent

6. General terms :

7. The mobile app paradigms :

8. The mobile app paradigms :

9. The mobile app paradigms :

10. The mobile app paradigms :

11. EVALUATION AND RESULT:

12. For developers :
 Native apps and HTML5 are the best selection
 To build a mobile app that requires accelerated
graphic processing. ( using native )
 More straightforward content driven service
(HTML5)
 Widgets are valuable for developers when they
want to make a lightweight, and portable mobile
app.
 Mobile web app paradigm obtains the lowest
grading .

13. For mobile users :
 Native apps are very robust.
 HTML5 mobile apps are the second choice of
mobile users since they are lightweight.
 Mobile widgets come third because they are
lightweight and quite convenient to use.
 Users are not interested in mobile web apps.

14. For service/content provider :
 HTML5 mobile apps are the best choice.
Service providers can build an HTML5 mobile
app once and distribute it everywhere.
 Mobile Web apps work in the same way and get
the second position in the race.
 widgets and native apps have the lowest grading
because of platform fragmentation.

15. VERIFICATION:
 Native application :
Android platform , Eclipse , Java .
 HTML5 application :
The user load the app onto their device and run it on
browser .
 PhoneGap application :
HTML5 , CSS3 , JavaScript.

16. Result :
Developers prefer HTML5 mobile app to native app
paradigm .
For users, it is understandable that native app is more
preferable than the HTML5 mobile app paradigm.
VERIFICATION:

17. Key finding and recommendation :
Native apps are well-known for their fast and
responsive user interface, and the seamless
capability to access hardware features.
PhoneGap framework also lets developers make
the HTML5 app access built-in apps and run on
multiple platforms effectively.
VERIFICATIO:

18. CONCLUSION:

19. [1] Huy, Ngu Phuc, and Do vanThanh. "Evaluation of
mobile app paradigms."Proceedings of the 10th
International Conference on Advances in Mobile
Computing & Multimedia. ACM, 2012.
References: