Closed rpwoodbu closed 7 years ago
I've observed that it takes a really long time for the app to update on its own, even after it is closed. This is a very bad UX. I should detect when all sessions are closed, and automatically call chrome.runtime.reload(); no need to have the user take an action beyond just closing the sessions.
This doesn't seem to work. I still have to wait a long time for updates to take effect.
When a new update is available, the app presents a low-priority desktop notification, as well as a yellow "butter bar" at the top of the new session dialog, suggesting that the user close all Mosh windows to get the new update. But it can take a very long time after that for the app actually to be updated.
I have seen some apps present a button to force an update immediately, which closes the app and restarts it at the new version. That would be a nice addition. The button should be careful, though, not to close any Mosh sessions that may be open, but to ask the user to do so first.
I have also noticed that the Secure Shell app superimposes an update notification in the top-right of the terminal window. That may be worth considering as well.