Only show channel progress indicator if it's taking >500ms to avoid jarring UX

[wwwillchen]

closes #365

[richard-to]

Yeah this is an interesting issue. I agree that on the on input it is can be feel jarring and visually makes Mesop feel slower. I often wait for the indicator to stop before I press submit. However, that's because I know it may not include all my text if I submit too early.

Especially for long running operations, I definitely think a good practice is to force disable other inputs. Otherwise you run the possibility of user's queuing up many actions and that can be weird. This can be a useful indicator that something is happening.

I haven't tested out how this feels (haven't tested out the branch), but I'll keep an eye on it when I'm testing out Mesop apps.

[richard-to]

LGTM

[wwwillchen]

Yeah this is an interesting issue. I agree that on the on input it is can be feel jarring and visually makes Mesop feel slower. I often wait for the indicator to stop before I press submit. However, that's because I know it may not include all my text if I submit too early.

Especially for long running operations, I definitely think a good practice is to force disable other inputs. Otherwise you run the possibility of user's queuing up many actions and that can be weird. This can be a useful indicator that something is happening.

I haven't tested out how this feels (haven't tested out the branch), but I'll keep an eye on it when I'm testing out Mesop apps.

Yeah, makes sense. You should document that pattern of disabling other inputs in our docs :)