Context API has a lot of problems that state lib can fix like Redux, what i mean by problem lets say u have big app with User state in context when u update that state whole app will rerender unless u use useMemo for almost every component, so i think he mean this by that, there is a lot of reason that people still use Redux or other, cuz u have rerender controll within "useSelector" hook and more, in my opinion Context API is great for small project or if u want to use "useMemo" everywhere but its fine if people doesnt want to learn Redux, RTK Query , cuz learning can be little hard, but every year its easier, with thunk and other things u can setup redux in few linesnow also when u use other libs then Context Api there is a lot of libs like "redux-persist" for "redux" or other where u dont need to store data or load them its done automaticaly ( u can just pass whitelist or blacklist, if u want be strict ) unless u want some custom logic that can be defined too ( yea it support secure storage too, witch is useless in most cases, it only slows down everything, and on iOS other apps cant access your other app data anyways ... ), u can also make it work with "react-native-mmkv" with custom expo plugin ... but overall great video@@ToThePointCode
Thanks @Engazan for your detailed comment. As you said, both approaches have their own advantages and issues. So one is not necessarily a wrong tool to use.
![CAMPปลิ้น | EP.82[1/2] แก๊ง 3 สาวเพื่อนซี้บุก CAMPปลิ้นครั้งนี้ห้ามเสียอาการ](http://i.ytimg.com/vi/_6WUjXHe1TM/mqdefault.jpg)
i have to declare that using context as state management is completely wrong method choice.
Why do you say that?
Context API has a lot of problems that state lib can fix like Redux, what i mean by problem lets say u have big app with User state in context when u update that state whole app will rerender unless u use useMemo for almost every component, so i think he mean this by that, there is a lot of reason that people still use Redux or other, cuz u have rerender controll within "useSelector" hook and more, in my opinion Context API is great for small project or if u want to use "useMemo" everywhere
but its fine if people doesnt want to learn Redux, RTK Query , cuz learning can be little hard, but every year its easier, with thunk and other things u can setup redux in few linesnow
also when u use other libs then Context Api there is a lot of libs like "redux-persist" for "redux" or other where u dont need to store data or load them its done automaticaly ( u can just pass whitelist or blacklist, if u want be strict ) unless u want some custom logic that can be defined too ( yea it support secure storage too, witch is useless in most cases, it only slows down everything, and on iOS other apps cant access your other app data anyways ... ), u can also make it work with "react-native-mmkv" with custom expo plugin ...
but overall great video@@ToThePointCode
Thanks @Engazan for your detailed comment.
As you said, both approaches have their own advantages and issues. So one is not necessarily a wrong tool to use.
Create a video for the complete ui of the app please. Thanks always
What's the difference between expo secure store and async storage
Expo Secure Store encrypts the data before storage, so it's more secure. Async storage doesn't encrypt the data.