I am a bit confused about the importance of a CLBeaconRegion UUID and the string identifier. If my CLBeaconRegion already has an unique ID, what is the point of forcing the usage of an additional, non-unique string identifier? Is it purely "cosmetic"?
Since users will not be able to scan and connect to beacon regions as they do with WiFi (and SSIDs) for example, and since the receiver app needs the CLBeaconRegion pre-coded and pre-defined in order to enter and range for beacons in a region, what's the real usage of the identifier?
I've seen examples where people are using it for place things like com.companyname.app, which I thought made more sense, in case the identifier was used to match the signing certificate of the app (but it seems no!). Others have been using it to place names like "Beacon Example", "Apple", "Kitchen".
In other words, I don't get why the receiver also needs to specify a region.identifier since it doesn't know to which broadcaster name it will connect. No matter how I name the broadcaster, the receiver will always get the identifier defined on its side.