> I don't want websites and apps to connect with me on an emotional level. I want to turn my phone/computer on, use the app/program to achieve what I'm trying to do, and turn it off again

Building a B2B SaaS app one of the most refreshing thoughts I've had about it was: "people don't like using my app". The software I'm building nobody wants to use, but they have to use it for their work.

Given that I try my hardest to make the app as efficient and as fast as possible so that people can go in, do their thing, and get out. With things like design's I'm very careful to preserve the button layouts of all the UI's because I know my customers have largely memorized where they are.

I could see adding some "flare" like this in lower touch points in my app but I would not do this for high touch points. Those places need to be fast and predictable, a customer won't look too kindly on any redesign if they now have to spend an extra second or two looking for an action or waiting on an animation.

In terms of MaterialUI though, my app actually uses M2 (via the React MUI lib) and I'm pretty happy with it. I wish like hell Google would finish their M3 web implementation so I could hop on that instead of using a 3rd party lib but it seems Google has gotten M3 to where they personally want it and just kinda abandoned development.