In August, we introduced the first version of Estimote Monitoring, with an improvement to microlocation experiences and more developer control over what happens when users enter/exit the beacon’s range (more about it here).
It was the first version of that feature and understandably, had its shortcomings. You gave us tons of valuable feedback, so we had our work cut out for us in the last few months. Here’s what we’ve been up to:
Fewer unexpected notifications
The first issue we addressed in this release can be summarized as such: “I do nothing, and notifications pop up on my screen!” This could be observed in certain areas that are challenging in terms of physics and radio signal responsiveness, like inside a car or in a room with many people inside.
Fewer missed notifications
Another reported Monitoring issue was related to the app being stopped while not in the foreground. After exiting the beacon’s range and staying away for an extended period of time, Monitoring would not respond when a user reapproached. Now it does, every dang time!
Give it a try
We’ve included fixes for the said issues in the latest Estimote SDK. To use the new version of Estimote Monitoring, configure your beacon’s settings accordingly by using the code snippet available here. Then, you can use an app generated in Estimote Cloud if you want to start a project from scratch, or use the template’s code for your own app.
If you have any further suggestions, or if the aforementioned issues occur, please reach out at contact@estimote.com.
Alex & Bartek, Beacon Reliability Engineers at Estimote