Applying from a phone

Steps

1. 1 Guest Open the application on a phone 0:01 ▣

   390x844 is the design width, not an edge case — it is where the owner reviews.

2. 2 Guest Every row is one field wide 0:03 ▣

   Five inline `grid-template-columns` used to outrank the media query here, so Instagram and Twitter shared 150px each and the run-of-show slots — the one grid written as auto-fit — were the only ones that behaved.

3. 3 Guest Reach the financial estimates 0:04 ▣

   Headcount min, max and bar minimum were 95px each — three columns forced inline — with a four-line capacity note in one of them. That is the 'not aligned' in the note, exactly.

4. 4 Guest The submit bar is a strip, not a panel 0:06 ▣

   It was 179px — 21% of the screen — and covered 14 elements of the table above it. It keeps the submit button, the error line, and the one read-out that changes as you type; the other two moved up beside their own inputs.

5. 5 Guest Scroll to the bottom — nothing is stranded 0:07 ▣

   `position: fixed` was rejected: it trades an overlap you can scroll past for one you cannot. Sticky is right, and the form reserves the bar's height so nothing ends up behind it.

6. 6 Guest Scroll the form the way a host fills it in 0:08 ▣

   The strip steps aside while the page moves and comes back when it stops, so the name of the field you are scrolling past is never the thing underneath it.

7. 7 Guest Ask to submit with nothing filled in 0:11 ▣

   The bar goes 62px to 110px because plan 244 makes it name every missing field. That is the state the owner was in when he wrote the note both plans answer, so it is the state worth measuring: taller bar, and still no label behind it.

8. 8 Guest The same form on a desktop 0:17 ▣

   Two- and three-column rows, the tier table, a strip-height bar. This was a phone-width regression, not a redesign — desktop must be untouched, and it got shorter rather than different.