3 ms·

I actually really hate material design in general. It's "okay" on Android, and that's the only place it works. The Material web design layout never feels good

by XorNot 5y ago

I actually really hate material design in general. It's "okay" on Android, and that's the only place it works. The Material web design layout never feels good in the browser - it's floaty. Interactions don't ever feel "solid" - basically the experience is always like using a buggy webapp where you're thinking you need to open the dev panel to see if it's erroring silently. Try using any of Google's setting panels or the like compared to an old school bootstrap app - regardless of actual quality, you constantly feel like your interactions with Google are being ignored and that's on Material designs floatiness. Bootstrap feels solid and clean. Heck even the AWS UI console - which is broken a ton of the time between corporate IAM and just jank - always feels more responsive to your inputs. It's just a terrible system.

p_l 5y ago
I remember back before Material design, I think it was called "Polymer", and how it generally meant I needed to be extra careful because reimplementing basic browser behaviours in JS meant I was never sure if typing text in a textbox will work, not to mention dropdowns and such...
alephnan 5y ago
I worked at Amazon, too. People look down on Amazon, especially relatively to Google. But Amazon had their priorities straight when it comes to frontend. I worked on the team that made shares UI widgets, and it was forking off of Bootstrap. Yes, people may remember Amazon retail being bloated, still kind of is sometimes, but those are product design decisions separate from the ui components. AWS wise, there is just so many products and maybe not enough users / page where it doesn’t make enough business sense to invest more resources. Actually, Amazon had the most practical designers I ever met. They were also closer to the metal in the terms of being considerate about CSS bloat. > interactions don't ever feel "solid" - basically the experience is always like using a buggy webapp where you're thinking you need to open the dev panel to see if it's erroring silently Funny you mentioned AWS. This is exactly the problem with the GCP web console, even though it had a better overall visual hierarchy than AWS. Disclaimer: I also worked on the frontend for GCP
howenterprisey 5y ago
I absolutely get what you mean when you say "floaty". I use the word "plastic" for that, as in cheap plastic.

by XorNot 5y ago

p_l 5y ago

I remember back before Material design, I think it was called "Polymer", and how it generally meant I needed to be extra careful because reimplementing basic browser behaviours in JS meant I was never sure if typing text in a textbox will work, not to mention dropdowns and such...

alephnan 5y ago

I worked at Amazon, too. People look down on Amazon, especially relatively to Google. But Amazon had their priorities straight when it comes to frontend. I worked on the team that made shares UI widgets, and it was forking off of Bootstrap. Yes, people may remember Amazon retail being bloated, still kind of is sometimes, but those are product design decisions separate from the ui components. AWS wise, there is just so many products and maybe not enough users / page where it doesn’t make enough business sense to invest more resources. Actually, Amazon had the most practical designers I ever met. They were also closer to the metal in the terms of being considerate about CSS bloat. > interactions don't ever feel "solid" - basically the experience is always like using a buggy webapp where you're thinking you need to open the dev panel to see if it's erroring silently Funny you mentioned AWS. This is exactly the problem with the GCP web console, even though it had a better overall visual hierarchy than AWS. Disclaimer: I also worked on the frontend for GCP

howenterprisey 5y ago

I absolutely get what you mean when you say "floaty". I use the word "plastic" for that, as in cheap plastic.