Build native mobile chatbot app connected to Watson Conversation

Briefly about the architecture here: The app will include only one screen – a chat thread. Together with a form containing textinput field to enter user inputs. Conversation history will be collected in Local Database (on mobile device), and displayed in chat-thread-style using Kinetise LIST widget. First, you need to set up Watson Conversation on IBM Bluemix. … Continue reading Build native mobile chatbot app connected to Watson Conversation

Build native mobile chatbot app connected to Watson Conversation Add-on: using dynamic variables throughout chat

First part of Watson Conversation tutorial described how to quickly develop chatbot native mobile app, but not too dynamic one. User input was the only changing piece of data submitted to Watson Conversation API, while this API is much richer and enables or in some cases even requires more data to be delivered. For example, payload … Continue reading Build native mobile chatbot app connected to Watson Conversation Add-on: using dynamic variables throughout chat

MUST READ: Integrating Kinetise with any backend

In this tutorial you will learn how to connect your app to existing RESTful APIs. API Specification page at Kinetise Help Center describes all the rules Kinetise-powered app uses when interacting with external systems. It is a key reference when integrating app with custom backends. As a sample backend we will use a test service … Continue reading MUST READ: Integrating Kinetise with any backend

Injecting data from the backend to Kinetise mobile app

There is variety of ways data, information and variables can be delivered to the mobile app to be stored for later use. When making API-call via POST or PUT method, and server responds with status 200 “success”, the mobile app can read and parse response body payload. Below is example body of such response: { “message”: { … Continue reading Injecting data from the backend to Kinetise mobile app

Screen animations

Screens are main components of Kinetise application and sooner or later you will have multiple screens in your app. To move between screens you can use many different types of navigation regarding your application design. No metter how this navigation looks like, to go to other screen in Kinetise you use “actions”. You can read … Continue reading Screen animations

Changing status bar color to match your application color scheme.

To make the application blend better with the system, you can change your phones status bar color to one that matches your application better. There are two places where you can modify this. One is application Skin, that lets you define default appearance for whole application. The other place is screen settings panel, where you … Continue reading Changing status bar color to match your application color scheme.

How to inject Local Variables to mobile app from backend

There is an easy way to inject those variables, when application is making API-call using POST method. We need some preparation though. We need a backend script, which will send response, after being queried from the mobile app. Our test one is here: http://assets.kinetise.com/variables.php. It looks like this: <?php header(“Content-Type: application/json”); echo “{\”message\”: \”Success\”,\”applicationVariables\”: {\”my_variable\”: 123}}”; <font-size=14>so the … Continue reading How to inject Local Variables to mobile app from backend

How to initiate values in FORM fields and TOGGLE

This is a bit tricky. As you might have noticed, each subwidget for the FORM widget (i.e. TextInput, Dropdown, Checkbox), can have “Init Value”. You can retrieve it from the backend by switching this “Init Value” to “Dynamic” mode… if it wasn’t disabled. To enable it, whole FORM must be put inside another widget, which retrieves … Continue reading How to initiate values in FORM fields and TOGGLE

How to define logic deciding which screen to go to, based on server response

The scenario is this: application makes the API call (or sends data via FORM widget to API), and then navigates user to screen A or screen B, depending on server response. The order of events would be like this: a. User taps a button or submits a form from a mobile app. b. Mobile app … Continue reading How to define logic deciding which screen to go to, based on server response

How to populate Dropdown with values defined in KinetiseCMS?

1. You need two tables in Kinetise CMS, so create them: * “temp” * “selections” 2. In “selections” table add some values and numbers into first two columns, like this: 3. In “temp” table, add new column: type: Relation, name: “dropdownselections”, related table: “selections”. Like this:  4. Now click  and check all selections from “selections” table: 5. You … Continue reading How to populate Dropdown with values defined in KinetiseCMS?

Google spreadsheet as your data backend

Displaying data from Google Sheet Firstly, publish your sheet and get public URL address (File -> Publish to web). Now in Kinetise editor drag List widget  and drop it in application editor screen. From right menu select “From Google Sheets”. Paste your URL address to a sheet that should be displayed and click “OK”. Editing Google … Continue reading Google spreadsheet as your data backend