Do you support backend-controlled minimum app versions for iOS and Android that can be managed without releasing a new app? If so, could you share details on hard vs. soft upgrade behavior, the version-check endpoint, expected behavior if the endpoint is unreachable, and who can manage this configuration?
Yes, we support backend-controlled app versioning for both iOS and Android without requiring a new app release.
Operators can configure version values directly from the Operator Control Panel → General → Apps section. Specifically, you can set:
-
Current Version
-
Minimum Version
-
Store URLs (iOS / Android)
These values are exposed publicly via the /kit endpoint under the apps object. The mobile application can read these values at runtime and apply different upgrade logics accordingly.
Hard vs. Soft Upgrade
The platform provides the version values, and the mobile app implements the enforcement logic:
-
Hard upgrade: If the app version is below
min_version, the app can block access and force the user to update. -
Soft upgrade: If the app version is below
current_versionbut abovemin_version, the app can display an optional update prompt.
This allows full flexibility in how strict the upgrade policy should be, without requiring a new app release.
Version Check Endpoint
-
Endpoint:
GET /kit -
Field:
apps -
Includes:
current_version,min_version, and store URLs.
This configuration can be managed by the exchange operator (Admin role) via the Operator Control Panel.