Understood. The “publish to marketplace” is not an option at all since it is not possible to publish a “normal” reusable component — only “custom” component with React/JS code. Also having to wait for approval, and making the entire Backendless community look at various specialized components would be crazy.
Our biggest problem (and I know we are not alone with this) is that it’s not feasible for different team members to work on the same application at the same time, because work gets overwritten and lost. That’s because Backendless gets conflicting information about what to save to the server when there are multiple browsers accessing the same app. But working in different containers in our app is OK. However, then there is no way to copy components, pages, extensions from one container to the other, so we have to use the file system (as suggested by the Backendless support — see here and here)
If you know of a better way for teams with more than one person to work on the same application simultaneously, please let me know 