Roughly 80% of bookings on Zedule come from a mobile device. If your booking page works great on desktop but awkwardly on phone, you’re losing four out of five customers to friction.
This post covers what good mobile design looks like for a booking page specifically.
The mobile-first checklist
Single-column layout
No side-by-side service grids. One service per row, full-width on phone. Customer scrolls vertically, taps the service, moves to the next step.
16px minimum text size
Anything smaller and customers can’t read it without zooming. iOS Safari auto-zooms when input fields are below 16px font-size — use 16px to prevent that.
Tap targets at least 44×44 pixels
Apple’s HIG specifies 44×44 minimum for touch targets. Smaller and customers mis-tap; mis-taps cost ~3 seconds each and break the flow.
Calendar grid that fits in 360px width
The smallest common phone screen is 360px wide. The calendar grid in your booking flow has to fit, with usable date cells and clear “available vs unavailable” indicators.
Time-slot list, not grid
A vertical list of available times reads faster on phone than a grid. “9:00 AM, 9:30 AM, 10:00 AM…” in a scrollable list works.
Auto-advance on selection
Customer taps a service → advances to staff/time selection automatically. No “next” button required.
Sticky button at the bottom for primary action
Once the customer fills in their details, the “Confirm booking” button should be visible without scrolling. Make it sticky-bottom on mobile.
Real keyboard types for inputs
Email fields use email keyboard (with @ button); phone fields use
phone keyboard; date fields use the OS date picker. HTML input
types handle this; verify your platform sets them.
One CTA per screen
Multi-CTA screens confuse mobile customers. “Book this slot” + “Choose a different time” on the same screen halves the conversion rate.
Test on the slowest network you can find
Cellular 3G simulates real-world conditions for many customers. Chrome devtools has a “Slow 3G” throttle. If the booking page takes more than 3 seconds to load on Slow 3G, optimize.
Common mobile failures
Things we see that destroy mobile conversion:
- Service descriptions that take 5 paragraphs. Mobile users skim; they don’t read.
- Pop-ups asking for cookie consent before showing the booking flow. Cookie banners on phone are larger relative to the screen; they hide the booking entirely.
- “Best viewed on desktop” warnings. Modern customers will close the tab.
- Multi-step modals stacked on top of each other. Mobile UX can’t handle modal-on-modal; the back button breaks state.
- Auto-playing video on the booking page. Eats bandwidth; customers on cellular hate it.
What Zedule does
The Zedule booking page is mobile-first by default:
- Single-column layout on phone.
- 16px+ text sizes.
- Tap targets 44px+.
- HTML5 input types for email/phone/date.
- Sticky-bottom primary action.
You don’t need to configure these — they ship with the platform.
Test it
Open your booking page on a phone over cellular. Walk through a real booking. Time it. Anything over 60 seconds is worth fixing.