šŸ†• All-New Team Plans to Be Announced Next Week

General
102

Yesterday I thought of paying too muchā€¦but revealing something yesterday and today looks cool.it may be great after knowing everything.Great work.

103

Keep them coming! Iā€™m sure others in the community have similar questions

  1. 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

  2. Interesting idea! I will take this back to the team

  3. 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

3 Likes
104

Thank you for taking the time to respond to all my questions. I am more excited about this change than when it was first announced. There really seems to be something on the table for everyone. You guys have really exercised deep thought into this and it is much appreciated :pray:

3 Likes
105

I have a question that may not be answered in the public announcement.

I currently have several ā€œteamsā€. One has my Pro app in it (thatā€™s the only thing in it), another has free apps Iā€™ve developed for personal use, another has templates that Iā€™ve copied from the template market or from other places that Iā€™ve been modifying to test different scenarios, and the last one I have apps which I have developed for the template marketplace (only one has been ā€˜releasedā€™).

They currently have a ā€œbillingā€ section. Only one has a credit card attached (the team with the pro app). Will upgrading my team with the personal free apps have any affect on the team with my pro app?

1 Like
106

Going back to the migration paths listed here, each team will be placed on its own path depending on the Apps and Pages inside of it: šŸ†• All-New Team Plans to Be Announced Next Week - #103

Let me check internally about what would happen to Apps or Pages that are templates. Are these Free Apps and Pages?

107

Can you move apps from one team to another with (or before) the new system? The reason I made teams in the past is another than I maybe would do now. I would like to combine a few teams (or a few apps in different teams) into one team.

1 Like
108

Currently, only Legacy ā€œMy Appsā€ projects can be transferred between teams. Projects on teams today cannot be transferred, weā€™ll similarly not be supporting transfers on the new team plans

1 Like
109

So if you build apps for other people too, you can only build them in a team with them? Not build, approve, pay, transfer?

110

One of the things I love about the new plans is that you can mix the use of apps and pages. Apps for on the road, Pages for on the desktop.

7 Likes
111

I only have one pro app, and it is in a team by itself right now (along with several apps that were copied from it as ā€œbackupsā€.)

112

Currently, I can transfer from team to team because I am the owner/admin of each team. I cannot transfer an app from a team if I am not the owner of that team. Please donā€™t drop that organizational capability. I cannot be the only one who copies from an app to start another app, and if that app is on a different team that I am the owner of, I should be able to copy it over.

1 Like
113

Yes, I have been using teams like folders, just for organizing different projects. Need to know before upgrades how to consolidate or separate them.

1 Like
114

Same here

115

If I can have a Team with 3 apps for 25 dollars can I make a second Team with the same participants for 3 more apps?

1 Like
116

Teams cannot share subscriptionsā€“each team can either be free, or have a Starter, Pro, or Business subscription.

We plan to add folders to teams, so you donā€™t need to use teams as folders.

5 Likes
117

I expressed myself wrong. That would be just that, a team with the $25 Starter plan. Could we have more than one team with the same members and also have 3 apps published for 25 dollars?

118

If one of the team members has, say, 10,000 lines, can that team publish 3 apps for 25 dollars and the apps have 10,000 lines?

119

The announcement is now public: šŸ†• All-New Team Plans Coming Thursday, April 21st

Check out the details of the new team plans there :point_up:

3 Likes