crdt-example-app
redux-offline
Our great sponsors
crdt-example-app | redux-offline | |
---|---|---|
2 | 4 | |
567 | 6,137 | |
- | 0.1% | |
0.0 | 0.0 | |
over 1 year ago | 18 days ago | |
JavaScript | JavaScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
crdt-example-app
-
Downsides of Offline First
* https://www.youtube.com/watch?v=DEcwa68f-jY
And his demo implementation (and annotated fork):
* https://github.com/jlongster/crdt-example-app
-
Why do Webdevs keep trying to kill REST?
Better protocols lead to improved UX (eliminating user-facing errors and offering faster updates) and DX (shifting errors left) and they're so relevant to the "why are you avoiding REST" debate that I split them out to their own category. Technically of course, whatever protocol you use may be a layer atop of REST - if you have a separate layer (like CRDTs) that handles syncing/conflict resolution, then that is the protocol you are really using.
redux-offline
-
Offline-First Development in React Native: Creating Robust Apps📱🔌🛠️
Further Reading: Redux Offline Documentation
-
I haven't used React in over 5 years. Can I still use the same add ons I used then? [ react-redux and react-saga ]
I haven't ever tried to build an offline-capable app myself, but from looking at things like https://redux-offline.github.io/redux-offline/ it seems based on capturing actions that describe what requests need to happen, akin to how sagas usually work, as opposed to using thunks that are just "a function that executes and then dispatches actions".
-
Why do Webdevs keep trying to kill REST?
Offline. Both Firebase Firestore and Amplify AppSync also support offline persistence. Since they know your database schema, it's easy to offer a local replica and conflict resolution. There are vendor agnostic alternatives like RxDB or Redux Offline that take more glue work. Being Offline-first requires you to have a local replica of your data, which means that doing CRUD against your local replica can be much simpler (see below).
-
Do you know a tutorial that exaplains how to allow CRUD API calls offline in a React PWA?
https://github.com/redux-offline/redux-offline Worth a look as well
What are some alternatives?
absurd-sql - sqlite3 in ur indexeddb (hopefully a better backend soon)
supabase - The open source Firebase alternative.
RxDB - A fast, local first, reactive Database for JavaScript Applications https://rxdb.info/
hotwire-rails - Use Hotwire in your Ruby on Rails app
reactjs-interview-questions - List of top 500 ReactJS Interview Questions & Answers....Coding exercise questions are coming soon!!
react-boilerplate - :fire: A highly scalable, offline-first foundation with the best developer experience and a focus on performance and best practices.
offix - GraphQL Offline Client and Server
shelf
Winds - A Beautiful Open Source RSS & Podcast App Powered by Getstream.io