Srinivas Rao
Apr 22, 2019 · 9 min read

React Native Learnings


The goal of this article is to guide mobile application development teams who are planning to adopt React Native framework for their application. This guides on application architecture, design for React Native framework, some of the development items that we need to take care for React-Native framework and challenges that could be faced during development when compared with Native development.

React Native Benefits

React Native is a cross-platform development framework that provides native look and feel in mobile applications. Such a cross-platform framework includes the following benefits.

  1. PoC’s need not be done separately for each platform (iOS and Android). Thus it helps in quicker evaluations.
  2. The core business logic and unit tests need not be written specific to each platform
  3. UI Implementations need not be platform specific. Being platform specific needs extra effort to complete the functional requirements and customizations.
  4. Separate application design considering different patterns like MVP/MVVM for Android and MVC/VIPER for iOS need not be done.
  5. Single codebase to reduce maintenance effort.

Evaluation approach to React Native

React native can be used in multiple ways, Team would like to see how it can be integrated with existing native modules. Identified the following items need to be evaluated for react native adoption.

  1. The amount of code reusability possible across IOS and Android platforms based on the features required by the application.
  2. Integration of existing native modules which consists of UI and API specific to mobile platform are BLE, Camera, etc.. Complexity that can result when a common mobile application architecture is implemented across IOS and Android platforms
  3. The amount of platform specific customizations. eg. UI (List and customized layout with flexbox) and transition based animations
  4. Route Library evaluation to pick better navigation library based on existing application scenarios
  5. Deep linking behaviour for push notifications
  6. Redux Design pattern adoption
  7. JS Network Library (i.e Axios, apisauce, apollo-link) evaluation

Application Architecture

Application Stack


The React-Native community-driven navigation library and it is purely JS based. It’s the result of many experiments of the initial react-native based applications from the react-native community.


State management library for react based applications. It’s core principles are Immutable data and predictable state update with pure functions. It helps to share the centralized state information with multiple components.


Redux-Saga helps to manage the side effects of asynchronous calls. It uses ES6 generators to make asynchronous code readable much like async/await feature.


Interface library for modifying control flow of GraphQL Requests. This is designed to make links composable with single purpose links. Used as a standalone client to consume API from Graphql server

Native Modules

Integrated with multiple native existing SDK’s to support BLE, Amazon Fling, Amplify, Firebase and Authentication SDK with Native UI screens.



Used as CI and CD server for Android, iOS. Configured pipe-lines for automation and code-push


This plugin helps to push product improvement changes to end user quickly and new features can be rollout for feedback. The main advantage is we can push JS bundle changes to users without releasing new APK/IPA to play store. Always use signing mechanism to avoid man-in-the-middle attacks


Static Type checker for javascript and it can be applied progressively. Helps in large refactors.


Has support for React, React native and Flow types. Easy to configure rules based on project and it helps team members to write consistent code


Package dependency management tool has capability to cache the downloaded packages

Application Architecture Diagram

Image for post
Image for postImage for post

Design considerations

  1. The targeted application interacts with GraphQL server for user data, It uses an apollo-link client which has the capability of chaining, split and channelizes the request based on operations
  2. Application completely relies on side effects of asynchronous operations that will go nicely with redux-saga. Designed multiple root saga’s to take control of actions based on the socket state (i.e ignore specific actions if there is no socket connection )
  3. The communication will happen over websocket link except for few critical operations which are routed to HTTP when a socket connection is unstable
  4. The application deals with very complex data, but want to store only the important data which is used across screens. As a result, it leads to skipping store update for certain events (step 6) which are either temporary results or useful only at that context.
  5. Step 6 is deviated from regular react redux based design but that is one of the best alternatives to avoid store updates with unnecessary/temporary data

(ex: Presenting alternative products or suggestions based on the currently selected product — As it is valid only given context and data varies drastically for each product. Storing the entire data in the store may not be a good idea as it leads to stale data). Identified many use cases like this in the application and avoided updating redux state based on context.

  1. Used Selectors, Reselect to transform data and memorize which will help in avoiding unnecessary renders

Apollo-Link Chain

Image for post
Image for postImage for post


  1. Must be able to log the complete operation information with request-response details after processing for debug purpose (Configurable and can be removed in production builds)
  2. Should be able to configure the timeout for all operations and provide retry mechanism based on status codes
  3. Would like to queue requests and process gracefully to handle intermittent network issues as reconnection takes 2 ~ 3 sec
  4. Must be able to handle specific errors based on the operation and take a decision either to retry or not
  5. The operation must be queued to avoid intermittent network issues
  6. Must log only elapsed time and status for all the requests to evaluate geographical network latency

Test tools

Identifying the better testing frameworks and tools are important to any mobile application to improve product quality, code coverage, and faster regression test iteration cycles

Unit & Integration Testing

Jest :

Test Framework which has preset for react-native and pre-configured with react-native

Features used

  1. Snapshot — To track UI component Styling and Actions creators to avoid unintentional data changes
  2. Mocks — Mocking Native framework API’s and Timers
  3. Spy — To validate API invocations mainly used in behaviour driven scenarios
  4. Code Coverage — Integrated with JUnit to provide results with CI server


