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

What is the proposed idea/solution? It would be great to be able to toggle between different views  whilst in an expanded record.  How does is solve the user problems? Being able to update various relevant fields whilst in the same record without having to make 100s of fields visible can be a huge time saver. How was this validated? ... Who is the target audience? ... ... View more

Creating a new interface isn’t intuitive - you have to click on the interfaces button from within the base instead of using the standard + button in the interface area. It would be much nicer to have a more intuitive and easy way to create a new interface. Hope my drawings in my screenshots are up to snuff, haha. I would also like to request to be able to duplicate Interfaces - aka interface groups. It is nice to be able to duplicate the individual interfaces within an Interface Group, but being able to duplicate the whole thing for users is essential. Thank you ... View more

It would be great if I could dynamically use a colour from a field in my base for the static elements in Page Designer. Similar to how the static text element can use {Field Names} to intersperse content from a base with static text, it would be really helpful if for background fills and border colors. I think there are lots of ways to better support color, for example Airtable covers all of the field types that Webflow supports (and more, i know) with the exception of color, which I use a lot, and would be very helpful to have here too. ... View more

It would be incredibly nice to have a calendar feed in interfaces that will allow you to incorperate different feeds from multiple tables. This is super important when trying to do any kind of schedule management with AT - like social media posting. I want to have my scheduling and be able to break down the data / performance on the back end. Can’t do that with Google Calendar. I know there is an extension that does this, but I’m already paying for AT pro. I shouldn’t need to pay for someone else’s extension to have a basic feature like this. Anything scheduling / time related feels woefully neglected or behind some sort of paywall. Thanks for your time and attention, AT is always getting better. It’s why I’ve stuck around. Looking forward to more improvements! ... View more

I really love the whole page designer concept, but I wish I was able to link to a specific record. The current implementation seems broken: when adding the record to the page designer URL, it expands the linked record instead of just changing the record shown in Page Designer itself. Example: Airtable - Binaural Database Catalog This URL should load the Portal view, but instead it expands it, while the wrong/default record (in this case, Half-Life) is shown on the Page Designer view behind it. ... View more

It would be great to have a field appended to the URL - I’m sure there would be a few uses for it but I’m thinking specifically time tracking. eg. For a project called ‘Browns Engineering’ url would be airtable.com/appsVTW…=recbrownsengineering Hope that makes sense ... View more

When you use “Link to other record fields” in Interfaces you can show several items. However if you use links or buttons, they are not useable in the interface. My workaround for now is to also fetch a link from the same table and then show that link as a separate field in the Interface. But as you can see it is not pretty. If you could only just click the button directly… ... View more

This is my first post…sorry. I’m using an interface to display relevant information from a table. The user can add records to the table using editable field elements. However the list of records that appears is very large and it’s difficult to easily find what you want. In this example the record is information relating to a machine, the machine has subassemblies. The user needs to log some information regarding a specific subassembly of a machine but the field element lists all subassemblies of all machines. An improvement would be to only list the subassemblies for the specific machine the information is being logged to. The field element could have a filter that can be chosen based on a record from another field. This way when the user presses on the field element they are presented only with records that match a filter that was determined by another field that is already set. Hope that makes sense and somebody can advise? Thanks ... View more