Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

54% Positive

Analyzed from 471 words in the discussion.

Trending Topics

#material#design#mobile#https#com#components#github#more#looks#bad

Discussion (20 Comments)Read Original on HackerNews

pavlovabout 1 hour ago
For a UI framework landing page, this looks impressively bad on mobile.

Big Arial at random sizes. No margins, no grid, component examples scattered all over the screen.

MetaMalone5 minutes ago
This was my first impression as well. The layout options just didn’t work on mobile
albedoaabout 1 hour ago
Welcome to the future! We better get used to it.
jgalt21239 minutes ago
Are you being a troll, or is there a trend afoot to ignore mobile rendering?
Yannik_Sc11 minutes ago
It is a shallow trend to ignore or on-purpose worsen mobile experience and force users to mobile apps instead of using the browser version.

Though I'm not sure if this can be applied in this specific case.

bbg240116 minutes ago
The trend is people releasing barely conceived software and products written by language models, backed by equally thoughtless marketing materials written by language models.
doodlesdevabout 1 hour ago
I'm impressed that, in the meanwhile, Google has already thrown into the grave not one, but two different implementations of Material Design in the web: Material Design Lite [0] and Material Components for the Web [1], bot of which never managed to actually be competitive UI libraries.

edit: Actually, they've thrown a total of _three_ implementations into the grave, as MWC is in maintenance mode already [2].

[0]: https://github.com/google/material-design-lite

[1]: https://github.com/material-components/material-components-w...

[2]: https://github.com/material-components/material-web/discussi...

cynicalsecurity4 minutes ago
Perfectly generic for perfectly generic applications, I like it.
gr4vityWallabout 2 hours ago
Wasn't familiar with it, looks interesting.

Some animations are painfully slow, though. After opening a menu[0], it takes a long time to close once you click outside.

How well does it work without JS? I assume that's how the ripple effect is implemented.

[0] - https://www.beercss.com/#:~:text=Menus,-code

Edit: they have documented what works and what doesn't with JS disabled here : https://github.com/beercss/beercss/blob/main/docs/JAVASCRIPT...

That file hasn't been updated in a while. Not sure if nothing has changed since then, or if it's outdated.

remix200043 minutes ago
I thought I'm the hardest to impress gremlin out there, but despite what the comments here look like, this is the best looking and practical MD3 CSS I've seen to the time. Not fond of promoting ethanol consumption though.
ghrlabout 3 hours ago
Beer CSS is great. I've used it for multiple simple projects and it provides a great DX with the clean html code and the many snippets on the official website. The only downside is that LLMs are quite bad at working with it from my experience, maybe it's just too simple for them..
fallinditch27 minutes ago
I guess it needs a skill.md file to help the LLM navigate the patterns and conventions.
miohtama27 minutes ago
I like the name more than Tailwinds
zsoltkacsandiabout 2 hours ago
This is a great project, but material design was the worst thing that Google invented and implemented. Completely tasteless, visually unappealing. Would be nice to see such a project with anything else than material design.
promiseofbeansabout 1 hour ago
And worth noting that this mostly implements the newer version of material design (M3). However, M3 was a lot more focused on shapes besides just circles and rectangles, but they don’t seem to have quite gotten that here
hmokiguessabout 1 hour ago
Thank you, I could not agree more. Material design is awful.
robvirenabout 1 hour ago
Extended FAB not rendering correctly for Firefox on mobile from what I can see.
1f60cabout 2 hours ago
Reminds me of https://getmdl.io (RIP :()
basilikumabout 2 hours ago
Why is there so much empty space under the yellow header?
drabbiticusabout 1 hour ago
Because they were more focused on the stills than the movie.

IOW, a screenshot when you scroll it to the "right" spot looks clean and balanced. Personally, I think it's a bad UX decision, but also easy to scroll past once you know.

Advertisement