UI Design in Airtable
Airtable Development and Consulting Services
UI Design in Airtable
UI work in Airtable today means Interface Designer. Grid views and colour-coded fields still have their place for the people who maintain the base, but everyone else, from the sales team to the executive checking a dashboard on their phone, should be working in an interface built for their job. BaseBrainers designs, builds, and governs those interfaces.
Interface pages built around roles
An interface is a set of pages, each showing exactly the records, fields, and actions one audience needs. We start by listing who touches the base and what they are trying to get done, then design one interface per role: a record review page for account managers, a dashboard for leadership, a form for intake, a kanban for the delivery team. Each page is scoped so users see what matters and nothing that distracts or that they should not edit.
Permissions and audiences
Interfaces have their own sharing and permission model layered over the base. We use it to grant interface-only access to people who never need to see the underlying tables, restrict editing to specific fields per page, and lock down buttons and actions. This is how you give a contractor, a client, or a regional team a safe window into the base without handing them the keys.
Record review, dashboards, and forms
Different jobs need different layouts. Record review pages put one record's details and linked records side by side for processing work. Dashboards combine number, chart, and list elements for at-a-glance status. Forms collect new records with validation and conditional fields. We pick the right layout per page and keep each page focused rather than cramming every element onto one screen.
Portal-style apps for external users
With the right combination of interface pages and permissions, Airtable can act as a lightweight portal: clients viewing project status, vendors updating delivery dates, applicants checking an application. We design these with the external user in mind, with plain-language labels, no internal jargon, and only the fields that matter to them.
Omni-generated interfaces, human-refined
Airtable's Omni can generate an interface from a description, and for a first draft it is worth using. What it produces still needs a designer: the generated pages tend to surface every field, use raw field names, and miss the permission model entirely. We take the Omni draft, cut it to what each role needs, rename and regroup, set permissions, and test it with real users before publishing.
Multi-device design
Interfaces render on desktop, tablet, and the Airtable mobile app. We design for the device each role actually uses: dense dashboards for desktop, simplified record pages and forms for people in the field.
Automations and buttons
Interface buttons can trigger automations, open URLs, and run scripts, which is how an interface moves from "view" to "app". We wire buttons to the workflows your team runs every day, such as approving a request, sending a quote, or advancing a stage, with status changes users can see immediately. Where a task needs more than a button can do, we combine interfaces with custom extensions or workflow automation.
Training and iteration
We do not hand over an interface and disappear. We train each audience on its pages, collect feedback in the first weeks of use, and iterate. Interfaces are cheap to adjust, so we treat the first publish as a starting point rather than the end.
At BaseBrainers, our goal is an Airtable front end that people use without being asked to, because it is faster than the spreadsheet it replaced. If your team is still working in raw grid views, contact us and we will show you what an interface could look like for them.