Native

International Journal of Current Trends in Engineering & Research (IJCTER)
e-ISSN 2455–1392 Volume 2 Issue 6, June 2016 pp. 563 – 572

Scientific Journal Impact Factor : 3.468
http://www.ijcter.com
Native Vs Hybrid Apps

Ketan Anant More1, Ms.Priya Chandran2
1,2
Bharati Vidyapeeth’s Institute of Management Information Technology, University of Mumbai,
Maharashtra, India
Abstract—Objective of this study is to compare Native Apps Vs Hybrid Apps. The comparative
study is based on the advantages and disadvantages between Native and Hybrid Apps. We have
studied seven popular Hybrid Apps frameworks, Ionic and Titanium while comparing with native
frameworks. Based on the comparative study, the developers can choose the best Mobile Application
option to build the mobile app.
Keywords— Native App, Hybrid App, Ionic, Titanium, Phone gap, Sencha Touch, Kenda UI,
Mobile Angular UI, Intex XDA
I. INTRODUCTION
In Today’s Generation are much more depended on mobile applications. So the Mobile application
development are very essential to any business organisation. We want the fast application
development in today’s environment. There are different kinds of ways to develop the mobile apps.
Also there are different frameworks to develop the mobile apps..
Businesses that need a mobile app have three available options:
1. Native apps can Built using the device’s native programming language, native apps only runs
on their designated platforms. For example, Android applications can’t run on iOS and
Blackberry applications can’t run on Android, iOS applications can’t run on Windows platform,
and so on. Native apps are distributed through their respective platform’s with marketplace/app
store and installed on the devices itself.
2. Mobile web apps run in the device’s browsers and operate across all platforms. For example, a
mobile web app works equally well on android platform, iOS platform, Blackberry platform,
and Windows Phones platform. Unlike native apps, the mobile web apps are distributed via the
webs, and are not installed on the devices itself. It’s important to note the differences between a
mobile web pages and a mobile web apps. While often confused, mobile web apps and mobile
web pages are quite different things. A mobile web page is a static HTML/CSS/JavaScript page
formatted for use on a mobile device.
3. Hybrid apps are the cross between native apps and mobile web apps. A hybrid app is a mobile
web app wrapped in a platform-specific shells. This platform-specific shell gives the
application native qualities, such as full device integration, Portability, native installation, and
app store/market distribution.
In Today’s Generation the Mobile apps development are very essential. Mobile apps
development are crucial for any business organizations. There are Native apps, Hybrid apps and
Mobile web view option for mobile development. In this research paper we focus on the Native apps
and Hybrid apps. Also we discusses on different frameworks of hybrid apps which is used to develop
the mobile apps.
@IJCTER-2016, All rights Reserved 563

Volume 02, Issue 06; June – 2016 [Online ISSN 2455–1392]
II. LITERATURE REVIEW

