Heartry
Heartry copied to clipboard
Google Drive Backup Restoration and Account Information
Describe the feature
There are two features I thought of:
- Show which Google account and e-mail ID are associated with the backup.
- Show a button to restore a Drive backup.
- Show a warning if non-backed up data exists or if current data does not match data in the Drive. (Hashing might help.) (Don't delete new notes that are not backed up.)
Motivation
Background: I was migrating Heartry from an old phone to a new one. I had never enabled Google Drive backups on my old phone.
New phone: I migrated Heartry over to my new phone, but that didn't transfer app data. It did give me a Google sign in option, so I used it.
Old phone: Now I remembered that I had some notes in my old phone and so I wanted everything in my new phone. I enabled Google Drive backups on my old phone for the first time and backed up my notes.
The issue: Now the issue is that there is no way I can figure out which Google account I used on both devices and I also cannot see an option to restore backup (and maybe a notification of overriding non-backed up data if it exists). How do I figure out which Google account I used for backups on both phones and how do I restore the backup?
Plan to execute
Sorry, I have never worked with Flutter or Google Drive before.
Screenshots
NA
Are you willing to make a PR?
Sorry, but I don't have the bandwidth for it right now.
- Show which Google account and e-mail ID are associated with the backup.
Yeah this will be added. Don't know how I missed it.
- Show a button to restore a Drive backup.
- Show a warning if non-backed up data exists or if current data does not match data in the Drive. (Hashing might help.) (Don't delete new notes that are not backed up.)
How can we handle a condition where the user deleted a poem and then there is a mismatch because the backup version has that poetry but the current version doesn't.
Asking users can be a potential solution but it will be annoying and overkill.
How can we handle a condition where the user deleted a poem and then there is a mismatch because the backup version has that poetry but the current version doesn't.
Asking users can be a potential solution but it will be annoying and overkill.
I would just restore the backup. The user will have to delete the file again. I don't see a huge problem with that, unless the user has maybe something like 30+ notes that they deleted, which the backup restored. To be honest, they should've backed up their changes. That's how backups work. They restore tracked files to the state they have.
Hmm... Makes sense 🤔
Can have this as an enhancement after auto backup is released in stable