Thank you, this is valuable feedback for us and you’re not the first to say so.
To be honest, we’re still thinking about pricing and I’m sure there will be updates in the (hopefully near) future.
Personally, I’m a big fan of usage-based pricing because it’s the fairest approach. We are also thinking about splitting the price tiers into different modules, e.g. for OpenAI integration, collaboration, maybe support and so on. I said “hopefully in the near future” above because it’s going to be a huge amount of work for us to change that (for example, we have to change our payment provider) and we’re currently focused on other things like implementing new features that our users are asking for most.
What do you think about module-based pricing (in combination with usage-based pricing)?
Module-based would be ideal. For context, I'm building a writing app. I have basic functionality + OpenAI integration, but these things have been a huge pain:
- collaborative editing
- offline editing
- faster loads with sw caching
- git history
- end-to-end encryption.
It's taken me forever to build these, and the code's still not where I want it to be. If you had modules for these that I could pay for, I totally would.
To be honest, we’re still thinking about pricing and I’m sure there will be updates in the (hopefully near) future.
Personally, I’m a big fan of usage-based pricing because it’s the fairest approach. We are also thinking about splitting the price tiers into different modules, e.g. for OpenAI integration, collaboration, maybe support and so on. I said “hopefully in the near future” above because it’s going to be a huge amount of work for us to change that (for example, we have to change our payment provider) and we’re currently focused on other things like implementing new features that our users are asking for most.
What do you think about module-based pricing (in combination with usage-based pricing)?