Hello,
I have looked both in the forum and in the issues on Github. I am surprised that I seem to be the first one to wish for a smoother upgrade experience.

Honestly, I love Joplin. But very often, when I open it on my Mac, it tells me that an update is available. Installing it involves downloading the DMG, opening it, and dragging the new bundle to my applications.

Though not too much of an effort, it does feel like a waste of time for every update. So, have there been considerations to improve this?

Best regards, Arne

Hello Laurent,

thank you for sharing your opinion - I took a quick scan across the link rxliuli posted above.
I am not sure how I could contribute. Of course, I could include the auto updater in the code and make a pull request. But I don't see how I could easily set up the infrastructure (code signing, building, providing releases on GitHub) to test it.

So please, let me know how I could help in this regard, as someone not fluent in JS or Electron.

What I already did, regardless of my feature request, is set up a GitHub sponsorship, because I really appreciate Joplin.

Hi all, I've been using Joplin on macOS for quite a while, I upgrade it via Homebrew, but I usually prefer the workflow available in other apps, that is: - the app shows a pop-up to the user about an available update - if the user continues, the app downloads a new distribution file containing the new .app - if necessary, the user is asked to enter the credentials of an admin (ie, cause the old .app folder isn't writeable, as it shouldn't) - if admin challenge succeds, old .app is replaced and the app restarted.

Maybe Sparkle can help?