[ruyi]

You are essentially building a marketplace so you'll need both suppliers and consumers. This is hard because one side relies heavily upon another. Typically, you need to boost one side first and then the other side might catch up. In other words, you need to build up either 1) the consumer side (say, if you can make this app so easily to use that people will love it despite a poor supply of UI components) or 2) the supplier side (for example, if you can somehow import 20k React components from npm or github to your marketplace)

[ipselon]

Thanks, that is exactly what I'm thinking about. I made the first part, but not many developers like it so far. That's why I will start making the next part - importing components.

[ruyi]

That's awesome! You might also want to rethink what your market is. Is your users going to be engineers who build web app for their company, engineers who build their side projects, some developer-designers or maybe some technical product managers/product engineers? You can still catch all of them eventually, but in the beginning focusing on one or two groups might help quickly get more users and also help on morale.

[ipselon]

Yes, you are quite right. And I already decided the following. Acting as market we will be focusing on engineers who build web apps and freelancers. And as a company with own product we will provide development teams with something like component generator service (installed on internal server) for Structor - this is for enterprise customers.