NativeScript vs. J2ObjC vs. JUniversal
|
|
|
||||||
NativeScript |
J2ObjC |
JUniversal |
||||||
Favorites74
|
Favorites8
|
Favorites5
|
||||||
Hacker News, Reddit, Stack Overflow Stats |
||||||||
GitHub Stats |
||||||||
Description |
What is NativeScript?NativeScript enables developers to build native apps for iOS, Android and Windows Universal while sharing the application code across the platforms. When building the application UI, developers use our libraries, which abstract the differences between the native platforms.
|
What is J2ObjC?J2ObjC is an open-source command-line tool from Google that translates Java code to Objective-C for the iOS (iPhone/iPad) platform. This tool enables Java code to be part of an iOS application's build, as no editing of the generated files is necessary. The goal is to write an app's non-UI code (such as data access, or application logic) in Java, which is then shared by web apps (using GWT), Android apps, and iOS apps.
|
What is JUniversal?The vision of JUniversal came from some guys at Nokia who possess considerable expertise both in Java and in building cross-platform apps. They built this tool to provide an elegant way to translate source code and make it useful across multiple platforms. JUniversal offers you the freedom to write your shared code in Java and then translate it to C# (available now) or to C++/Objective C++ (coming soon). You can also combine JUniversal with Google’s j2objc translator to translate Java to Objective-C for iOS.
|
|||||
Pros about this tool |
|
|
|
|||||
Companies |
8 Companies Using NativeScript
|
3 Companies Using J2ObjC
|
0 Companies Using JUniversal
|
|||||
Integrations |
NativeScript
Integrations
|
J2ObjC
Integrations
|
JUniversal
Integrations
|
|||||
|
What are some alternatives to NativeScript, J2ObjC, and JUniversal?
|
||||||||
Latest News |
Announcing NativeScript-Vue 1.0
February 19, 2018
Building an Awesome Login Screen with NativeScript
February 13, 2018
A New Way to Learn NativeScript Layouts
February 06, 2018
|
|||||||
Reviews of NativeScript, J2ObjC, and JUniversal
The best framework for cross-platform mobile development
May 15, 2015 07:47
NativeScript allows you to reuse your JS skills to build Native mobile apps without any sacrifices. It takes a bit to learn about all possible features, but each time you discover a new one you can't help but get more and more excited.
The new way to build native apps with a single source code
February 25, 2016 22:44
It is using the native components to build the UI and offers the best skills reuse story. All you need to know is JS/TS and CSS. Angular 2 is also supported which leads to even more code reuse across web and mobile.This is also the best way to access the native platform APIs directly.
J2ObjC is amazing!
April 21, 2016 12:33
This is one of the most amazing open source projects out there. Tom and Kieth do an amazing job working with the developer community and quickly responding to questions and concerns. I was blown away by how solid the ported code was. What a life-saver and a ridiculously awesome tool.
How developers use NativeScript vs J2ObjC vs JUniversal
fileee GmbH uses J2ObjC
We use J2Objc and GWT to provide a shared library of cross-platform code that is used on all our client platforms (Android, iOS and the web) and even in the backend.
Google uses JUniversal
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.