We are happy to share a successful project with our platform! We got the pleasure of getting to know two Cognitive science students from Sweden with a great idea. They wanted to include a functional aspect to their thesis about Icon based Indoor Navigation and decided to develop an app that uses proximi.io’s platform for navigation. The result is a very interesting take on wayfinding and here follows Kristoffer Karlsson’s and Arvid Horned’s thoughts about their project:
“Did you know that the apps and tools you use for daily assistance may be bad for you?
Dear Proximi.io blog readers,
I hope your summer is going as well as ours! Our regular blog readers are most likely aware that Proximi.io started to look for our next new talents in the end of May. We were happy to see a great amount of amazing and interesting applications, thank you for those who applied!
This post will provide you the results of our exciting recruitment. We are more than happy to write and share our very first blog post here with our new hires and tell you a bit more about them. So Kalle and Jenni, welcome to Proximi.io!
We are thrilled to announce that Proximi.io has closed its second funding round! Butterfly Ventures will be joining Proximi.io as a new investor alongside the previous Finnish and Danish investors. This means that we will have even better resources for improving the technology and growing our business from now on – and that we are hiring!
Official press release underneath.
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.
This a topic that we discuss very often with developers and marketers. How can I create a geofencing campaign that will be able to push a notification in the background? This blog post will cover the whole issue, as clearly as possible. This is the geofencing-for-dummies version. If you don’t want the whole babble, skip to the summary.
This post was updated 2nd May 2018.
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
We’ve added a very important update for the SDK’s permission request handling (location & BLE). You now have the option to do that manually, or though utilizing the ready-made calls in the SDKs.
In the previous SDK versions the permission requests were handled automatically in both iOS and Android. Now the permission requests need to be fired up manually:
- Android: public void checkPermissions();
- iOS: [[Proximiio sharedInstance] requestPermissions];
Alternatively you can handle the required permission requests fully on your own in which case the SDK’s wont be asking for any permissions as they already exist.
If you update the SDK’s in your existing projects, make sure to change the permission requests according to these instructions. This poses no breaking changes to currently running applications, until the SDK’s are updated to the newest versions (version 2.4 in Android and version 1.1.7 in iOS).