4 ms·
I agree that handling offline devices is important. I've tried before an "offline first" database before, and it ended up really difficult to feel like an onlin
by HWR_14 5y ago
I agree that handling offline devices is important. I've tried before an "offline first" database before, and it ended up really difficult to feel like an online and synced app. So I think I'm going to have to go with some caching system.
I'm hoping this thread produces some good choices. Ideally, other than account creation (which seems like requiring internet is fine), everything caches automatically and syncs magically. Offline account creation would be great, until you want to verify people's email addresses or use OAuth
- lytefm 5y ago> Ideally, other than account creation (which seems like requiring internet is fine), everything caches automatically and syncs magically. This is pretty much how an offline-first app using rxdb (or just PouchDB) together with PouchDB works. Offline account creation? Just let the user use the app locally without creating an account. I only have two pain points with a CouchDB/PouchDB setup: 1. Technically, a user could post some garbage into his database after obtaining a session token. Design docs can help, but still cause overhead. 2. Only the "one database per user" approach properly ensures that each user can only access his private stuff. But then, querying information across users always requires to write some script that fetches the info from each database and aggregates them - instead of making one simple query.