Over the past few months - close to a year - we’ve been intensively building a SaaS solution on WeWeb (Xano backend). The project is (very) big and includes a large number of custom components and complex (workflow) logic. We are at a point that it becomes challenging to maintain - keep ‘clean’ - variables, workflows, functions, pages, … There is duplication, little reusability, … It created a ‘technical debt’ due to the speed of development; the development team size, our limited knowledge of WeWeb (in the beginning) and fast product iterations on our side. We have a team of six (6) front-end developers (WeWeb) working on this project simultaneously.
We’ve come to a point that we need to address these challenges and maximize reusability - this includes (rigid) coding/building conventions, DRY (don’t repeat yourself) and a ‘component’ guide (implementation, correct version, …) and other methods to prevent and reduce this ‘debt’.
I am sure we are not the only one facing these challenges. Hence this post to reach out to other WeWeb power users and share our experiences, best practices, ideas, … on how to best manage big projects in WeWeb, managed by large teams, in a constant state of change.
Looking forward to get into contact with software companies, agencies and others, power using WeWeb and experiencing similar challenges on large WeWeb projects.