J2ObjC vs NativeScript: What are the differences?
J2ObjC and NativeScript can be categorized as "Cross-Platform Mobile Development" tools.
"Backed by Google" is the top reason why over 3 developers like J2ObjC, while over 55 developers mention "Access to the entire native api" as the leading cause for choosing NativeScript.
J2ObjC and NativeScript are both open source tools. It seems that NativeScript with 17.2K GitHub stars and 1.27K forks on GitHub has more adoption than J2ObjC with 5.47K GitHub stars and 771 GitHub forks.
What is J2ObjC?
What is NativeScript?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using J2ObjC?
What are the cons of using NativeScript?
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
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.
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.
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.
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.