Create a UX flow for Onboarding (setup) on install
UX Description
The team has identified a need to update the setup on install. We have a preliminary wireframe that we have discussed. Several changes will need to be made to move forward.
Request type
Application mockups / wireframes
Primary Contact
No response
Deadline for request
No response
To do:
-
[x] warning for people when they are pressing skip: i.e. You are about to cancel the setup. You can always change these later in Settings.
-
[x] draw a screen for when users already have podman running (and have a podman machine)
-
[x] do a sort of progressive disclosure for recommended / advanced: so people can see what they will be setting up right away, without leaving the screen with radios
-
[x] setting up right away, without leaving the screen with radios - add checkbox for Admin access (see docker desktop example) - needed for setup and compose, as they are installed globally
-
[x] have a dropdown for container engines and include Lima
-
[ ] Extensions selection would have to be contextual based on what users already have installed and what OS are they running
⚠️ THESE ARE WIREFRAMES ⚠️
Recommended setup:
Advanced setup:
- extensions will need to be contextual - exact ones for different OS TBD
Warning for skipping onboarding
If podman and / or podman machine already are installed, we can show an indicator:
@MariaLeonova Looking awesome!
Few notes
- For Container Engine, what would be the other engine? I think we can install only Podman. So I don't think the dropdown with other options guessing "Docker" should not be an option here
- When installing podman, there is (mostly on Windows) some errors with WSL/and other requirements. What if we detect some problem ? will we show this whole error or just some short sentence like "There are some required steps in order to make Podman Engine work"
cc @Firewall WDYT?
While updating the Onboarding flow it's also important to identify the metrics we'll be looking at to define success. Given our goals to reduce time to value and improve adoption by minimizing friction, those would be the main things to focus on. Can we measure:
- onboarding time
- success rate
- conversion
- retention
- skip setup rates
- telemetry check / uncheck
- separate extensions
- number users going through recommended vs advanced setup?
cc @Firewall @jiridostal @gastoner @feloy @deboer-tim @vancura what are your thoughts?