Mobile-first polishing
public UX

question without friction

Mobile forms and keyboards

Textarea, email, login, recovery, and checkout forms should work with the mobile keyboard, not against it.

Forms do not make the user fight the screen, keyboard, and tiny buttons.

Mobile rule: Every field has a label, clear placeholder, large submit, and clear error.

Get answer

Main mobile CTA door for a question.

Recover

Mobile access recovery check.

Quick wins

  • Increase textarea and submit on question pages.
  • Add inputMode for email/number where needed.
  • Show errors near the field, not only at the top.

Trust microcopy

  • Do not enter medical, legal, or financial instructions as an oracle request.
  • Phrase the question as a next step, not a verdict on the future.

Question field

A user writes a question while uncertain, so the form must be friendly.

  • Placeholder gives a safe example question.
  • Submit does not disappear behind the keyboard.

Recovery

A lost link on mobile should recover without a support thread.

  • Email field uses email keyboard.
  • Success state says what to do next.

Red flags

  • User cannot see submit after keyboard opens.
  • Error sounds like it blames the user.

Related doors