Problem Statement
Currently, users must manually download and install new versions from GitHub Releases.
- This creates friction, especially for:
- non-technical users
- frequent alpha releases
- corporate environments where reinstallation may require validation
A proper update mechanism improves:
- user experience
- adoption
- trust
- release iteration speed
Proposed Solution
Implement update handling using electron-updater with the following behavior:
- Check for updates on app startup
- Notify the user when a new version is available
- Allow the user to choose when to download and install the update
- Apply updates silently on app restart (no installer UI)
- Preserve all local data (SQLite, backups, config)
Updates will be served from GitHub Releases.
Alternatives Considered
🔄 Expected behavior
- App starts
- App checks for new version
- If an update is available:
- User accepts update
- Update is downloaded in background
- App restarts and launches the new version
No reinstallation wizard or additional permissions should be required.
Feature Area
Settings
Priority
Medium - Would improve workflow
Contribution
Mockups or Examples
No response
Additional Context
No response
Problem Statement
Currently, users must manually download and install new versions from GitHub Releases.
A proper update mechanism improves:
Proposed Solution
Implement update handling using electron-updater with the following behavior:
Updates will be served from GitHub Releases.
Alternatives Considered
🔄 Expected behavior
No reinstallation wizard or additional permissions should be required.
Feature Area
Settings
Priority
Medium - Would improve workflow
Contribution
Mockups or Examples
No response
Additional Context
No response