itzamna314 / boardgamebanker Goto Github PK

Implement securesocial to handle accounts, and enable some SSO providers. Could be tricky to do in one-page app.

Allow players to have a title unique to the game. I.e. house name from Game of Thrones, civilization from Chaos, order from dominant species, etc. Editable in-game to support smallworld civilizations a plus. Maybe including history?

Allows some scrolling on mobile devices. Page should be fixed and should fit comfortably on mobile screens.

Allow creators to specify resources to use in game creation. For instance, game of thrones could have separate resources for Supply, Influence, Fiefdoms, Iron Throne, and King's Court.

Remember recently used e-mails, and present a dropdown.

Use local storage, not db.

User should know when page refreshes

Allow game creator to mark game as finished. This would reveal all scores and transactions to all players.

Users should be able to delete games.

Games should be deleted after 1 day.

(Optional) users should be able to have a limited number of games that live longer.

Once securesocial is in place, allow users to post results on social media.

gmail seems to be unhappy with sending auto e-mails. May want to use cloudbees-provided free e-mail.

Allow users to edit username/email address.

Allow players to create new, player-specific resources on-the-fly. Differentiate global resources from per-player resources. Allow game creator to specify whether per-player resources are allowed or not.

Allow game creator to advance turn. Then each transaction happens within the context of a turn.

Clicking buttons should make adorable noises

Move menu bar for active game to the bottom.

Use ng-animate to add some fun animations on screen changes.

Users should see an indicator that the app is thinking while AJAX requests are processed.

Create transaction on the same page, above/below current total on direct interface. Submit transaction from same page.

Keep track of all player score changes in a new audit table.

At game creation, allow creator to specify options. These could include turn usage, number of turns, public/private scores/transactions, etc.

On create game, if there is an error, should be surfaced to user.