There is several research papers available on Mobile Apps Developments in internet. Lots of
Information on Native Apps, Hybrid Apps and Mobile Web Apps. In [15] the authors discusses the
comparison of Native app and Mobile web Apps. They show the actual strength of the native and
mobile web apps. But they did not study the hybrid apps information. In [10] the authors show the
Real Challenges in Mobile Apps Development. They have done the survey on the mobile apps
development which gives the actual use and real challenges when develop the mobile apps. In [11]
authors provides the information about cross platform development approaches of mobile application.
They gives the total information of mobile application which developed in different platforms. In
other research papers [18],[19],[20] which gives the information about HTML5 and W3C which in
hybrid apps development and Native ,Mobile web and Hybrid apps development information but
they not provides comparison between them.
In [23] the cross platforms for mobile apps development is discussed. They shows the different
platforms for new mobile apps development. In [21] shows the different stages of mobile app
development. In this research paper very essential for basic mobile apps development. But they
didn’t show the different frameworks of mobile apps development. also in [6] author shows whole
information about Ionic framework. It provides good information to develop the mobile apps using
Ionic framework. It focus on whole Ionic framework under the Hybrid Mobile Apps. In [25] authors
show the comparison study of cross platform mobile development tools. They provides the different
platforms for mobile apps.
This paper focuses on Native Apps, Hybrid Apps and its frameworks, also comparative study
between Ionic and Titanium framwork. In this study we comparing the native apps and hybrid apps.
We study the comparison between native apps and hybrid apps. Then we also study the 7 top hybrid
frameworks which use to develop the mobile apps. Then we detail study on Ionic and Titanium
framework which is the best 2 frameworks. Depends upon comparatively study between the Ionic
and Titanium we get best frameworks for mobile apps development.
III. NATIVE APPS
Native apps live on the devices and are accessed through icons on the device home screen. Native
apps are installed through an application store which is available on App stores. (such as Google
Play or Apple’s App Store). They are developed specifically for one platform, and can take full
advantages of all the device features — they can use the cameras, the GPS, the accelerometers, the
compass, the list of contacts, Bettery icon and so on. They can also incorporate gestures.
IV. HYBRID APPS
Hybrid apps are part of native apps as well as part web apps. It bridges gap between different
mobile apps. Like native apps, they live in an app store and can take advantages of the many device
features available. Like web apps, they rely on the HTML being rendered in a browser, with the
caveat which is that the browser is embedded within the apps. Often, companies build hybrid apps as
wrappers for an existing web pages; in that way, they hope to get a presence in the app store, without
spending significant efforts for developing a different apps. Hybrid apps are also very popular
because they are also allow the cross platform development of mobile apps and thus the significantly
reduces the development costs of the mobile apps development.

V. NATIVE VS HYBRID APPS

Table I.
An Explanation of How Native And Hybrid Apps Presumably Address Key Characteristics of Apps Usage and
Development
Native App Hybrid App
 HTML
 Objective-C  JavaScript
Skills/tools that needed for  C++  CSS
cross-platform apps  Java  Web programming
development  VB.net languages (i.e., Java etc.)
 C#  Mobile development
frameworks
Apps needed to reach all
4 1
major smartphone platforms
Installed on device? Yes Yes
Distribution App Store/Market App Store/Market
Full integration: for eg Full integration: for eg
(camera, microphone, GPS, (camera, microphone, GPS,
Mobile Device integration
gyroscope, accelerometer, gyroscope, accelerometer,
file upload, contact list) file upload, contact list)
 Cross-platform apps that
 Highly graphical apps
need to full devices
Best used for  Apps that need to reach access.
the large consumer
 Business apps that need
audience
to app store distributions
A. ADVANTAGES OF NATIVE APPS
1. Highly graphical
Built using the main device’s native language, and installed on the devices itself, native apps
offer the best graphics and animations. If a business needs a highly graphical applications, such as
a game, native apps are their best option. It provide graphical features.
2. App store distribution
Native apps are distributed through their own platform’s native app stores and marketplace.
While not often a requirement for business applications, app store distribution are essential for
companies that require wide consumer distribution, or need to sell their applications. It’s
important to note that hybrid apps also offer app store distribution. It is satisfied app store
distribution.
3. Device integration
Native apps are provide full access to the device’s hardware, such as its GPS sensor, contact
list, camera, microphone, gyroscopes, and accelerometer, bettery. These capabilities are essential
for any apps that require device data, like geographical location or device positions/movements.
It’s important to note that hybrid apps also offer full device integration, while mobile web apps
offer to partial integration. Device Integration very essential for any apps development.
B. DISADVANTAGES OF NATIVE APPS
1. No portability
Since each native applications only runs on one platform, businesses building native apps
must make a choice-builds for one platform or builds for multiple platforms? Unfortunately,

