The 3 mobile bugs that took longer to fix than the entire desktop version

Building the API request tester for Quietbench, the desktop version came together fast — headers, body, response view, done. Mobile is where I actually lost time.

1. The CORS warning banner. On desktop, a dismissible banner explaining a blocked request has plenty of room. On a narrow viewport, it either pushed the actual response out of view or got truncated into something unreadable.
   Fix was less about styling and more about rethinking the banner as collapsible-by-default on small screens, expandable on tap — not just shrinking the same layout down.

2. The URL input row. Method dropdown + URL field + Send button in one row is fine until the viewport gets narrow enough that the URL field shrinks to a few visible characters. Testing a real API URL when you can see 8 characters of it is useless.
   Ended up stacking the method selector above the URL field on small screens instead of forcing everything into one row no matter what.

3. The Send button itself. Small thing, but on mobile it kept ending up either off-screen when the keyboard was open, or too close to other tap targets to hit reliably.
   Pinning it above the keyboard and giving it more breathing room from neighboring elements fixed more "why isn't this working" confusion than any logic bug did.

None of these are hard problems individually. What actually cost time was assuming "responsive" meant "the same layout, smaller" — it doesn't.
Each of these needed an actual layout decision for narrow screens, not just a breakpoint that shrinks things proportionally.

Live at quietbench.dev/api-tester if you want to try it on your phone — genuinely curious if anything's still awkward.