Initial Wireframing

[kingdomlevel]

We need initial rough wireframing so that we can start to think about component structure for the client app

[johnpooley]

edited spelling of "wireframing"

https://drive.google.com/file/d/1dNS9l7AO8ULnMDUFWeloAgW1fqqnaCTv/view?usp=sharing <<--- WireFrame Link

[kingdomlevel]

This is looking so goooood! V exciting to be getting started on it...

I've been taking a look and trying to identify a rough component structure as it stands now... here is what I'm thinking:

components
  home
    AppTitle
    Rules
    GameConnect   // create/join
  lobby
    GameAdmin
    LobbyTitle
    GameShare     // thing w the copylink
    PlayerList
    Player        // might be overkill - just in case the PlayerList ends up beefy 🥩
  Game
    ChatLog
    UserInput
    GameProgress    // round 2/3 etc
    SongList
    TurnTimer       // points are awarded based on turn time - so could try and combo "toaster" in here
    PlayerList      // this probably includes scope of BreadBin to show all players + points, current active player, points earned in current round etc
    Player          // simple player-in-list component
  EndGame
    Results
    PlayAgain

The main thing I think is worthy of discussion is the TurnTimer / Toaster / BreadBin / PlayerList in the Game.

For my 2 cents, I think PlayerList will be capable of doing most of the heavy lifting. Consider the following scenario:

Name	Points in game so far	Points in this round
Meadow	3404	+760
Paulie	2450	+140
➡️ AJ	1856	...
Carmella	4245	+340
Tony	3476	...

Thinking that like names in bold (more likely names that are not greyed out or something) are players who have already had their turn in this round. So here, Meadow and Paulie have already had their turn to perform. As players perform, their names are coloured differently or something.
Something like an arrow indicates that it is presently AJ's turn to perform.
Ellipsis (...) inidicates that points for this round are still pending. In our scenario, Meadow answered first, followed by Carmella then Paulie. Tony is yet to guess correctly. AJ's points are pending as his performance is not over yet.

I also think TurnTimer (or at least the data it is rendering, maybe from parent) will be used for working out the score a player gets for a particular turn!

Any hot takes on this greatly appreciated 🙏

[kingdomlevel]

^ in terms of that component stuff also - basically each of these big sections (home, lobby, game, endGame) will need a container of some description also.... so not sure whether like components / containers will actually be a good file structure or not 🤔 i mean i guess it doesn't make much odds but just something to think about in terms of file structure!

[kingdomlevel]

I've copied this comment from Slack, not sure if this should be its own issue or should be added to rules or wireframes?

heres an idea, if we are going for a fixed number of rounds/turns for the end of the game, maybe the loaf of bread could represent all the remaining songs?

so when it's your turn you get a slice of bread with 3 songs written on it and you toast it for the length of the timer, it pops out of the toaster with the correct answer on it for all to see, rather than everyone has a loaf

Originally posted by @johnpooley in #3 (comment)

suggestion from John about re-structure of thematic components in gameplay

[johnpooley]

is this all front end components? will we need an equivalent for backend?