Hey @TheJaaba, I am doing this currently. (The decentralization part is code under work, not for sharing yet).
What you do is that you pick the libraries with available FFI bindings, and then you code a wrapper in the language of your choice. So, currently you can interact with the data storage of SAFENet.
When crust has FFI bindings you could also create an overlay network. But you can do that anyway, with WebRtc for example. (There’s no out of the box solution for a decentralized app story though, meaning that there’s no multisig available in SAFENet yet, and implementing a secure consensus system in your overlay network is quite an undertaking.)
The easiest thing is to let users have a client application that works for them on their machine, i.e. there is no distributed logic processing. (You can look at my SAFEEventStore implementation for an example)
That way you can have constant client side processing of data stored on SAFENet. The user can then access this through a desktop interface, or if you prefer web tech for UI, you can code a regular web app - or even better: a SAFE web app - which calls your desktop application (i.e. on an http endpoint on localhost). This way you can have a background process without the need to keep a tab open in the browser (which would be needed to have js run that same logic).
So, with a SAFE web app UI, the site can be accessed from anywhere, and you could upload the installer to SAFENetwork, and the website tries to connect to the application locally, if it is not there it prompts to download the latest installer, and then you can install and run, and the website then can connect. This latest part is not solved or done, it’s just an idea I’ve had