They started with iOS and when Android release was ready, took them only 2 days to build.However, they immediately stopped after identifying various issues such as poor performance of touch events and <a href="https://github.com/facebook/react-native/issues/2814">lack of 64-bit support </a>.Though they thought React Native was ideally for iOS.

Start with iOS, Try Android Later

React Native is a great framework that bridges the gap between web and mobile. At Discord it has brought us incredibly efficiency. It allows us to write reusable code, learn from each other, and move fast with a two person team. Although there are real pain points and challenges, the overall gains significantly outweigh the costs which motivates us to keep investing in the platform.

Sticking with React Native

Immature long lists have been a well known issue since day one, using for chat view. Alternatively, they use <code>UITableView </code>for smooth scrolling performance and dynamic cell heights.This is the only view which was implemented on native, which means the hundreds of other of React Native components are provided at 60 fps.

1. Immature Long Lists

Time to Interaction (TTI) is a key aspect of how a user perceives the performance of an app. The TTI of our iOS app is noticeably longer than other competing messaging apps written in native code. Since React Native loads and parses all the Javascript code before execution, you get startup delay based on bundle size. In our case, it’s roughly 1.5s startup delay to load a 15mb bundle on an iPhone X.Fortunately, Facebook documented <a href="https://facebook.github.io/react-native/docs/performance#unbundling-inline-requires">unbundling </a>to only load necessary portions of the bundle for startup and progressively load more as needed via their packager.

4. Startup Delay

A few days ago, we were able to quickly deploy a post-release fix for cameras and skip the approval process. We can’t even begin to count how many OTAs we’ve shipped. Being allowed more room for mistakes, engineers can ship often with confidence and avoid coordination, which unblocks everyone.

Over The Air Patches (OTA)

Facebook is solving this problem by <a href="http://facebook.github.io/react-native/blog/2018/06/14/state-of-react-native-2018">re-architecting the threading model </a>: It will be possible to call synchronously into JavaScript on any thread for high-priority updates. After various attempts at solutions like <code>InputAccessoryView </code>, we eventually figured out a way to "portal" the React Native component into native iOS views hierarchy and therefore manage high-priority keyboard updates synchronously in native. We will detail this more in a later blog post.

2. High-Priority Updates

Used <a href="https://github.com/storybooks/storybook/">storybook </a>to quickly render "dumb" components that don't manage any state internally with mock props. By leveraging the same tooling, they could quickly follow the web team who originally adopted storybook. Along with hot reloading, storybook dramatically accelerates their UI development cycle.Designers can even easily tweak styling directly in storybook.

Faster Iteration of UI components

Being one of the first apps built with React Native, we were excited to share our first year journey using React Native back in 2016. Looking back at the past three years, React Native has proven to…