In order to skip the design phase of this app and really concentrate on the iBeacon related functionality, I've provided the view and map content in a separate responsive website.
Most of the content of our app will be delivered as responsive web pages presented in UIWebViews from http://museum.ibeacon.university/.
Our companion site also uses real-time socket connections so that you can actually see which exhibit you're currently visiting in real time from any browser as shown in the following figure:
iBeacon museum current visitors
The role of the supporting website is to track our user's journey but also to return the content associated to the beacon that they are nearest to. In order to do both and effectively track our user, we need to follow a strict order of calls to our service. We'll do this by maintaining a browser session in a hidden UIWebView, which belongs to our main view controller. Consider the following steps to track our user...