React Native logo

A React Native Retrospective

I recently tweeted about us removing the final React Native code from our codebase at Udacity.

Nate Ebel on Twitter

removed React Native from our codebase… – decreased apk size 35% ๐Ÿ‘ – decreased build time ~20% ๐Ÿ‘ – decreased number of languages required to fully understand/work on the project ๐Ÿ‘ probably my favorite PR merge in a while ๐Ÿ˜ƒ

As a result of the responses to that tweet, I decided to write a retrospective on our usage of React Native on the mobile-engineering team at Udacity.

Whether React Native is right for your team/project is up to you Click To Tweet

That post can be found here:

React Native: A retrospective from the mobile-engineering team atย Udacity

 

The big takeaways:

  • React Native’s viability will depend on your teams needs/goals/experience
  • React Native seems to be better suited to fully cross-platform projects and greenfield development
  • React Native can be very effective in those situations

 

Can we say definitively whether or not React Native is right for you? No. Click To Tweet

 


I love to meet/talk/discuss and help where I can. If you want to chat or ask a question you can follow me onย Twitter,ย YouTube,ย Medium,ย andย Facebook.

 

Check Out My YouTube Channel

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.