Tookan is a delivery management software that assists companies in streamlining dispatch processes and improving communication between managers and delivery drivers.
Canny is a cloud-based solution that helps small to large businesses collect, analyze, prioritize and track user feedback to make informed product decisions.Canny Integrations
It's easy to connect Tookan + Canny without coding knowledge. Start creating your own business flow.
Trigger when new task created.
Triggers when a new comment is created.
Triggers when a new post is created.
Triggers when a new vote is created.
Triggers when a post's status is changed.
Adds a new agent
Create a new customer.
Create a Delivery Task
Create a Pick and Delivery Task.
Creates a pick task.
Create an Appointment Task
Create an FOS Workflow Task.
Changes a post's status.
Tookan is an open source distributed system for building, distributing and publishing mobile applications and services. It is based on Apache Cordova and supports Android, iOS and Windows Phone through one API. (http://tookan.io)
The purpose of this section is to explain how Tookan and Canny work together to provide a better mobile application experience. First, we are going to install Tookan. Then we are going to install Canny. Finally, we will tie them together and explore the advantages of this integration.
First things first, let’s begin with installing Tookan in our mobile application. We are going to do this using the Node Package Manager (NPM. NPM is the standard Node.js package manager which enables us to manage our dependencies easily by using the “npm install” command. It is the default package manager for Node.js projects. To use it in our project, we have to add “npm” as a global dependency to our project’s package.json file.
Installing Tookan via NPM gives us access to an up-to-date version of the library from NPM. To make sure that this is the case we can check the version of Tookan by running the fplowing command:
npm info tookan --version
This should output the version of Tookan that we have just installed in our project:
C:projectsmy-project> npm info tookan --version 2.0.0
For more information on setting up Tookan please visit. https://github.com/tookan/cordova-plugin-tookan#installation.
Next up on our journey is installing Canny (https://canny.io. If you need assistance with installing Canny, please visit https://canny.io/docs/quickstart/. Once we install Canny, we need to set up an account so that we can use it without restriction by creating an account at. https://canny.io/signup/. As you can see from the image below, when you create an account you are immediately given access to the full functionality of Canny for one week for free! This will allow you to get familiar with Canny before deciding whether or not to pay for a subscription. Note that every new account also gets a free 14 day trial of their premium plan (which includes unlimited users, 3rd party integrations, advanced analytics, etc.. Note that after the 14 day trial you will be charged $179 per month for their premium plan ($199 if you pay annually. For more information about pricing please visit. https://canny.io/pricing/. After I create my account I am redirected back to my account page where I can start exploring all of the features that are available to me now that I have an account. When I click on “Analytics” I am given access to all of the analytics features which include. Real-Time Dashboard, Historical Data Analysis, Insights Explorer, Actionable Metrics and Custom Reports. Real-Time Dashboard. The Real-Time Dashboard provides me with real-time insights into my app’s performance and user behavior within a single location where I can view my data and analyze it in real-time. Historical Data Analysis. The Historical Data Analysis top gives me access to various reports and charts so that I can analyze my historical data which gives me deep insights into my app’s performance, traffic and user behavior over time. Insights Explorer. The Insights Explorer top helps me gather insights about my app’s user behavior by giving me an overview of all of my app’s activity over time including its online traffic, sessions, retention rate and user retention rate. Actionable Metrics. This top helps me view my app’s session data, visit duration and frequency data so that I can pinpoint interesting trends with regards to how my users behave while they are using my app as well as what they are doing when they are using it (i.e., which features they use most. Custom Reports. The Custom Reports top allows me to create custom reports which help me gain deeper insights into my app’s user behavior so that I can determine what aspects of my app are working well and what aspects need improvement. For more information about setting up an account and getting started with Canny please visit. https://canny.io/docs/quickstart/. Now that we have both Tookan and Canny installed in our project, we are ready to tie them together! For more information regarding how to tie them together please refer to the fplowing tutorial. https://canny.io/docs/quickstart/. Once we finish tying them together we should see the results in our Real-Time Dashboard as shown in the image below. As you can see in this image there are two separate groups of pie charts (one for Android devices and one for iOS devices. as well as two separate groups of line charts (one for Android devices and one for iOS devices. The first thing that stands out in this image is the fact that there is zero difference between the two iOS line charts! Because there is no difference between these two line charts the X axis has been removed from these line charts in order to make room for more data points since there is no difference between them anyways (note that these two line charts still have the same Y axis so it is still possible to tell which line chart corresponds to which group of values. The second thing that stands out in this image is the fact that there are four different lines being displayed on each Android chart but only two different lines being displayed on each iOS chart! This difference in lines is due to the fplowing reason. In order for a particular device type (for example Android. to be considered "active" it needs to meet a certain criteria (which is currently set at 100 Sessions. This means that if we have 100 sessions recorded for Android devices then they are considered "active". However, if we only have 50 sessions recorded for iOS devices then they are not considered "active" because they do not meet our "active" criteria. This means that Android devices must have 100 sessions recorded in order for them to be considered "active" whereas iOS devices must have 200 sessions recorded before they can be considered "active". This criteria was chosen as it works well with Tookan which has a default limit of 100 sessions per device type (which means that if we have 100 sessions recorded for Android devices then those 100 sessions will be tied directly to their device type which makes them "active". Finally, note that there are green numbers displayed under each group of charts indicating how many sessions have been recorded for each device type (for example 29 sessions have been recorded for Android devices and 44 sessions have been recorded for iOS devices. Also note that each session has been assigned a unique number (which corresponds to a specific device type. so that we can relate any particular session back to its corresponding device type. You can view these unique session numbers by hovering over each individual pie chart or line chart respectively as shown in the image below. This image shows the number of sessions recorded for each device type underneath each group of charts so that we can see how many sessions have been recorded for each device type (note that this number is updated automatically whenever new sessions are recorded. Let’s go ahead and click on one of these green session numbers so that we can explore some aggregated data points related to this session (this will give us some insight into how this particular session was recorded. Once we click on one of these numbers we should be taken to our Analytics section where we will see a detailed report related to this particular session as shown in the image below. From this image we can see multiple sections containing valuable information related to this particular session. The first section contains general information about this session including its Session ID (which is unique), Device Type Name (which matches the name that was assigned based on its unique device type identifier), Session Duration (which denotes how long this session lasted), Session Start Time (which denotes
The process to integrate Tookan and Canny may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.