One shape, everything in it
The card pattern emerged from a specific, legitimate problem: how do you present a grid of discrete, tappable items — contact, article, product — at a consistent size without implying a hierarchy you haven't designed? A bounded, elevated rectangle solved it neatly. Each item occupies the same visual weight; the shadow lifts it from the ground and signals interactivity without a label.
That rationale was solid. What happened next was not a design decision so much as a default settling into place. Component libraries codified the card early and made it cheap to reach for. Once it existed as a ready-made primitive — border-radius, box-shadow, padding preset — it became the answer to every containment problem, including ones it was never meant to solve.
A data table inside a card is a table that has been told it might be a product. A long-form paragraph inside a card is text that has been told to sit still and look tappable. A form inside a card is a transaction wrapped in the visual language of a social feed. The shape doesn't lie exactly, but it implies an equality and discreteness that the content often doesn't have. Everything becomes a tile; the page becomes a mosaic; relationships between ideas flatten into a grid of interchangeable units.
The shadow is the second problem. It was borrowed from material metaphors — the idea that content has physical depth, that layers sit above layers. On that logic, shadow intensity should communicate actual elevation, and elevation should mean something about the information architecture. In practice, the shadow became decoration. It says "I am a card" rather than "I am above this other thing." Strip the shadow from most modern interfaces and nothing about the hierarchy changes, because the shadow was never doing hierarchy work.
Rounded corners compound the effect. Softening was initially a reaction to the sharp, institutional rectangles of earlier desktop UI, a signal of approachability. It read as intentional when it was rare. The choices nobody made are often this: a corrective gesture that outlives the thing it was correcting, then ships as a neutral default. Any container that arrives from a library now has a radius unless someone actively removes it.
None of this makes the card wrong. It is genuinely the right unit for discrete, scannable, parallel content. The cost is using it everywhere, for everything, as the path of least resistance rather than as a considered answer to a specific spatial question. When the container stops being chosen and starts being inherited, it stops communicating.