Live data from Hacker News

Transition to React Native

blog.coinbase.com

31–40 of 221 posts

Re: Transition to React Native

#31
post #23

Earlier quoted context omitted.

How utterly dismissive. They rebuilt their apps, increased the number of developers able to contribute to their codebase and improved metrics. That should be praised. Their point about brownfield development was a good one. In my experience the intersection between RN and Native (both code and people) is the biggest impediment.

AirBnb went exactly through this transition and back... Coinbase is just behind by a couple of years. Perhaps Coinbase' engineers, are better, or a different breed from Airbnb' ones, or perhaps React Native has matured more since 2019. Can't give you an answer. Linkedin had the exact iteration years ago. They had one of the first NodeJS Apps, driven mobile apps, and made some glossy block posts, praising it. Then qui…

The article specifically mentions that they spent a lot of time interviewing AirBnB about their experience and links to the same post.

"If you’ve read Airbnb’s excellent Sunsetting React Native article, these challenges may sound familiar. We spent many hours speaking with engineers from Airbnb and trying to learn from their experiences. We’re grateful to the team for sharing the details of their journey, as the information was invaluable in deciding the best path for Coinbase. One of our key takeaways was that the brownfield approach seemed to be core to many of the challenges they faced. While the idea of incrementally migrating is at first glance appealing — leveraging the benefits of React native for new features without the upfront cost of a full rewrite — it introduces significant technical and cultural migration risk over the long term."

Re: Transition to React Native

#33
post #12

Two years from now, it will be 'why did we decide to move on from React as it was not working out' blog post It is like the circle of life with native vs semi-native (which react is), and just html apps. Teams build a fast new version, looks great as it is new code, without much baggage, and over time it gets bloated and people complain that it takes too much to debug/develop on it. Some people in a internal team wri…

RN is better from the business point of view. I have noticed that some devs don't like RN, because they can't write native code or they only can write native code to Android/iOS. So they can't do everything and are disappointed.

Re: Transition to React Native

#34

I've been doing a RN app lately after not using it for almost two years. It's still a very fast way to iterate on both Android & iOS but it also still feels extremely brittle. I've tried and failed to upgrade to the latest version of RN several times now but every time gotten tangled up in dependency hell. I also haven't been able to get it to build on my M1 Mac at all. RN is good for fast prototyping and market valu…

If at all possible, I can't recommend Expo enough. I hated building RN apps prior to it, and now I hate building apps without it.

Re: Transition to React Native

#35
With regards to UI elements and layouts nothing beats React and Flexbox CSS on mobile. Also, when it works correctly Expo is a pure bliss.

C'mon iOS devs you can't tell you enjoy the byzantine layout model of the native iOS apps and working in xCode.

Some parts of React Native are problematic but creating screens is simple and intuitive.

Re: Transition to React Native

#36
post #12

Two years from now, it will be 'why did we decide to move on from React as it was not working out' blog post It is like the circle of life with native vs semi-native (which react is), and just html apps. Teams build a fast new version, looks great as it is new code, without much baggage, and over time it gets bloated and people complain that it takes too much to debug/develop on it. Some people in a internal team wri…

The airbnb cycle

Re: Transition to React Native

#37
Having just finished an 8 month Expo RN contract I'm excited to never touch it again. For personal projects keen to see how far I can go with Svelte PWA + Capacitor.

Google + Microsoft should really double-down on PWA apps. I think at one point Microsoft was crawling the web and automatically listing any PWA in their app store. If that became the norm then maybe Apple will make their PWA install UX less deliberately clunky.

Re: Transition to React Native

#38
post #12

Two years from now, it will be 'why did we decide to move on from React as it was not working out' blog post It is like the circle of life with native vs semi-native (which react is), and just html apps. Teams build a fast new version, looks great as it is new code, without much baggage, and over time it gets bloated and people complain that it takes too much to debug/develop on it. Some people in a internal team wri…

Have you worked with React Native or done other mobile development?

Re: Transition to React Native

#39
Many comments here are comparing this transition to the one Airbnb did a few years back. These two transitions could not be more different.

Coinbase decided to greenfield their new apps, Airbnb (attempted) to brownfield it. I've worked with a number of clients that have gone down the same path that Airbnb did, from a business perspective it makes perfect sense, keep what you have and slowly move over, but the technical reality is this will be a complete dumpster fire and you will probably fail.

When you try to convert a native app to React Native everything that makes React Native wonderful to work with just seems to break. Hot reloading either barely works or not at all, load up times increase exponentially, the app just becomes a pain in the ass to work with because nothing seems to work like it should.

Whenever companies propose this I always shoot down the idea and recommended a rebuild in React Native from the ground up. Doing so will take just as much time as browfielding because when you try to do a native -> react-native conversion it always seems to go south somewhere, either slowness, having to write 3x the code, or other problems.

Re: Transition to React Native

#40

If I wanted to do android development again, I have no idea which skillset to optimize for React Native? Kotlin? An old version of Java that just got lambdas? Are we doing Model-View-Presenter (MVP) no matter which? Or are we still doing Massive-View-Controller (MVC backronym) Are there adequate networking, database ORM, and image loading libraries for all frameworks? Last time I interviewed for any mobile developmen…

Are you optimizing for jobs/interviewing or for learning? If the former, just do native in Kotlin, if the latter, I like Flutter personally.
Post reply on HN