What is the proposed idea/solution? My suggestion is that you make all desktop data views and interfaces phone fields function just like the mobile app so that if you click on it you have the option to choose Call or Text (tel/sms). Workaround is to at least make this work with the Button field, right now the tel: or sms: links do not work with the button in the data views or interfaces, they are just kind greyed out and don't work.  How does is solve the user problems? Most business run on computers not mobile phones. The option to just click a phone # and then choose call or text is an invaluable time saving option. Why do you have a phone number field that does not act like a phone number on a desktop from a data view or interface when it works like this in the airtable mobile app?! Is not one of the most common uses of airtable include CRM /customer data? How can I have a customer contact crm type database/interface that does not have native clickable phone numbers on a desktop PC when the mobile app has it built in? All webpages do this now, all CRMs do this now.  How was this validated? There isn't even a good work around for this!  adding a button with a URL tel: type link does not even work. Who is the target audience? Everyone who uses artable to manage cutomers... ... View more

Personally, I like the default color options (despite the limited number) that are provided for the base/interface appearance color. That said, members on my team really wish we could match the exact color of our base with the primary company brand color. I feel like it wouldn't be too hard to have an 'advance' section under appearance that allowed us to input a HEX number. ... View more

What is the proposed idea/solution? Give the user a way to switch the font used to render numeric data. This would allow me to switch to a font that has fixed width numerics so numbers have identical sizes. How does is solve the user problems? In pivot tables, make 100.000 and 111.111 look equally big. Currently the first will look like a huge number. The second will look tiny in comparison. How was this validated? Look at any table with numbers. See that 1 is not treated the same as 8 (width-wise) Who is the target audience? People who like to have a quick-look at a large quantity of numbers and not have to translate the things they see internally. ps. there is no label for User Interface. ... View more

I created an interface that pulls from one table in my Base. With some of the demos I've seen on how interfaces can be used, I thought this would be a great way to display non-sensitive data via a public share link. Other tables in this base, however, do contain PII and cannot be shared with the public. So, after creating a lovely interface that seemed it would do exactly what was desired, I tried to share and found that I can only share with individuals who are signed in and have access to the base. Chat support let me know that the Base's permissions determine the interface's share permissions. In my specific use case, I have a base that shows all the volunteers that work with my organization, including a table for their basic contact info, a table for their engagements with us, a table for touchpoints we have with them, and another table that holds all the categories of expertise for our volunteers. The interface is based on this last table, and is a record review that tallies the number of available volunteers with each area of expertise. The data on that table is fine to share publicly, but not data from the others. Ideally, when building an interface you could choose how to share the individual interface without the whole base being set to public. Anyone with ideas of workarounds, I'm all ears! ... View more

This would make everything a lot easier. What i have in mind is that when creating an automation based on an interface, you would be able to access all data displayed in the interface, not just the record the Automation is connected to. ... View more

I would like to propose an enhancement to Interface Builder regarding new record creation.   I created an automation that will auto-populate three fields in the Data View when a new record is created on my "Entries" table.  The automation works as expected in Data View, however, when I create a new "Entry" record in the Interface Builder, the fields that are set to auto-populate in Data View do not auto-populate in Interface Builder.   I know that creating the record in Interface Builder, closing the record and then opening that same record in Interface Builder will reveal that those fields have been auto-populated on the backend, however, the User Experience (UX) is (I think) greatly impacted by potentially causing confusion at best and unnecessary / time-consuming rework at worst. This enhancement would also send a positive signal to those who have invested signifiant amounts of time crafting their automation workflows.  Having a more consistent experience across the Airtable platform is a win for the platform and the users. ... View more

Option to Limit the Access to Interfaces. I want to build an App for my co-workers that are not that techie. So i want to keep them from seeing the Base and only allow them to see certain areas of an Interface. Would be helpful for customers too. Sadly there is no way, as far as i can see ... View more

I'm a HUGE fan of interface builder and it's becoming more of a replacement for my day-to-day interactions with my Airtable bases.  One feature that I would like to see added to the Button options is "Open Interface Form".  Below is a screenshot of the current list of options that I would like to see extended.   Because Interface forms offer a much tighter integration with Interface builder (not to mention increased usability and elevated design) it would be nice to have the option to create new records via Interface Builder forms without having to add a record picker and then selecting the option to create new item (as seen in image below) If this feature is already in the pipeline, thank you! If not, I hope to garner enough support from the community to get this feature on the roadmap.   Thanks for lending me your ear and I welcome any feedback / questions. Justin       ... View more

Currently, Calendar interface users can collapse weekends by switching a setting in the timescale: My suggestion is to have this setting available to creators, enabling them to change the default interface setting: As you can see, currently this is not possible. ... View more