Magic UI: UI Library for Design Engineers
magicui.design
magicui.design
What is the difference between the animated Border Beam in this library and the animated hr in the vintage example of an archived geocities page?
That said, WTF is with all these "libraries" thats basically just collections of shit from codepen stacked in 1 place that they thought was cool, shit most of these don't even have cohesion from one to the other really besides... "cool motion"
"Companies spend $30,000 and several weeks to get designs like this"
Yes. Because being a first or early mover is expensive. You commoditizing their style after they've put in all the brain work to create or build it isn't the same thing.
Also, isn't the point of design engineering to be capable of coming up with relatively original and innovative UI?
that's definitely why I got into it years ago, but it seems like it has lost it's meaning and been simplified into "engineer that likes design" or "engineer that wants to be good at design"
A classic example is the rotating globe that you can click and drag. That was usually meant for showing sales happening across the world, but now people are just throwing it in a card with the header: "Innovative new features".
Like there's just no thought put into anything and what bothers me is how popular low-effort is becoming in tech. Startling.
Oh, the nostalgia: http://www.sasg.com/mui/preview.gif
Due to how slow it is, it feels more like an attempt at sabotage.
- https://magicui.design/docs/components/border-beam - https://ui.shadcn.com/
I'd be interested in an analysis of common patterns in marketing pages. We have a pretty good standardized set of components for productive interfaces (buttons, fields, tabs etc.)
But looking at this makes me wonder if there really is a common set of abstractions for marketing pages beyond just throwing out 200 templates and calling them blocks.
It's just passing JS properties to the `linear-gradient()` css function which is already well documented on MDN. I can't see what value Magic UI is providing there ... https://developer.mozilla.org/en-US/docs/Web/CSS/gradient/li...
Cobe does not seem to trigger huge time spent in Layerizing and Style recalculations, which are the main areas the web page spends time for me.
Curiously it's not as bad on corporate windows laptop that has worse specs, and which was outputting to 30fps-locked display (personal laptop was rendering to 165Hz screen...)
The rise of bento box designs [at least for now] is very visually appealing. Glad to be moving away from illustrations. Some of the designs animated with Rive are mind blowing: https://x.com/alex_barashkov/status/1790748157141213237
What's minimal about it? Washed out colors, everything white, and grey font do not make something minimal.
Come on, even the too lines in their call out slide in with unnecessary animations. Everything on the page is moving, bouncing, animating. If it's .minimalism, it's Michael Bay of minimalisms
Highly anticipating State of JS 2023 data though...
[1] https://2022.stateofjs.com/en-US/libraries/front-end-framewo...
It's easy to work with, there's nice router and internationalization packages, ready made components with PrimeVue (though PrimeReact and PrimeNG are nice too; as well as other component libraries), PrimeFlex and Pinia for state management is wonderfully simple and scales pretty far. There's devtools for most browsers, the toolchain isn't super complex and while the ecosystem could be bigger, it's not inadequate either.
There are still many teams that choose to use something else. But experience in React is most easily transferrable. Even if I had a project in Vue, I would still look for React expertise.
Like the blink or marquee tag of Internet Explore reloaded.
Keeping a huge Figma component library in sync with a component library / design system feels more and more like busy work.
I don't even care what it shows due to just how audibly resource heavy it is while showing pretty much nothing other than some simple copy.
There's no way in hell opening the main page should cause so much load my computer sounds like I just opened Cyberpunk 2077 or Doom Eternal at max details, especially given the amount actually rendered (I just opened the page, didn't even scroll anywhere!).
Looking into Chrome's performance metrics it's as if there's constant, ridiculous re-rendering of everything, with just calculating the layering causing CPU fans to go to 80%.
Not a persuasive demo.
edit... reading through the other comments I see LOTS of people are having this issue. Not sure why I'm the lucky one, but I went back and clicked through all the pages, still no perceivable lag at all.
But it's audibly resource hungry, because it puts so much load my computer immediately jumped to high power cooling due to how much load it puts.
So yes, it's smooth, but that's more because I actually can run both the aforementioned titles at max detail at 4k, not because there's something secret breaking the site for some but not all.
Magic UI.design lags and stutters even when just scrolling up and down.
That tells me everything I need to know.
It's very difficult to navigate.
Performance: 81 / Accesssibility: 93 / Best Practices: 96 / SEO: 100
Performance is on the lower side, but the others are all tracking pretty well!
Like, my friend who took a 3 month js / react bootcamp and is working as a front end dev for our local pizza place, she's an engineer now ?
Cool.
“Web designers are not even programmers”
Building a half mile suspension bridge supporting millions of cars per day will require a different depth of understanding.
I just find it silly to use a definition that you typically need 4-6 years of maths heavy formal education for front end javascript that you can learn on youtube in a month.
Not in my country..
Some frontend developers are doing more actual engineering than I did when I was working as an actual electrical engineer, and I was working on buildings and shit.
Not all frontend devs, though, and certainly not the ones straight out of a bootcamp, but a lot are.
But the people building foundations for others to work on (like the target audience for this library) definitely are doing some sort of engineering.