Personally my experiences with iBeacons have been horrible. For an app of any real scale, you want to control your own messaging, but most of the vendors in this space want you to use their messaging platform (otherwise, what would be the point in partnering with them?). Unless you go all in and do it yourself, you&#x27;re potentially setting yourself up for a very fragmented user experience and fruitless campaign.<p>Additionally, for iBeacons to work you basically need the stars to align (or for you to have some of the most trusting users in the world). You need:<p>* the user to have a data connection (likely and reasonable)<p>* always on location permission (depends on your app, possibly difficult to justify)<p>* the users bluetooth to be on (somewhat likely)<p>* access to send the user a push notification (in most cases, without this beacons are fairly useless as you&#x27;re using them to message the user in response to their location)<p>In my experience, getting a few of these isn&#x27;t hard, but getting them all requires a lot of story telling and justification (and rightly so!)<p>This is much worse on iOS than it is on Android, but with Android 6.0 you&#x27;re going to see the same issues for iBeacons are you now need to ask permissions as opposed to simply getting them as part of the installation process.<p>Essentially, in my limited experience with two different beacon installations, beacons are great in concept, but in practice difficult to turn a profit on.