Phonegap VS Appcan

About PhoneGap

PhoneGap is a fast-developing platform for creating mobile cross-platform mobile applications using HTML,CSS and JavaScript. It enables developers to take advantage of the core features of Iphone,android,palm,symbian,wp7,bada and BlackBerry smartphones-including geolocation, accelerators, contacts, sounds and vibrations, and PhoneGap has a rich plug-in, You can extend unlimited functionality with this. PhoneGap is free, but it requires additional software from a specific platform, such as the iphone sdk,android Android SDK for iphones, and can be developed with DW5.5. Using PhoneGap is only a little bit more than building an application for each platform, because although the codebase is the same, you still need to compile the application separately for each platform.

Appcan

Appcan is an advocate for the development of hybrid app hybrid in China, Appcan application engine supports the development and operation of hybrid app. It also focuses on the problem of "not fluent" and "poor experience" of mobile applications based on HTML5. Using the naitve interactivity provided by the Appcan application engine, the HTML5 development mobile app is nearly as close to the native app experience.

Framework pros and cons Phonegap advantages

Support for most systems: Android,ios, Symbian, Windows Phone, Palm WebOS,

Bada, Symbian

Open source for framework-level optimization

Framework provides custom controls that can invoke Android native functionality

Rich third-party plugins

Small size of installation package

Document Rich

Can be debugged locally, published

Support for local packaging, cloud packaging

Disadvantages

Different platforms need to build different development environments

The framework does not have a UI and needs to use a third-party UI plugin

The framework provides only basic APIs, and extensions require the use of third-party plug-ins

The framework does not support automatic encryption and requires manual HTML encryption

The framework is not optimized for the UI and is slower to apply load and UI accordingly

Plug-in quality is uneven due to different levels of third-party developers

Appcan Advantages

Support four major systems: Android,ios,symbian,windows Phone

Provide integrated solutions to facilitate the construction, development, commissioning and release of the environment

The framework comes with a UI package that contains common control styles

Rich Framework API

Support for local packaging, cloud packaging

Key-based Code encryption

Timely technical support

The framework optimizes UI, animation rendering, and fast response times

Disadvantages

No open source, unable to modify, optimize the underlying code

Do not support self-developed control/, can not be transferred to Android native function

The frame comes with too many features, resulting in a large application installation package.

Less documentation

Some systems cannot be debugged using the IDE

can only be published on the server side and cannot be published locally

IOS Publish, you need to upload the certificate to the server

Detailed comparison of basic conditions

	Phonegap	Appcan
Framework Goals	The ultimate goal of PhoneGap is to end the differences between existing target platforms	Fast development, multiple platforms, solutions for HTML5-based mobile applications Today "not smooth" and "experience poor" issues, providing a unified solution
Frame function	Simple	Rich
Support Platform	Most platforms	4 + platforms only
Development environment	Different platforms require different development environments	Just one IDE package
		Windows 7 X64 English version, Windows 8 X64 English version does not perform simulator debugging
HTML tags not supported by the compiler	Can compile, debug, publish	Cannot debug, can only build APK package, install to phone
Debugging	can be debugged directly	A locally released iOS package that must be deployed on a jailbroken machine
Release	Can be directly published locally	The code must be uploaded to the server before it can be published
IOS Signature Management	Local administration	Need to upload to server
Code Leakage Risk	Low: Save code only on-premises, SVN	High: The code needs to be uploaded to the Appcan server
Chinese localization	Weak	Strong: Cooperation with Sina to provide cloud services, etc.
Multi-lingual	Plugin support	Plugin support
installation package Size	Small	Big

Development

	Phonegap	Appcan
Development language	HTML 5 + js + CSS 3	HTML 5 + js + CSS 3
Development environment	Different platforms require different development environments	Eclipse (IDE built-in)
Ui	JQM and other three-party controls or self-designed	Appcan.ui or third-party UI controls or self-designed
Custom controls	Support for custom controls (native code) for foreground calls	Calls to custom controls (native code) are not supported, and 2.0 will support
Official API	Less, more single function	More Rich
Third-party controls	More Rich	UI only, JS control supported
Multithreading	Support	Support
Multi-window	Need to use plugins	Framework Support
Iframe	Not supported	Not supported
Back off	Plugin Required	Framework comes with API
sockets, etc.	You need to develop your own controls (already have third-party controls)	Official API support, temporarily unable to maintain socket connection

Performance

	Phonegap	Appcan
Page load	There's a noticeable delay.	There's a noticeable delay.
Page switching	Some third-party controls can show significant jitter	When the brightness is not darkest, the new page is loaded, and there is a noticeable darkening
	A white screen appears and you need to use a third-party control mask	No white screen appears
Animated rendering	Poor	Better
Fine-grained testing	Poor	So so
Initializing memory	8.5MB	11MB
Initializing CPU Usage	So so	So so
UI Refresh	20 milliseconds per thread refresh, 4 threads start to refresh not in time	20 milliseconds per thread refresh, 120 threads with no noticeable refresh problem
		Content pages do not end after they leave, overlapping may occur
Application Load Speed	Faster (do not force the Welcome page, partial data initialization can be done on the Welcome page)	Poor (System mandatory use welcome interface, data initialization disaster free Welcome page)
Page load Speed	Slower (jumps directly without using plug-ins, but white screen appears)	General (the original page waits 0.5-1.5 seconds after the jump)

Other

	Phonegap	Appcan
Exit Confirmation	Self-developed	Frame Encapsulation
Document	Rich	General (gradual increase)
Technical support	So so	Convenient
Submit a problem Channel	Forum, Q Group (folk), official email	Forum, Q Group (official), official email

Attached 1

Content page causes overlapping effects

Note:

The above test system is: HUAWEI C8812

Different models of mobile phones, phonegap performance is completely different, due to time constraints, do not use multi-terminal testing.

(EXT) Phonegap VS Appcan