there’s no easy answer. As illustrated by the image below, the mobile platform landscape includes
four major smartphone platforms and four major tablet platforms. Native app not contains proper
portability. Building an app for just one platform excludes seven platforms, yet building for all
platforms requires significant time and resources.
2. Platform instability
The mobile platforms landscape is notoriously unstable. A popular platform today may
disappear in just a few years. For example, both the Blackberry and the Palm dominated the
mobile industry just 5 shorts years ago. Today's, Blackberry is struggling and Palm doesn’t exist.
There fact is, nobody knows what the mobile platform landscape will look like in another 5 years.
Companies that are choose the native approach always run the risk of wasting time and money
building for a platforms that might not last.
3. Development cost
While native apps development cost varies depending on the app’s complexity, it’s easily the
most expensive and time-consuming approach. Development costs high for native apps. For
example, Forrester Research estimates that most native apps require at least of 6 months of full-
time work, and cost between $20,000 and $150,000, depending on complexity which in
Reference [1]. It’s important to note that those estimates apply to single-platform native apps
development. The cost rises exponentially over when developing cross-platform native
applications. Based on the development cost estimates listed above, the chart in Reference [1]
outlines the cost of developing native applications.
4. Development time
As mentioned in Development cost point, Forrester Research estimates that a single native
app requires of 6 months of development time. If we try to building native apps for more than
one platforms, the time requirements rise depending on the number of developers needed and
applications complexity. Development time requires more for native apps. For example, using
just one developer for cross-platform smartphone apps development brings the development time
up to 2 years (4 applications x 6 months each). However, development time estimates become
increasingly complex when using multiple developers.
5. Maintenance cost
While all apps requires regular updates and maintenance, native apps require the most future
maintenance when compared with the other two mobile apps options. Maintenance cost depent
upon the size of native apps. Beyond regular apps maintenance, native apps must also be updates
with every new platform release in market. Additionally, businesses that build the native apps for
multiple platforms must maintains multiple applications, duplicating every change or updates
across all applications.
6. Limited control
When placed in an apps store, a native applications is completely controlled by the app store’s
owner (like Apple or Google). For example, if Apple rejects or bans a company’s app from their
app store, the company has no recourse. If Apple decides an app doesn’t meet their terms of
services, the app is removed. If another company claims copyright over an elements in the app,
the app is removed. Or, if Apple decides the app isn’t right for their store, the app is removed. The
app store model puts the companies at the mercy of a third party. All of the resources put into
their applications are wasted if that app store’s owner decides the app isn’t right for their store in
market.

C. ADVANTAGES OF HYBRID APPS

1. Native look-and-feel (without the native cost)
For businesses purpose that prefer the native apps look and feel, without the high development
costs, the hybrid apps is the method of choice. Like native apps, hybrid apps are also installed on
the device and launched like a typical applications. These native attributes make a hybrid apps
virtually indistinguishable from a native apps. In fact, many people even don’t realize that popular
―native apps‖ like LinkedIn, Foursquare, and Twitter are actually hybrid applications. It provides
Good look and feel to users.
2. Device integration
As mentioned in above point, mobile web apps offer nearly full device integration, with a
couple of exceptions. That is where hybrid apps come in. Hybrid apps offer full device access,
including the ―native-only‖ features in mobile apps, like the camera, microphone, and address
book.
3. App store distribution
While not usually a requirements for business apps, some companies needed the wide
consumer distribution offered by the apps store. For these companies, hybrid apps are the best
option. One mobile web app combined with a hybrid mobile framework lets businesses easily
create the ―native apps‖ for distribution in every major app store for new generation.
4. Inexpensive cross-platform development
While not as simple as the mobile web apps approach, building a cross-platform hybrid app is
considerably cheaper than building a cross-platform native app. Hybrid apps development
consists of building a mobile web apps and then the wrapping that apps in platform-specific native
wrappers. This process lets businesses develops cross-platform hybrid apps using their current
web development skills in market.
VI. FRAMEWORKS OF HYBRID APP
We have studied seven commonly used hybrid framework for comparison with native framework.
They are,
1. IONIC
Ionic is one of the most popular and promising HTML 5 mobile application framework. Built
using SASS, it provides many UI component to help the develop rich and interactive applications.
It uses the JavaScript MVVM framework, AngularJS to power apps. Two-way data binding,
interaction with backends services and APIs makes Angular JS a mobile developer’s common
choice. With the coming release of Angular JS 2.0, focused on mobile, its sure to gain even more
popularity.
The team at Ionic will soon be introduce an easier way to create the IONIC apps with ionic
creator. This will be released soon and will have the drag and drop functionality to get started
with apps development in minutes.
2. Mobile Angular UI
Mobile Angular UI is an hybrids's HTML 5 framework which uses the bootstrap 3 and
Angular JS to create interactive mobile apps.
The main features of Mobile Angular UI includes:
• Bootstrap 3
• Angular JS
• Bootstrap 3 mobile components such as the switches, overlays and sidebars which are
missing in normal bootstrap components.

