> you need to accept a model where there's ongoing pay for that work
Before they switched to subscriptions, it still worked like that: 1Password 4, 1Password 5, 1Password 6 - I paid money each time a new version came out. Sometimes I paid the same day of the release and upgraded immediately. Other times, I may have waited a little bit longer and continued with the version that I had.
They had a model that was ongoing pay for their work. 1password was healthy and happy providing flat fees for major version updates, which were every couple of years. Then some VCs wanted to see more profit so suddenly it's all online, subscription, drop the native clients, and a pivot to enterprise. It got enshittified.
No, the last twenty years has show us that we can't.
If you want developers to perform ongoing work on their products, you need to accept a model where there's ongoing pay for that work.