Lessons from building Electron auto-update across 25 releases
The article discusses the implementation of auto-update functionality in an Electron desktop app over 25 releases. It highlights the importance of this feature in reducing user complaints about outdated versions. Additionally, the author shares specific challenges faced during the implementation process and offers solutions to avoid similar pitfalls.
- ▪Implementing auto-update in an Electron app significantly improves user experience by ensuring they are on the latest version.
- ▪The author used electron-updater and GitHub Releases to manage updates without needing a separate update server.
- ▪Two main traps encountered included obfuscating network modules that caused production issues and forgetting to upload the latest.yml file.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3944430) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Sasaki Ryuji Posted on May 22 • Originally published at saas-diary.com Lessons from building Electron auto-update across 25 releases #electron #javascript #webdev #indiedev If you're shipping an Electron desktop app to end users and you don't have auto-update wired in, you're going to keep getting "this is broken" bug reports from users who are actually running a version from three releases ago.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
