hotwired / turbo-android

Android framework for making Turbo native apps
MIT License
423 stars 51 forks source link

Offline-first (aka local-first) use #222

Closed dumblob closed 6 months ago

dumblob commented 2 years ago

I wonder whether there are any plans for adopting the offline-first/local-first approach?

After many many years I think Turbo (and the ecosystem around) is in the best position among web-based or web-related technologies to make it happen.

Note I'm not advocating here advanced stuff like https://github.com/josephg/diamond-types (CRDTs on steroids) or Causal Trees.

I'd just like to support the workflow: "edit offline during long stay (hours to weeks) without internet, then synchronize automatically with manual merging in case of conflict".

Any thoughts?

Nodalailama commented 2 years ago

Hi,

An hybrid application, like built with turbo-android, rely on the internet most of time.

Best regards

dumblob commented 2 years ago

That's why I'm seeking the offline-first/local-first support :wink:.

jayohms commented 6 months ago

We plan to explore service workers for first-class offline support across all platforms. Until then, there are no immediate plans in this project.

jonahgeorge commented 6 months ago

@jayohms do you know the best place to follow for updates on service worker support?

jayohms commented 6 months ago

It'll likely take place in the core https://github.com/hotwired/turbo js library. Other than that, we don't have the specifics worked out yet.

nfacciolo commented 5 months ago

Waiting for this upgrade ! <3

Do you know when you plan to work on that ?