Getting Started on Mobile

The ChartIQ mobile SDK provides a native interface for iOS and Android developers to instantiate and interact with a ChartIQ chart. In order to use this mobile SDK you will need a copy of the Charting Library. Please contact to obtain an evaluation or permanent license.

Please read this tutorial outlining key information for building hybrid mobile applications using the Charting Library: Webviews and Containers.


Although the mobile SDK and the JavaScript library may use the same function call names at times, they are not the same and they are not interchangeable.

When using the mobile SDK, use the following documentation:

When directly calling the javaScript API use the following documentation:

Helper files and templates.

The following files are included in the library package to help you get going:

  • mobile/js/nativeSdkBridge.js: encapsulates simple functions to our library so any non-native javascript language can easily use it, without having to 'clutter' your code with string based queries.
  • mobile/js/nativeSdkAccessibility.js: an add-on for nativeSdkBridge.js that will help hook into the voice accessibility mode in both Android and iOS and allow for custom announcements of quotes.
  • mobile/sample-template-native-sdk.html: is nearly identical to sample-template-basic.html but with a custom quotefeed that can be used by a non-native javascript interface. It provides a simple html application that can be put into a mobile WebView to interface with our javascript bridge library (nativeSdkBridge.js).

Mobile specific library settings

Crosshair offset

By default, the cross-hair location will be slightly offset so a user can see where the cross-hair is instead of having render it right under their finger. This is done because in small devices, especially when displaying small candles the finger will cover a large area, losing track of where they are.

You can adjust the offsets by modifying the following parameters:

Device identification

The following flags are available to identify devices:

Next Steps: