I suppose an alternative design would be to be on-device storage first, and then have an optional sync to a server (or laptop/desktop).
I suppose an alternative design would be to be on-device storage first, and then have an optional sync to a server (or laptop/desktop).
The mobile app is also open source https://github.com/wger-project/flutter
I don't know how but I imagine you could build it and side load your own build to your phone?
https://raphael.lullis.net/thinking-heads-are-not-in-the-clo...
[0] localfirstweb.dev
That way your data is still in cloud and you don't actually need a server.
In fact if something is "in the cloud", it's by definition being made available by a remote machine, AKA a server serving the data.
The alternative is not to have a server and instead have clients share data if data needs to be shared.