I don’t use Airtable, so I don’t have much experience with it, and I don’t know much about it’s limitations. I do know that the API that was provided to Glide from Airtable had some limitations that affected performance. There is a recent update to that API which should provide some improvements, so when Glide can work that into their roadmap, they will make the necessary changes on their end.
With all that said, I find it interesting that people have delays when adding or changing data from Glide’s side…including when a new user profile row is generated. I don’t experience those same kinds of issues when using a google sheet. It has always been my understanding that Glide keeps their own copy of your external data, but periodically syncs the data between glide and the external source (eg. Airtable/Google). As long as all logic is handled within Glide, then there should be little to no concern about how long it takes for data to sync from Glide to Airtable. It should already be there in Glide’s copy, which is the only copy that the app itself communicates with.
If you have special logic or formulas within Airtable, then yes, I expect some delay for those calculated values to sync back to glide, because there is an extra step involved that is handled external to Glide. And let’s consider that glide as a whole could be connected to a million different Airtable, Google Sheet and Excel Databases, so for it to keep everyone’s data synchronized every second becomes a bit unreasonable, so that’s why there may be up to a few minutes delay between syncs.
I’ll also add, that those that use Airtable tend to use features that are highly specific to Airtable only, such as linked records, or attachment fields, which don’t always play well with glide, or they work completely different from standard glide column types, so it possibly makes Airtable more reliant on the sync happening between glide and Airtable. If airtable was treated purely as a data source to store data, and none of those “airtable only” column types and features were used, then I wonder if that would allow for things to work better and be more responsive. I really don’t know, since I have only worked with glide tables and google sheets.
Whenever possible, when I use google sheets for some of my projects, I try to avoid any special formatting, or any special formulas inside the sheet. For me, the google sheet is just raw data storage. Anything important happens within Glide. This allows my project to remain responsive without relying on when and how often data is synced with the google sheet. Glide’s copy of the data is always up to date, so it wouldn’t bother me if it took 30 minutes or more for data to sync between Glide and Google. It’s obviously not that slow, but I think you get my point.
If you are having sync issues with the user profile, then yes, you could technically keep using a glide table as the user profile table, and use a single relation to a contacts table. The only issue is that you would need several Lookup columns for any values you want pull into the user profile table to be accessible in the app through the user profile options. Also, if you need to update anything in the contacts, you would have to do it through the single relation. It’s all possible, but just a bit of extra setup.
Not knowing much about how the integration between glide and airtable works, I can’t say if syncing would become more reliable, but it may help to some degree. Maybe those with more Airtable experience can chime in.