NOTE: this feature requires a Wayfinding & Navigation subscription (Explorer or higher) to be used. For more information email us at firstname.lastname@example.org.
Around 3 months ago we announced the big update – our technology-agnostic indoor-outdoor wayfinding was released as a private beta. We were overwhelmed by the interest towards the feature (we got on front page of Product Hunt!), and got a selection of excellent venues and developers as beta testers. For the rest of you, who have not experienced the tools yet first hand, we complied this update to summarize all the goodness that is going to be included in our wayfinding and maps layer that is going the be released officially early next year.
Take a sneak peek into the tools through this 5min video (text continues below):
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 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.
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.
In this tutorial, we are going to learn how to limit notification rate through the action flow. Note: this flow limits the events triggered from all geofences. Read More
Important: Even though this flow works in theory, in practice this type of usage is currently blocked by most email providers. We cannot help with issues relating to using this flow.
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.
This post covers the basics of the Proximi.io action flows. The same content is discussed in the Zero to Hero tutorial series part 2.6. If you’ve read that, feel free to skip to the next chapter.
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.