Comes with ToS too. What the hell is going on there.
^ j/k fyi, since your comment sounded serious so I just wanted to ease the tension. We're planning to open-source the repo, but ATM we have not set up everything to welcome the community yet (CoC, contribution guideline, CI for testing, issue templates, etc...)
BTW, love your passion for open-source and appreciate the criticism (esp your effort in taking a deep look at the stuff we are building). The NPM page is nowhere ready for public view yet. The thought of slapping the TOS and Privacy Policy in the readme is so that if the user installed our CLI and managed to initiate some of the extra undocumented capability, we wouldn't be responsible for any damage to their hardware. But perhaps the MIT license should suffice for that case?
On the other hand, I am asking for feedback on the documentation, so if we can stay on that topic that would be much appreciated :D
Thank you in advance :)
It'd be great if the documentation could start with showing how is different from the many other similar solutions that came before you, to make users understand the value proposition of your framework a bit better.
I went to the main-page to see what the main product you were building, and seems the browser extension framework is the main product. I'm not sure if the Pricing is placeholder pricing or not, but $256 per user per month sounds like a lot for a extension framework, but maybe I'm not the target audience, I've only published a few browser extensions as an individual.
The framework itself is free. Only if the user require hands-on contracting work (i.e, a demo of integrating with their in-house framework) would it trigger the support price.
Your feedback indicates I should separate the "enterprise-support" pricing from the "Developer" or Team pricing, and also make it less expensive (certainly lower than $256). Since the base framework is free (like Next.JS), how much would you as a solo developer pay for a feature that allows you to test your extension without having to submit and wait for the chrome/edge webstore review?
