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 Universal with Next.js: Server-side React

#ReactJS Universal with #NextJS: Server-side React

  • /pages/index.js // Import React import React from ‘react’ // Export an anonymous arrow function // which returns the template export default () => (

    This is just so easy!

  • import React from ‘react’ import Head from ‘next/head’ import axios from ‘axios’; export default class extends React.
  • Our index page does not implement this performance related feature in details page.
  • /pages/details.js import React from ‘react’ // Import Link from next import Link from ‘next/link’ export default () => (

    Coming soon. . .!

The term “universal” is a community-coined term for building web apps that render happily on a server. You might be familiar with “isomorphic” as…
Continue reading “React Universal with Next.js: Server-side React”

Why Redux? Why Now? — Jumpcut Insights

Why Redux? Why now?  #ReactJS

  • For the frontend of Jumpcut Academy, we were using a ‘vanilla’ flux implementation with singleton stores.
  • Redux fixes that with reducers and one store.
  • We wrote thousands of lines of code in Flux and a multitude of stores and action creators.
  • The biggest advantage is that the reducers you create to manage your state can be nested (not flat like stores in flux), so you can combine reducers to build complex state structure from simple reducer functions.
  • With the Jumpcut Academy frontend, we had over 10 stores when we decided to migrate to Redux.

Read the full article, click here.


@ReactiveConf: “Why Redux? Why now? #ReactJS”


For almost a year, Jumpcut has been utilizing React and Flux for frontend development. Our experience with a ‘vanilla’ Flux implementation…


Why Redux? Why Now? — Jumpcut Insights

Learn React.js in a weekend!

  • 4. Building React Applications with Idiomatic Redux (2 hours)
  • 1. Learn React.js with React for beginners (5 hours)
  • You’ll have fun building a single page web app and definitely get your introduction to React.
  • 3. Getting Started With Redux (2 hours)
  • Start with a nice easy introduction to the framework with Wes Bos’ React for Beginners !

Read the full article, click here.


@wesbos: “Nice post by @jkup — Learn React.js in a weekend! (kinda)”


Ok, so you probably can’t really learn React.js in a single weekend but these are the resources I recommend if you want to try!


Learn React.js in a weekend!