Filling out a form on a phone shouldn't be a chore.

Mobile form design is the set of adjustments that let a form be filled in on a phone quickly, without errors and without frustration. The number of quote requests, appointments or applications your site receives is often affected by the form itself. A visitor opens the form, gets stuck on a few fields and gives up; this loss usually doesn't show up in any report. In this post we go through the rules of a form that is easy to fill in on a phone, one by one.

First, cut the number of fields

The most effective way to improve a mobile form is to remove fields, not add them. For every field, ask: "What happens if we don't collect this now?"

• For a quote request, name, phone or email and a short description of the need are usually enough for a first contact. Details such as the company's registered name, tax number and address can be collected during the conversation.
• Making at least one of "phone" and "email" required is usually enough; requiring both adds needless friction.
• Fields like "How did you hear about us?" are useful but shouldn't be required.

Asking for fewer fields is also in line with the data minimization principle in KVKK (Türkiye's Personal Data Protection Law), which means collecting only as much data as the purpose requires.

Open the right keyboard

The biggest time-waster on a phone is fighting the wrong keyboard. Defining the right keyboard type for each field is a small detail with a big impact:

In addition, turn off auto-capitalization and autocorrect for fields such as email and codes; the phone "correcting" an email address is a common problem.

Allow autofill

Phones remember name, phone, email and address details and can fill them in with a single tap. For this to work, the fields need to be labeled correctly (technically, the autocomplete attribute). On a correctly labeled form, users get through most fields without typing.

Likewise, if the verification code field (the one-time password sent by SMS) is marked correctly, the phone suggests the code above the keyboard, and the user doesn't have to go to their messages and copy it.

One column, large tap targets

• On mobile, stack fields one under another rather than side by side. Let the eye follow a single line.
• Put the label above the field. A hint shown only as faded text inside the field disappears once the user starts typing, and they forget what was asked.
• Make buttons and checkboxes big enough to tap comfortably with a finger; small checkboxes are the elements most often mis-tapped on mobile.
• Write the submit button in clear, action-focused words: "Request a quote" or "Book an appointment" instead of "Submit."

Split long forms into steps

For long forms such as job applications, service requests or detailed quote forms, splitting them into a few steps works better than dumping every field onto one page.

• Keep the number of steps low; three or four steps are enough for most forms.
• Show which step the user is on and how many are left.
• Put the easiest questions first; once users have started, they are less likely to quit.
• Information already entered shouldn't be lost when the user goes back.
• If possible, save a half-finished form on the device, so a user who gets a phone call doesn't have to start over.

Write error messages like a human

When a user fills a field incorrectly:

• Show the warning when they leave the field, not when they press submit.
• Put the message directly under the field, not at the top of the page.
• Tell them what to do: instead of "Invalid entry," say "Phone number should be 10 digits, without the leading 0."
• Don't reject users who type a phone number with spaces, dashes or parentheses; let the system clean that up itself.

Mobile form checklist

• Is every field really necessary?
• Do phone, email and number fields open the right keyboard?
• Does autofill work?
• Are labels above the fields and always visible?
• Are tap targets large enough?
• Has the long form been split into steps?
• Are error messages plain and helpful?
• After submission, is there a clear thank-you and a note on "what happens next"?
• Has it been tested on a real phone, filled in with one hand?

What happens after the form?

A well-designed form is useless if it produces a request that gets lost after submission. Getting form data to the right person quickly and following it up is a separate topic; we cover it in our post on web form and CRM integration. The form also needs protection against spam, bots and malicious input; that topic is in our post on web form security.

How we do it at Globya

In corporate website and app projects, we design forms for the phone first and build the desktop layout afterward. We test every form on real devices, filling it in with one hand, and plan from the start where incoming requests will land. Forms include the privacy notice and required consents in full; there is no extra charge for KVKK requirements.

Frequently asked questions