Code reusability between Projects

Hi Luis and welcome to Wappler and our great community!

I’m sure you will find a lot of similarities between Outsystems and Wappler. Wappler is more generic so you can use it in much more user cases and have of course actually hosting freedom.

As for library of reusable components, we do already have some. Like the library in the Server Actions ( although those are for reuse within the same project.

It is more challenging to make it very generic because we are dealing with many dependencies in Wappler. Like server actions are dependent on database with specific schema, so those won’t just work in other projects.

We do have a lot of generators that will save you a lot of work in generating bootstrap tables and forms based on a database source or server connect action output.

As everything is based on data schema in Wappler, we also just released a Database Templates library functionality so you can create your own for reuse indeed. It is in the latest Wappler 6 beta.

There is also a feature request for library chest, so you can vote on it:

Also keep on supplying us with good ideas, then we can just implement those in Wappler.