Comparing PhoneGap/Cordova and Codename One

DZone 's Guide to

Comparing PhoneGap/Cordova and Codename One

Shai Almog, CEO and co-founder of Codename One, spends some time comparing PhoneGap/Cordova, and Codename One. Check out the advantages that Codename might have in store for you.

· Mobile Zone ·
Free Resource

First, let's start with a big disclaimer: I'm the co-founder of Codename One so calling me biased would be an understatement. Having said that I would not have bothered comparing Codename One to PhoneGap/Cordova had I not thought that they are excellent tools!

Last time around we compared Codename One to Xamarin and this time around I’d like to compare Codename One to what is probably the market leader: PhoneGap/Cordova. If Xamarin is big then Cordova is huge, it is so prevalent that it is often the default assumption when people mention cross platform today.

In fact, one of the big problems we had when describing Codename One was distinguishing it from HTML5 based solutions like Cordova.

One of the things we’d like to clarify before delving into the comparison is that our goal isn’t to proclaim Codename One as the "end all" of WORA.

We are biased so the comparison might be flawed. However, we think Cordova/PhoneGap are remarkably innovative tools that changed the marketplace significantly. The goal of this comparison is to highlight the differences/tradeoffs of each solution. In fact, we rather like Cordova and even offer some Cordova compatibility in Codename One.

We were debating a lot on whether we should include Ionic in this comparison and decided to mostly skip it for now. We mention it and related frameworks in the comparison in a few points mostly because PhoneGap is usually used with such frameworks. Unfortunately, because of the number of JavaScript frameworks and tools built on top of PhoneGap, it’s just impractical to single out each and every one of them.

We might do a proper discussion of Ionic as I think it’s a very interesting solution that is very similar to Codename One in some regards. Most of the things we discuss about PhoneGap/Cordova apply to ionic too.


PhoneGap was started in the iPhoneDevCamp hackathon, this highlights the genius behind the solution: the underlying idea is trivial. PhoneGap is, in effect, a very simple solution which is a pretty good thing.

PhoneGap places a single web view UI within an app which it then uses to display HTML. It exposes a set of JavaScript API’s to provide access to native functionality, e.g. camera, filesystem, etc.

It also includes a rich set of plugins that provide quite a few capabilities, in fact, we just ported one of those great plugins to add Bluetooth support to Codename One.

Adobe purchased Nitobi who made PhoneGap and open sourced the project thru Apache as the Cordova project. Both PhoneGap and Cordova are very similar with PhoneGap offering some pretty interesting features on top of the core open source product such as PhoneGap build.

Because Cordova/PhoneGap is so simple it was adopted throughout the industry practically all major enterprise mobility tools such as Worklight rely on it for their client side UI. It’s become a synonym for the idea of packaging HTML as an application and even tools that are not using Cordova internally are often referred to as PhoneGap or Cordova.

In fact, we even announced PhoneGap/Cordova support a while back and it didn’t take much to implement that.

At a Glance

Category PhoneGap/Cordova Codename One


HTML, CSS & JavaScript



Packaged code optionally obfuscated

Compiled binaries

VM Ownership

Device/OS vendor

Codename One

Cloud Build

Yes thru PhoneGap build


Web Deployment






Size Overhead

Depends on framework


In Detail


We’ve always said that if you love doing client side HTML/JavaScript for mobile devices then PhoneGap/Cordova is probably the right tool for you. HTML5 has come a very long way and is no longer as restrictive as it used to be especially with recent iOS updates.

However, Java is still a formidable opponent. Unlike HTML/JavaScript, Java is strict, statically typed and compiled.

JavaScript isn’t the most intuitive language to interface into native code. Native concepts such as threads or even binary data don’t map in a natural way to the higher level functions of JavaScript. This isn’t the case for Java which is literally the native language of Android and maps rather well to C/Objective-C/Swift concepts.

With modern Java 8 semantics Java is also quite terse and should be comparably elegant to JavaScript in most regards.


PhoneGap applications are just zipped into the standard OS distribution. A complaint some PhoneGap developers have is that hackers in some markets unzip their apps and take the HTML/JavaScript/CSS etc. into their own app. This allows them to sell the app within the standard markets as if it was their own. Such scams are quite common and very hard to catch/enforce.

