To go (or not to go)
React Native way

You won’t find here anything about how cool guys like Facebook, Netflix, and Airbnb benefited from React Native


  • One shared codebase. Actually, with React Native you’re building two separate app versions (IOS and Android). Yes, the two app versions that share 65–70%
    of JavaScript code. The same codebase gives you easier maintenance and fewer bugs to worry about (because the total amount of code is almost twice less).
    It saves extra days and weeks you that could spend on new functionality.
  • Damn close to native performance. Unlike other cross-platform options,
    like Cordova, Ionic or Titanium that emulate browser app (it’s like having
    a simulated responsive web app in app market), React Native runs native APIs. There are no tap and scrolling issues, and UI feels like a native app,
    not browser based.
So, Swipe in React Native would be completely the same as if you had implemented it in Swift or Java —  Source

There are tons of other UI-tool kits and libraries that help you handle performance challenges during the development stages just like in any other mature framework. And as always, you’ll only have to make sure that the library bundles you’re gonna use are frequently updated + don’t forget to study the backlog of existing issues for them.

  • Jan 14

    MVP is done. What to do next?

  • Jan 14

    Your product isn’t lean. Here’s why

  • Jan 14

    How to build the initial team for an early stage