@Ed_Pietrzak Are you saying that when the form is submitted you have a script running that does more modifications on your spreadsheet? Or is it just a pivot table that updates?
@Mark just pivot table updates.
US$ 1 = 5,181 X 5,000 = 25,905
With this price we buy a car 0km. A package of 5kg of rice costs 11.00 in Brasil. 25905 nor selling to the government gets that amount.
US$25 is not enough for the American people, for the Brazilian it makes a difference, in our case it would be unfeasible to buy the PRO plan, I am still studying the components of Glide to be able to offer, but I think about this value and I am in doubt.
They could offer us a plan for payment in BRL R $ within the reality of the country
Some Pro apps actually cost us more than we charge for them.
We cannot lower our price further so that you can make money selling apps to customers who cannot afford Pro in the first place—this can sometimes become the equivalent of Glide paying you to give away our service for free, which we cannot afford to do.
We are working on less expensive storage options for Glide that do not use the Google Sheet.
@Ed_Pietrzak We’ll fix that issue soon. Thank you for reporting it!
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:
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)
Predictability, transparency and the vision of the free tier is probably my biggest concern. A lot of us have started on a trip together with Glide. But it is unclear what we should expect and when. I would like to understand what kind of limitations (and possibilities) that will emerge in the future. Does it make sense to create such an app if the future looks very much different from the present. A 1000 edits per month is such a limitation. I was not able to predict that such a limitation was coming as there is no transparency in the roadmap. This brings me to the vision of the free tier. Who should use the free tier and for what? Is it just for fun, for small mvp’s - or what? As of now it seems as smaller app (less than 500 rows) with no input from the users could be a lasting free app - but next month there might be new limitations. So what is the vision of the free tier? Please let us know so we can do an informed decision whether to invest time in doing a free tier app.
The timing and the warning of a new limitation is also an issue. The limitation is put in place from one day to another. It is the time of year where a lot a people have holidays. If you need to adjust your app to comply with the new limitations, you might need to put in some extra time - but you haven’t been able to plan for that. It is actually a bit the same when Glide rolls out changes in existing functionality that alters the app significantly without giving us time to prepare for change.
Next thing concerns which functionality that constitutes “an edit”. Choice component is often used as a mean to control what should be shown in the app i.e. it is not the purpose of the choice component to set values in the sheet. But Glide cannot do such viewing selections without setting values in the sheet. Example, show only cities in western USA.
Then onto edits which actually adds data to Glide (and/or sheets). There are quite a few. If the app makes use of quick selections like ratings or favorites then the user can very quickly do a lot of edits. Thereby quickly racing to the 1000 edits limit. I have been working on an app where the user can use a number of the text input components instead of a form as this makes a nicer UX - but this will be an expensive way (number of edits wise) to do the design. This means that the designer will need to do other designs in order to keep the edits lower.
Testing the app in the Glide builder will also count towards the edit limit. So the limits isn’t only for the production app - that seems odd. As limitations are put on the free tier app workarounds will start to appear and the developer might copy the apps in order to circumvent the restriction and ending up with multiple apps in the builder. The app building experience would be worse - but possibly the same number of edits Glide will have to pay for as if the builder edits didn’t add to the total edit. The app developer that might also be put off going to the next level and buy a pro app. Maybe - just speculations.
Previously, Glide has provided grandfathering to existing apps. Have you considered that with this new limitation or have you left this idea.
To sum it up - tell us where you going so we know what to expect - and consider how restrictive you should be when doing the edit counts.
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, for example—were originally free but became too expensive for us to offer at scale (I still think we are the only service with a map on a free tier). If you need a guaranteed capacity or level of service, you should upgrade.
@david how is the use case when an app hits the limit? Are we getting a notice when the app is getting close to the limit? And what is the user told?
It is not described in the documentation.
Can’t wait for the referral program. Could you possibly be rewarded with more boosts for all of your apps? Like refer 10 people and get 100 extra rows across all apps. Thanks for all that you do guys!
Yes, we will email you when you reach the limit.
Our referral program is launching within a week and will give you +100 rows and +200 sheet edits for every active Glide developer you refer, across all free apps.
An active developer is someone who signs up, creates an app, and that app is actively used by any number of users. Referring signups only, or people who don’t use Glide, will not count
Awesome! Just curious @david… are you guys going to release some graphics for us to post to advertise referrals, or should we start creating our own? Thinking a 3:1 banner graphic within the app would look shweeeeeeetttt…
Totally reasonable, understandable and 100% support that the first one that has to earn money with GLIDE is you. When GLIDE shares come out at least 1 I will buy (if they are not very expensive). It also seems to me ok that they have only one price and one service for everyone, the day they are a great company they will be able to see if they can do charity with third world countries like Netflix and Spotify do that charge less monthly subscription.
The only thing that does not seem quite right to me, although I understand that they should do it since clearly you will be able to make estimates but it is very difficult to know all their costs, especially if they are not fixed, that they cut options in the free plans without giving advance notice at least so that one has time to make the modifications that he / she considers convenient and / or necessary to be able to continue using the platform or look for another option.
In my case I will surely look for a way to try to stay in the free plan and if the equation does not close I will try to find another alternative without deleting what has been done in Glide so far hoping that at some point the needs of Glide and mine will align.
@david Thanks for giving some feedback.
You mention personal use - what are you thoughts about community apps. As example a small home owners organization - quite likely they will not be willing to pay $229/yr for a pro subscription.
You also mention you will be forced to reconsider limits on free tier in the future. As we as developers don’t have any idea of how the cost structure looks like we wont be able to foresee where future limitations might come. And that makes it difficult to plan accordingly.
Going forward, you might consider (and I will consider) a fixed price plan like Adalo for $50/mo for all you apps. In order to keep you dev cost fixed. I know that this will put of some dev develops. Maybe also me actually, as I only do community apps and small discovery apps, and don’t get any inflow of money - i.e. just using my own money.
By the way, you have a vision to make billions of people app developers as I recall. Which price point should you do in order to make this happen.
How many people would use the HOA app per month? What do you think they would consider a reasonable price for a private app? What do they use the app for? Is this currently a free app?
I think this new limit is reasonable given the functionality and price point of moving to a Pro level app (and even more reasonable once a Boost is established to add more edits).
What does HOA app mean?
Just thinking wild here: (and this may be easier to keep up with)
How about 1500 of EVERYTHING for free? No counting the “buckets”. Just add all the rows+edits+zaps+storage+whatever.
(I am never going to use a zap or signature or location, so I may want to have those 100 zaps for my rows or edits.)
Case in point:
If you have a small app with not many rows, you would have more edits to play with.
And if you have a LARGE app (that stays the same mostly) you can get over 1000 rows. (because you will not have many edits)
(Downside: a form would count twice - once for a new row and once for an edit)
On second thought, maybe one price for 2000 of anything!
David is referring to an example I gave. HOA = Home Owners Association
I don’t mind this idea at all! To expand a bit on it, I think a new row should count as a new row and not an edit. “Edits” should be for changes to existing rows that force the app to refresh itself “manually” without the addition of a new row.
That’s just me thinking out loud. I’m sure the Glide team has considered different aspects of this challenge, but this amalgamated approach isn’t a bad option to consider for personal/low use organizational apps.