I’d really appreciate, if someone having Meteor based backend for mobile app(s) in production, could share his experiences related to the system architecture evolution, i.e. version updates.
What I mean is, once you have a mobile app tightly connected to a backend(as generally is the case with Meteor monolith approach), how do you handle different versions of data/API on server and client? I.e. you have full control over server versioning, but you basically cannot influence how often a user updates his or her app, which can lead to version mismatch. Given that hot code push is not that reliable at all(in our experience), which mechanisms could be used in such a situation?
One possible solution would be to send client version to the API in each call and route the API call on server accordingly.
Link on any text about it or real life experience is highly appreciated.