Optimistic UI?

[tslocke]

Unless I've missed it, the website doesn't say anything directly about optimistic UI (i.e. instant updates without a backend roundtrip).

However it does mention "online and offline data sync", which is largely the same problem.

The days of click -> spinner -> update are coming to an end. Increasingly web apps are indistinguishable from fully local desktop apps, in terms of responsiveness. Making this easy is becoming table stakes for modern infrastructure IMO.

What's the SurrealDB story?

Thanks

[sp90]

@tslocke correct me if im wrong, but isn't this up to the implementor in the frontend to do?

So as I see it like this:

Button click -> Inside the function that is fired following happens

1. shows (successful) state to the user
2. then fires api request
3. if request succeeds do nothing
4. if request fails returns and notify the user with a toast or similar

How would that fit in SurrealDB, or in other words how would that be part of something Surreal should handle?

[tslocke]

That way quickly becomes a lot of work. Have a look at InstandDB, Replicache, and many other solutions in the local-first space.

…

On 3 Oct 2024 at 10:21 +0100, Simon ***@***.***>, wrote: @tslocke correct me if im wrong, but isn't this up to the implementor in the frontend to do? So function called on button click shows (successful) then fires api request if request fails returns and notify the user with a toast or similar How would that fit in SurrealDB? :) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[sp90]

@tslocke havn't worked much with the local first databases, but have done a lof of web apps without offline capabilities that work that way.

So cant say if it could lie in the database layer - i would need to spend some time trying it out :)

But i guess if the database return some state that are just updated by the database similar to live queries