I know this is kind of wired to say that you can make React Native Apps on iPhone and iPad. Yes, you heard it right, you can use iPhone or iPad to develop fast and reliable applications with a full fledge code editor that features code autocompletion, a file navigator, documentation, syntax highlighting for many languages. You can share your projects uploading them to play.js servers or directly managing your code from the Files app that iOS includes.
Your scripts and apps will run locally so no computer or internet connection needed!
You can get the app from iTunes by paying $3.99 (299 INR).
I have already described the Lean Core project running by the React Native Team. In progress to remove the unwanted components and to make the separate libraries for some components, they have moved the WebView component to the new Home @react-native-community/react-native-webview.
AboutReact have the following examples which are using the WebView component from the react-native:
- Open any Website in React Native WebView.
- React Native Load Local HTML File in WebView.
- React Native Show Progress bar While Loading WebView.
So instead of updating the old one, I have added a new post which is a combination of above all. Please have a look.
Yeah, you heard it right `react-native link` without package name is now deprecated and will be removed in next version. You can find more details in `react-native link` without package name is Deprecated post.
For the past several months React Native Core Community has been discussing and making progress on a project called “Lean Core“. Over the years React Native has accumulated a lot of parts that are now outdated, unused or otherwise legacy.
So the big point of discussion was “React Native is a huge repo. Would it make sense to move UI components (ScrollView, Switches, WebView) and Native Modules like PushNotifications, etc into separate repos?”
The basic answer was yes, and in the past few months, this has started becoming reality via a few proposals and some commits from the FB team. They decided that it’s time to clean everything up and put the repository into a much more manageable state going forward.
In the process of that, they have moved many React Native component to a new Home like AsyncStorage is deprecated from the react-native library and now has a new separate library react-native-async-storage. This is not just a single library there are many libraries which are moved and can be used from there. You can follow Separate Libraries under Lean core Project in React Native Version 0.59 post. I’ll update all the updated library there.
In React Native Version 0.59 according to Google’s latest recommendations, Android support has been cleaned up, which may result in potential breakage of existing apps.
This issue might present as a runtime crash and a message, “You need to use a Theme.AppCompat theme (or descendant) with this activity”. For that you need to update your project’s
AndroidManifest.xmlfile, making sure that the
android:themevalue is an
AppCompattheme (such as
react-native-git-upgrade command has been removed in 0.59, in favor of the newly improved
react-native upgrade command.
To upgrade to 0.59, RN Team recommend using
rn-diff-purge (Which was a separate repository but now included in the official repository) to determine what has changed between your current React Native version and 0.59, then applying those changes manually.
Once you’ve upgraded your project to 0.59, you will be able to use the newly improved
react-native upgradecommand (based on
rn-diff-purge!) to upgrade to 0.60 and beyond as newer releases become available.
While making a React Native Application React Native’s command line tools are the first thing that we have to use, but they had long-standing issues and lacked official support.
- Logs are formatted much better now
- Commands now run nearly instantly.
This feature will affect the apps with a deep and varied component architecture. The developers who develop the complex component structure will see the most improvement.
In this update applications load resources as needed rather than slowing down launch. This feature is called “inline requires”, as it lets Metro identify components to be lazy loaded.
React Hooks are part of React Native Version 0.59, which let you reuse stateful logic across components. Hooks let you use state and other React features without writing a class. Take a look at some of the wonderful resources to get the idea about the hooks:
- Introducing Hooks explains why we’re adding Hooks to React.
- Hooks at a Glance is a fast-paced overview of the built-in Hooks.
- Building Your Own Hooks demonstrates code reuse with custom Hooks.
- Making Sense of React Hooks explores the new possibilities unlocked by Hooks.
- useHooks.com showcases community-maintained Hooks recipes and demos.
Be sure to give this a try in your apps. We hope that you find the reuse as exciting as we do