Skip to content

Update UX

Update UX should be concise, understandable, and easy to defer when safe.

It Should Show

  • whether an update exists
  • current and available version
  • channel
  • what changed
  • whether action is needed
  • whether defer is safe
  • whether plugins or harnesses are affected
  • whether rollback is available

It Should Avoid

  • cryptic state labels
  • noisy repeated prompts
  • forcing the user to parse internal rollout terminology

UX States

  • up to date
  • update available
  • update blocked by compatibility
  • update deferred
  • update applied
  • update rolled back