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!

That's also a good way to implement it.