Proximi.io Blog

Most interesting case studies and how-to guides from the field of mobile positioning
Apr 03 2017
0

Part 9. Integrating to your own app

By | From Proximity Zero To Hero, Tutorials | 4 Comments
Menu
To integrate to your own app

Now that you are ready with your setup, We do warmly recommend testing it out with our Management Applications, to ensure that everything is working well regarding your setup. Once you are happy with the result, go ahead and integrate our platform to your application!

For each framework we have both an SDK file, and a base app that can be used as the starting point for app development.

Note: You’ll find your auth token on the portal under “Manage Application”. There are two seperate token types and the default token to use is the Mobile token, but there are some rare cases where using the other token is also applicapble. Here is a rundown of which token to use:

Master token and Mobile Token

 

Master token

Master token is the key to all of your account’s features. The Master token will grant access to all objects and all operations (CREATE, READ, UPDATE and DELETE). This is especially meant to be used when doing REST API calls with our endpoints. We strongly advise you to use this token with care and only use it in the mobile app when it is detrimental to the functionalities of the app.

There can only be one master token and this token cannot be deleted or changed. If you believe the master token has ended up in the wrong hands, please inform us immediately and we will change it for you.

 

Mobile token

On the mobile side we have made some precautionary security measures to prevent your master token ending up in the wrong hands. With the mobile token you get access to all objects with limited operations. If this token ends up to the wrong people, they don’t have the ability to delete and create any crucial elements of your setup.

With the Mobile token you READ for core objects like places, geofences etc. and READ & WRITE for position updates and event. This token is recommended to be used within mobile applications when using our SDK.This applies when you are integrating our SDK into your own application, when you are asked to provide our auth_token, you should use the Mobile token for this matter. More information can he found here: (https://proximi.io/part-8-integrating-app/)

NOTICE! There are exceptions to using the Mobile token in apps. In use cases where the app requires functionalities like CREATING and DELETING objects within the app, you would need to use the Master token.

You can create multiple Mobile tokens to with different setups and they can be changed and deleted, if needed.

Android_Robot_100
Android

Documentation
Gradle file
Starter app

logo_ios

 

iOS

Documentation
CocoaPod
Starter app

logo_cordova

Cordova

Documentation
Cordova plugin
Starter app

logo_ionic

 

Ionic

Documentation
Cordova plugin
Ionic starter app
Ionic 2 starter app

dbs-cassandra

REST API

Documentation

Sep 28 2016
0

Part 3.4. Gimbal Beacons

By | From Proximity Zero To Hero, Tutorials | No Comments
Menu
This post will guide you through the whole process after you’ve received your Gimbal beacons. We’ll look into Gimbal configuration and finally importing the beacon fleet using Proximi.io Web Portal.

If you haven’t ordered any Gimbal beacons yet, you can do that using the Gimbal Store https://store.gimbal.com/.

We also recommend you to check out the previous articles in this tutorial series to get all the basic things done before importing any beacons.

Read More

Aug 17 2016
1

Testing with Proximi.io Management App

By | Developers, From Proximity Zero To Hero | No Comments
Proximi.io Management app is available for iOS and Android devices.  The main purpose of the management app is for quickly to test how the actions and analytics work, and to see how your indoor positioning setup functions. You can also use the management app to add places, import beacons and so forth, but that is not the optimal way. It is best to finalize your setup on your computer, and use the management app just for testing.

Read More

Aug 15 2016
0

Part 4. IndoorAtlas

By | From Proximity Zero To Hero, Tutorials | No Comments
Menu
indooratlas_tutorialThis post will guide you through the whole process from getting started with your IndoorAtlas account. We’ll look into setting up your venue on indoorAtlas, and finally connecting to your IndoorAtlas venue using Proximi.io Web Portal.

We also recommend you to check out the previous articles in this tutorial series to get all the basic things done before getting your hands on geomagnetic positioning. Read More

Aug 13 2016
0

Part 3.3 Sensoro Beacons

By | From Proximity Zero To Hero, Tutorials | No Comments
Menu

This post will guide you through the whole process after you’ve received your Sensoro beacons. We’ll look into Sensoro registration and finally importing the beacon fleet using Proximi.io Web Portal.

We recommend you to check out the previous articles in this tutorial series to get all the basic things done before importing any beacons.

Please note: Even though it’s possible to add beacons into our platform manually or using the management applications, it’s highly recommended that you use the import tool in the web portal to add the beacons. Read More

Aug 08 2016
0

Action flows

By | From Proximity Zero To Hero, Tutorials | No Comments
Action flows are optional event chains that are processed within the Web Portal instance. Action flows can include interactions with third party systems as well as with the visitor’s mobile device. Action flows are stored in our backend database, but performed within the Web Portal instance.

Our action flow editor is based on the Node-RED project which is a creation of IBM Emerging Technologies. We’ve added our own storage driver and improved the overall stability of the system, but it’s still compatible with the original Node-RED project and especially with all the community built nodes that are available.

Read More