Licencing Suggestion

Idea
1

I am trying out .bubble, paid a for a subscription and just found out the licencing for a “personal” subscription is per app and not, app per subscription. There is a subtlety here. I was at first understanding it was a subscription of which I can have one app at a time assigned to it; not so apparently.

I wanted to see everything offered, especially the JSON export so after creating deleting several times, I attached one to a subscription so I could test those features. I created deleted etc. I was not expecting to pay a new subscription every time I did that.

My suggestion is a better license engine that still achieves the same monetary income for .bubble is to have a subscription that can have apps assigned to it while the subscription is active. A new app requires a new subscription. This way you can be in development with the full feature set available, delete a non-viable app, create a new one at will - still only one assigned to the license at a time and not paying for a subscription every time you restart a development cycle…

If I have misunderstood this, please educate me :slight_smile:

2

I think your point is valid. Bubble’s pricing structure could be more straightforward in this respect. And I’ve been in a similar situation (ie. doing a buildout that needs paid plan features to function, but ultimately not pursuing the project yet having paid for the billing).

To state another way, you believe the billing system should be based on “seats”. Those seats should be transferrable between apps. I’d very much like to see this as well.