Designing for hover, then forgetting hover exists

You design at a desk. Your users are on a couch.

Mobile-first means state-first

Hover isn't a state on touch. Build affordances that don't depend on it. Your menu items, your tooltips, your reveal-on-hover image grids — none of those exist on a phone.

The fix is small but uncompromising: every hover-only interaction needs a pressed-state equivalent. No exceptions.