Bored Room Bingo

Group 11: Andrew Carey, Tom Reinhart, Ian Wilkes

We implemented three use cases in iteration 3
1) Login with email: Firebase server authenticates user email / password
2) Login with Facebook: Calls FB api, which authenticates user based on their FB account
3) Sign up. User enters email and password. If email is unique, server adds account.
In short, we accomplished the login/ signup part of the application. This is displayed in our test cases. Our good login test case demonstrates that – after a valid username/ password is entered – a token is returned with the appropriate user data we expect. On the flip side, our bad login test demonstrates that – after an invalid username/ password is entered – the user will still not be logged in.
We have also produced HTML documentation for the classes we have been using. (Link)
This was what we hoped to accomplish, as this allows us to focus more the game side of the application in the upcoming iterations.
Going off this, we plan to implement more game specific features in iteration 4. Specifically:
1) Create a very basic Bingo Game
This will display words on the screen. A tile will be responsive to user actions. Also, game creator should be able to add other users.
2) Join a game
We want to implement a public game. This way, we don’t need to worry about Friends.
3) Adds words to a list
User can add words, which are displayed on Bingo board. This should be open to anyone in the game.
4) Logic to board
Set up rules to Bingo, so that a game can be run.

Broadly speaking, our goal in future iterations will be to build out. In iteration 5, we would like to have private games, the ability to leave a game, and social consensus working. Essentially, we want all the key features to be accounted for.
Iteration 6 will primarily serve to get as many of the other features done as possible. The icing on the cake, so to speak. Included in this will be chat, user profile, victory sounds, and anonymized names.

DOXYGEN Docs