This is a game written with exponent, react-native and redux.
Here are a few quick notes. I'll write a longer blog post soon explaining in more detail!
- Redux actions are used for all game events. For example, the
{ type: 'TOUCH', pressed: <whether pressed> }event, when dispatched, causes the game's reducers to respond to a touch press. You see in the above GIF image aqueueDispatch(...)call which queues an action for dispatch on next'TICK'(which is itself an action{ type: TICK, dt: <time since last frame }which advances game time bydt).'Touch'dispatches the'TOUCH'actions,Clockthe'TICK'ones. - There is a babelified remote-REPL interface. Works on simulator as shown in the GIF image above, works on device too. The REPL has access into the context of a module, and can modify private variables or update functions in there. So, hot-reloading (gotta clean up some details)! It shouldn't be too hard to make an emacs or atom interface that's similar to SLIME for Lisp. Since it uses babel and also seems to catch the project-specific
.babelrc, you can use fun ES6 things. - The game has time travel. Redux makes this easy. After you lose, if the plane is still on screen, a touch makes the game start going backwards in time (a quick peek of that in the GIF image above). Sort of like Braid.
- I tried to be super modern and used stateless function components and nice destructuring etc. everywhere.
- You can queue dispatches from within reducers. Reducers get their usual
state, actionsparameter but also adispatchparameter which queues actions to be performed after the current action is fully reduced. Used here for example to queue anADD_PIPESaction (handler visible a few lines of code below) when the distance to the next pair of pipes is< 0.