3 ms·
Even returning the most bog-standard message like "Try again (Error #12345)" would be immensely more helpful than having the UI simply do nothing, unclear on wh
by pavlov 4y ago
Even returning the most bog-standard message like "Try again (Error #12345)" would be immensely more helpful than having the UI simply do nothing, unclear on whether it's still working or not.
Sure, async UI is hard, but the world's richest corporation with a reputation for UX excellence could afford to try at least.
- AlbertCory 4y agoThis. You have nailed it. And why does Support and Marketing push back on that idea? Because they don't like when a customer reaches Support and says "I got error #12345! What should I do?" They'd much rather the customer just shut up and go away however, the programmer who put 12345 in the code would dearly love to know that it was hit.