Feature: Feature Toggle Base Mechanism

[eylulnc]

Problem Description

The Android app previously lacked support for a feature toggle mechanism, which is useful for dynamically enabling or disabling functionality via the backend.

Available features are listed in the /management/info endpoint — the same endpoint used for force update checks. Therefore, the logic for force update and feature availability has been merged into a single flow.

Additionally, the old system waited 2 days before rechecking for updates. Since feature availability needs to be checked more frequently, this delay has been removed.

Changes

• The update check now parses feature toggles from the /management/info response and makes them available through FeatureAvailability.
• Update checks are restarted when the server URL changes, ensuring that the latest app version and feature availability are always fetched in time — without waiting for a fixed delay.
• The check runs only when the app is in RESUMED state and isLoggedIn, reducing unnecessary processing and ensuring updates appear promptly.
• Unit Test Extended for Feature Toggles

Steps for testing

I have added the same step for force update please check that the logic works after user logged in. (In ios this logic trigger after logged in check)

Case 1: No Update Required
The update screen should NOT be displayed if the server version matches the local app version.

• Ensure the server reports a version equal to the current app version.
• Launch the app.
• ( Log in if you are not)
• Verify that no update prompt appears.

Case 2: Update Required
The update screen should be displayed if the server requires a newer version, and clicking the "Download" button should navigate to the Google Play Store.

• Locally modify the server response to return a higher version than the current app version.
• Launch the app.
• ( Log in if you are not)
• Verify that the UpdateScreen appears.
• Click the "Download" button.
• Confirm that the button redirects to the Google Play Store.
• If the app cannot reach the server, it should not force an update.

Case 3: Feature Toggle

• Observe the logs – every 60 seconds, the update and feature information should be fetched and printed.
• Confirm that feature availability is correctly set in logs.
• These logs will be removed after testing.

Screenshots

[FelberMartin]

Just a few smaller code comments :)