5 Reasons Why You Should Use React Native For Your Next App Idea

5 reasons why you should use React Native for your next app idea  #ReactNative

  • But then I saw that the React team was working on framework called React Native that would work on both iOS & Android (despite the Android version coming out much later)…GAMECHANGER.
  • Neither the React Native code for iOS or Android was available yet but just the fact that a large team like the Facebook Dev group was working on a solution like this got me excited enough to start all my new web projects in React.
  • In the past when other javascript frameworks (Meteor, Ionic etc.) tried to build tools to compete with native development they simply used Cordova to make javascript look like native Swift or Java code when in reality they were super wonky.
  • I just mention Live Reload first because when switching between React Native and Swift and/or Java…or Objective-C, it is the first thing you notice in speed of development.
  • While you certainly won’t just be copying the same code you wrote from the web application and pasting it into the iOS and Android version expecting it to work, there are a lot of reusable modules between platforms.

tldr; I’m a React “fanboy”. A few years ago, I came across two brand new javascript frameworks in Meteor and React. At first glance after comparing the two I di
Continue reading “5 Reasons Why You Should Use React Native For Your Next App Idea”

How to Draw an Owl with React: A Migration Story

Do you know the four P’s of migrating to React? Learn 'em now:  #reactjs cc: @ReactJS_News

  • A few months ago, I wrote about our adventures building a brand new project using React.
  • Our existing SparkPost app was built many moons ago in the ancient framework known as AngularJS.
  • Shortly after that article was published, I started in on my plan to improve the Angular app.
  • Ultimately we realized that the fastest and safest way to rebuild our entire app in a brand new framework was to do exactly what I’d publicly ridiculed: direct migration, i.e. a parallel rebuild.
  • Step 2: Draw the rest of the [censored] owl.

Sometimes even the best-laid plans need to be re-laid. A walk through on how (and why) we’re migrating our Angular app directly to React.
Continue reading “How to Draw an Owl with React: A Migration Story”

Our React Native GL library is in alpha – Points of interest

We're now supporting #reactnative Mapbox GL 🙌 Try out our alpha

  • Our React Native GL library is in alphaBy: Nick ItalianoWe’re officially supporting React Native Mapbox GL.
  • Our mobile team has started a rewrite of our current experimental React Native library and released an alpha 🙌Using the React Native framework, developers can build cross-platform mobile applications in half the time.
  • Our React Native library will make it as efficient as possible to access our APIs and open source libraries, so you can focus on shipping features.Reusable components are the strongest aspect of React, which is why we’ve created expressive and easy to use components for powerful features like runtime styling…
  • With this in mind, you can render a custom styled map centered on San Francisco in just 25 lines of code.First look runtime styling in React NativeRuntime styling is the first major feature with added support in this alpha release.
  • Here is a preview of a couple examples you can find in our sample application.3D buildingsMarker clusteringWhat’s nextWe plan on bringing our React Native SDK to feature parity with our Android/iOS SDKs and want to be active in the community:We have a Gitter channel where you can post any questions…

We’re officially supporting React Native Mapbox GL. Our mobile team has started a rewrite of our current experimental React Native library and released an alpha 🙌 Using the React Native framework…
Continue reading “Our React Native GL library is in alpha – Points of interest”

Share Code between React and React Native Apps – Hacker Noon

  • Share Code between React and React Native AppsDevelopers are adopting Higher Order Components (HOC) Stateless Functional Components, and for good reason: they make it easier to achieve code reuse, a coveted aspiration of developers.There are many articles on HOC and Functional Stateless Components.
  • But here are a few benefits to consider:UX consistency, both within an application and across devicesMake cross-cutting upgrades: improve a component and update all its uses easilyreuse routing and authorization rulesSwitch libraries (for example, the apps below uses MobX for state management, but Redux could be swapped in)I’ll focus on using HOC and Functional Stateless Components to achieve reuse.
  • It will not use routes nor multiple scenes as the focus is on component reuse.We will add a second pair of applications (React and React Native), which will reuse the components we extract.This GitHub repo branch has the baseline applications (The final result is here.)
  • You have to “see” the duplication, which might require rearranging code blocks.Applying these ideas is like moving puzzle pieces around, to find where they meet and what patterns they reveal.Let’s start by looking for duplication.Seeing DuplicationThe web and mobile applications have two main components.In the web application, App.jsIn the mobile application, SearchView.jsThe following outlines their structure.Almost the same, but the platform differences between React and React Native are in the way.The two components have similar structures.
  • But they are in the README for the GitHub repo branch.Instead, I’ll focus on the refactoring to a common SearchBox, which our web (React) and mobile (React Native) applications will both use.Extracting a Shared Component for Web and MobileFor clarity, I’ve renamed SearchInput.js, SearchResults.js and SearchBox.js to WebSearchInput.js, WebSearchResults.js and WebSearchBox.js, respectively.Let’s look at (Web)SearchBox.jsLines 2–10, 19, 20, 26, 27 are specific to React.MuiThemeProvider, a container for Material UI components, is the only direct dependency on Material UI.

