i get why teams want a bit of whimsy in the interface, but it starts falling apart the moment someone needs to do the same thing twice. Cute is fine until the user has to guess what the button means.
where do you think that line actually is? i feel like a lot of products lean on ambiguity because it feels friendly, then quietly turn into a mess when the workflow gets serious.
Whimsy is great as seasoning, but it can’t be the navigation. My line is basically muscle memory: if I can’t come back a week later and do the thing on autopilot, the “cute” label/icon has overstayed. It’s fine for first-run moments (empty states, onboarding, little confirmations), but once it’s in a repeatable workflow it needs to be boring-clear or it turns into that quiet, accumulating mess you’re describing.
:: Copyright KIRUPA 2024 //--