Joonas Bergius • 6/9/2021

Coding pattern: preventing the use of '0 results' as a loading indicator

Read Original

The article criticizes the poor user experience of displaying '0 results' as a loading indicator, arguing it misleads users. It provides real-world examples from Google Drive and Windows, explains why developers fall into this pattern, and highlights the compounded issue of missing error handling. It concludes by proposing a technical solution using a TypeScript Result wrapper to force explicit handling of loading and error states.

0 comments
#user experience #error handling #frontend development
Coding pattern: preventing the use of '0 results' as a loading indicator

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 4 votes
2
Better react-hook-form Smart Form Components
Maarten Hus • 2 votes
3
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
4
Quoting Thariq Shihipar
Simon Willison • 1 votes
5
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
6
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes