Get an overview of the classes and intended functionality found within the app project file.
- [Instructor] Taking a look at our app, we see that we have a number of view controllers in our project. When a user first launches the app, they're brought to the menu table view controller. This is the class where we'd be performing a lot of our segues as users interact and activate the notifications that we push to them. We have three additional view controllers that we're gonna be presenting, and those are welcome view controller, dining table view controller, and attendance table view controller.
All of our view controllers have corresponding scenes in our main storyboard. And all necessary IB outlets, actions, and segues have been created and linked for each of these view controllers. Coming over to BeaconManager.swift, this is where the majority of our work is going to be performed. And this class is a singleton that performs all of our Beacon-related management. Currently, it's an empty class with only the declaration of our singleton, the importing of both CoreLocation and CoreBluetooth, and we've adhered to the CLLocationManagerDelegate.
Now that we've gone over our app, let's get started on our first important subject, which is how we will define and store multiple Beacon data in our app.
- What is iBeacon?
- Turning your iOS device into a beacon
- Discovering device locations
- Monitoring for iBeacons
- Responding to beacon discovery
- Creating a beacon-based app