I would contact AppSheet directly. I wonder if there's just a difference in what "general availability" means and maybe AppSheet/Google needs to be more careful about qualifying the intention.
I understand that in the industry "general availability" usually meant a fully baked feature made available in a non-Beta form. But that has been historically done because there is a targeted rollout to a smaller set of dedicated Beta testers to iron out issues before a full rollout. And this is normally because promotion of code happens in a well-defined broad cycle.
Invariably, as soon as a full rollout occured, a slew of new issues would be submitted because users used the features in a way no one thought of and there were problems anyway.
It's a different world today where issues can be fixed and rolled-out immediately, or at least same day, Many platforms, not just AppSheet, are making new features available through opt-ins so ANYONE can test them and give feedback. So, I think "general availability" means a slightly different thing today than it has over the past couple of decades.
For what it's worth, in AppSheet I struggle with understanding when a new feature crosses that line from a "please test and provide feedback" feature into a "now ready for full use" feature. There are many features that have been around for years, still labeled as Beta.
LinkedIn
Twitter
