Ivan Maximiliano Saldano
The only thing I am concerned to apply it for react-native is "queryCache". For offline purposes, we usually cached the data in redux persist and show when offline. currently, in react-query, we can cache with AsyncStorage but the process will be:
network request native serialized -> pass-through bridge -> deserialized in js thread -> react-query serialized as string -> pass-through bridge again to stored cached data -> deserialized again anytime we used cache. It may bottleneck if the query data is too big and serialized JSON is CPU process can freeze the js thread (redux has the same issues but we choose what we need to store)
Anyway, When the new architecture of RN is released and more popular, we will have more library that uses JSI to reduce the serialize process, we can apply it as a stored layer for react-query
Ivan Maximiliano Saldano The only thing I am concerned to apply it for react-native is "queryCache". For offline purposes, we usually cached the data in redux persist and show when offline. currently, in react-query, we can cache with AsyncStorage but the process will be: network request native serialized -> pass-through bridge -> deserialized in js thread -> react-query serialized as string -> pass-through bridge again to stored cached data -> deserialized again anytime we used cache. It may bottleneck if the query data is too big and serialized JSON is CPU process can freeze the js thread (redux has the same issues but we choose what we need to store)
Anyway, When the new architecture of RN is released and more popular, we will have more library that uses JSI to reduce the serialize process, we can apply it as a stored layer for react-query