Subscription based app

Can we please have the ability to add new users as subscribers. Certain apps on App Store are charged per month so just copy that model.

Be good if you could have two instances of this.

So if we create an app for a business we charge them for building/using/supporting/covering the cost of custom domain renewals/updating content and cover the $19 pm to glide for their business. So we need ability to just enter a suitable amount for build - so one off payment, then regular reoccurring payments.

The second one for the business to have the ability to charge their customers for using it.

Happy to expand if needed.

Thanks

5 Likes

This would be huge for me. Any chance of it happening in the near future or is it a pipe dream at this stage?

Many have asked for this, we’re interested in offering it but it is not on our short-term agenda.

2 Likes

Thanks for confirming, even if we would have a form with buy button (so the form data is not added to the google sheet until payment made) that maybe a short term work around? Just a thought - not sure how hard that would be.

Thats the only thing I am trying to find a work around with.

A work around could be directing your customers to a website where you place a stripe checkout form. Set up a zap to send the email that the customer enters in the checkout form to a new row in the google sheet which sets them up as a whitelisted user.

This could work?

2 Likes

Thanks, yeah that works, have used this solution before but want it built natively within glide :slight_smile:

I don’t have any experience with the buy button, but it’s my understanding that an App:Purchases sheet is populated when a purchase is made and contains an email column. This doesn’t solve a monthly subscription based solution in your original post, but wouldn’t you be able to use the App:Purchases sheet to build another sheet with emails to use with visibility or filtering to show or hide certain parts of the app to paying users? I know there has been some mention in the past about submitting additional form data along with the standard payment form details and I totally agree that it would be a good thing. I’m just curious to understand what you are attempting to do. I’m thinking once a payment is made, additional components could show up in the app to allow the user to continue entering data in a new form. I understand the desire to do both at once, but I’m just curious.

3 Likes

Hey Jeff thanks, that’s a good idea, gonna have a play around later to see if that will work for me, cheers :beers:

1 Like