Defining the Action in UI Design

• Log in to the Kuika platform.
• Open the project you want to work on from the Apps screen.
• Go to the UI Design module and select the screen where you want to retrieve the version information.

Adding an Action

• Open the Properties panel on the right.

• From the + ADD ACTION menu, add the Device > Get Version Info action according to the trigger event you want (Initial Actions, OnClick, OnBlur, etc.).
• Click the SAVE button to complete the process.

In a mobile application, version checking is performed to ensure that users are always using the latest version. This process is triggered by an action that occurs when the application is launched or on a critical screen.

Adding the Check Application Version Action

Go to the UI Design module and select the screen where you want to perform version control.

• To add the Get Version Info action to the screen at startup or linked to an appropriate button:
  
  • Select the Initial Actions or OnClick trigger for the screen or button.
  • Add the Initial Actions → Device → Get Version Info option from the + ADD ACTION menu.
• Click the SAVE button to complete the configuration.

Using Version Information

• The version information returned by the action can be linked to an in-app variable or Label element.
• The current version number is retrieved from the server or a fixed source on the same screen or across the app.

Notifying the User When an Update is Available

• For example, with a modal popup or banner:
• ‘A new version is available! Please update your app for a better experience.’
• The user is redirected to the relevant store page by clicking the update button.

Normal Behaviour in the Current Version

• If the version is up to date, the user continues to use the app without any warning.

• Dynamic Version Comparison: The version information received can be dynamically compared based on different environments (test, prod) or user groups.
• Update Flow Integration: Automatic update redirects or notifications can be integrated using version information.

Technical Risks

• Version Format Incompatibility: Comparisons may be incorrect if the version number is not in the expected format.‍
• Unauthorised Access: Ensure that version information is displayed to the correct user and used only in authorised operations.