Gizmo VS Store

. Web backend (with various frameworks available) . Web Assembly (one of them is vugu framework) . Microservices (some frameworks: Go Micro, Go Kit, Gizmo, Kite) . Fragments services (Term mentioned by @jeffotoni in a microservices discussion group) . Lambdas (FaaS example) . Client Server . Terminal applications (using the tview lib) . IoT (some frameworks) . Bots (some here) . Client Applications using Web technology . Desktop using Qt+QML, Native Win Lib (example Qt, Qt widgets, Qml) . Network Applications . Protocol applications . REST Applications . SOAP Applications . GraphQL Applications . RPC Applications . TCP Applications . gRPC Applications . WebSocket Applications . GopherJS (compiles Go to JavaScript)

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

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)