Update Mechanism Flow Design

[AbdelrahmanBayoumi]

I've implemented a mechanism for checking and applying updates in the application. Below is a detailed flowchart illustrating how the update process is handled based on user interaction and settings:

Link to the Flow Design: Mermaid Flowchart Design

Overview

The update process can be initiated in two ways:

1. Manual Check: The user can manually trigger a check for updates by clicking the "Check for Updates" button available in the settings page. This method provides direct control and is useful for users who prefer manual updates.

2. Automatic Check: If the user has agreed to enable automatic updates, the application waits for 6.5 minutes after startup before it automatically checks for updates. The delay ensures that the initial load time is not impacted by the update check.

Details of the Flow

• The flow begins when the application starts. It first checks if the user has agreed to automatic updates.
• If the user has agreed, the application waits for 6.5 minutes before making a request to retrieve the updates.xml file hosted in the repository's master branch.
• If the user has not agreed, the application remains idle until the user manually initiates the update check from the settings page.
• Once an update check is triggered (either manually or automatically), the application retrieves the updates.xml file and compares the current version of the application with the version available in the file.
• If a newer version is available, the application downloads the executable (EXE) from GitHub Releases and installs it. If the versions match, no action is needed, and the application proceeds as normal.