My concern is that you alienate the primary audience (non-coders) and dilute and confuse the product roadmap with features that require coding. If a Baserow product manager says, “our users really wish they could do X,” saying that it is possible “with a few lines of JS/CSS” is not the solution for this audience. Also, any solution that requires a paid account with external services completely destroys the economic argument for choosing this platform.
I am a huge fan of this product so far and want to be able to recommend that my employer make the purchase. I have taken the time to provide this feedback, not to complain, but in hopes that it will fall on receptive ears within the Baserow product team. Maybe make a non-coder persona and apply it in user testing every time you create a new feature. If a non-coder can’t use the feature, then it’s not ready for production.
I’ll be lurking in the forums and rooting for your success.
