Sachin Saini I haven't implemented anything like this yet, but I'm confused when/how the App State is updated. Shouldn't this be a constant that holds the current version of the app?

Here's my theoretical approach, but feel free to correct me!

Instead of Remote Config, I'm thinking of using my database system configuration table.
The \"app version\" database key-value row contains: release date, version, required.
Custom action retrieves the config
- If config not found exit.
- Set custom data type app version.
I think there might times when an update is required and suggested:
- If not required, display banner on home page that update is available (or defer to \"Please update\" page with a \"Maybe later\" option).
- If required, redirect to the \"Please update\" page.
- Can switch to a suggested update in the database if bad things happen.

Immediately ignore Is Web.
For metrics, write to a log when forced update message is displayed.
Display the version number to the user somewhere for support reasons.

How to force the user to update the application?