Jan Lehnardt :couchdb:
hot take: having dozens of UI components go through a placeholder/loading/populated state progression on an individual timeline makes for a terrible user experience.
This includes most modern web and native things. I know how we got here, but the flickerfest needs to be a transitional period and I’m not seeing a way out. 🔥
esmevane, sorry
@darius @polotek @janl Yeah. I get the motivation, too. Saying "just do this thing" (where in this case it's "take proper care to thoroughly model out your async state and design your component space so it' knows about that state") is kind of bad vs "let's make an official API". But man, the API is tough to grok and even tougher to talk about w/ folks.
Darius Kazemi
@polotek @janl yeah Suspense is sort of trying to mitigate the thing where every single individual async component has its own loading indicator and pops in. It lets you draw a line around components (technically just children of the Suspense component) and have finer control over when the sub-components pop in, what order they pop in, etc.
this is not me saying it's GOOD btw, haha
Marco Rogers
@janl this is what the Suspense thing in react does right? I don't fully understand it. But it seems like it's meant to wait until all async calls are resolved? Either way I find it very confusing.
Jan Lehnardt :couchdb:
@polotek native apps suffer the same fwiw. Terrible database access can be done anywhere ;D
Marco Rogers
@janl guarantees? On the web? Ha!
Jan Lehnardt :couchdb:
@polotek no idea, but blocking the UI until all async things are done is also not great if those aren’t guaranteed to resolve fast.
Jan Lehnardt :couchdb:
@mattly @polotek yup, native used to be better at this but no more
esmevane, sorry
@janl @darius @polotek oh shoot. haha welp. so you did! my bad.
also, re: the flickerfest limbo - 😭
Jan Lehnardt :couchdb:
@ironchamber @darius @polotek as I said, I know how we got here :)
Brian David
@janl @mattly @polotek Yes, it's mostly the org chart vomiting onto the screen. And also, I have found that all backend devs and engineering VPs I've talked to about this seriously believe this is a better user experience than waiting longer with a splash screen but getting a more complete final render. A lot of people don't realize that multiple shimmers resolving at different times is usually perceived as slower to the user and introduces tons of jank.
Jan Lehnardt :couchdb:
@mattly @polotek just realising this is conway’s law striking yet again.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.