> [...] I consider "software as a service" model personally unacceptable. [...] I will try to keep my offline software functional as long as possible, before ma

> [...] I consider "software as a service" model personally unacceptable. [...] I will try to keep my offline software functional as long as possible, before maybe I find self-sufficient solution to replace I am not trying to convince you of anything, and you have the right to hold to your contradictions, but I find this at odds with most proprietary software, even more so if their execution environment isn't stable or 100% under control. Regarding your specific needs, it also does sound a bit like the XY problem: you don't really need an app (unless locked-in by data you can't migrate), you just need the functionality it provides, though that may require some unlearning first. Oh and yeah, of course there aren't alternatives for everything. But if you are really locked in and see the writing on the wall for your solution, you always have the option of creating your own migration path, or a stub application that does the bare minimum you need. Other might step in and help you, so it might be worth asking around first.