Library to test React components with shallow-render, event triggers and dom manipulations


Sinon is a standalone library (provides features same as jest i.e spy, mock, ..) but used only to advance timers as there was a problem with the jest in specific scenarios (i.e max timer count reached issue with Animation Views)

End-To-End Testing

Had prior experience with Appium but evaluated Cavy and Detox for end-to-end tests. Finally chosen Appium as it helps to test in both platforms(Android, iOS) with existed native screens( Native SDK Integrations i.e Social login) in the application flow


JS Static Analysis

  1. Type Check: It’s important to have a static type checking which will help in large code refactors and improves confidence. It’s better to opt progressive approach with Flow
  2. Lint: EsLint has default styles and easy to configure rules. Has support for react, react native, flowtype

React Native

  1. As a cross-platform, it is well suited for both Android and iOS. No major challenges in the build configuration
  2. Identify the popular SDK (i.e Expo) and boilerplates (i.e Ignite, Pepperoni ) as it avoids configuring and installing platform-specific tools. Must consider its limitations(i.e Limited API ’s, binaries can only be built online).
  3. Consider using NativeBase or React Native Elements for cross-platform toolkits. In case if there are no custom styling components in the application
  4. Almost 90% of JS code is common for both platforms as there are no platform -specific UI (The % varies based on the UI mostly)
  5. One must not assume feature works the same way in both platforms. Developers must validate in both platforms and must consider platform specific behaviour differences in estimations
  6. Decide early, how the application to scale across different devices and screen sizes because it requires a lot of effort to implement screens based on window size
  7. Team members must aware native platform specific things to improve performance and behaviour customization (ex: Use layout inspector and identify the hierarchy to reduce redundant layers)
  8. It goes well if state or contexts are not shared between React Native UI screens and native UI screens.
  9. Integration of existing Native modules is not complex, but try to reduce the data transfer via bridge
  10. Gif animated Images are supported in iOS by default but not in android, must need to add fresco animated library
  11. Always use a unique key to improve the performance of List renders
  12. There is no support for testID in Android for automation purpose must depend on accessibility(Can’t automate application if the application targets users with a disability)


  1. Try to avoid multiple sources of data like Internal state(derived or normal user changes) and props as it makes decision making tougher.
  2. Always use Proptypes for the components and containers to track the input data type validations at runtime
  3. Avoid nesting views un-necessarily as it increases node depth and layout computation in the native side
  4. Try to build as much as dumb reusable components(avoid internal state) and lift state to containers to reduce complexity
  5. One must be careful when using certain lifecycle methods (i.e componentdidupdate, getDerivedStateFromProps) must follow best practices else might end up with multiple renders
  6. UX must consider the data relation to improve application performance(i.e avoid listening to multiple nodes as it might increase renders) and design screen layout accordingly


  1. Choose the navigation library based on application use case. Community suggests react-navigation as it is purely JS based solution for react-native and maintain clear separation between JS & Native screens to avoid complexity in routing.
  2. Avoid redux integration as there won’t be any support from the community in future.
  3. Always check active screen and avoid rendering of the stacked screens to improve performance (i.e props might change so that will trigger render more than one screen and containers)


  1. One must be very careful in designing reducers to improve performance based on the UI (i.e consider normalization to avoid deep nodes)
  2. Use selector / reselect instead of referring state path directly. Selectors help to transform data and give the flexibility to avoid hard dependency on the path
  3. Go with action creators instead of plain actions as it provides readability, abstraction and helps to decouple the multiple layers. Don’t worry about extra boilerplate code
  4. Consider offline behaviour and provide middlewares to customize


  1. Upgrading to newer versions are painful as it breaks features.
  2. Making synchronous calls between JS and Native modules are not possible. Must consider asynchronous APIs approach in the design phase
  3. React native always behind to native especially Android, One must wait until new release to adopt new API or features(Current android supported version is 26)
  4. In the long run package updating, 3rd party packages might cause compatibility issues with latest React Native versions and it leads to clones
  5. Some of the 3rd party packages are not flexible to adopt in every application, one must wait for PR to merge and release or clone and maintain as private packages
  6. Yet to identify the better tools to trace crashes in both JS and Native layers
  7. Improving initial screen load time (Takes time to load 25 MB js bundle file roughly 5~6 sec)

Should switch to React Native

It entirely depends on the application features like Navigation, Animations, Platform specific API usage will play a major role in success.

  1. Planning to start a new application with less divergence in functionality.
  2. Consistent UI design and feature irrespective of platform.
  3. Limiting native screens scope or well aware of native UI boundaries.
  4. Limiting context switch between Native and React native UI screen navigation
  5. Not using complex gesture-based features.
  6. Not sharing application state/data between native and JS screens.
  7. Very limited use of hardware specific feature API’s(i.e BLE, NFC, Audio/Video, Camera)


Benefited with React Native framework, as targeted application developed from scratch and following the best practices. Reduced overall development time and able to share single codebase (90 %) for both platforms.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store