So the aforementioned pattern would be something like this:

  • User submits form
  • Page immediately updates to show new entered data, with no page loader or wait time
  • If there is a problem with the async api call, the state is reverted and an error message is then shown

I swear that I have seen a pattern with this name but I am drawing a total blank.

  • I'm not sure what it's called, but it seems like a flawed pattern. There's no transparency to the user as to when it saves successfully. Also, if I submit the form, it shows everything the way I entered it, then I close the page, there's no way for me to know there were any errors. Again, I don't know what it's called, but I'd describe it as "opaque" or "fragile". Nov 13, 2018 at 21:35
  • It's really going to depend on the use case and is not meant for every call. I've seen this sort of pattern in play in Google apps. Essentially, it's just setting the local state so as to not block the user. It seems popular with progressive web apps or "offline" type of situations.
    – boardlemur
    Nov 13, 2018 at 21:40
  • Hm.. Yeah, perhaps with non-critical calls it could be alright. Unfortunately, to your question, I can't offer any answers. Nov 13, 2018 at 21:47

1 Answer 1


It is known as an Optimistic UI.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.