Why Every App Feels the Same Now

There was a moment — sometime between the death of skeuomorphism and the birth of the design system industrial complex — when every product team on earth quietly agreed on what an app looks like. Tab bar on the bottom, five icons, the middle one maybe raised. Cards with 16-point corner radii. A floating action button if the founders are ex-Google, a segmented control if they're ex-Apple.

The official story is that this is good for users. Familiar patterns reduce cognitive load; nobody should relearn navigation to order a burrito. The official story is even true. But it's not the whole story.

Design systems promised consistency and delivered it — then kept going. When the component library decides the spacing, the type scale, the empty states and the button hierarchy, the designer's job collapses into arrangement. The tokens are the taste.

The result is a strange inversion: products differentiate on brand marketing, then converge completely the moment the user signs in. The billboard is bespoke; the app is a template.

The differentiation didn't die — it moved down a level. The products people love now win on details the pattern library can't specify: the weight of a haptic, the timing curve of a sheet, the way an empty state teaches instead of apologises. The grid is table stakes. The details are the design.

Which is, not coincidentally, what this entire issue is about.