After building my first React Native app, I’m now convinced it’s the future.
Taylor Milliman

Nice article. Thanks so much for sharing. I did want to point out one correction if you don’t mind.

React Native compiles your code to native code for the respective OS, either Android or iOS.

These cross-platform don’t compile code to native. They either run your app as a “webapp” inside of a Webview component with a relatively limited bridge that gives access to native components (as you’ve pointed out with the “Hybrid” approach) or they set up a more complete bridging mechanism where the core of your code (the brain, if you will) remains in the non-native language (Javascript in the case of ReactNative or Titanium) and invokes native components/modules via the bridge.

I call these “near-native” apps because what the user sees and experiences is usually native to the platform while the source that controls everything remains in a non-native language.

About 2 years ago, I put together a review on what I call the “5 App Types”. I went into detail on what “Near Native” means and how it compares to “Native”, “Hybrid”, etc. Here’s the link to that article:

Like what you read? Give Mahlon Gumbs a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.