Store VS react-query

Assuming you're using something like okhttp, I usually just check to see if a refresh token is available on the device, then let an interceptor handle token validity with some type of listener that the view observes on (MainActivity would do this in a single activity app) to handle navigating back to login. For refreshing data I tend to rely on my repositories to handle cache validation as needed. Something like Store can do this for you.

Store simplifies reading and writing to and from local and remote data sources. We recommend an underlying persistence library that supports observable queries. Store's SourceOfTruth delegates to, for example, SqlDelight. For more background, here's the talk Mike and Yiğit gave at KotlinConf when premiering Store4: https://www.youtube.com/watch?v=raWdIwsDe-g

Hey! Great question. Yes we moved Store from Dropbox to Mobile Native Foundation. We made changes to the implementation of Store. However the contract is the same as Store4. MutableStore and StatefulStore (in proposal) are net new. But both will delegate to Store. For example, this is the implementation of MutableStore. I have a branch at Dropbox using Store5 alongside Store4. One of our criteria for releasing the Store5 alphas was all Store4 tests needed to pass. We are working on docs and can definitely address these concerns 👍

Store is a KMP implementation of Google’s offline-first guidance and general solution for reading, writing, and resolving data conflicts

Related project that I really like https://github.com/MobileNativeFoundation/Store

I've been meaning to look into using the Store library since I heard Yigit Boyar talk about it on this Android Developers Backstage episode I started implementing it today and I'd love to see some samples or articles to better understand how they intend you to use it.

I’ve been a bit interested https://github.com/MobileNativeFoundation/Store in this but could easily be overkill for such a simple scenario

- the new york times publishes kyt, gizmo and store (which they have now moved to a different organization store 4)

react-query

React Query: This library makes it easy to manage data in your React applications, from fetching to caching and updating data. It offers a simple, powerful, and flexible API for handling data and keeping your UI in sync with your data. https://github.com/tannerlinsley/react-query

useQuery (react-query) (+) all from above (+) even more features (-) more complex, even the examples are complex, has more aggressive defaults (re-fetching every 2s)

see here Overview

Rapini is a new tool that can generate custom React Query hooks using OpenAPI (Swagger) files.

React Query is the gold standard for using async data declaratively with hooks. I ended up needing to modify even my simple useTimer hook to work more like useQuery to take multiple keys in order to work as an inner observable for other operators.

For most situations, I would recommend using a library like React Query. It handles a lot of common data-fetching boiler plate and already accounts for this useEffect() issue. Also, it supports Suspense if you want to use that.

At this point, I want to move on to the react-query cache management library. Give a brief overview and see how you can improve your developer experience with cache using this library.

There isn't the "service" concept in React. If you need to send off data you can just do so with fetch. If you need to load data and cache it so it can be used across components and unmounts, then something like react-query is what I'd recommend. But it's basically a combination of React Context, useEffect, and useState to manage the cache and lifecycle of a request.

react-query is pretty neat too. I default to that for most projects unless it's something unusual