---
title: "Comment by Mohsan Ikram on \"Local Way to Prompt Users to Update Your Flutter App Based on App Version Check and Handling Staged Rollouts\" | Hashnode"
description: "Good one. But lets suppose if you upload an app and you published this release first only for 20,30% people to check the stablitiy of the app just like Whatsapp"
url: "https://hashnode.com/posts/local-way-to-prompt-users-to-update-your-flutter-app-based-on-app-version-check-and-handling-staged-rollouts/66e20aa9665598fb3efa9c21/comment/66e29721490878ced1fc761f"
---

[Discussion](https://hashnode.com/posts/local-way-to-prompt-users-to-update-your-flutter-app-based-on-app-version-check-and-handling-staged-rollouts/66e20aa9665598fb3efa9c21)

Comment [Local Way to Prompt Users to Update Your Flutter App Based on App Version Check and Handling Staged Rollouts](https://hashnode.com/posts/local-way-to-prompt-users-to-update-your-flutter-app-based-on-app-version-check-and-handling-staged-rollouts/66e20aa9665598fb3efa9c21)

[Mohsan Ikram](https://hashnode.com/@MohsinIkram)

[Sep 12, 2024](https://hashnode.com/posts/local-way-to-prompt-users-to-update-your-flutter-app-based-on-app-version-check-and-handling-staged-rollouts/66e20aa9665598fb3efa9c21/comment/66e29721490878ced1fc761f)

Good one. But lets suppose if you upload an app and you published this release first only for 20,30% people to check the stablitiy of the app just like Whatsapp is doing. Then in the word, few of people get the updates. So by your method, User will notice there is an update and when he will go to playstore then there is no current update as i mentionde few of people get the updates. So I think there is no good user experience.

[Atuoha Anthony](https://hashnode.com/@atuoha)

[Sep 12, 2024](https://hashnode.com/posts/local-way-to-prompt-users-to-update-your-flutter-app-based-on-app-version-check-and-handling-staged-rollouts/66e20aa9665598fb3efa9c21/comment/66e29721490878ced1fc761f#reply-66e29df311a119f137f88555)

Thank you for your feedback! You’ve raised a great point about staged rollouts, and you're absolutely right that in such cases, some users might receive the notification for an update, only to find it’s not available to them yet.

To handle this better, an alternative approach could involve integrating a remote configuration service (like Firebase Remote Config) or a custom backend API to manage version control. This way, the update prompt would only be shown to users who are eligible for the staged rollout. This ensures a smoother user experience by aligning the notification with the percentage-based availability of the update.

I'll update the article to mention this consideration for apps using staged rollouts. Thanks again for bringing it up!
