Third pass of the device-walked spacing audit. Measured on the artistant AVD (Pixel 6, 420 dpi = 2.625 px/dp). Method and raw screenshots: docs/design-qa/spacing.
What is wrong
Five screens pin a primary button to the bottom edge. All five leave a different gap under it.
A 45 dp spread. The wizard's 12.2 dp is the one to look at first — the Continue button sits hard against the home-indicator zone. Confirm request's 57.5 dp is partly explained: it carries a caption line under the button, which the others do not.
Design 04 is explicit about the shape of a dock:
<div style="padding:14px 20px 30px; display:flex; align-items:center; gap:12px">
14 top, 20 sides, 30 bottom. Only Request quote comes close.
Relationship to existing issues
Fix direction
One tailroom token, consumed by one component. F-BC-04's direction still holds: make CtaBar a thin wrapper over BottomActionBar, give that component the design's 14 / 20 / 30 padding and its 12 dp gap, and delete the per-caller re-padding. The wizard, the artist profile and Data export should all end up on the same component.
Worth handling the navigation-bar inset once in that component rather than per caller, since that is the most likely source of the drift.
Acceptance
Walk the five screens and measure the gap under each button. One number, and it is 30 dp plus whatever the system's bottom inset adds.
Third pass of the device-walked spacing audit. Measured on the
artistantAVD (Pixel 6, 420 dpi = 2.625 px/dp). Method and raw screenshots: docs/design-qa/spacing.What is wrong
Five screens pin a primary button to the bottom edge. All five leave a different gap under it.
A 45 dp spread. The wizard's 12.2 dp is the one to look at first — the Continue button sits hard against the home-indicator zone. Confirm request's 57.5 dp is partly explained: it carries a caption line under the button, which the others do not.
Design 04 is explicit about the shape of a dock:
14 top, 20 sides, 30 bottom. Only Request quote comes close.
Relationship to existing issues
feature/booking/BookingChrome.ktCtaBarvsdesignsystem/component/BottomActionBar.kt. That is the right root cause; this issue supplies the numbers and shows it is five bars, not two.Fix direction
One tailroom token, consumed by one component. F-BC-04's direction still holds: make
CtaBara thin wrapper overBottomActionBar, give that component the design's14 / 20 / 30padding and its 12 dp gap, and delete the per-caller re-padding. The wizard, the artist profile and Data export should all end up on the same component.Worth handling the navigation-bar inset once in that component rather than per caller, since that is the most likely source of the drift.
Acceptance
Walk the five screens and measure the gap under each button. One number, and it is 30 dp plus whatever the system's bottom inset adds.