r/react • u/Present_Ad3152 • 22d ago
Project / Code Review Stop using your boring gray skeleton thing π use this aura effect
I built an aura ascii-reveal component for reactjs to replace the old ancient gray skeleton. Put this cool effect in your project! I'm happy if there's feedback about the product!
13
u/sohnya_u 22d ago
I love them, but animations are for developers to show off to other devs, not for users IMO
3
u/Present_Ad3152 22d ago
Got your point! User/ also love the beauty, why not making them happy while waiting for data to land?
8
u/Mootilar 22d ago
You'll be shocked to learn most users don't have the same attachment to ascii as the average developer. My grandfather would think his webpage got hacked.
3
u/Present_Ad3152 21d ago
I'm not even that shocked since I am a product designer! And this component is of course only for niche user, not your grandfather
5
u/Salatet_Fattoush 22d ago
Any performance issues on non chromium browsers (Firefox based specifically)? Did you test it on less capable hardware? Otherwise looks good and i like the idea.
5
u/Present_Ad3152 22d ago
Thanks! Honest answer: I benchmarked it in Chromium only so far. That was without GPU acceleration and with the CPU slowed 4Γ, as a worst case. The skeleton paints as fast as a gray box there, and the shimmer used about 22% CPU vs 13% for a gray pulse (12 cards). So it worth to try! π
3
u/simonraynor 22d ago
Feels kinda janky on FF mobile, not totally broken but it has that "they're trying to do too much" feel
5
u/thefarixz 22d ago
tbh grey skeleton loading looks better than the first thing, but the things at the end is cool yes
2
2
62
u/Intelligent-Main539 22d ago
Usability > pretty
8
u/TechTuna1200 22d ago
I don't think those skeleton designs hurt the usability.
But I don't think there is anything to win either, once the novelty wears off. It will fresh for a week and then people will stop paying attention to it.
8
u/Intelligent-Main539 22d ago
For big surfaces or simple layouts, sure. But it can be distracting or annoying for people. I find it hard to believe that it is has the same performance as a gray box like the OP commented before (it was deleted). Especially on devices with less processing power.
2
u/Diadia_Uddy 16d ago
screen readers also tend to choke on ascii blocks unless you hide the whole thing from the accessibility tree
1
u/ArtisticConnection19 21d ago
Use it and ship 10mb of JS because our users want more!
1
u/Present_Ad3152 21d ago
Ha, close! It's about 15 KB gzipped, zero dependencies. Your users will have to want a bit more π
1
1
u/Legal_Spend_8912 19d ago
Just do some SSR and stop reinventing the wheel for problems you made by doing all this madness.
1
u/Present_Ad3152 19d ago
SSR is great and I'd use it too, but it doesn't remove loading states. It just moves them. Anything fetched after first paint still needs a fallback. This is just a less boring fallback. And it plays fine with SSR, the real text is in the DOM from the start.
1
u/Legal_Spend_8912 19d ago
The feedback is already provided by the web browser I don't need to reimplement that just to look cool. I rather having users knowing exactly what to expect from my website and simple SSR achieves that properly way before the SPA madness started. At the end of the day I need my website to be snappy not to have some wow effect no one actually needs because I'm serializing the same data at least 4 times when doing CSR.
1
u/Present_Ad3152 19d ago
Honestly, for that kind of site you're right. If plain SSR gets your users the content fast, you don't need this, and you shouldn't add it. It's for apps that already have loading states, where the choice is gray box vs something a bit more fun, interesting. Different tools for different jobs. It's not for every body π
1
u/Legal_Spend_8912 19d ago
You're missing my point. The skeleton was already a terrible abstraction, attempting to work around a structural problem: I need to make 10 separate fetch requests just to render the simplest website imaginable.
Those requests take time, and by the time they finish, the UI is already stale.
You don't go grocery shopping by making 10 separate trips. You make one trip, optimize what you collect, and bring everything back in one go. That's where the optimization should happen, reduce the number of requests and deliver everything the UI needs upfront, instead of masking the underlying problem with a skeleton.
1
1
u/ui_as_vindimas 22d ago
It's 2026 and react programmers still need to use skeleton because their fancy web app can't load the information in less than 5 seconds.
3
u/Present_Ad3152 22d ago
I agree. Better make it look interesting rather than things look the same in every apps
2
u/moinotgd 22d ago
Loading icon avatar with title and caption is good enough. no need show off animation, etc.
1
1
1


13
u/abrahamguo Hook Based 22d ago
Your documentation mentions an npm command, but your package doesnβt exist on npm under that name.