Also, some context to keep in mind here.
Airtable API is extremely slow, and has gotten even worse as of late (evidence here: Airtable & Softr load times extremely slow/Timing out - Clients complaining - #12 by Ben)
And this updated datasource method will be a big help to improve performance, among many other benefits.
So our hope is that once we implement some of the feedback we’ve received here, and other, that you all will see an big improvement to using Airtable as a datasource, even with its limitations as a non-performant API.
Just hang in there with us, share what you’re experiencing, and we’ll make it great again. Appreciate all of your help! 