I would like to know your thoughts about whether you should "force" a game to be updated? I am thinking of releasing my next game as a workable basic version of a game ( I know some already do). I would publish the game without any revenue streams, without leader boards, without any thing else you and or I can think of that clutters up development. If the game gathers traction/interest, downloads, reviews, then release updated version with everything I have left out (or revenue stream at minimum). I would "force" the update by firstly informing at startup that there is a new version on the store. After ~10 days, if the user has not updated, prevent the game from playing. Pro's Keeps your game updated. Informs players that a bug fix or features are available. Prevent bad reviews due to bug fixes, that you have already fixed. Added features, especially something like leaderboards, will become more relevant (I hated opening one of my games, look at the leader board, only to see 20 entries. Con's Your game might be deleted. You could get bad reviews from the "nag". The user might just close the app and never play again. I think its that relevant to the conversation as there are probably many ways to do this, and what I am going to do is use the Unity Analytics Service Remote Settings to hold a date of the version update and app version, then on app startup check if app update date is at least current date + 1 and app version is not the same (I would do this as iOS in particular takes a while for an app update to propagate across servers, so I dont want to indicate to users that there is an update, only for them to check and there is nothing). Is this something you already do / don't do? What is your reasoning?