No More Private Apps for multiple Users?

[Krivo]

@nico I do understand your frustration - something that was previously free is now a paid feature.

I made a longer longer post here about the main issue (from my perspective) - that is transparency and predictability: What is going to be a paid feature - and the problem of not being able to predict that before the change occurs. I hope you have a bit of time to adjust to the change.

Sheet Edits Quota—1000 per month?

@david This post might be buried way down of a long thread but I thought I will contribute anyway. Introduction of a 1000 edits per month limit on free tier - what does that mean to us as developers? I have a few perspectives on that: Transparency Predictability Vision of free tier Edits in the builder also counts Navigating by use of choice components Form vs one-bit-change (rating, favorites, text entry component) Workaround Grandfathering Predictability, transpare…

Please also look at Davids response.

Sheet Edits Quota—1000 per month?

This is not official policy, but we view Free apps as being used for personal use, or trying Glide. If you’ve built an app that is somehow critical to your business, you should really upgrade it to a paid plan. As Glide becomes more popular, we will be forced to reconsider limits on the free tier to control our costs, and we’ll grandfather when it’s feasible. Grandfathering often creates a lot of complexity and support burden that slows down new features. Most limits we’ve introduced—map pins,…

so free apps are for personal use or for trying Glide. Keep that in mind at all times when you are going to consider (trying to predict) whether a feature will be a paid feature in the future.

I would expect to see more of such changes for free tier plan in the future - but it is difficult to plan when you don’t know what is going to hit you - and it could potentially hit you with short notice.