0
It is possible to create some criterion that makes it impossible to update my application in the published google play?
Current scenario:
- I have a sales force system on Android and an ERP on Desktop that exchange information.
It happens that to have this communication, the versions must be updated according to the layout of message exchange. And for this reason, I can’t allow the android app to upgrade to a newer version without first updating the Desktop.
Why doesn’t the Desktop version accept more than one message exchange protocol (versioning the protocols)? Otherwise you will always have a package to update first. And even if it is solved, and who does not want to update the app?
– Wakim
That’s where the problem is. For each N users, the desktop versions can be: v1, v2, v3. Playing the app on google play, all users will be able to download the new version. Soon I will have no way to update the desktop in the short term. So I believe that if there was a way to validate the update by google play would solve this problem.
– Herik R
You do not need to validate, as long as you are versioning the protocol and sending the version to the Desktop, just update the Desktop first with VN higher than the App, keeping all versions. In this case, you can send the version of the protocol that the Android app uses to the Desktop that using some Pattern (Strategy or Factory for example) it selects the implementation relative to that version. If so, no matter when the user updates the app, will always have a compatibility on the part of the Desktop.
– Wakim