JocelynYH
commented
3 years ago hmm, what if we added another screen between the homepage and the turns. AKA what is we add a lobby. that way people can change options, read rules, and most importantly, see who else is in the game.
A lobby would also let us indicate whether or not a single person is a reader or a guesser, a distinction which isn't totally clear in the current UI.
I think the last big feature we need to add ( along with #34 ) before we're really in beta for this project is the ability to select what clue sets you want for a given game. Right now we've just got the base clue set ( #37 ) but I've already got some clues for additional clue sets like movies, books, etc (we've also talked about a set of inappropriate adult clues which I think is great). Now we just need to build in the ability for users to select what clue sets they want in their game.
We could do something like Codenames online, where there is an option on the home page, but I actually think keeping the home page clean and adding it within the game page would be better. The backend is also set up to accommodate changing the clue sets at any point in time without messing anything up, so users should have the ability to update their selections whenever they want.
I'm thinking from the backend perspective, setting up an API endpoint _get_cluesets which would return all available clue sets for users to select from and an additional socket endpoint, _update_cluesets, that would take a list of clue sets and update them for a given game. The front end would then just need some additional form that shows what clue sets the user is currently using and allow them to update that list (the list of current clue sets would also become a field for the game state object).