Grape checks for a new version a few seconds after it opens, and stays quiet unless it finds one.
The notice in the corner
A small card appears in the bottom left naming the version that is waiting for you. Nothing downloads until you say so.
- Download starts it and the card steps aside, leaving a short note that the download keeps going in the background. Carry on writing.
- Not now puts that version away. Grape will not raise it again, and the release after it brings the card back.
Finishing the update
When the download lands, the card comes back to say the version is ready to install.
- Restart to Update closes Grape and reopens it on the new version right away.
- Not now leaves it alone. The update installs by itself the next time you quit Grape, so you get it without ever restarting on purpose. This is the one place the two Not now buttons differ: on the first card it drops the version, here it only puts the restart off.
After the restart
The first time Grape opens on the new version, the same corner lists what changed, once.
Checking yourself
Settings, General, Updates shows the version you are on and a Check for Updates button beside it. That is the way back to a release you closed the notice on.
On Windows
The Windows build installs from a setup file instead of replacing itself, so Download opens the release page for that version. Run the installer you get and Grape reopens on the new version.
Your notes during all this
An update touches the app, never the database it reads, so notes, folders and attachments stay exactly where they were. If you would rather have a copy in hand first, back up before you restart.
The phone updates on its own
The mobile app comes from the App Store and Google Play, so it follows whatever update setting you gave your phone. Installing Grape on mobile covers the rest.