In Part 1, we talked about how at Opendoor we made some decisions in the way we’re using React, and how anyone running React in a real world production app might need to make those same decisions, and why. In this part, we’ll walk through how to actually implement those decisions.
First, let’s recap the React stack that we settled on:
“Hey, I have a ticket to Nordic.js in Stockholm next week, wanna pop over?”
… asked my friend last week. My immediate response?
Next thing I know, I was on a plane to Stockholm. ✈️
Little did I know that it’d turn out to be one of the best experiences I’ve had at a conference in a long time! …
This article will share how we at Opendoor used React in a real world production app, the decisions we made, and why.
You’ve probably heard of React and have been told how awesome it is and that you should be using it. You can find many “React Starter Kits” out there that get you up and running with a basic app in React. But when you try to use it for anything production-ish, you quickly realize that to do something useful, there’s a slew of tools and packages that you’ll need.