3 ms·
Hey there, do you know anything about those users who have tried the demo? We have a SaaS but when thinking about whether we would use your boilerplate, the ho
by tixocloud 8y ago
Hey there, do you know anything about those users who have tried the demo?
We have a SaaS but when thinking about whether we would use your boilerplate, the honest answer is I wouldn’t because I’d have to learn the tech stack that you’ve decided for me. That’s a big learning curve than rolling out with something I’m familiar with.
If you have a boilerplate that limits tech to a few and simplifies the learning curve, there might be a bigger interest. Or you can go down the route of creating a UI version where non-developers can configure their own SaaS app for building an MVP, which would be useful just to validate ideas, raise funding and hire someone to fix it.
- tima101 8y agoThanks for the comment. Valid point. It encourages me to write tutorials to shorten the learning curve. Building a tool for non-developers is too much effort for me. I should mention that some parts of the stack, say MobX, has a shorter learning curve, in my opinion, than an alternative, Redux. I tried a bunch of tool from JS world, this stack, once learned, is easily manageable by really small technical teams (1-3 people). Overall, I am from the camp "whatever works, customers don't care about stack". Just posted to HN to see if something is not clear in the README or some features can be added/removed from boilerplate. EDIT: I did not answer your question. Majority of signups at the demo app is web development agencies and freelancers.
- tixocloud 8y agoThink this would be good to include in your README - about why you chose the tools. Also reach out to those signups and ask them what would it take to get them to really use it for their own projects. What’s holding them back, etc.