Symptom

The FTUE PIN entry dialog showed two dense instruction paragraphs (~10 lines total) before the PIN field. The proportion of instruction text to input was roughly 5:1 in vertical height, and the second paragraph (security rationale about encryption, clock-sync, PIN rotation) competed visually with the primary CTA — a user’s eye had to work through a wall of text before reaching the action they needed to take.

Root cause

Both an action prompt (“how to use”) and a security rationale (“how it works”) were rendered as plain Text composables with no visual hierarchy or collapse affordance. The security rationale is relevant context but is not needed to complete the task.

Fix

• Replaced the two Text paragraphs with a PinEntryExplainerRow composable following the ConnectExplainerRow pattern already established in ConnectNodesWizard.kt.
• Summary line: “Enter the 4-digit PIN from your server installation to connect. Tap the avatar to skip.” — rendered inline, always visible.
• Security rationale collapsed behind a “Learn more” / “Less” toggle (AnimatedVisibility), primary-colored underlined link, matching the connect-wizard pattern exactly.
• Fixed the pre-existing typo “Pins a stored securely” → “PINs are stored securely” in the detail text.

Prevention

• When a dialog has both an action prompt and reference/rationale copy, the rationale belongs behind a collapsible — not as a second paragraph at the same visual weight. The ConnectExplainerRow shape (summary + Learn more toggle + AnimatedVisibility detail) is the established krill pattern; reuse it rather than adding parallel prose.
• UX audits now catch this class of issue via the “FTUE empty-states” audit theme; the nightly audit filed this as Finding 6.