Week 5 Update

After setting up the basic functionality of Firebase we finalized the structure of how we save meetings and manage attendees. We are able to save meetings based on a unique ID associated with each meeting, then when fetching attendees the app can sort which users where at a specific meeting using this ID.

While finalizing the Firebase architecture we were also researching and implementing geofencing. We wanted the admin to be able to select a location on Google maps where they would like the meeting to be and the radius for the associated geofence. We were successful at implementing this, providing a nice and simple UI for administrators. Then they create the meeting directly from the geofence. This also is able to get the users location as well.

The next step was fully integrating the two halves of our project (BLE/Firebase and location/geofencing). This went well and we were able to create a user list that gets populated from firebase when the admin request to see the attendance. Additionally the user is able to check into a meeting with just the click of one button. This is more involvement than we originally desired but is still really simple by design.