8

Both frameworks are (hybrid) mobile app frameworks which try to access the native UI components with the JavaScript API provided by the different platforms like iOS and Android. They don't use any HTML and CSS for the UI design like e.g. Ionic do and they are not wrapper frameworks but actually a kind of cross-compiler frameworks. That's what i found out. BUT I didn't get the actual differences between these two frameworks. Why should i prefer one of these? Are they doing exactly the same job?

best regards, Tom

Hardik Vaghani
  • 2,163
  • 24
  • 46
Thomas Strauss
  • 81
  • 1
  • 3
  • I just started a blog post series about this topic, maybe it helps you: https://medium.com/@dschmidt1992/how-to-pitch-react-native-to-developers-dcf092cb4614 – Daniel Schmidt Apr 22 '16 at 20:07
  • Thank you for your blog post! But what i need is a much more detailed description of the differences between Titanium and React Native. It sounds like that you're a real React Fan and all other frameworks are not that good as React is right? ;) Have a look at Titanium, it uses the same approach as React Native and then tell me why React Native is better ;) A comparison to Cordova or PhoneGap is easy because it's a completely other approach --> WebKit vs JavaScript Interpreter (Cross-Compiler). However thank you very much :) – Thomas Strauss Apr 23 '16 at 07:15
  • 1
    Both frameworks are not to create hybrid but native mobile apps. – Shawn Jan 05 '17 at 19:58

1 Answers1

3

I know this is quite old, but I'll give my answer for the benefit of anyone else arriving here.

Full disclosure, I worked for Appcelerator from 2012-2019.

In short, they're both quite similar.

  • You write a specific flavor of JavaScript that includes custom objects
  • Your JavaScript code gets compressed, minified, etc. so it becomes the input to an interpreter that gets shipped with your app
  • When your app runs, it launches the interpreter which starts executing your code
  • At this point, JavaScript is being run in "native land", so the interpreter can act as a bridge between your JavaScript code and the native SDK
  • The result is a native app with access to features of the underlying platform

A "native app" shouldn't simply be defined as an app that runs natively, because that would make a PhoneGap app a native app.

A "native app" should be defined as an app that runs and behaves natively. That means, an app that abides by the native OS' ui/ux guidelines.

MAIN DIFFERENCES?

I'd have to say that the main difference is its internal design. Appcelerator started in 2007, when "mobile" was very young.

React Native was launched in 2015.

In 2015 mobile was already in full swing, and mobile OS' were pretty mature, so I infer that React Native's design benefits from all lessons learned by Appcelerator (and others).

As for which one is better, I'd say React, because Titanium is now dead.

Alco
  • 149
  • 5