Responsive media queries which are stripped out of bootstrap as separate files, you only need
to include what you need. Mobile Angular UI doesn not have any JQuery dependencies, all you
need are some Angular JS directives to create awesome mobile user experiences.
3. Intel XDK
Intel XDK is the cross platform application tool developed by Intel company. Getting started
with Intel XDK is very easy that all you need is to download their application which is free and
available for Linux, Windows and Mac operating systems. It provides a number of templates to
get started and supports a number of UI frameworks such as the Twitter bootstrap, jQuery Mobile
and Topcoat. Intel XDK provides a live preview on the connected devices whilst you are
developing the alongside many useful tools. On a personal note, I think development using Intel
XDK was the very easiest. It uses a drag and drop approach which is very simplest, although it
does create a lot of unnecessary codes.
4. Appcelerator Titanium
Appcelerator’s Titanium is an one of the open source mobile application framework of hybrid
apps that provides an environment to create the native apps for several mobile platforms.Titanium
is a complete solution for creating hybrid mobile apps with all you need in one place and develop
the mobile apps. To get started with Titanium framework, first download Titanium studio. The
Titanium SDK which is equipped with a number of mobile platform APIs and Cloud service to
use as an app backend for development. It comes with platform independent APIs which makes it
easier to access phone hardware. Titanium often uses Alloy, a MVC framework to enable rapid
development of mobile applications. Modules created using Alloy are easy to reuse across
different applications, hence the significantly reducing the development time of mobile
applications and the lines of code. The core component of Titanium is one of the Apache-licensed
software development kit, Titanium SDK. Titanium also makes Alloy, an Apache-licensed,
Titanium-based model–view–controller framework, and Titanium Studio.
5. Sencha Touch
Sencha Touch is an one of the HTML 5 mobile app framework of hybrid apps for creating
applications for several platforms including iOS, Android and Blackberry and Windows. It has
been in existence for some years now and is popular among hybrid mobile applications
developers. Sencha Touch scores highly against its competitors by providing a native look and
feel the across all of the platforms it supports for developement. Getting started with Sencha
Touch not that difficult but in order to get the best things out of Sencha Touch which one needs
to invest a considerable amount of the time for development of mobile apps.
6. Kendo UI
Telerik’s Kendo UI is an one of the HTML 5 framework of hybrid apps whivch used for
creating cross platform mobile application. Kendo UI relies heavily on JQuery and has number of
JQuery based widgets. Learning Kendo UI in not difficult, developers familiar with the JQuery
will find the Kendo UI easy to learn. Kendo UI has open source most of Kendo UI’s toolset and
JavaScript framework feature. However most of the commonly used widgets are still under a
commercial license.
7. Phone Gap
Phone Gap is the odd one out in this list as it’s not framework for creating an app, but for
packaging and releasing an app.
Phone gap in based on the Open Source Cordova and is the commercial versioned owned by
Adobe. With a dedicated support team, Phone gap is popular amongst many mobile developers.

