player makes a great move / sees a great move in a race, and wants to be able to watch it later / share the moment with his/her friends. Player would like to mark/pin the moment to watch it later, and be able to even watch the whole race later.
Player would also be interested marks/pins made by other players.
Player would be interested in finding out about replays that have been saved/starred/pinned by lots of people, viral.
[ ] server stores all race results and their replay (as JSON or something more compact) (must) (1) (after MVP (aka once we care) we can prune those replays that are not starred/saved)
[ ] client can select any past game and visualize it (replay data is downloaded to client) (must) (1)
[ ] client has a list of its past games on the menu screen, and can select them to watch the replay (must)(1)
[ ] menu shows a slightly blurred replay in the background. the most impressive one, maybe the last league race. (must) (1)
[ ] replay visualizer has a unique url for the race replay, which can be shared with people. (must)
[ ] visualizer has queryoption to navigate to specific time/turn in the race) (could) (not so important since races are quite short right now)
[ ] client/server can generate gif of frame selection (must)
[ ] highlight of the race is detected and played to the players at the end. plus gif for it is auto generated. (should)
[ ] client has button that prompts tweet with gif and race link (should)
[ ] client can generate video of whole race (could)
[ ] (Optimization) Server and client can delete turn data for lavaed turns, while a replay can still be generated because whole race can be simiulated from the initial turn + events for each turn. This needs separation of Turn from Events. (could) (3)
Simpler way
[ ] client can locally save replay for the just-finished race
[ ] client/server can generate gif of frame selection
[ ] client has button that prompts tweet with race results
Meeeeeh storing replays in the server shouldn't be that hard, and it makes sharing much better. Can share link to race visualizer. <3
user flows:
player makes a great move / sees a great move in a race, and wants to be able to watch it later / share the moment with his/her friends. Player would like to mark/pin the moment to watch it later, and be able to even watch the whole race later.
Player would also be interested marks/pins made by other players.
Player would be interested in finding out about replays that have been saved/starred/pinned by lots of people, viral.
[ ] server stores all race results and their replay (as JSON or something more compact) (must) (1) (after MVP (aka once we care) we can prune those replays that are not starred/saved)
[ ] client can select any past game and visualize it (replay data is downloaded to client) (must) (1)
[ ] client has a list of its past games on the menu screen, and can select them to watch the replay (must)(1)
[ ] menu shows a slightly blurred replay in the background. the most impressive one, maybe the last league race. (must) (1)
[ ] replay visualizer has a unique url for the race replay, which can be shared with people. (must)
[ ] visualizer has queryoption to navigate to specific time/turn in the race) (could) (not so important since races are quite short right now)
[ ] client/server can generate gif of frame selection (must)
[ ] highlight of the race is detected and played to the players at the end. plus gif for it is auto generated. (should)
[ ] client has button that prompts tweet with gif and race link (should)
[ ] client can generate video of whole race (could)
[ ] (Optimization) Server and client can delete turn data for lavaed turns, while a replay can still be generated because whole race can be simiulated from the initial turn + events for each turn. This needs separation of Turn from Events. (could) (3)