First user experience gets in the way of advanced users
Bug #1349477 reported by
Jorge Castro
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-gui |
Triaged
|
Low
|
Unassigned | ||
Bug Description
We do two things when a user deploys the GUI:
- Show the Tour button
- Show some legal cookie thing at the bottom.
The tour button should become non-blocking because after the first time using Juju GUI you don't need it anymore and it's an extra click to get to where I need to be. Right now you have to close it explicitly, I can't even choose to ignore it.
The bottom cookie bar just takes away screen real estate and just gets in the way. I've not seen a single web app other than the Juju GUI that uses a cookie warning.
Revision history for this message
| Richard Harding (rharding) wrote | #1 |
| Changed in juju-gui: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
Thanks for the report Jorge.
because the GUI is deployed on a fresh machine and IP address each time, there's no way for the GUI to know if you're a repeat or a new user to the GUI. The Tour is shown each time. There is a new onboarding design that will be less intrusive that is in progress, however it also will have the same limitation.
The cookie bar is an EU requirement. The GUI does not ship with the ability to know if it's deployed in the EU or not. Most hosted apps can tell because you hit a central server. The GUI cannot do the same work as a single hosted service. What we can do is evaluate if there's some way to get a IP address check that will pass legal muster. We can research how the law applies to things like internal IPs or self hosted services. Since the law is around data collection, maybe we can find a 'you installed service X' loop hole for the juju deployed gui instances.