Thought of the pun "Tweat" of the word "Tweet" and thought of Twitter user data visualisation using an Agar.IO like game environment.
What it does
Players are represented as 'blobs', these blobs have a size proportional to the influence of a Twitter user. When one user tweets another in the game they will being travelling towards them. When a user sends a tweet they grow in size. When a player encapsulated another it gains the others influence.
How I built it
Twitter as a backend, Java as a back/frontend.
Challenges I ran into
Twitter API usage limitations, rather obscure bugs.
Accomplishments that I'm proud of
What I learned
The value of planning and scrum meetings.
What's next for TwEAT
Open source on GitHub (as soon as we remove API keys...)