We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
低代码的类比 Low Code Analogy
http://wind13.github.io/post/2022/low-code-analogy/
The text was updated successfully, but these errors were encountered:
我这里谈的快速是指在项目初期的快速
我这里谈谈我的理解,前些天看到一个lowCode产品:nocobase。非常适合搭建企业内部erp系统。 但是其中的自定义性很差,但是非常适合初创公司初期快速在市场上试错
结合当下的环境,C端市场已经趋于饱和,运营成本远远大于开发成本。对于初创公司,最困难的点在于没钱,不懂行的创始人会让开发人员前期996甚至007的干活。以此来降低开发成本
对于我个人来说,我非常倾向于前期使用lowCode。较低的试错成本可以快速去验证我当前的商业模式是否可行(可以盈利)
当赚到钱,或者说收支平衡后,我会放弃lowCode,采取科学的方式去开发我的产品
我们的用户已经被国内的产品喂的很挑剔了,所以当下只能找到一个非常细分的领域去做。前期需要的是快速的验证商业模式的可行性,因为中国公司老板口袋的钱没法子支撑开发团队长期的工资(这里的长期指半年以上)
然后再说说C端的产品,和B端产品不同的是,很多C端的项目前期拥有较强的确定性,自定义的需求占比也很高。所以不需要使用lowCode这种方式在前期快速的验证市场需求
Sorry, something went wrong.
No branches or pull requests
低代码的类比 Low Code Analogy | 世风十三学堂
低代码的类比 Low Code Analogy
http://wind13.github.io/post/2022/low-code-analogy/
The text was updated successfully, but these errors were encountered: