Apache Cordova vs. Tabris.js
At EclipseSource we’ve been doing frameworks for many years now. We did server and UI frameworks… Web and mobile frameworks… Open and closed frameworks… If we had only learned one thing, this would be “Play well with others!”. With this post I want to show you how our cross platform solution Tabris.js compares to Apache Cordova and how they are playing well together.
Apache Cordova comes with a very handy tool known as the Cordova CLI (Command Line Interface). It provides a very convenient way to build your applications as .ipa, .apk and others. The CLI also provides Scaffolding, Plugin and Platform Management. This means you will “install” a Cordova Platform using the CLI when developing an app. Because Tabris.js ships as a Cordova Platform you can use the standard Cordova CLI to create, manage and build your application exactly the same way you would do it with any other Cordova app.
To brand an app Cordova provides the “config.xml“. This file contains the application’s configuration like ids, icons, splash screens and more. Tabris.js apps also make use of the config.xml. As a result you can configure a Tabris.js app the same way you would configure a Cordova app.
As you can see Tabris.js and Apache Cordova do not compete with each other. Instead they are filling each other’s gap. You can put it this way:
- Tabris.js provides a native UI for Cordova applications
- Cordova provides plugins and the CLI to Tabris.js applications
To get more details read about Cordova plugins, online build and local Cordova CLI build in Tabris.js docs.
You need to get invited to access it. So, don’t hesitate and request an invite try Tabris.js. It’s free!
Feedback is welcome!Want to join the discussion?
Feel free to contribute!