Currently we need to be backwards compatible with our app versions since a user can update an app without updating the OS.
One way to allow us to make new features and breaking changes and also "force" users to update the OS would be to guard a version behind an OS version.
I think we can simply add a new field to the version file blocking this, e.g. in a v0.99 file:
{
"icon": "💀",
"description": "example",
"min_os_version": "v0.985",
"v0.97": ["Tiny fix"],
"v0.98": ["Major fix"]
}This would make it so you can't update the app if you're not on at least OS version v0.985. It doesn't matter if we later add v0.99 and require OS v0.986, we would just update min_os_version and it would keep blocking users from updating.
Currently we need to be backwards compatible with our app versions since a user can update an app without updating the OS.
One way to allow us to make new features and breaking changes and also "force" users to update the OS would be to guard a version behind an OS version.
I think we can simply add a new field to the version file blocking this, e.g. in a
v0.99file:{ "icon": "💀", "description": "example", "min_os_version": "v0.985", "v0.97": ["Tiny fix"], "v0.98": ["Major fix"] }This would make it so you can't update the app if you're not on at least OS version
v0.985. It doesn't matter if we later addv0.99and require OSv0.986, we would just updatemin_os_versionand it would keep blocking users from updating.