Warn user their version is EOL and prevent from updating to a version that is not compatible

[ImaCrea]

Your use case

Context

Currently, many users are facing difficulties with older versions of MacOS or Windows due to the app's auto-update feature. As a result, they are unable to use Element on their desktops, which can be particularly problematic for those who rely on it daily, such as in a work environment.

The issue lies in the app's auto-update functionality, which upgrades to a version incompatible with their operating system. Consequently, users are left with a crashing app and no guidance on how to resolve the issue. Only developer users familiar with GitHub have found solutions by visiting these respective issues: #1315 and #808, #1505

Suggestions

Here are some suggestions to assist struggling users and prevent similar issues in the future:

• Enhance the content on https://element.io/download to include a section for users with End-of-Life (EOL) operating systems. This section should highlight security risks and provide a download link for the latest compatible version. Additionally, the primary download buttons should direct users to this compatible version rather than the latest, which may cause crashes. -> UX improvements to download older versions element.io#67

• Modify the latest compatible version's package so that when the app starts, it displays a warning message instead of automatically updating. This message should inform users that their app will no longer receive updates unless they upgrade their operating system.

• Implement a version check in recent packages to prevent installation if the version is incompatible with the current OS.

Why?

While security is paramount for Element and Matrix, many users are drawn to the platform for its decentralized messaging capabilities, not solely its security features. Users should ultimately have the autonomy to decide whether to accept security risks and continue using the app on an older OS without being forced to update.

There are various reasons why users might opt to stick with an older OS:

• They may lack the technical know-how to update or be content with their current setup.
• Updating could potentially slow down their system, prompting them to avoid it.
• Some users aim to minimize their ecological footprint by prolonging the lifespan of their devices and avoiding unnecessary upgrades.

Maybe at some point their app will be so old that they won't be able to communicate anymore with other users with an updated version. It's fine if they are well informed of it and know what to do if they want to keep communicate.

Closing Notes

I understand that these suggestions may seem mundane to implement or that other issues might appear more pressing. However, for Matrix/Element to thrive, we must cater to all users, not just advanced ones who can tweak configuration files in hidden folders.

I hope these suggestions are perceived as constructive contributions rather than mere complaints. The work done and the value offered by Element are truly remarkable, and I am immensely grateful for them.

Have you considered any alternatives?

No response

Additional context

No response

[t3chguy]

Closing in favour of Squirrel/Squirrel.Mac#280

[ImaCrea]

@t3chguy There are suggestions that are directly related to Element website, not linked to Squirrel. But maybe you didn't take the time to read.

[t3chguy]

Then wrong repo - https://github.com/element-hq/element.io is the tracker for the website

[ImaCrea]

And about the suggestion consisting of reviewing the latest EOL versions so they don't crash and warn user updates won't longer be applied? Isn't here the best place?

[t3chguy]

Well unfortunately as the support policy stands, issues concerning unsupported environments are immediately closed - https://github.com/element-hq/element-web#supported-environments - so this falls down a hole by policy.

[richvdh]

@ImaCrea I can't really speak on behalf of the web team here, but the long and short of it is that they are very stretched for time, which means that even if this issue hadn't been closed, it would have little chance of actually getting fixed. If you have ideas for simple improvements which can be landed without negative impact to supported environments, they might have more success if proposed as pull requests.

Also:

But maybe you didn't take the time to read.

I appreciate it's frustrating to have an issue that you put a lot of effort into be closed 5 minutes after opening it, but accusations like this aren't terribly helpful for persuading busy maintainers to your viewpoint. Please remember that the team is just trying to make best use of their very limited resources.

[ImaCrea]

Thank's for taking that time @richvdh

Much appreciated and sorry for the accusation @t3chguy , I was a bit frustrated in deed and I can imagine you had a lot on your plate already. ☺️