Its often an Apples == Oranges comparison since Codename One is so different from everything else…
This section is being retired in favor of a more open comparison system in the blog . This is an ongoing process of migrating comparisons to the new format, during this update we are keeping this section as reference.
To properly evaluate a platform we often look at our existing experiences and evaluate based on what we know. The set of options below present some of insights about how we match up to other cross platform solutions in the market today. But first lets start up with the Codename One benefits:
Love it or hate it Java is still king of the hill. With 9-10 million active Java developers and a permanent spot as one of the top programming languages. The language/platform are familar to tens of millions of developers world wide guaranteeing code maintainability well into the future.
Codename One translates all the code to native code or the native VM resulting in performance that matches the performance of native code.
Developers can use the rich tools available for Java developers such as Eclipse/NetBeans to work with the code. Codename One has its own GUI builder and many niceties to track issues in your code. The biggest benefit though is in the build server which generates a native application for you without having to deal with all of the complexities of building a native app for every platform.
Due to its unique lightweight architecture Codename One boast greater portability than HTML5 and more supported devices! Thanks to its unique cloud build system it doesn’t require any native toolchain or dedicated hardware.
Codename One supports embedding a full Cordova application as is see our announcement on the subject. Codename Ones native capabilities still have the following additional advantages over HTML5:
  • Performance – HTML5 is slow to begin with but made slower on devices due to some architectural choices on iOS devices.
  • Portability – while HTML5 on the server side can be ported with some effort, when embedded using PhoneGap like packaging adapting the UI for multiple DPI’s becomes challenging. Web technologies were designed for HTTP delivery not for local execution. Codename One was built from scratch to work on all DPI’s and provides the visual tools to do so.
  • Power – mobile browsers are fragmented and constantly late with new features requiring a full OS upgrade for new features. Basics such as threads aren’t at the moment of this writing supported by any device. Codename One provides most of the power and convenience desktop Java developers are used to.
  • Ease – HTML isn’t hard but JavaScript with CSS and adapting for all devices becomes harder? Its not as easy as it used to be. Codename One provides visual tools including a build server alleviating the need to install native tools on your machine.
  • Stable target – since your code executes on the device browser you are very likely to have device only issues that can’t be debugged properly. Codename One is statically linked to your application which means you will have a stable application with an identical version of Codename One on all devices! Since the code is handled by a single entity if you run into problems we can actually help you fix them!

This section is true not just for Appcelerator but to most other tools of its kind such as MonoTouch, RhoMobile and others. We think the biggest difference between Codename One and all of these guys is that we have a Java based solution and are a true “WORA” solution.

  • Native tools – in order to build an application for iOS you must have a Mac and for Windows phone (if supported) you need a windows machine. This is tedious and painful! Codename One uses a build server to remove that need and provides seamless simulator execution, debugging, profiling etc.
  • Standard IDE – most such tools have their own IDE’s with limited features. Codename One works with NetBeans/Eclipse, which are mature industry leading IDE’s. Appcelerators Titanium IDE is particularly limited, highlighting its “code completion” abilities as a “new feature”…
  • Fast builds – Appcelerator Titanium literally translates JavaScript to a platform project with every build (thru the command line no less) which takes quite a while to run. Debugging is a HUGE challenge there as well… With Codename One you just press play.
  • Portability – Appcelertor requires that you rewrite your UI (roughly 50% of the code) for every platform. Better solutions limit the developer to the lowest common denominator approach, this requires coding specifics for every platform. Codename One uses a unique lightweight architecture that enables it to offer high level features on all devices.
  • Ease – most such tools don’t offer features such as integrated GUI builders, themes, localization etc?
Google’s J2ObjC compiler is an open source project that isn’t really comparable to Codename One and solves a completely different problem. However we get asked about this frequently so this is a direct quote from their site:
J2ObjC does not provide any sort of platform-independent UI toolkit, nor are there any plans to do so in the future. iOS UI code needs to be written in Objective-C or Objective-C++ using Apple’s iOS SDK (Android UIs using Android’s API, web app UIs using GWT, etc.).
Other than that, the tool just deals with the iOS porting of business logic. Requires a Mac and requires that developers work with xcode. It doesn’t include a full featured garbage collector (the OS X GC mentioned in their wiki was deprecated on OS X and ARC is not a GC) and isn’t really a cross platform solution.

