Native Apps: Moving to React Native

Client: Patch Media, 2021

Summary: Moving to React Native apps created faster development cycles and more control

I was able to relax knowing Cedric would bring as much value as possible from the situation.

- Head of Engineering

Problem: The iOS and Android apps were built by a contracted overseas team:

Solution: Move the iOS and Android apps to React Native to bring the projects to the same language as other projects in-house:

Acknowledgements: I'm incredibly thankful to Matt Zuzolo for getting me up to speed on Patch APIs, Brian Reidy for constant source of good code and good will, and everyone else that helped that project go more smoothly.

&

Client: Huffington Post, 2018

Summary: Moving to React Native allowed more of the engineering team to contribute

Cedric managed the transition of our most important app users on iOS and integrated with 3rd payment providers at the same time.

- Director of Engineering

Problem & Solution: The same promise of a single codebase, easier to onboard engineers, and a common language with the web app drove the decision to move the iOS app to React Native.

This process was less smooth. It was both early in the lifecycle of React Native and we didn't gracefully handle off-boarding iOS engineers.

Ultimately, once the apps were in React Native, we were able to move much more quickly and in-sync with other teams at HuffPost.

Native Apps

Sometimes code isn't the answer

No code refers to the process of using tools and platforms that allow you to build technical solutions that previously would have required code to accomplish.

The advantages of no code solutions include:

Of course, this comes with tradeoffs: