Using Native SDKs and Libraries in React Native

Using native SDKs and libraries with #React Native

  • Most of the time, these are only available in their native version, and only accessible as Objective-C or Swift libraries in the case of iOS apps or as Java Classes for Android apps.
  • Step 2: Call our bridge from our React Native code.
  • Step 1: Create two native files for our bridge.
  • An Objective-C class is made out of two files, a .m and a .h, holding the module implementation and the header for this module respectively.
  • When building an app in React Native we may end up needing to use third-party SDKs or libraries.

Read the full article, click here.


@PacktPub: “Using native SDKs and libraries with #React Native”


Using Native SDKs and Libraries in React Native written by Emilio Rodriguez: one of the many blog articles from Packt Publishing


Using Native SDKs and Libraries in React Native

react-boilerplate/Changelog.md at v3.0.0 · mxstbr/react-boilerplate · GitHub

  • Testing setup : Thanks to @jbinto’s herculean efforts, testing is now a first-class citizen of this boilerplate.
  • No more context switching, no more “Create new file, copy and paste that boilerplate structure, bla bla”: just npm run generate and go.
  • “Smart” containers are now isolated from stateless and/or generic components, tests are now co-located with the code that they validate.
  • Documentation : Thanks to @oliverturner, this boilerplate has some of the best documentation going.
  • New server setup : Thanks to the mighty @grabbou, we now use express.js to give users a production-ready server right out of the box.

Read the full article, click here.


@SitePointJS: “React Boilerplate (RBP) v3.0.0 is out, and it’s a complete rewrite #ReactJS”


react-boilerplate – :fire: A highly scalable, offline-first foundation with the best developer experience and a focus on performance and best practices.


react-boilerplate/Changelog.md at v3.0.0 · mxstbr/react-boilerplate · GitHub