Developers are adopting Higher Order Components (HOC) Stateless Functional Components, and for good reason: they make it easier to achieve code reuse, a coveted aspiration of developers. There are…
Continue reading “Share Code between React and React Native Apps – Hacker Noon”

React and React Native [Book]

Adam Boduch's

  • Use React and React Native to build applications for desktop browsers, mobile browsers, and even as native mobile apps

    Who This Book Is For

    This book is written for any JavaScript developer—beginner or expert—who wants to start learning how to put both of Facebook’s UI libraries to work.

  • What You Will Learn

    React and React Native allow you to build cross-platform desktop and mobile applications using Facebook’s innovative UI libraries.

  • The first part shows you how to start crafting composable UIs using React, from rendering with JSX and creating reusable components through to routing and creating isomorphic applications that run on Node.
  • We then move on to showing you how to take the concepts of React and apply them to building Native UIs using React Native.
  • Split into three major sections to help organize your learning, this hands-on, code-first book will help you get up to speed with React and React Native—the UI framework that powers Netflix, Yahoo, and Facebook.

Use React and React Native to build applications for desktop browsers, mobile browsers, and even as native mobile apps About This Book Build React and React Native applications using familiar … – Selection from React and React Native [Book]
Continue reading “React and React Native [Book]”

React-based UI frameworks – Prototyping: From UX to Front End

React-based UI frameworks  #webdesign #uidesign #webdevelopment #react #javascript #reactjs

  • Most of these are meant more as a window into process (and as a recruiting tool) than as an open standard that other developers can use, but the principles are the same: a reusable library of components with standardized markup.Having a strong design system and a frontend architecture that’s designed to support it is incredibly powerful.Today, even more of the frontend stack has evolved toward a modular, component-based architecture.
  • Here’s the markup for the Feedback component in MailChimp’s library:div class=”feedback-block warning section” role=”status” div class=”lastUnit size1of1″ div class=”c-media” div class=”c-mediaImage v-isFreddicon” span class=”freddicon warn-circle”/span /div div class=”c-mediaBody–centered” h4Account status /h4 p You closed your account on Nov 29, 2013 07:00 pm /p /div /div /div/divDepending on the component, you may also need to include a JS file to handle any interactivity or other logic the component needs.In React, the markup and logic for this component would be defined in only one place, so rendering it would look something like this:Feedback type=”warning” title=”Account status” You closed your account on Nov 29, 2013 07:00 pm/FeedbackReact’s templating system is JSX — this concise version will get translated into the same markup as the top example in the browser.
  • The great thing about this system is that if the keepers of the MailChimp design system wanted to change this component, they’d just change it in one place — the JSX for rendering it would stay the same.
  • In the old world, updating the uses of this component would be a messy and error-prone find-and-replace operation.Having a strong design system and a frontend architecture built around it is incredibly powerful.
  • More importantly, users benefit from a predictable system that works the same everywhere across an app — every time I see a Feedback block in MailChimp it looks and works exactly the same, so my brain spends less effort understanding what’s happening and more on whatever I’m actually trying to accomplish.The list of React-based UI frameworks is steadily growing.

There’s a new crop of web UI frameworks in town, in the grand tradition of Bootstrap, a framework developed at Twitter. Five years ago, Bootstrap was not only an easy way to put together a UI that…
Continue reading “React-based UI frameworks – Prototyping: From UX to Front End”

Frontend freedom with a moltin-powered ReactJS store

We now have an awesome sample ReactJS store built on moltin! Thanks @TarikFojnica 🙌🏼 🎉

  • ‘ReactJS works by storing the state of your application internally, and only re-rendering your content into the browser (the DOM manipulation) when the state changes.
  • With flexible, reusable components to make development workflows efficient and giving freedom to your store’s UI, it’s simple to learn and use and fits in with our own philosophies at moltin perfectly.
  • It was actually Tarik, a freelance frontend engineer who built an example store using ReactJS and moltin.
  • Fast forward to 2017 and with AngularJS becoming depreciated and Angular 2 having an entirely different API, Tarik took advantage of switching and experimenting with ReactJS.
  • Tarik’s sample store can be seen at and demonstrates the power and freedom that ReactJS gives frontend developers.

Here, we’ll look at ReactJS for moltin to demonstrate the power of this new front end framework, coupled with the flexibility of Moltin.
Continue reading “Frontend freedom with a moltin-powered ReactJS store”