Apache Cordova vs JUniversal: What are the differences?
Apache Cordova and JUniversal belong to "Cross-Platform Mobile Development" category of the tech stack.
Some of the features offered by Apache Cordova are:
- Cross-platform (CLI) workflow
- Platform-centered workflow
- Hundreds of plugins
On the other hand, JUniversal provides the following key features:
- OAuth (based on Scribe)
- Unit testing (JUnit)
Apache Cordova and JUniversal are both open source tools. It seems that Apache Cordova with 766 GitHub stars and 327 forks on GitHub has more adoption than JUniversal with 132 GitHub stars and 22 GitHub forks.
What is Apache Cordova?
What is JUniversal?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose JUniversal?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Apache Cordova?
What are the cons of using JUniversal?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Comment from HackerNews (https://news.ycombinator.com/item?id=8998736)
This is how Google Inbox and Google Spreadsheets works. See the slides from my recently produced GWT Create Session (http://t.co/ZvoaHxCoZT). J2ObjC slide deck here (https://docs.google.com/presentation/d/1mW_Plm5jAygELf7qjVK7...) Videos of the conference will be online soon.
Prior to that, some 20% Googlers also produced the PlayN library (https://github.com/threerings/playn) This was taken over by Michael Bayne who added an iOS backend by Bytecode -> IKVM -> Mono conversion. I beleive j2objc and RoboVM backends exist now as well.
The major benefit of the j2objc approach is the avoidance of GC in favor of ARC, the conversion of message-sends into C-method calls when possible, and integration with existing iOS toolchain.
When we started, it seemed like an iffy idea, but after developing a product delivered to millions of users on a high volume site (gmail) that has 70% code sharing, and being able to simultaneously develop, test, and deploy across the platforms reasonably efficiently, a lot of skeptics have become converts to the concept.
used in conjunction with ionic to build out ios and android app for a client. a little slow to run on devices but saves a ton on development time.
Used with Ionic to support various plugins and integrations with the native environment of iOS and Android.