Schedule

630pm Doors Open

630pm-715pm Happy Hour

715pm-800pm Talk & QA

8pm-9pm Networking & Close

Building Version 2 as a React/Flux Single Page App - Wins, Losses, Decisions and Lessons Learned

Our company's internal recruiting app outgrew its status as a MVP built on Rails. The team wanted to build version 2 of this application with UX as top priority and decided to build it as a React/Flux SPA with the Rails app serving as the backend. This was early 2015, before there was Redux or Relay. In this talk, we hope to share about our journey:

Why React and Flux: Technical decisions and architecture choices

Technical tooling, testing and deployment: The team's flow in getting code from development to production

Wins, losses and pitfalls: Dealing with the missing parts of Flux

What we gained from using React/Flux: Why not keep it on Rails or use Ember (the blessed framework of the team)

How we're integrating Relay incrementally into our stack

By sharing the team's journey and lessons learned, I hope it helps anyone thinking building a React SPA (or thinking about doing so) to have gain some insights on what we did.