After few days on WeWeb, I’m wondering why it is seen as a good tactic, or a business strategy to discourage people from building custom plugins, elements, or sections by gating this possibility via a paid Workplace plan?
I’m wondering whether there is any reason, perhaps it costs resources? Or something else?
In my opinion… giving the users ability to actually create stuff without having to pay for the possiblity to do so would bring more innovation and addons (which would in the end benefit WeWeb and not the developers themselves), I really like WeWeb, but some choices, such as gating the content to just the editor (without a staging .weweb.io domain) or this fact about extensions and plugins just makes no sense to me.
Is there a reason for this that I’m failing to see? Please, don’t take this as critique, it’s more like, me wondering why would you gate something that could give you more exposure and growth, since you have such an amazing community.
Thanks for your feedback on our pricing. It’s been two months since we rolled out the new model, and we are actively gathering feedback like yours to make informed decisions on the path forward.
Your feedback, along with others’, is critical in this process. If the consensus shows we’ve missed the mark, we’ll consider adjusting our model. The goal is to ensure that most users feel they’re getting a good deal while we also meet our business targets.
Thanks for your patience while we sort this out and for caring enough to share your thoughts. Keep them coming - we are listening!
Thanks for letting me know @Slavo, I’m actually pretty fine with the pricing, maybe the plugins number is a little less than some might end up needing, but that can be solved with some code, or an upgrade, the only pain points for me are as of now the ability to create the integrations and staging urls. Other than that I’m loving WeWeb <3