I was co-conscious with Maria and the things I saw on her dash pissed me off.
With the posts about the simply plural shutdown on her dash, it would seem that the general attitude of the community when a developer releases a DID/OSDD management app is "you must provide technical support and updates for this forever, oh yeah it should be free too."
I feel very validated in NOT releasing anything I experiment with making for my system's own use if that's the attitude of the community.
On the other side of this, pwDID need to start thinking critically about the digital tools they use to manage their system. Ask these questions:
Who made this, are they likely to stick around?
Is this alpha or beta software, or has it been around for a while?
Does this have commercial backing, or is this software someone's hobby?
Is this open source? If the developer disappears, can I take the source code and keep patching / updating it myself (or pay a developer to do it)
How is my data stored and processed? Is data saved locally or in the cloud? If it's stored in the cloud, can I run my own server or export my data? Is the file format of the exported or locally stored data easy to understand? Is there another program that can read it, can I write code to read it? or is it proprietary. If it's stored locally, can I access it to back it up or write code to read it? or is it stored in a location protected by the operating system that I can't access?
As an example, Microsoft Onenote fails these requirements because onenote tries to lock your notes into Microsoft's servers. You can export with difficulty, but the file format is proprietary and extremely complex. A spec is available, but it would take me 2+ years to write and test a proper library to read it.
Obsidian passes most of these requirements, we would rather it was open source. But the files are plain markdown files. So if Obsidian went away, it wouldn't be too difficult for us to either just use a text editor or make our own application that works like obsidian did.
In general people have been conditioned not to think about this kind of thing and have also been conditioned to expect things to be free. This serves the interests of tech companies who make money from controlling and selling our data [1]
Some counties have passed laws to help with this situation, for example in EU regions being able to export data to a common format like JSON or CSV is a legal requirement.
Mobile operating systems also nudge developers to do things in certain ways. For example, on android saving data to a server via a REST API is easy. But saving data to a folder of the user’s choice is surprisingly difficult (API level 36), requiring you to present a UI flow where the user grants your app permission to access the folder they want to save to. You then have to access the granted folder with a different API than the normal filesystem APIs in your programming language. In some app frameworks, the APIs to do this aren’t even available.
We are told this is for security, but it is actually about platform holders maintaining dominance and control. App developers don’t want to deal with this, so they store data on their servers which is exactly what the platform holders want.
User expectations also come into this as we expect to be able to sync between devices without giving any thought to how this is achieved.
[1] I am NOT intending to imply that SP was selling people's data. I am rather talking about user expectations and how platforms restrictions shape developer choices.