What actually happened first
Every design trend gets described the same way after the fact: a shift in taste, a generational aesthetic, a reaction against what came before. Most of the time, something more boring happened first: a constraint changed, and the aesthetic was just what was left standing once it did.
Flat design
Flat design didn't arrive because skeuomorphism went out of style on its own. It arrived at the exact moment screens multiplied into a dozen different pixel densities and interfaces had to render cleanly, and load quickly, across all of them at once. A beveled button with a drop shadow and a leather texture is expensive: more assets, more file weight, more ways to look wrong on a screen it wasn't specifically drawn for. Flat color and clean shapes scale across resolutions almost for free. The taste followed the constraint. Explaining it as an aesthetic awakening skips the part where it was also just cheaper.
Mobile-first minimalism
The decade of minimalism that came after wasn't purely a reaction to visual clutter either. Small screens have less room for it, and slow connections make every extra asset a cost the user pays in load time. Restraint wasn't a philosophy teams arrived at independently. It was what worked on the hardware and networks everyone actually had. The philosophy got written afterward, the way it usually does, once enough people had already landed in the same place for a completely practical reason.
Why the order matters
Get the causality backwards and you chase the aesthetic without checking whether the constraint that produced it applies to you at all. A pattern that exists because it once solved a rendering problem on old hardware isn't automatically the right answer for a product with none of those constraints today. The question worth asking about any trend isn't whether it looks current. It's what problem it was actually solving before anyone called it a trend, and whether that's the problem you actually have.
Seen up close, most trends are just a constraint that got resolved. Seen from far enough away, a resolved constraint looks exactly like taste.
