> "Tinder has been updated. Deal with it".
is an interesting choice of example. The anger at updates only really makes sense for apps that are entirely local to your hardware. As soon as you have an app where part of it runs on a server that you don't control, that logic goes out the window. They can stop your non-updated app from working with no effort, just by making the server API incompatible. As long as you are depending on someone else's server to be up and responding and not changing, you give up your rights to be in control of local updates.
It sucks, but that's the reality of SaaS. I'm a fan of using local apps whenever possible. For instance, Google Docs is just too damn useful not to use sometimes. But I still, majority of the time, will choose to use a local word processor whenever I can get away with it. And when I'm done working on a Google Docs project, I download it in several formats and put it in the drawer.
In the meantime I'd really like to see more take-up of open source, federated hosted solutions based on open document standards and open protocols. But so far the big corporations are winning that game.