Hi @Andreas_Marinopoulos ,
As I wanted to reflect in my comment above, currently I do not see a reasonable way to do team development on Backendless in a reliable way. This is at first not related to creating “Codeless Logic”, or “Code Logic”. Both ways create development artifacts, which have to be managed consistently within a team.
By deploying from my local node.js project, I have the “small” advantage that I can choose my source code repository to be Git which offers a solid version control and provides a way to do team development. The backendless code repository is the repo which then can hold the final, consolidated productive code. Git provides means to consolidate code within a team before deploying to BE.
What I’m looking into now is to create a test/dev app which receives a first consolidated code deployment, then run tests and then use the BE merge feature to merge into the productive app.
My hope is, that at some point I don’t need a second app, but the Backendless team is enabling somehow to use different “models”.
This was about the backend code side of the house. For the frontend, I’m in the same situation as you for the backend, because there is no way to version control the frontend sources within a team setting. Also, working on frontend sources with UI Builder simultaneously with multiple team member is not possible/dangerous.
Hope this helps