You’ll notice that apps that target stable protocols—POP3/IMAP mail clients, RSS newsreaders, vCard calendar apps—never force you to update. They don’t need to. The app will keep working as long as the server they are configured to talk to keeps speaking the same protocol (and it will, because public, RFCed protocols evolve really slowly.)

The fault here lies mostly, I think, with backend developers who have spent their entire careers working on web projects—where, if they want to make a breaking change, they can just ask the web frontend developers to make a matching change on the website that conforms it to the new wire-protocol, and at most the only problem users will have is that their webpage might spontaneously refresh itself if it was relying on a websocket connection. You can’t do that when you have a native frontend pointed at your backend service, but these backend engineers just don’t seem to put much weight on the needs of native frontends. It's web-frontend chauvinism, basically. (Either that or it’s their management forcing them to act as if they don’t.)