Posts

Post not yet marked as solved
6 Replies
1.1k Views
On an app I'm working on we're experiencing some frequent issues in new App version adoption. Our release policy is the following: We usually release a new version of the app twice per week (usually on Monday and on Thursday). Each new version is released as a phased rollout over a 7-day period When we are ready to release a new version, if no major issues are found in the previous one, we release to all users the previous version and we start the phased rollout for the new version. Sometimes (not every time) it happens that an old version keeps an high adoption even if we released at least a couple of new versions to all users after that one. As you can see from the attached screenshot, the version released at least 20 days ago still keeps the majority of the user sessions even if we released at least 2 other versions to all users and another one as phased rollout. Anyone has suggestion how would be possible to improve adoption for newer app versions? At the moment we tried to wait a bit of time (half a day) between the moment we release to all the users the N-1 version and the moment we start the new phased rollout for the N version but it seems that it's not solving the issue. Could the issue be related to the fact that we're releasing new versions too frequently?
Posted Last updated
.