You can also use any of choice of JavaScript or UI frameworks to get started with the Phone
gap. JQuery mobile is along side KnockOut.js or Angular JS is a nice combination. Once you are
done with your code, Phone gap takes it from there and wrap it based on the intended platforms.
Application built using phone gap use a web view to render their content. Phone gap has minimal
set of web APIs to access the phone hardware features and it’s possible to write custom plugin to
suit requirement.
8. Bonus
Apps.js is JavaScript library for creating mobile web apps. It’s lightweight and unlike other
framework, doesn’t use Angular JS. It provides several customs themes and widgets. You can
write app using zepto or JQuery.
D. DISADVANTAGES OF HYBRID APPS
Some of the disadvantages of Hybrid Apps are :
1. Limited graphics
Despite for their ―native‖ appearance, hybrid apps offers the same graphical abilities as
mobile web apps. Again, while mobile web apps and hybrid apps offer graphical capabilities
suitable for most any business application, highly graphical applications are better suited for the
native approach.
2. Requires familiarity with mobile framework
Turning the mobile web apps into a hybrid apps requires familiarity with a mobile
frameworks. While still simpler than the native apps development, the hybrid approach adds a
level of complexity to the mobile web apps development process, as the developers must
familiarize themselves with a hybrid frameworks.
Table II.
An Explanation Of Ionic vs Titanium Framework of Hybrid Apps
IONIC VS TITANIUM
Ionic (it is the current trend. Everyone is
Type opting it) Titanium
Memory starvation issues. (Mark this point

Memory
No memory starvation issues as the most imp one.)
Leaks
It come bundled with angular is and Over
500 custom designed font icons MIT
It does not support custom JavaScript’s
licensed. With the coming release of
Angular is and limited functionality without an
AngularJS 2.0, focused on mobile, it’s sure
Internet connection
to gain even more popularity.
As ionic use Angular JS, it provides MV*

architecture. Due to this the model and view
are separated and with the support of
Architecture Angular JS, any changes made in model are It doesn't support pure MVC architecture.
directly affected to the view.
Cross Supports multiple platforms like It only support Android/IOS platforms.

platforms Android/IOS/Firefox/Windows/blackberry Requires different code for different
support complex GUI requires same code for platforms

functioning
Ionic has a native plugin to directly interact

Accessing
with the hardware. Such as Cordova or
Mobile It doesn't support 3rd party library
phone gap in order to run native app.
hardware
It’s fast as native Application, and There is
It's faster than the most currently available a small delay at app startup due to library
Speed
competition loading.
Ionic is HTML5, CSS3 and Angular JS

based front end development platform, Titanium uses C# to design GUI which does
GUI essentially it’s a browser based framework not give a better user experience as
that helps to build cross platform UI. compared to HTML5 and CSS3
App boot
The boot time was 2 seconds or less. The app boot time took about 2.5-3 seconds
time
Titanium doesn't have any built in libraries
Charts for charts. It requires 3rd party tools like
Ionic has built in library for chart support.
functionality High Charts.
Provides users with full access to tools and

Tools and
UI components including Pull-to-Refresh, Limited controls and restricted access to
UI
Infinite Scroll, and assorted tabs. certain components of a mobile OS
components
Built using SASS, it provides many UI
components to help develop rich and
SASS Not support SASS
interactive apps.
The animations and DOM elements are

Animations
Support both laggy and less responsive
and DOM
Titanium is more complex and requires a JS
SDK to do its heavy tasks. Thus,
Open source and free licenses (Mention development times are More and it costs
Cost here as the development time required is les more to the produce an Application. You
and this is why the cost is less) will also need a expert JavaScript developer
with good skills of development
Uses JavaScript or C# codes to create a

Languages It develops hybrid mobile application using
fully native mobile applications.
used HTML5 and JavaScript.
While Native Apps offers lots of benefits in graphics, app store distribution, and device
integration their lack of portability poses the significant problems for business. Besides the risk of an
unstable mobile platform landscape and limited app control, the Native applications required the
most significant investment of both time money. Considering that the Hybrid approach also offers
apps store distribution and device integration, graphics are the only advantages of unique in to the
Native approach. Unless a business required game like graphics in their apps, the Native approach
offers few benefits for business. It required more development time and cost. It requires the
maintenance cost also.
As also above study we can say that Hybrid apps bridge the gap between Native apps and Mobile
web apps. While Mobile web apps still offers the simplest mobile apps development for most of
mobile companies, Hybrid apps are the next best option. Hybrid apps are ideal for any company that

wants to develop simplicity of the mobile web apps and combines with the device integration and
app store distribution of Native apps. Ionic framework provides all the functionality that can be
found in native mobile apps development SDKs. Users can build their applications, customize them
for Android or iOS, and deploy through Cordova. Ionic includes mobile components like typography,
interactive paradigms, and an extensible base theme.
V. CONCLUSIONS
Today's Mobile generation, the client architectures used for mobile applications can be broadly
classified into the mobile Web Apps approach, Native Apps approach and Hybrid Apps approach.
Each of these approaches has its strengths, advantages and the drawbacks. ’One size fits all’ is not
applicable. The different choice of the client architecture for any mobile applications depends on the
demands of the applications and business considerations for mobile apps. There are distinct
difference between the Web Apps approach and the Native apps approach. The two key drawbacks
of using the Web Apps approach over the Native apps approach are: Inability of web apps to access
the device sensors/other hardware Difficulty in building the unique games like interface with native
look and feel for applications. The key benefit of the Web Apps approach is cross-platform support.
The Hybrid Apps approach emerged precisely to bridge the gap between the Web Apps and the
Native Apps approaches. With the Hybrid Apps approach, one gets cross-platform support without
having to forgo access to device capabilities.
The conclusions from comparatively study of Ionic and Titanium frameworks that Ionic is the best
framework to develop the Mobile Apps in today’s Environment.
ACKNOWLEDGMENT
Apart from the efforts of us, the success of this research paper depends largely on the
encouragement and guidelines of many others. We take this opportunity to express our gratitude to
the people who have been instrumental in the successful completion of this paper. We feel motivated
and encouraged every time. We are also thankful to the teaching and non-teaching staff of College.
Special thanks to people who involve in this survey.
REFERENCES
[1] http://www.mrc-productivity.com/research/whitepapers/NativeAppsWrongChoice.pdf.
[2] http://julyrapid.com/hybrid-vs-native-mobile-app-decide-5-minutes/
[3] https://en.wikipedia.org/wiki/Appcelerator_Titanium
[4] https://www.researchgate.net/publication/268153001_Native_Apps_Vs_Mobile_Web_Apps
[5] Drifty, Creators Of The Ionic Mobile Framework". Retrieved 14 March 2015.
[6] Sarah Perez (10 March 2014). "Drifty, Makers Of The Ionic Mobile Framework, Raise $1 Million". Retrieved 14
March 2015.
[7] "How 2015 Went for Ionic". The Official Ionic Blog. January 5, 2016. Retrieved 11 January 2016.
[8] http://blog.teamtreehouse.com/ionic-reigniting-native-vs-html5-debate
[9] http://www.joshmorony.com/8-reasons-why-im-glad-i-switched-to-the-ionic-framework/
[10] Mona Erfani Joorabchi Ali Mesbah Philippe Kruchten University of British Columbia Vancouver, BC, Canada
{merfani, amesbah, pbk}@ece.ubc.ca
[11] Henning Heitkötter, Sebastian Hanschke and Tim A. Majchrzak Department of Information Systems, University of
Münster, Münster, Germany heitkoetter@wi.uni-muenster.de, sebastianhanschke@gmx.de, tima@ercis.de
[12] Spyros Xanthopoulos Directorate of Technical Services and Computerization Aristotle University of Thessaloniki
54124 Thessaloniki, Greece 0030 2310998828 xant@auth.gr
[13] Stelios Xinogalos Department of Applied Informatics University of Macedonia 54006 Thessaloniki, Greece 0030
2310891820 stelios@uom.gr
[14] Berg Insight, ―The mobile application market,‖ http://www.berginsight. com/ReportPDF/ProductSheet/bi-app1-
ps.pdf.
[15] http://dx.doi.org/10.3991/ijim.v7i4.3226 William Jobe Stockholm University, Stockholm, Sweden
[16] Kendo UI, ―HTML5 Adoption Fact or Fiction,‖ Sep. 2012.

