Repository navigation
Why the gaslighting on the Async Rendering and SSR “Modes” documentation #4837
Replies: 4 comments 1 reply
|
I think the tone of your post is unnecessarily aggressive and quite rude, but I'm happy to address your specific points:
|
|
I'm sorry for the wait! I appreciate the earnest response.
This is my opinion: The documentation would be better if it reflected usability goals rather than showing off tech. The outcomes would be better. |
Loading Indicators are an Apology to your UsersOne of the things I hate the most about modern app design is that many companies seem to make the mistake that the point of the application is to show spinners and shimmering effects instead of content. Here is an example on Ecosia of a design I hate.
Google is a bit more subtle, but also not great.
When a page is moving while loading, it depletes the concentration of your users while they try to understand what they are looking at... making your app feel slower. Back in the day, Netscape has a feature called progressive loading, where it would show the content of a page as it downloaded it. This was great on a slow internet connection... But when internet connections increased in speed, Internet Explorer felt faster than Netscape because the page didn't move around and the show as a whole happened faster. If you can show content in under a second, you should prefer showing everything at once instead using loading indicators. In a modern context, there are metrics like CLS to help explain the experience. It's also important to remember spinners and loading skeletons also take critical development time. It is much simpler to show everything at once in terms of engineering and will constantly take more effort to maintain. Skeletons need to be designed to mimic the shape of your content.
Just to wrap everything all together, loading indicators should always be your LAST option. You use it for communicating APIs that cannot be optimized. It is a sign of failure and you are apologizing to your users. If you are worried about no user feedback.... well it is also possible to show a spinner on a delay to show the app isn't frozen. |








Uh oh!
There was an error while loading. Please reload this page.
Hey all,
There are multiple parts of this screenshot is a lie for normal design.
This documenation is pushing for engineers to write pages with high CLS. To put this another way, junior engineers nowadays develop webpages like the point of it is to show as many spinners as possible rather than fix performance issues because of documentation like this.
All reactions