🆕 All-New Team Plans Coming Thursday, April 21st

General
114

Good questions!

  1. I would not use the ratio of Public Users to Updates as a proxy for how valuable each plan is. If you look at our FAQs, we recommend using Rows per Project and Users as a rule of thumb to determine which plan best suits a customer’s use case

    A minority of users will be at 5,000 Public Users on Pro, which is why a simple ratio of Public Users to Updates is not a helpful heuristic

  2. I would also not look at Rows per Project and compare with Updates because much of the data connected to a Glide project is not added by the project’s App or Page users

    For example, imagine you have an App to manage inventory. Let’s say you add 5,000 rows of data for all your various SKUs to a Google Sheet. You then connect the sheet to Glide. None of these rows count as an Add because Adds are incurred when App or Page users add rows to your data source. When an employee interacts with the App to manage inventory, that is when an App user might then Add, Edit, or Delete rows

    Note: Currently, adding, editing, and deleting rows in the Builder count as Updates, but we are planning to not count these soon

  3. We have done an analysis of our customers’ usage patterns to determine these Updates quotas. We will continue to monitor how our customers’ usage evolves to see if any changes need to be made

4 Likes