Adding a folder and moving back and forth will not remember the folder

[Natalia Bidart]

Attaching screencast with details.

[Roberto Alsina (ralsina)]

It happens because we only create the UDFs when we move *past* the computer-to-cloud page, so until that moment, the UDF is just an item in the list.

I *could* not clear the list when initializing the page, though, but that breaks other stuff more subtly, for example, if you unsubscribe UDFs from the cloud-to-computer page, they would still appear subscribed in computer-to-cloud.

OTOH, losing state when you move back is sort of expected, isn't it?

[Natalia Bidart (nataliabidart)]

Well, me as a non-regular user, was not expecting it. But let's ask UX team!

Can you please coordinate that?
Thanks!

[Roberto Alsina (ralsina)]

Assigning to rtgrant so he gives us an opinion.

[Lisette Slegers (lisette-slegers)]

I agree that the list not being persistent is unexpected. If it is technically not possible to keep the list intact, we should remove the back button from these screens. It is nice that users can go back (and worse if they can't), but if doing so breaks the list they just created, we should take it out.

[Robert Grant (rtgrant)]

IMHO ordinarily if I was using a wizard for something and I clicked the 'back' button I wouldn't expect the wizard to complete the task. This is because clicking back is a tacit acknowledgement that you did something wrong and need to go 'back' to change it before you go forward. With this in mind the behaviour feels okay to me.

BUT

Having said that, this is not really a sequential action. Once you have chosen a folder to add to U1 you kind of expect it to stay there. If we cannot change this due to a technical constraint, we should probably think about forcing the 'next' step to make sure it happens. We could possible remove the back button, or we could change the wording on the next button to 'Confirm' or something so that they know they have to click it. If they then click the back button they should realise they haven't confirmed and so the folder will not remain listed.

Thoughts??

[Roberto Alsina (ralsina)]

Another alternative solution is to make the settings page a popup instead of part of the wizard, since it's not really part of the workflow, but that doesn't sound like a good idea, although I can't express why.

[Lisette Slegers (lisette-slegers)]

If we want this thing to be a wizard / druid, it should happen in one window. The users that need a wizard most to set up U1 will not open additional windows that can easily be perceived to be 'advanced' functionality.

[Robert Grant (rtgrant)]

I'm sure there's a better way of doing all of this but it needs some thought.

The issue (for me) is that there is a sequential process to set things up when you first initiate the service and you are a new user, but once you have used the service for a little while and move to simple day-to-day tasks the user behaviour changes - and the UX should change to accommodate this.

That change requires a bit more thought than simply removing a button or switching things around.

Give the design team a couple of days to think this through and then we'll have a call to see what's possible and what's not.