To be clear, your remarks are 100% accurate. Besides, Is anything in tech really 100% certain?
I referenced a total hack - just typing that message made me puke in my mouth a little.
This is precisely why Airtable needs to embrace the idea that no single company – no single team – knows with any certainty exactly the features they should build. As such, they should create an environment that makes it possible to create new features.
This assertion is simple logic that’s based on the same philosophy that makes it possible for Airtable users to create tables with their own fields, their own field names, and data type choices. Could Airtable anticipate every user’s table structure for every use case? Of course not and no more than they could predict what users will do with API access to schemas.
With schema support in the API, including the ability to build bases, tables, and Blocks, the horizon of possibilities expands and most importantly - the human hours devoted to Airtable’s future becomes exponential.