Adam Terlson

Building an app destined for production is a daunting task, especially to replace existing legacy apps available for download in the App and Play Store. We could have pursued a typical release strategy—instead, we got creative with React Native.

We built a strangler-style architecture, a technique commonly reserved for web services, to release our greenfield React Native product user-by-user. The effect was some pretty unique and awesome advantages to how we built and tested our new app—but software is never perfect.

2019

React Amsterdam

Strangling Legacy with React Native

I will articulate what I have come to find to be a superior approach to building React applications — treating them as functions, not templates.
I will introduce how to:
- Separate the application you’re building and the platform its on from the components you write (Hey, that’s this one! Read on!).
- Inject state into your application, and what a “container” aka “connected” aka “smart” component really is.
- Implement more complex features by leveraging Higher Order Components and a compose function — it’s awesome.
- Make your application UI understandable by looking at a single file, not dozens.
- Make your codebase flat without sacrificing grokability.

https://gist.github.com/adamterlson/7997795e4735f5c4a495c8dabd4c368a