Our onboarding flow is designed to meet the needs of the average user, and it does a pretty good job of this. However, there are options that advanced users might like to adjust before account creation, and we don't currently allow that.
This is especially problematic when it comes to weighing privacy against usability, as we're stuck with the poor options of either leaving a third-party integration on by default despite the privacy concerns, or leaving it off by default and leaving most users without the benefits that feature brings. If we allow adjustment of settings during onboarding, we can have the best of both worlds - we can maximize usability without sacrificing privacy, as users can always opt-out via the advanced flow.
The installation process for Windows uses a similar process - they allow the user to continue with all default settings, or they allow the user to choose each one.
In order to ensure this has minimal impact upon most users, I'm imagining this being an option that we don't strongly emphasize - to make it clear that this is a detour that most people don't need to take. This might be accomplished by making it a regular link instead of a button, or at least making it a smaller button that isn't with the main bottom navigation buttons.
I'm not sure where in the onboarding process this should be. It could come after the password and seed phrase has been setup - that's a decent option. But it might be worthwhile letting this come before that step if we want to make it easier in the future for users to customize aspects of that flow as well (e.g. perhaps we could allow opting into alternate seed phrase backup options, maybe via plugins).
Our onboarding flow is designed to meet the needs of the average user, and it does a pretty good job of this. However, there are options that advanced users might like to adjust before account creation, and we don't currently allow that.
This is especially problematic when it comes to weighing privacy against usability, as we're stuck with the poor options of either leaving a third-party integration on by default despite the privacy concerns, or leaving it off by default and leaving most users without the benefits that feature brings. If we allow adjustment of settings during onboarding, we can have the best of both worlds - we can maximize usability without sacrificing privacy, as users can always opt-out via the advanced flow.
The installation process for Windows uses a similar process - they allow the user to continue with all default settings, or they allow the user to choose each one.
In order to ensure this has minimal impact upon most users, I'm imagining this being an option that we don't strongly emphasize - to make it clear that this is a detour that most people don't need to take. This might be accomplished by making it a regular link instead of a button, or at least making it a smaller button that isn't with the main bottom navigation buttons.
I'm not sure where in the onboarding process this should be. It could come after the password and seed phrase has been setup - that's a decent option. But it might be worthwhile letting this come before that step if we want to make it easier in the future for users to customize aspects of that flow as well (e.g. perhaps we could allow opting into alternate seed phrase backup options, maybe via plugins).