Lol, I just stayed at the SF Grand Hyatt for 5 weeks and noticed lots of bad design in the hotel rooms.
1. a shallow basin on top of bathroom counter that encourages splashing water outside the sink
2. because its a basin on top of the counter it's impossible to clean well under it so it looks disgusting if you happen to look on top of the counter under the basin. Like if you happen to push a toothbrush under there (easy) you'll likely never want to use that toothbrush again after to see what it touched.
3. because it's shallow the overflow drain hole faces up meaning bending over to get a mouth full of water has you staring straight into a moldy yucky hole. A more normal deep, more vertical sink the overflow hole might be just as gross inside but it's hard to accidentally look inside it and get grossed out with your nose and mouth being 3-4 inches from the mold.
4. The mirror like surface of the bathroom counter shows a very clear reflection into the back of the mirror light which has tons of gross dust and mold.
Yea, don't design like a hotel room (eg, bad design)
Note: The hotel was not bad, especially for the current price which I'm guessing is a COVID price ($150-$200 a night). It's just interesting how much form over function the interior designer's choices were.
As for your comment in general, I like interesting UIs but I hate bad UIs more. 2 examples I've run into recently.
* Match.com, if you start editing your profile it pops up an overlay to edit. If you click anywhere outside that overlay you lose anything you had entered. I wanted to grab a piece of text and lost several minutes of work.
* Hinge. IIRC if you start entering something and switch away to another app for a moment you lose everything you started entering.
* I forgot which app it was but today I needed to copy a phone number but the app wouldn't let my select it.
* Shopify's phone number entry takes 10 characters. So if you type 123-555-1212 you get 123-555-12. If they don't want the dashes why not ignore them. Or better, allow them and just ignore them on the server. There's no good excuse for forcing the user to format a common form of number into some other format when the computer can do that for them.
My point is, I'd much rather UI designers start with some framework that supports known best practices and also learning what are best practices before just making some random new UI because they feel the need to be different (not saying Material Design is that)