Hi everyone, I'm AP, a product manager on Core Product.
As of today, full-page custom interfaces are available to all in the Airtable iOS and Android apps. If an interface page is a full-page custom interface, the people who use it can open it on their phone, with the same live data and the same permissions they have on desktop.
It works no matter how you built it:
- Omni: describe what you want and Omni builds it
- Airtable MCP server: build it from your favorite AI tool
- Blocks SDK: write the code yourself and release it to your base
Why this matters
Custom interfaces are for the things standard interface elements can't do: maps, org charts, drag-and-drop boards, focused approval queues, and dashboards built around one team's questions. Previously, they only worked on desktop. Now, your team can use them wherever they are.
What you can build for mobile
- Field inspections: a checklist crews can tap through on site. Every answer writes straight back to the record.
- Event check-in: search for an attendee at the door and check them in with one tap.
- Approvals between meetings: a review queue where managers open a request, see the context, and approve it or send it back from their phone.
- Territory maps: reps see their accounts plotted on a map before the next visit.
- Team directory and org chart: find out who's who and who reports to whom, even away from your desk.
- Inventory counts: big +/– buttons for counting stock in the stockroom, synced live with the base.
- Pocket KPI dashboards: the three numbers your team checks every morning, sized for a phone.
Omni makes your existing pages mobile friendly
Already have full-page custom interfaces? Open Omni and ask it to make one work on mobile. This works whether you built the page with Omni, the MCP server, or the Blocks SDK. Omni is really good at this. It reworks the layout to fit a phone screen, stacks columns that sit side by side on desktop, and makes buttons big enough to tap. Try telling Omni to "Make this page mobile responsive. Keep the desktop layout the same."
Omni builds every new custom interface for mobile and accessibility by default
We've trained Omni to build every new custom interface to work on phones and desktops from the start, and to be accessible. Unless you ask for something else, Omni does it's best to:
- Adapt the layout from a phone screen to a wide desktop window, with no sideways scrolling
- Make buttons and controls easy to tap (touch targets of at least 44px) and never hides an action behind hover
- Use semantic HTML, labels every input and icon button, shows a clear keyboard focus state, and keeps text contrast at 4.5:1 or higher in light and dark mode
- Never rely on color alone to show meaning, and respects reduced motion settings
- Handle loading, empty, and error states, including missing fields and missing permissions
You don't need a special prompt for any of this. Describe what you want to build and Omni takes care of the rest. Building with the SDK or MCP instead? The same tips apply: design for a narrow screen, use large tap targets, and don't rely on hover.
Get started
- Update the Airtable app on iOS or Android. You'll need Airtable for iOS 11.0 or later, or Airtable for Android 6.46.0 or later.
- Open an interface with a full page custom interface and try it out.
- Have an older page? Ask Omni to make it mobile friendly.
Good to know: this rollout covers full-page custom interfaces. Custom elements placed on a dashboard next to other elements still show a "not supported" placeholder on mobile for now.
We'd love to see what you build. Reply with a screenshot of your favorite mobile custom interface, or tell us what you'd like to build next. 🚀
