Hello, I'd like to suggest that you freeze the header row in the Interface list element! I prefer to use the list over the grid because it's more visually appealing, but when you're scrolling through a long list it would be helpful to still see the header row like you can with the grid element. ... View more

What is the proposed idea/solution? Can the interface have a right-side "sticky" block that allows you to put additional editable fields in place. How does is solve the user problems? This would allow us to put in a few different reference items as we work down a page but most of all would be a great place to have record comments  How was this validated? We have an issue with having to scroll back to a specific block area to take notes or make comments and ruins the flow of the interface Who is the target audience? Any interface user who has to reference a large page and use information from different areas while making notes. ... View more

What is the proposed idea/solution? Have a privacy field that requires certain permissions or password protected for information stored such as social security numbers.  Who is the target audience? - services industry where private information from the clients is collected.    ... View more

What is the proposed idea/solution? Other elements, such as Calendar, Timeline, Gallery and Kanban to act as Record Pickers, allowing for records to be clicked within the element, and their subsequent fields to be looked-up and displayed within the interface. Think of the way a Record Picker element behaves, and now apply that behaviour to the other Elements. When you think about a Calendar, it's showing records just like the record picker is showing records, just in a different visual format. Further to these mentioned elements, this same Record Pick behaviour should also be added to Linked Fields and Lookup Fields. How does is solve the user problems? The Record Picker is a very powerful element - but I feel it shouldn't have a monopoly over its specific functionality, and that the other elements such as Calendar etc would all benefit vastly from having this same ability. Who is the target audience? Anyone building and using Interfaces, where multiple tables are in play, typically at 3 levels deep - for example, Project -> (Task Dictionary) -> Task. ... View more

What is the proposed idea/solution? Our interfaces are growing ever more complex, longer and more difficult to handle. Two things that would make life much easier: Being able to create sections (visual containers) that can be collappsed and unfolded. Conditional visibility of these sections and individual fields (like in forms) How does is solve the user problems? This would help us to only show the fields and sections needed for specific cases or situations based on conditions that we can define, similar to conditional fields in forms. ... View more

What is the proposed idea/solution? When viewing a record's comments in a base, any comments made against an attachment also appear, as in the attached image. When viewing a record's comments in an interface, comments made against an attachment do not appear, as in the other attached image. I would like the record comments in the interface to behave like it does in the base. How does is solve the user problems? Though it is very convenient to be able to comment directly against attachments, it is inconvenient for the person reading the record to view all of these different attachments to find comments they may or may not care about. The record's comment should be the central place to find comments. This is how it currently works when viewing comments from the base and I would like it to work the same way (at least as a configurable option) for interfaces for the same reasons. Asking Interface users to check multiple places for comments isn't friendly. ... View more

I'd like to suggest that you add the ability to wrap text in the Interface List element, the same way it gets wrapped in the Grid element. I want to use the List element because it's more visually appealing than the Grid, but it's more challenging to see all the information at once, especially for fields where I'm listing multiple linked records.  ... View more

Mobile-friendly interface: To make the AIRTABLE interface more mobile-friendly, the following improvements could be made: Design the interface to be responsive to different screen sizes and resolutions, so that it can be used on any device without losing functionality or readability. Simplify the interface by removing unnecessary elements and prioritizing the most important ones, to make it easier to use on a small screen. Use larger fonts and clear, high-contrast colors to ensure that all text and visual elements are easy to read and distinguish. ... View more

Passing multiple records into an automation by clicking on one button would enable a great deal of flexibility: Dynamically linking multiple records, especially in junction tables Passing information into one record that is taken from another record Conditional execution of automation actions based on multiple inputs Updating multiple records at the same time (eg. please edit both Record 1 and Record 5)   ... View more