The Plan

We need users

1. A user should be able to log in and register.
   • Issues:
     • Done
2. A user should be able to edit his/her username (cvan), display name (Sea Van), avatar (gravatar), bio, and homepage URL. Changing the email address is something that the user needs to deal with with Persona.
   • Issues:
     • cvan/galaxy#22
     • cvan/galaxy-api#23
     • cvan/galaxy-api#24
3. A user should be able to become a vouched developer, reviewer, or admin.
   • Issues:
     • cvan/galaxy-api#37

Developer profiles

We need games

1. A (vouched) developer should be able to submit a game.
   • Issues:
     • cvan/galaxy-api#29
     • cvan/galaxy-api#30
     • cvan/galaxy-api#31
     • cvan/galaxy-api#33
     • cvan/galaxy-api#35
     • cvan/galaxy-api#36
     • cvan/galaxy-api#37
     • cvan/galaxy#5
     • cvan/galaxy#17
     • cvan/galaxy#24
2. A reviewer should be able to review a game.
   • Issues:
     • cvan/galaxy-api#34
     • cvan/galaxy-api#37
3. A developer/reviewer/admin should be able to edit an existing game.
   • Issues:
     • cvan/galaxy-api#38
     • cvan/galaxy-api#39
     • cvan/galaxy#25
4. A developer/reviewer/admin should be able to feature an existing game.
   • Issues:
     • cvan/galaxy-api#40
     • cvan/galaxy-api#41
     • cvan/galaxy-api#42
     • cvan/galaxy#26
     • cvan/galaxy#27
     • cvan/galaxy#28
5. A user should be able to find a game to play.
   • Issues:
     • cvan/galaxy#27
6. A user should be able to accrue points on a leaderboard.
7. A user should be able to unlock achievements.
8. A developer should be able to use our navigator.game API to manage game state and player interaction (e.g., peer-to-peer, multiplayer text/video messaging; in-game notifications).
9. A user should be warned if his/her device lacks the minimum requirements (i.e., "buchets") needed to play the game.
10. A user should be able to play a game for free but access more advanced functionality via in-app payments (using Stripe or a home-rolled payments solution, for example).

We need a community

1. A user (authenticated or anonymous) should be able to share a game via Twitter, Facebook, or Email.
   • Issues:
     • cvan/galaxy-api#43
     • cvan/galaxy#32
2. A user should be able to add friends.
   • Issues:
     • cvan/galaxy#2
     • cvan/galaxy#10
     • cvan/galaxy-api#19
3. A user should be to be able to see the games his/her friends are playing.
4. A user should be to be able to see the games he/she is playing.
5. A user should be able to get recommendations for new games based on similar games, what his/her friends are playing, and what's trending in his/her region/language.

We need to help users

1. A developer should be able to use our RESTful API with ease.
   • Issues:
     • cvan/galaxy-api#44
     • cvan/galaxy#33
2. A developer should be able to use our developer tools with ease.
   • Issues:
     • cvan/galaxy#34
     • cvan/galaxy#39
3. A user should be able to play in our game centre with ease.
   • Issues:
     • cvan/galaxy#35
4. A user should be able to submit feedback about our game centre.
5. A user should be able to submit feedback about a game.
6. A user should be able to be able to look up public analytics for a game.
7. A user should be able to be able to look up analytics for his/her own game usage.
8. A developer/reviewer/admin should be able to be able to look up private analytics for a game.

We need tests

1. All API endpoints should be thoroughly unit-tested.
2. All UI functions should be thoroughly unit-tested and views should be thoroughly end-to-end-tested.

We need amazing performance

1. CDN
2. Statsd
3. Nagios
4. fastHAR
5. New Relic
6. Pingdom
7. Client-side JS errors (raven-js?)
8. Backend JS errors (Sentry for node?)
9. Navigation timing (sampled for 10% of users?)