Building an app: React Native vs Ionic – Hacker Noon

Building an app: React Native vs #Ionic  #ReactJS #JavaScript

  • In this article, we are going to make a comparison of two frameworks, React Native and Ionic, based on our real time experience in frontend development.When developing various products, either for ourselves or for the clients, there has always been a question that interested us: how can we narrow down time and cost of product development.Android and especially iOS developers have always been valued greatly and cost a lot, and when developing for two platforms one has to spend twice as much money.At some point we were experimenting with Cordova, but it didn’t feel as if we can get something valuable out of it.Then we noticed Ionic.
  • Now we would like to give you detailed frameworks comparison and explain you why React Native is better solution for our developers.We were always trying to get more expertise on different technologies and use them in practice in order to define the best solution.
  • We also kept on watching Ioinc2, which was supposed to become an innovation that would solve many issues that we had while working with Ionic1.The approaches of given frameworks are very different but for us React Native is an ultimate winner.We chose main React Native advantages that are superior in relation to Ionic1/2:Response time that could be compared to native apps.Ability to reuse the code parts (not all code) for desktop (web apps) and mobile (mobile apps) and even for the server.
  • (:-))Incredibly convenient toolchain for developers that allows to quickly develop and debug the app.Big amount of elaborated components from Facebook.Even bigger amount of components from community.Ability to realize the ideas of functional programming in development which ensures great stability and reliability of the app and relative scaling simplicity.However, we don’t make a point here that React Native is 100% perfect.
  • We also chose some of React Native disadvantages in comparison with Native Apps:Those code parts that are linked to work with hardware solutions, camera, external libraries integration, etc are still done in Native parts.The interface between javascript and native part is not so simple (but not more complicated than cordova).

When you start to use new technology, you cannot be sure it will be the best solution. In this article, we are going to make a comparison of two frameworks, React Native and Ionic, based on our real t
Continue reading “Building an app: React Native vs Ionic – Hacker Noon”

React, Webpack, and Horizon Quick Start — Frontend Weekly — Medium

#ReactJS, Webpack, and Horizon quick start:

  • Were going to add in Message and Messages Components, along with a stylesheet to make it a little more tolerable to look at (right now, we only really need a ‘center’ class).
  • import React, { Component } from ‘react’; class App extends Component { render() { //return html } } export default App;
  • /messages’; class App extends Component { render() { return (

    ); } } export default App;

  • Passing in the chat object down to the child component is how we will be able to get our messages and map them to our Message component
  • import React, { Component } from ‘react’; export default class Message extends Component { constructor(props) { super(props); this.props = props; } render() { return (
    {this.props.msg.author}
    {this.props.msg.text}

    ); } }

Read the full article, click here.


@ReactiveConf: “#ReactJS, Webpack, and Horizon quick start:”


This tutorial will give you a quick start example to follow along to, and help you build a barebones React chat application with Horizon.io…


React, Webpack, and Horizon Quick Start — Frontend Weekly — Medium