GameNight is a web app that records & analyzes group game nights without the hassle of tracking everything by hand with pencil and paper.

Having watched my family record countless domino games by hand with post-it notes and scratch pads, and seeing their struggle in organizing and tracking their games, I decided to upgrade their form of record-keeping to an online platform.

In addition to tracking games by hand, the issue of recording who won became an issue. While physical pieces of paper have finite space to write, an online application does not have to conform to those limitations and can record much more data as well as display connections between their data as charts and graphs in a visual format.

This began the month-long push of creating GameNight.

The two main goals of this project are to:

1. Learn about serverless architecture
2. Create a useful product that can be used in the real world.

Specifically, I want to do a deep dive into AWS products such as Amplify, Cognito, and Dynamo DB as well as learn more about GraphQL.

A group, defined as a family unit or collection of friends, can create a single account to track their entire group. Within this account, anyone can add members, games, and/ or record a game. This single account login allows any member at any time the freedom to edit the account. The idea behind this is that, while there may be multiple players who play a game, there only needs to be one player to record the game. This eliminates the need for every player to update the account and saves time.

Once members and games are added, a game can be recorded, and then the dashboard page will populate with data.

All users has their own collection of memmbers, games, and games played. This process is handled through user authenticaiton that filters data per account.

• 🏗 Create and edit members and games to your account
• ✍️ Record every game you play
• 📊 Analyze data from recorded games in visual graphs and charts

The analysis is the most interesting feature due to the endless possibilities of data visualization. Currently, GameNight offers four views of analysis:

• Game History: A table view listing each recorded game
• Leaderboard: A bar chart listing the number of wins and losses each player has per game
• Game Distribution: A pie chart depicting the fractions of games played
• Game Activity: A heatmap showcasing how often games are played by anyone in the group

1. Win to lose ratio (A moving average of a player's ability per game)

An additional tile view in the Dashboard

Currently, GameNight takes in three types of data:

• Games
• Members
• Recorded games (winners, losers, date, game name)

and outputs the same data, but only visualized, not truly analyzed.

Inputs of Winners, Losers, and a Recorded game creates a leaderboard, but it does not show any higher order analysis. For example, using calculus as a metaphor, when students take the derivative of a Position vs. Time graph, they get Speed. In this same manner, by taking the "derivative" of Players ("Winners" and "Losers") and a Recorded Game, a moving average can be calculated.

A moving average is simply the win to lose ratio a player has over time. This will normalize the player's wins and losses making it possible for members to view a fuller picture of who is getting better or not.

This can be implemented in the form of a line graph to depict the rises and falls of each player.

Overall, this will give members a clearer picture of each member's ability in a given game.

2. Update Notifications When updates are made, the user should be notified of any changes when they sign into their account.

I'm glad you are considering contributing to this project. I've poured a ton of hours into this and I would love to see any of your additions. Please read the following to make contributing easier for both you and me.

Note: You shouldn't need to install or setup any AWS services. Note: When you are prompted to sign in, use the following credentials:

• username: testaccount
• password:qwerty123

Feel free to edit this account as you see fit to complete your contribution.

If you have any issues logging in, please let me know.

If you see an issue that sparks your interest or if you would like to contribute something else please follow this guide:

• Branches should follow this format
  • feature/name-of-branch (a new feature that is being made)
  • update/name-of-branch (an update to an existing feature)
  • bug/name-of-branch (a bug fix)

Once you are happy with your branch, submit a PR with comments and a descripting documenting what you changed.

When I get the notification that you submitted a PR, I will review the PR and if there are no errors, merge it into main. If however, there are errors, I will provide you with what errors exist so you can fix them.