search

replayio / design

Tasks for the Replay design team
1 stars 0 forks source link

[UX] Design alerts for slow indexing and crashing #7

Closed jonbell-lot23 closed 2 years ago

jonbell-lot23 commented 2 years ago

Inspired by this bug: https://github.com/RecordReplay/customer-support/issues/74

Every failure in Replay should message itself appropriately (and if possible, it should automatically retry without requiring user intervention).

Users shouldn't ever be left staring at a broken Replay without some idea of what happened.

jonbell-lot23 commented 2 years ago

Go link: http://go/failinggracefully VIdeo explaining POV:

https://user-images.githubusercontent.com/9154902/163736914-e71d9681-77fb-4565-bfc1-85f4445cf4af.mp4

jonbell-lot23 commented 2 years ago

Status: Jon to do visuals and align with other places in the app:

  1. Global indexing
  2. Print statements loading
  3. Pause panel
  4. Loading in console
jonbell-lot23 commented 2 years ago

Note to self: this is high priority

jonbell-lot23 commented 2 years ago

Here's some UX work for item 1 above, the global indexing: https://www.loom.com/share/0a166bf55c72457dbd760dc2c9947251

And here are sketches (not final visuals!) that show it:

image image image
jonbell-lot23 commented 2 years ago

Here's a Loom walking through 16 screens -- 4 areas x 4 states: https://www.loom.com/share/26c51adcb1014f8d89a0b6f32921387b

Next steps: Not all of these 16 screens are equally important, of course. I'd start by implementing each of the failure states as its own ticket. From there, we break out the other items in chunks.

jonbell-lot23 commented 2 years ago

I've done my explorations and carved off the highest priority task: adding a message for a failed indexing process. Find the task here: https://github.com/RecordReplay/devtools/issues/6476