Why React Native is the Best Choice for Making Native Apps

  • The React Native CLI lets you start a new native app project that will work on both iOS and Android.
  • One of my favorite features of React Native app development is live reload.
  • React Native builds upon React’s philosophy of “Learn once, write anywhere,” making it easy for React web developers to build native apps.
  • Composable unified UI codebases, instant app updates, and better development tooling make React Native the better way to make native apps.
  • And if you want to check out a great example of a React Native app for data visualization, Victory UI Explorer by Angela Nicholas is one of my favorite Formidable projects.

Composable unified UI codebases, instant app updates, and better development tooling make React Native the better way to make native apps.
Continue reading “Why React Native is the Best Choice for Making Native Apps”

Introducing Twenty Sixteen React and NodeifyWP

This looks nifty. @10up introducing NodeifyWP and Twenty Sixteen rebuild w/ #reactjs #Nodejs

  • JavaScript and Node.js are used to create isomorphic applications, since JavaScript runs natively in the web browser and is the foundation for server-side Node.js.
  • Since WordPress runs on PHP, it can’t be used in conjunction with an important breakthrough: isomorphic applications .
  • Since we can’t run PHP in the web browser, we have a few options for creating JavaScript-powered “app-like” experiences in WordPress.
  • By using popular, new Node.js technologies, we think that developers can make first class, “app-like” experiences with the web’s most popular CMS, WordPress.
  • Isomorphic web applications run the same code on the server and client (web browser), providing the flexibility, extensibility, and consistency to build the most modern “app-like” experiences on the web.


As web technologies and mobile devices improve and global internet speeds increase, consumers increasingly expect taps and clicks to deliver results nearly instantaneously; the “app-like” experience has become an expectation in web browsers. To this end, we’ve seen huge strides forward in web platforms and frameworks.
Continue reading “Introducing Twenty Sixteen React and NodeifyWP”

Page object for testing React.js components – Medium

  • Let’s add one more test on handling submit.
  • Our test code encourages to do everything through Page object.
  • Page object wrapper gives you nice API to interact with your component, so test code will be more expressive and neat.
  • I also work a lot on developer infrastructure, especially in terms of testing.
  • We don’t test the whole web page, only one component, but we can think that our component is actually a little page, that we are going to interact with.

Today I will tell you a little trick how to make your test code a bit fancier and easier to maintain. The PageObject pattern is quite…
Continue reading “Page object for testing React.js components – Medium”

How to structure real world Redux/React application – Medium

  • I decided to move the tests into the src/app folder so that they are close to the source.
  • It’s quite easy to see this coming because the file nature will always remain the same but features and data domains grow in real world applications .
  • -app/ – data/ – artifacts/ ArtifactReducer.js ArtifactActions.js ArtifactSelectors.js – calls/ CallsReducer.js CallsActions.js CallsSelectors.js – filters/ …
  • ./data/calls/CallReducer.js’; import * as CallActions from ‘.
  • A better way is to encapsulate the data domain by creating an index.js that exports the internal files of this module.

Recently I was rewriting in Redux/React the web application of Flow, a tool to help developers better understand the structure and the…
Continue reading “How to structure real world Redux/React application – Medium”

Dynamic Vendor Bundling in Webpack – On Frontend Engineering – Medium

  • In the above code we’re chunking into a “vendor” bundle only when the path of the bundle is in node_modules .
  • The way, we only include 3rd party libraries that we actually reference in our app into the vendor bundle.
  • It turns out, the CommonsChunkPlugin minChunks property accepts a callback that allows you to return a boolean for whether or not to include each module it comes across in the bundle.
  • One common optimization people do with code-splitting is to define a Vendor bundle to include all the 3rd party libraries in a separate bundle that can be cached much longer than your main App bundle (because, presumably, you wouldn’t update your 3rd party dependencies nearly as much as you would update your app code).
  • The key is to externalize this mapping into a “manifest” bundle.

If you aren’t already, there’s very little reason not to take advantage of code-splitting (bundle chunking) in Webpack. Especially for…
Continue reading “Dynamic Vendor Bundling in Webpack – On Frontend Engineering – Medium”

Invoke Any Native API Directly From Pure Javascript in React Native — Medium

  • Overall, the React Native team did a great job wrapping the basic native components you need.
  • Since the entire specification is now serializable, we can send it over the React Native bridge to the native side.
  • Because adding native code to an already existing native wrapper is an ugly task.
  • Using the technique introduced in this library, you can access any native API directly from Javascript without wrapping it first.
  • Assuming the native return value is serializable, we’ll send it back over the React Native bridge and consume it in Javascript.

Read the full article, click here.


@koltal: “Invoke Any Native API Directly From Pure Javascript in #ReactNative @WixEng @reactnative”


The native iOS SDK has over 15,000 API’s. React Native provides access to a tiny fraction. Wouldn’t it be fun to access all of them from…


Invoke Any Native API Directly From Pure Javascript in React Native — Medium