Save card drafts before clicking "Finish"

I was tempted to file this under bug reports but I’ll leave it here because I understand that the current behavior is intentional.

My wife indulged me and tried out Supernotes on my recommendation. She was using it to draft an important email that required some research to compose and wasn’t familiar with the need to click on “Finish”. As a result, she lost all of her work, which had taken hours. Needless to say, she was extremely upset and will not use Supernotes again as a result. I even stopped using it for a time because it’s useful to have a tool that we can use together.

Data loss is really unacceptable for an app that contains such important information as one’s private notes. I understand that this isn’t data loss per se, but the effect was the same. So, it might be useful to persist a draft, even in a device’s local storage, so that one doesn’t experience this (and maybe I could then convince my wife to come back :wink: )

Hi @distefam, (welcome back by the way!)

We’re happy to hear your wife is keen to try Supernotes, but we’re sorry to hear her initial experience was marred by losing a card.

We’re honestly a bit puzzled as to how this happened. We totally agree that data loss is unacceptable, and that’s why we already have many fail-safes in place to prevent this from happening, including caching a card even if it’s just a draft. You can test this yourself by typing a new card and then quitting the app – when you reopen the app the card will be there.

Can you reliably recreate the method your wife used to lose a card? The only thing we can think of is that she might have pressed the cancel button, which would indeed wipe the card you are creating if you haven’t finished it. We were considering displaying a modal to confirm whether you want to cancel if your card is over a certain length. Would that help?

I will ask her. She’s a software engineer too so I’m sure she’ll figure out how to reproduce it, if possible.

I do know that she was tired at the time and she might have clicked on cancel inadvertently. I will ask her to confirm though.

Personally, I do find asking for confirmation for destructive actions is usually a good idea so that likely would have helped.

Ah that’s awesome, that would be really helpful!

Yes we’ve been hesitant about this as we already have this failsafe in place using the keyboard (you have to hold down esc for a few secs to confirm cancellation), and have previously thinking that tapping / clicking cancel is more intentful / less accidental. Nevertheless, we’ll see what we can do to improve this further :smiling_face: