Re:Downsides of Offline First
by firebase-user on Friday October 01, 2021 @10:57AM
(#28719257)
You should try using Firebase. It handles the data-sync for you, and it applies all updates locally first so that your app feels snappy.
[ Parent
| on HN ]
Last write wins is not handling data sync, it's washing your hands of it.
Your users will be frustrated.
Firebase is offline-resistant more so than offline-first I’d argue.
Re:Downsides of Offline First
by davidzweig on Friday October 01, 2021 @04:36PM
(#28723148)
The (JS) frontend SDK can be set to either online or offline mode. When in online mode, it seems to insist on downloading full copies of records, even when a version is somewhere in the local cache, slowing things down and incurring cost. Some optimisation could have been applied here, I didn't find anything about it in the docs. Does this match others experience?
Re:Downsides of Offline First
by code-is-code on Friday October 01, 2021 @12:51PM
(#28720774)
Firebase works until you want a different conflict resolution then last-write-wins.
It is also only offline first if the user is authenticated. Otherwise you need a connection to the servers before using the local state.
Re:Downsides of Offline First
by JamesSwift on Friday October 01, 2021 @12:02PM
(#28720168)
I mentioned Realm because thats what Im familiar with but yeah Firebase is also a good choice if you want a client-server setup.