-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Once restoration has started, require as little user interaction as possible, so the user can "walk away" #758
Comments
No, because when apps fail to install, this is the time where they can manually install the apps, so their data will get restored in the next step. We could however, auto-proceed when there were no errors.
Would be a bit tricky. We'd need app selection and file selection to happen first and then provide some sort of unified progress/result page that combines all information that currently is separate. I personally don't consider all that high-priority, because I for one would like to follow the restore closely, so I am aware of any issues and any apps that may not have restored as expected. |
Why does it need to happen here / why does the data need to be restored in the next step?
I get that. Typically, a user can do nothing if something fails, though. We don't even display actionable errors. So it seems like they'd be most interested in trying to move on with their life. |
You need to install apps before you can restore data for them.
In the case of installing apps, you can actually do something.
Maybe we need user research on this. In any case, re-doing the restore process as outlined would be a big undertaking, so ideally it is worth doing. |
Agree, let's pause this and see what comes out of user research if/when we have some. |
Right now, when restoring a backup, there are a few interactions that - from a user perspective - may be considered unnecessary, or that could be frontloaded.
The text was updated successfully, but these errors were encountered: