What you see is what you get. The thing that my company found to be the most frustrating is when you follow the project's game plan, and when we hit the button, it doesn't work as we expected it to function. Some of the issues associated with the tool were related to some misunderstanding regarding the instructions mentioned in the documentation part of the product. The issues related to the product could be resolved with just a phone call.
They should align the price with the value. We feel that it has limited value, possibly even less than anticipated. This prompts a consideration of whether there is room for improvement in the offered services or if a reevaluation of the pricing structure itself is warranted.
The product's AI feature needs improvement. There could be an option to share the data with others without inviting them to the platform. They should allow us to duplicate the data to share it with others.
Reporting, specifically anything involving exports, could be improved. The recent rollout of interfaces, and visual presentations of the underlying data, was a great step in the right direction to make reporting more executive-friendly. More work needs to be done to make it more user-friendly to get your data out of Airtable in simple and clean ways. It can be overwhelming for teams who may not be familiar with the backend and are faced with numerous formula fields or lookup fields to be able to summarize their data in a way that can be exported. Additionally, there is work to be done for users to be able to design exports of data groups for reporting purposes. The good news is that Airtable is actively working to improve exports. As I mentioned, I’m a big fan of Airtable Automations. That said, there is an opportunity to streamline duplicative automations by adding a trigger that covers both matches and updates. Currently, you need both a matches XYZ conditions trigger for an automation and an updated record trigger for an automation to capture when something is first created and then when it's updated. This means two separate automations to keep the same field/output updated. Airtable releasing a trigger that captured both the creation and future updates would be super handy and cut down the number of automations needed to maintain data accuracy for this example. Another feature I'd like to see is an easier way to self-link within tables. When you link records across tables, the link is automatically created within both records, but self-linking within a table requires manual linking and/or the creation of a complex automation to do it for you. It took several hours to come up with a suitable workaround to capture when a parent record changed in the child record’s linked field. In an ideal world, you would use two different tables, but then you hit the challenge of plotting those two tables on the same calendar, which has its own set of more technical workarounds.
The template library is huge. I have a few suggestions with respect to that. But to complete automation, I think a bit more documentation around that would be really helpful because there are a lot of features in that which common people explore them less. And I don't know how many people are using that, but that has great potential. But product-wise, feature, expansion, it's good for now. If they can give, you know, role-based permissions for viewing the data, that may be more interesting to work with. There are twelve fields and an editor. A salesperson can view a few areas. Whether an ops person can edit a few fields, an admin or a manager will be able to view and edit these fields but not edit the others. So you understand what I mean by user basis. So if there is user-based field-level access, that could be more interesting. I don't know if it's related to any of the new versions already, but that is something that I love trying.
The tool has changed the syncing time between the tables which has affected our multiple systems. I would like the product to add more calls per second to the API. It also needs to improve data storage. The tool starts to have problems after having huge amounts of data.
Airtable was founded on the belief that software shouldn't dictate how you work – you should dictate how it works. Our mission is to democratize software creation by enabling anyone to build the software tools that meet their needs. Creators and creatives around the world use Airtable to do everything from cattle tracking to filmmaking, and they have great things to say.
Our team brings experience from building and scaling products touching millions of people at Google, Facebook, Salesforce,...
What you see is what you get. The thing that my company found to be the most frustrating is when you follow the project's game plan, and when we hit the button, it doesn't work as we expected it to function. Some of the issues associated with the tool were related to some misunderstanding regarding the instructions mentioned in the documentation part of the product. The issues related to the product could be resolved with just a phone call.
They should align the price with the value. We feel that it has limited value, possibly even less than anticipated. This prompts a consideration of whether there is room for improvement in the offered services or if a reevaluation of the pricing structure itself is warranted.
The product's AI feature needs improvement. There could be an option to share the data with others without inviting them to the platform. They should allow us to duplicate the data to share it with others.
Reporting, specifically anything involving exports, could be improved. The recent rollout of interfaces, and visual presentations of the underlying data, was a great step in the right direction to make reporting more executive-friendly. More work needs to be done to make it more user-friendly to get your data out of Airtable in simple and clean ways. It can be overwhelming for teams who may not be familiar with the backend and are faced with numerous formula fields or lookup fields to be able to summarize their data in a way that can be exported. Additionally, there is work to be done for users to be able to design exports of data groups for reporting purposes. The good news is that Airtable is actively working to improve exports. As I mentioned, I’m a big fan of Airtable Automations. That said, there is an opportunity to streamline duplicative automations by adding a trigger that covers both matches and updates. Currently, you need both a matches XYZ conditions trigger for an automation and an updated record trigger for an automation to capture when something is first created and then when it's updated. This means two separate automations to keep the same field/output updated. Airtable releasing a trigger that captured both the creation and future updates would be super handy and cut down the number of automations needed to maintain data accuracy for this example. Another feature I'd like to see is an easier way to self-link within tables. When you link records across tables, the link is automatically created within both records, but self-linking within a table requires manual linking and/or the creation of a complex automation to do it for you. It took several hours to come up with a suitable workaround to capture when a parent record changed in the child record’s linked field. In an ideal world, you would use two different tables, but then you hit the challenge of plotting those two tables on the same calendar, which has its own set of more technical workarounds.
Airtable needs improvement with the loading speed. It takes a lot of time to load.
The product should improve the mobile interface. The user interface should be more intuitive.
The template library is huge. I have a few suggestions with respect to that. But to complete automation, I think a bit more documentation around that would be really helpful because there are a lot of features in that which common people explore them less. And I don't know how many people are using that, but that has great potential. But product-wise, feature, expansion, it's good for now. If they can give, you know, role-based permissions for viewing the data, that may be more interesting to work with. There are twelve fields and an editor. A salesperson can view a few areas. Whether an ops person can edit a few fields, an admin or a manager will be able to view and edit these fields but not edit the others. So you understand what I mean by user basis. So if there is user-based field-level access, that could be more interesting. I don't know if it's related to any of the new versions already, but that is something that I love trying.
The tool has changed the syncing time between the tables which has affected our multiple systems. I would like the product to add more calls per second to the API. It also needs to improve data storage. The tool starts to have problems after having huge amounts of data.