Pull up your own application on a phone and try to finish it during a ten minute break. Use the resume you have stored in your email, not a laptop file system. If you cannot get through it, your candidates cannot either. For hourly, retail, healthcare support, logistics and hospitality roles, well over half of applications now start on a phone. The share that finish is much lower, and the gap is almost entirely down to form design.
Where mobile applications die
Drop-off is not evenly spread across the form. It clusters at a few predictable points. Knowing where lets you fix the biggest leaks first.
- Account creation. Asking someone to invent a password before they have applied loses a large share on the spot. Illustratively, expect a 30 to 40 percent drop at this step alone.
- Resume upload with no alternative. Many phone users do not have a file handy. Offer a link, a photo of a paper resume, or a short manual entry path.
- Retyping the resume. If the form asks for every past employer with start and end dates after the resume was uploaded, people quit.
- Long free-text answers. A 200 word 'why do you want to work here' on a phone keyboard is a wall.
- Broken layout. Fields that overflow, date pickers that need a mouse, dropdowns with 200 options.
Design for thumbs and interruptions
A mobile application gets interrupted. The bus arrives, the shift starts, a child needs something. Save progress automatically and let candidates come back through a link in a text message, not by logging in. Keep each screen to one or two questions. Use the phone's own input types: a numeric keypad for phone numbers, a native date selector, tap-to-choose instead of typing for shift availability.
Resume parsing changes the math here. When the candidate uploads a resume, or even a photo of one, and the system extracts contact details, employers, dates, education and skills into the record, the form can shrink to a confirmation screen. 'We found these three jobs on your resume. Does this look right?' is a very different experience from twelve empty fields.
Text is the mobile candidate's inbox
Someone who applied from a phone will read a text within minutes and an email within days, if at all. Confirmation, screening questions, interview invitations and reminders all work better over SMS for this group. Ask for consent on the form, and then use it. Two-way texting matters more than one-way notifications, because the follow-up question ('is the 6 am shift the only option?') is where a lot of good candidates decide whether to stay in the process.
- 01Confirm receipt by text within a minute of submission.
- 02Send a scheduling link by text, not a calendar invite they have to open in an app.
- 03Let candidates reply to reschedule or ask a question, and route replies to a shared inbox.
- 04Keep every message short enough to read on a lock screen.
Measure completion, not just volume
Application count is a vanity number if you do not know how many people started and gave up. Track starts and completions by device. If desktop completion is 70 percent and mobile is 35 percent, you have found a large, cheap source of applicants: the ones who already wanted the job and could not get through the form. Apex ATS shows starts, completions and device split per posting, and the picture is usually clear within a week of fixing the form.
Illustrative example: a 14 location restaurant group with a nine screen application was seeing about 30 percent mobile completion. They removed account creation, moved to resume parsing with a confirm screen, and cut knockout questions from seven to three. Mobile completion moved to around 65 percent over the following month. Nothing about their job ads or their pay changed. They simply stopped losing people who had already said yes.
The candidates you most want for frontline roles are often the busiest, applying between shifts on a phone with a cracked screen. Build for that person. If the form works for them, it works for everyone.