Proximity SDK is the latest version of our SDK for iOS and Android and we strongly recommend it for any proximity-based use case.
Ever since Estimote was founded in 2013, we've been recommending iBeacon and Core Location as the best solution for all of our developers. We've used it too in all our apps and wrote countless tutorials on making successful projects this way. And many people did.
Truth be told, though, there were also some limitations (e.g. 20 regions limit, exit events’ responsiveness) that we couldn’t overcome. We also wanted to make the tech even more reliable but since we couldn’t tinker much with Apple’s technology, we’ve ultimately developed our own Proximity SDK using Estimote Monitoring as the default packet. It allows you to monitor for as many beacons as you want and the exit events happen faster (no need to wait for 30 seconds anymore). You can also define at what distance (more or less) the event should happen instead of having to rely on the often-finicky physical range of the beacon signal. And on top of all these things, it allows for secure broadcasting, Fleet Management, Analytics and many others.
If you're interested in numbers, check out our article on Estimote Monitoring. And for a detailed comparison of Core Location and Proximity SDK, visit our Developer Portal. But we'll be honest with you, there's no better SDK on the market for enter/exit events.
If you wish to get started with Proximity SDK, head to our Developer Portal where we included a handy step-by-step guide. All our templates in the Estimote Cloud also work with the latest Proximity SDK so get the one of your choice and test for yourself.
If you already have a project running but you're not happy with the performance of beacons, Proximity SDK might be the solution you're looking for. Head off to the Developer Portal where you'll find many code snippets for both iOS and Android. We'll be happy to guide you in the right direction, just let us know.
If for some reason you don't want to try Proximity SDK, you'll be happy to hear that all our beacons are compatible with Apple's Core Location and Google's Nearby API. We also have a tutorial on buildings solutions with each available on our Developer Portal. Would you mind sharing with us why you prefer either of those solutions, though? We're constantly working on improving Proximity SDK and we could definitely use some suggestions. So if there's a feature that our stack is missing, let us know and we might be able to prioritize its implementation.
Keep in mind that Estimote Stickers don't work with Proximity SDK as they broadcast either Nearable packet or iBeacon. In order to use Stickers in your project, you'll need to use Estimote SDK. You'll find all our SDKs on our Github.