This is not feasible in Codename One where the source code is compiled together and obfuscated by default on Android making it even more "secure". A Codename One application can be decompiled but this would be a far harder process than doing the same for a PhoneGap/Cordova application.

VM Ownership

Java is the native platform for Android whereas JavaScript/HTML are supported everywhere by the OS vendor.

This brings about some interesting situations, Android completely replaced it’s browser implementation between versions of the OS relatively abruptly. This can trigger a situation where shipping applications will start misbehaving due to OS changes. This also means that the only way to fix some issues is thru a workaround, there is no central authority that can fix an HTML rendering issue or add a missing feature to an old OS.

With Codename One the VM and UI are the responsibility of a single entity. Since the implementation of Codename One is at a lower point in the porting stack most of the relevant code can be ported/fixed or worked around by Codename One itself. This means that if a low-level reproducible failure happens, Codename One has the ability to fix it whereas PhoneGap developers would need to workaround it.

Cloud Build

PhoneGap Build supports building native applications via the cloud which is a wonderful approach. Codename One works in the same way but unlike PhoneGap build, Codename One is built around that approach as a basic expectation.

PhoneGap build works with a set of pre-determined plugins whereas Codename One is more flexible with its support for native code and 3rd party libraries.


Codename One uses lightweight widgets to do it’s rendering. Arguably HTML can be considered lightweight as well but it is often not the case.

One of the core powers of HTML has been its complex support for dynamic reflows, this allows positioning components using a very elaborate box model. However, this power is also the source of HTML’s greatest performance challenges. Some HTML frameworks choose to position elements absolutely and lay them out thru code logic, which is pretty close to what Codename One does in its layout managers. However, this forces the JavaScript developer into a custom environment that won’t "play nicely" with everything else within the ecosystem.

Frameworks like Ionic have taken up the lightweight approach to creating native "themes" in a similar way to Codename One. This provides Ionic with many of the advantages Codename One enjoys but also some of the drawbacks/advantages inherent from layering on top of Cordova.

One of the core capabilities of Codename One is in embedding native widgets directly into the app. This is demonstrated in Codename One thru the native Google Maps support and other such capabilities. Since embedding an OS native widget into HTML is "problematic" that level of platform extension can’t be accomplished in Cordova.

Size Overhead

Cordova and Codename One can be used to create very small applications. In fact, Cordova can be even smaller than Codename One in the hands of a skilled developer.

However, using Cordova without a JavaScript framework/tooling is more challenging and less common today. These tools include their own overhead which is rather extensive in some cases, e.g. Ionic is specifically well known for producing very large application binaries.

Property Cross Comparison

The PropertyCross demo was built as a tool that allows us to compare two cross platform frameworks, as such, there are versions of the demo for many such platforms. You can check out details of the Codename One implementation here. The github repository for this demo is here.

Since PhoneGap/Cordova is mostly an infrastructure tool there are several implementations that support PhoneGap Build, e.g. jquerymobile, ionic, sencha touch, and too many others to even count.

With so many variations how can we properly compare the two frameworks?

There are several things we can glean from property cross by reviewing all of the above:

  • Codename One has 2 file types that aren’t configuration or build scripts: res file (resources) and Java files. PhoneGap solutions use JavaScript, HTML, and CSS.
  • Codename One doesn’t have splash screens or multiple icon sizes. Those are generated automatically unlike the PhoneGap-based solutions where you need dozens of resource files even without tablet support!
  • Codename One is terse. Ionic, is one of the smallest implementations. It includes more than 600 lines of undocumented code spread across JavaScript and HTML (not counting angular, other JS libraries or CSS). The Codename One implementation has 623 lines of code out of which over 150 lines are comments and 40 lines are import statements… Who says Java is verbose?

Final Word

Notice that Codename One can embed PhoneGap/Cordova code into Codename One applications. Would that make it superior to just using Cordova directly?

Not necessarily. Cordova is a mature, widely supported solution. If you like working with HTML/JavaScript then it’s hard to compete with that.

However, if you want to use proper Java to develop your app and care more about the security of your code then Codename One has advantages.

codenameone, cordova, java, javascript, mobile, opensource, phonegap

Published at DZone with permission of Shai Almog , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}