Practice — Responsive and Mobile Design (9 questions)

Your team inherited a marketing site built as three fixed, pixel- exact layouts — one targeted at 375px, one at 768px, one at 1440px — switched between at those exact widths with no adjustment in between. Users on an iPad Mini (viewport ~810px, technically between the 768px and 1440px targets) report that the layout "looks broken," with a two-column grid leaving a large awkward gap on the right and text that appears too small relative to the available space.

1. Using the responsive vs. adaptive distinction, explain precisely why this specific bug happens on an 810px viewport but not on a 375px or 1440px device.
2. What would change, mechanically, if this layout were rebuilt as responsive rather than adaptive?
3. Is adaptive design ever still the right choice? Give one legitimate use case.

A toolbar icon is drawn at a visually reasonable 20×20px with no padding around it.

Per the platform guidelines this subject cites, what are the actual minimum tappable-area sizes on iOS and Android/Material?

A layout's margin grows from 16px to 24px as the viewport widens.

Per this subject's definition, does that change count as a breakpoint?

A candidate says "I design mobile-first" and describes it as a fluid layout that reflows at any viewport width.

Per this subject's precise definitions, is that an accurate description of mobile-first?

A list row supports swipe-to-delete as the only way to remove an item, with no visible delete icon anywhere on the row.

Per this subject's gesture-discoverability guidance, what's the core problem with shipping it this way?