Keep them coming! I’m sure others in the community have similar questions
-
Teams with existing paid subscriptions will not be migrated to the new team plans initially. We will provide plenty of time for these users to adjust to the new plans
Teams with published Free Apps & Pages will be migrated to the new team plans sooner than teams with paid subscriptions, but there will also be a lead time. However, these teams will not be able to upgrade individual Apps and Pages once the new team plans are launched
Teams with no published Free projects will be migrated to the new Free team plan immediately
-
Interesting idea! I will take this back to the team
-
Our primary goal with the new team plans was to allow our customers to build more Apps & Pages:
-
First, we wanted to remove the friction of having to decide whether to upgrade each individual App or Page
-
Second, we wanted customers to not have to decide between Pro and Private Pro or Apps and Pages when they are getting started with Glide. With the new team plans, customers have the option to try Public or Private sign-in for Apps and Pages even on the Free plan
-
Third, we wanted to introduce plans that were not one-size-fits-all. On our current plans, a Pro App with a ton of usage costs the same as a Pro App with very little usage. This meant some customers were getting great deals while others were disincentivized from upgrading Apps and Pages that might not get a ton of use
Now going back to your question about our revenue and costs, the introduction of Updates is a core piece of creating plans that are not one-size-fits-all. A benefit of tracking Updates is that it better aligns the value customers gets out of Glide (i.e., App or Page usage) with our costs of hosting, maintaining, and distributing their projects
-