IPhone application - offering to upgrade the user to the latest version

Question

We currently have an iphone app in the app store. We periodically release version updates about once a month or so, sometimes more often. In most cases, the updates are small, just added bits of functionality, bug fixes, etc. Sometimes, however, there may be significant changes (so far this has happened once, a year ago, and this should be repeated).

When major changes occur, ideally I want users to update to the latest version. I know that there is no way to automatically install the update. Since the application contacts the web service to retrieve its data, I can use this service to check the latest version and, if it is not the latest, I can warn the user about the availability of the new version and the update request. If the user does not want to update, I have the following options: (1) allow them to continue working with the older version or (2) effectively force the user to update, blocking the functionality of the application, if this is not the latest version.

Since an application requires a built-in web service, usually for major application updates, a change in internal needs is required. Sometimes these changes make the background code incompatible with the previous version of the application. In the previous time this happened, I had to create a separate back-end for the new version (now I have two web applications running on the server: for v.1 application and for v.2). Although theoretically I can continue to do the same thing - configure v.3, etc., I would prefer not to use and not force the user to update.

Now, technically, it's pretty easy to set up. However, what is Apple's view of this behavior? Because of this, can they refuse to upgrade? Any experience on this front? Thanks in advance.

Answer 1

The Chase Bank app forces you to update when an update is available (or you cannot log in). I think this is rather annoying from the user's point of view, but Apple certainly approved updates that do exactly what you are describing.

Answer 2

It depends on the time intervals of your transitions. We have a client who definitely requires the behavior you described. We can send two signals to the client application: must-update and must-update. When a client receives a mandatory update, he will no longer be able to start the user. We have transition periods and changes are noted that can be changed, so perhaps the active backends are now, for example, V6, V7 and V8. We give users enough time to go.