![]() ![]() ![]() So with these two ideas in mind, rather than just creating a demo I thought it would be a good chance to address the common request for more information by writing this article and sharing it on DZone for other's to benefit. In addition NSLocationAlwaysUsageDescriptionone of my goals was to not hard code the beacon identifier and message in the app, but instead dynamically derive messages from a beacon cloud registry. ![]() This is a pretty common use case for beacons, but in building this I did discover that iOS's CoreLocation library doesn't make this entirely simple in the way that it raises events on our mobile user entering and exiting the beacon's range. This week's demo de jour (French was never my forté) is an iOS Swift iBeacon app designed to show a message when, say, our mobile user approaches a beacon identifying a theoretical shop "Chris's Emporium". In creating many proof-of-concept mobile apps and then presenting the apps at various events, we often get thanks from the audience but "can you please give me an article I can read to learn from your research and see how you solved the problem?" ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |