Page MenuHomePhabricator

Illustrate loading
Open, NormalPublic5 Story Points

Description

While the entity gets loaded, we show a very rudimentary "Loading..." text so signal to the user that bridge is still trying to gather all data needed to operate.

We probably want to make this more appealing than it currently is.

MOCKS

specs can be found here

Acceptance criteria

  • the loading indicator always has a minimum screentime of 0.5 seconds
  • The fade in starts after 1 second
  • look and feel of OOUI Progress bar (indeterminate)

notes:

  • might add a fade in and out later

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 10 2019, 12:22 PM
Charlie_WMDE updated the task description. (Show Details)Sep 18 2019, 3:21 PM
Pablo-WMDE updated the task description. (Show Details)Oct 8 2019, 11:40 AM
Restricted Application added a project: Wikidata. · View Herald TranscriptOct 8 2019, 11:40 AM
Charlie_WMDE updated the task description. (Show Details)Oct 8 2019, 11:42 AM

From the description:

@Charlie_WMDE also mentioned the idea to approach this in a more general fashion, e.g. always showing the loading indicator if a transaction which is known to by asynchronous (e.g. the "saving") takes longer than 1 second.

I'm not sure about the "takes longer than 1 second" part of this. Most often we don't know how long the request will take and if it takes only 1.1 seconds, this would result in the loading screen being visible for 0.1 seconds. Maybe there should also be a rule of "If we show the loading bar, then we show it for at least 0.75 seconds"?

@Michael you have a very good point, thank you for voicing it. After talking to the UX-colleagues I think it's the best idea to stick to the 1second rule, but make sure that we always show the loading indicator for at least 0.5 seconds.

the idea is to always add 0.2 seconds fade in and fade out at the beginning and end of the animation, which would ensure we always get 0.5 seconds in the worst case (worst case being the 0.1 seconds).

Is that technically possible?

@Michael you have a very good point, thank you for voicing it. After talking to the UX-colleagues I think it's the best idea to stick to the 1second rule, but make sure that we always show the loading indicator for at least 0.5 seconds.
the idea is to always add 0.2 seconds fade in and fade out at the beginning and end of the animation, which would ensure we always get 0.5 seconds in the worst case (worst case being the 0.1 seconds).
Is that technically possible?

Sure ⏱

Charlie_WMDE updated the task description. (Show Details)Wed, Oct 16, 3:37 PM
Charlie_WMDE updated the task description. (Show Details)
Lydia_Pintscher triaged this task as Normal priority.Mon, Nov 4, 10:02 PM
Charlie_WMDE updated the task description. (Show Details)Tue, Nov 5, 9:46 AM
darthmon_wmde updated the task description. (Show Details)
darthmon_wmde set the point value for this task to 5.

During the task break down we discussed that there seems to be an interesting ratio between the effort it takes to use/show the progress bar and the animations mentioned.
This is particularly alienating as it was mentioned that it is hard to imagine how these animations/transitions look/feel like.
The more agile approach might have been to add the loading bar and then have dedicated feature requests to modify its animations/transitions if we realize that the look and feel leaves something to be desired.

@Pablo-WMDE that is what we agreed from from my side. We leave the animations out, see how it is, and only if neccessary add the fade-in and out. or are you referring to smth else?