Just automatically click the save button for the user on a one minute timer. Done.
setInterval(() => {
document.getElementById("save-button")?.click();
}, 60000);For example, imagine you've got a template for a presentation. You open the template, you add/edit as needed, then you save it with a new filename. You don't want it to autosave over the template.
Or you need to produce a cut-down version of an internal document to send to an external stakeholder, so you load the document, cut it down, then export-as-PDF. You don't want it to auto-save the deletions atop the original.
And of course traditional PC software didn't store a rewindable document history, and exiting the software discarded the undo buffer. So if the software auto-saved a cut-down version of the document over the original, the original was gone forever.
With autosave you've got to change your way of working, making the copy before you make the changes.
Update, answered in detail here: https://news.ycombinator.com/item?id=42016231
I have been working with computers for 30 years, and I would find lack of a timed autosave surprising. Autosave was common on desktop applications in the mid 1990s. See: Everything in the MS Office suite.
Of course there is the "Previous versions" feature, but it still breaks my logic of Checkpoint-Experiment-Revert cycle. But I might be alone in this and users would be happier with autosave.
Update, answered in detail here: https://news.ycombinator.com/item?id=42016231
Update, answered in detail here: https://news.ycombinator.com/item?id=42016231
So yes, you're old fashioned.
I still hit "Save" in every single offline or online app every time I've made a minimal change, because of old-timer PTSD reflexes: I used to edit files in vi over modem and telnet without screen (tmux), and if the connection had a hiccup, the connection died, my editor died, and the changes died with it. So saving (extremely) frequently was just a way to not lose your changes.