I've been developing apps using react native for a while now establishing my project architecture on redux, React.Component lifecycle and react-native-router-flux (for navigation).
Now, I need to start to develop a big new project which is going to be in production and needs to handle a lot of users.
As I understand I cant keep using React.Compoent as my lifecycle and I need to implement the functionality of the new hooks system.
My main concern is that react native with redux and hooks aren't stable enough and I won't be able to create a stable application.
As I see it I should use react-native with hooks, redux and react-navigation as my main architecture. I will be glad to get your opinion on this one.
Thanks
All component in react can be defined as classes or function. It depends on you.
As I understand I cant keep using React.Compoent as my lifecycle and I need to implement the functionality of the new hooks system
You can still use React.Component if you write component as classes. Use hooks if you write your component as function
My main concern is that react native with redux and hooks aren't stable enough and I won't be able to create a stable application
Why do you know that they aren’t stable. I am using them on my production apps.
Basically, redux use for state management, react navigation for navigation. You could use hooks or not, it doesn’t matter
Related
I am building a React Native game with multiple screens. I am trying to instantiate Ably one time and use it throughout the application without having to call new Ably('api-key') on every screen, as this is creating multiple new connections and making it impossible to keep a single connectionId. Is there a way to architect this so that I can define
const client = new Ably('api-key')
one time in App.js and use it throughout the other screens? Either by passing it as props through React Navigation props or using Context? The documentation on this is sparse as most of their documentation only uses this on one page.
Redux will not work. You can create an Ably client and pass it to other components using props, or just use React context to make it available to the whole application. Using redux to store an Ably client will cause an error since Ably clients aren’t serialisable.
See https://reactjs.org/docs/context.html for more info.
Here are some examples:
https://github.com/ably-labs/react-hooks
https://ably.com/blog/ably-react-hooks-npm-package
Cheers,
Richie
I'm new to the react native platform. I'd like to create an app with bottom, stack, and drawer navigation.
I'm not sure which navigation is appropriate for the same react navigation (v4, v5, or v6).
I'd also like to make some API calls. Is it necessary to use redux for this?
Is it better to use React native element or react native paper for ui design?
Please, someone assist me with this.
This doesn't seems to be an appropriate question to ask here, you can go through their official documentations, some courses maybe to learn react-native and its best practices. As for the questions you have asked, since you are learning react native now,
Go with the latest navigation (v6)
It's always a good practice to use redux for api calls.
For UI, you can go with any library that suites your purpose, it does not have to be one, you can use multiple, based on what you want to achieve.
This question already has an answer here:
How to use redux-toolkit createSlice with React class components
(1 answer)
Closed 1 year ago.
I am new to using React Native, and was recently planning on using Redux Toolkit with my project. I was previously using standard Redux, but really like how RTK keeps everything concise with slices.
My project currently uses Class Components for the Screens and would like to keep it that way, but I can't find any documentation on using RTK with Class Components, only with Functional Components. I wanted to know if it was possible to use Class Components and what changes need to be made in order to add RTK. I feel like I should be able to just import the actions from the Slices and then use MapDispatchToProps, but any insight would be appreciated.
Thanks!
Redux Toolkit is purely about writing Redux logic, and is totally separate from how you write your React components and use React-Redux.
So, you can use any combination of:
Redux logic: vanilla hand-written Redux or RTK
React-Redux: connect + class components, or function components + hooks
See the React-Redux docs on using connect:
https://react-redux.js.org/using-react-redux/connect-mapstate
https://react-redux.js.org/using-react-redux/connect-mapdispatch
I'm trying to understand how I can do a signature capture in React Native. My App is created with create-react-native-app and Expo and I'd prefer to not have to eject the app to get this functionality to work.
Would it be possible to wrap something like this in a webview? https://github.com/szimek/signature_pad
I've also looked at this project, https://github.com/RepairShopr/react-native-signature-capture but it requires me to eject the app and use react-native link.
Looking for any advice or suggestions on how to implement this feature while keeping my project as straightforward as possible (ideally, using create-react-native-app, but if this isn't possible could someone please explain to me why?)
The way React Native works is that each component available in React Native maps to a native component in the underlying platform.
ie. a <Image /> is an ImageView in Android and a UIImageView.h in iOS.
The Javascript code itself runs in a Javascript thread on each platform and as you use Components in React Native, there's a translation layer that passes information from JS into the React Native bridge that then results in corresponding native components being created.
By default, React Native has included the following components: https://facebook.github.io/react-native/docs/components-and-apis.html#basic-components which means that only those components come out-of-the-box in React Native. If you want other components, then you have 2 options, either create a "composite" component in which your JS component is written into other JS components or, if your feature needs a native component not yet exposed by React Native, write your own "native" component to expose certain native functionality to your React Native code.
The way Expo works is that they have wrapped React Native and a handful of 3rd party components and built it within their application. The reason why you can't use a 3rd party native component they don't support is because when that component is used, the app itself doesn't have translation code to go from JS to a native Android/iOS view.
So, to do what you're asking, you'd need to find either a "native" drawing component that Expo has included in their platform/app. OR you need to find a "composite" drawing component that is built with other default React Native components (or other components Expo supports).
ie. On Android, I might build this with a Canvas view, but from what I can tell React Native doesn't support that object natively, so I would probably write this myself, etc.
It's hard for Expo to support every 3rd party "native" component out there because React Native is open source and it iterates so fast that most community-built components aren't always up to date or they might conflict with one another.
I am using react-native-signature-capture.
Working properly on both Android and iOS.
I know it's been a while, but there is an interesting article here: https://blog.expo.io/drawing-signatures-with-expo-25d1629ca1ac
Wait, but how?
Using “expo-pixi”, you can add a component that lets you choose your brush’s color, thickness, and opacity. Then when your user lifts her finger, you get a callback. From there you can take a screenshot of the transparent view or get the raw point data if that’s what you’re looking for.
Navigation Experimental, Navigator, Flux-style Navigation etc. etc. There are so many theories and options out there. I know, this is a question with a very high "it depends" potential. But maybe some of you have already figured out an absolute favourite option to handle navigation for react native apps.
I'm a redux user and use https://github.com/aksonov/react-native-router-flux/ . You can integrate it with redux. React-native-router-flux is also usable without Redux.
The advantage is that the Navigation API doesn't change as much as React-native's does. There is also pretty good community support.
If you start application you can use this starter kit https://github.com/infinitered/ignite. This starter kit contain redux and React-native-router-flux. And more
features (Battle Tested, redux persist, ...)