Large parts of Codename One were inspired by the design of Swing however a great deal was fixed, Codename One fixed many concepts in Swing thanks to hindsight and experience in Swing development e.g.

  • Optimized for phones/tablets, this includes support for gestures and complex key layouts
  • Proper styles & themeing
  • Resource file format/standard GUI builder
  • Truly open source
  • Static linking
    Java FX however got off in a completely different direction by using a scene-graph graphics layer approach to GUI. This is very much the approach taken up by Flash and one of the main stumbling blocks for flash on mobile devices.
    It is remarkably hard to port a scene-graph implementation consistently to every platform and then integrate it with the native platform widgets as we are sure the guys at Oracle have found out. Making this sort of implementation performant is even harder as the guys from Adobe found out.
    While Swing had a lot of traction (30% of the GUI development market at its peak) JavaFX never reached any measurable market penetration. Its only major users are Swing shops that have no future migration path other than JavaFX. Oracle itself fired most of its developer advocates and JavaFX related teams, it doesn’t use JavaFX for any of its core products, e.g. MAF has no relation to JavaFX.
    Up until recently there was no JavaFX on mobile devices and arguably there still isn’t, a team at Oracle open sourced a half baked JavaFX for iOS implementation that suffers greatly from the limitations mentioned above. This was picked by some developers and shipped as a product for mobile application development. We consider such efforts to be callous & irresponsible to the developers who look at them as a serious solution, it breeds confusion within the community that’s already fragmented:
  • Java FX is HUGE and remarkably complex – can a bunch of hackers maintain/support something as big as this? Even Oracle with all its resources has a ridiculous amount of bugs within the desktop version of JavaFX.
  • Oracle already vetted JavaFX’s potential on mobile and came to the realization that its not a practical solution for the mobile ecosystem due to its complexity. E.g. JavaFX requires its own kerning on top of OpenGL ES, this is nearly impossible to do properly because of the complexities of subpixel anti-aliasing on mobile screens.
  • To further cemenet the point Oracle has so little faith in the future of FX that it killed the Scene Builder project.
  • JavaFX was designed for desktops where manipulation of native widgets is possible and documented. Native widgets are ESSENTIAL on mobile, you can’t do input without a native widget. Video, HTML rendering etc. must all be done natively… That’s REALLY hard to do in a portable way that won’t crash the VM.
  • JavaFX applications are HUGE because they need a HUGE VM. This translates to slow download, slow performance and slow builds.

To further contrast these issues with Codename One, since the project is so huge, complex and clearly not supported by Oracle picking this up will leave developers in an untenable state where bugs can’t be fixed and issues can’t be addressed (e.g. bug when migrating to iOS 10).
Codename One is much smaller in terms of code size but has a much larger active developer community, because projects are translated to native OS projects they should be buildable and maintainable even without Codename One’s support.

MAF (mobile application framework) is a tool that provides the ability to create some iPhone applications using a combination of Java EE and HTML5 essentially bringing the worst of all worlds together.
The tool is marketed as a free tool which is misleading since its free for development but not for distribution. The cost is per application and is in the range of 50,000USD!
MAF suffers from all the problems of PhoneGap/HTML (mentioned in the first section) and it adds to that all the complexity of working with a Java backend without removing those other complexities.
To make matters worse, since the VM is embedded into the code you are limited to an interpreted mode which means slow performance on top of the existing HTML5 overhead!

We compared React Native to Codename One/Java in a somewhat controversial blog post. We stand by every word on that post. To sum the advantages:

  • React native isn’t a WORA solution – it uses native widgets and even has its own lightweight implementation of a controller since the concept of controllers is not universal
  • React native has on device performance issues because basic UI concepts aren’t interchangeable between native widgets. This isn’t a problem for Codename One where all components are lightweight
  • React Native requires a Mac for iOS development and a complex toolchain for every platform
  • React abstracts everything behind callbacks reducing code size but making the behavior and flow more opaque
  • React Native isn’t as porable, you can’t reuse the code for a web embedded app or a desktop app
  • React native isn’t more terse than Codename One with Java 8
  • JavaScript is a fragile language and the practice of working outside of an IDE is inferior as projects grow in size