Tabris.js provides API to create and control native UIs. In addition, some native functionality like device sensors, camera or specific native APIs like push notifications are available as Cordova plugins.
To see examples of widgets and layouts, download the Developer App and have a look at the Examples section. For an explanation of the underlying concepts, check out the “Tabris.js Examples” blog series. In addition, we have many code snippets demonstrating how to use specific API.
Unlike a regular Cordova app, a Tabris.js app is built without HTML and its UI is truly native. Tabris.js uses Cordova in two ways:
Find out more about how Tabris.js and Cordova fill each other’s gap: [Apache Cordova vs Tabris.js] (http://eclipsesource.com/blogs/2015/03/02/apache-cordova-vs-tabris-js/).
If you want to keep up with the latest developments in Tabris.js, you can consume tabris.js from the dist tag
package.json, set the dependency for tabris to
"nightly" or run
npm install tabris@nightly.
In the build service, select nightly for Tabris.js version in build settings.
Many Cordova plug-ins that provide access to device functions will work out of the box. However, plug-ins that access the DOM of an HTML page won’t work because Tabris.js uses a native UI.
In order to test additional plug-ins you will need to create a custom build app.
You can either create a release-ready version of your own app, or an enhanced version of the developer app which contains the additional plug-Ins.
For the latter, set debug mode to
We don’t store your credit card data. We use Braintree to process all payments, and it never passes your credit card information to us. Braintree is a certified Level 1 PCI DSS provider.
If you are using Cordova plug-ins, the plug-ins themselves are responsible for adding all necessary permissions, in which case you don’t need to handle them at all.
If you are targeting pre Android 6 devices and you need to modify permissions yourself at build time, you can create a build hook (official Cordova hooks guide).
You have to use an app store provisioning profile if you want to submit the app to iTunes connect for verification. Otherwise use an ad hoc profile to run the app on your devices.
Make sure that you have downloaded the right certificate and provisioning profile from developer.apple.com. The certificate should be for “Production” use and the provisioning profile for “Distribution”. Then upload the provisioning profile with the corresponding p12 file at tabrisjs.com.