[17] dotMobi, ―Global mobile statistics 2013 Section E: Mobile apps, app stores, pricing and failure rates,‖ mobiThinking,
May-2013. [Online]. Available: http://mobithinking.com/mobile-marketingtools/latest-mobile-stats/e#appdownloads.
[Accessed: 06-Sep- 2013].
[18] R. Larsen, ―HTML5, CSS3, and related technologies,‖ developerWorks, 26-Apr-2011. [Online]. Available:
http://www.ibm.com/developerworks/library/wa-webstandards/. [Accessed: 26-Sep-2013].
[19] ―Native, web or hybrid mobile-app development,‖ IBM Software, Thought Leadership White Paper. [Online].
Available:http://www.computerworld.com.au/whitepaper/371126/native-web-or-hybrid-mobile-app-
development/download/
[20] ―Voice of the Next-Generation Mobile Developer, Appcelerator / IDC Q3 2012 Mobile Developer Report,‖
http://www.appcelerator.com.s3. amazonaws.com/pdf/Appcelerator-Report-Q3-2012-final.pdf.
[21] N. P. Huy and D. vanThanh, ―Evaluation of mobile app paradigms,‖ in Proceedings of the International Conference
on Advances in Mobile Computing and Multimedia, ser. MoMM. ACM, 2012, pp. 25–30.
[22] Y.-W. Kao, C.-F. Lin, K.-A. Yang, and S.-M. Yuan, ―A cross-platform runtime environment for mobile widget-
based application,‖ in CyberEnabled Distributed Computing and Knowledge Discovery (CyberC), 2011
International Conference on, 2011, pp. 68 –71.
[23] T. Paananen, ―Smartphone Cross-Platform Frameworks,‖ Bachelor’s Thesis., 2011.
[24] M.-C. Forgue and D. Hazael-Massieux, ―Mobile web applications: ¨ bringing mobile apps and web together,‖ in
Proceedings of the 21st international conference companion on World Wide Web, ser. WWW ’12 Companion. ACM,
2012, pp. 255–258.
[25] M. Palmieri, I. Singh, and A. Cicchetti, ―Comparison of cross-platform mobile development tools,‖ in Intelligence in
Next Generation Networks (ICIN), 2012 16th International Conference on, 2012, pp. 179 –186.
[26] Agrawal, S. and A.I. Wasserman, ―Mobile Application Development: A Developer Survey‖, submitted for
publication, 2010
[27] World Wide Web Consortium, Mobile Web Application Best Practices W3C Working Draft, 13 July 2010.
http://www.w3.org/TR/mwabp/ Accessed on 6 September 2010.
[28] W3C, ―HTML5,‖ W3C Candidate Recommendation, 06-Aug- 2013. [Online]. Available:
http://www.w3.org/TR/html5/. [Accessed: 05-Sep-2013].
[29] Berg Insight, ―The mobile application market,‖ http://www.berginsight. com/ReportPDF/ProductSheet/bi-app1-
ps.pdf.
[30] J. Dehlinger and J. Dixon, ―Mobile application software engineering: Challenges and research directions,‖ in
Proceedings of the Workshop on Mobile Software Engineering. Springer, 2011, pp. 29–32.

Native

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Native

Transféré par

Droits d'auteur :

Formats disponibles

International Journal of Current Trends in Engineering & Research (IJCTER)

e-ISSN 2455–1392 Volume 2 Issue 6, June 2016 pp. 563 – 572

Native Vs Hybrid Apps

Businesses that need a mobile app have three available options:

@IJCTER-2016, All rights Reserved 563

II. LITERATURE REVIEW

@IJCTER-2016, All rights Reserved 564

V. NATIVE VS HYBRID APPS

@IJCTER-2016, All rights Reserved 565

@IJCTER-2016, All rights Reserved 566

C. ADVANTAGES OF HYBRID APPS

@IJCTER-2016, All rights Reserved 567

@IJCTER-2016, All rights Reserved 568

Memory starvation issues. (Mark this point

As ionic use Angular JS, it provides MV*

Cross Supports multiple platforms like It only support Android/IOS platforms.

@IJCTER-2016, All rights Reserved 569

Ionic has a native plugin to directly interact

Ionic is HTML5, CSS3 and Angular JS

Provides users with full access to tools and

The animations and DOM elements are

Uses JavaScript or C# codes to create a

@IJCTER-2016, All rights Reserved 570

@IJCTER-2016, All rights Reserved 571

@IJCTER-2016, All rights Reserved 572

Vous aimerez peut-être aussi