Hi, I'm Robert Walter

This is an interesting Federico.

I have two things to share :

I envision it is possible to have low-code technology rather than “a specific low-code platform :

This is made possible specially with the code generation low code approach (as opposed to the interpretation low code approach). Let me explain my idea:

The code generation low code approach is to transform a meta-model to an application code through generation template. A low-code platform is usually both the business user-friendly UI that is used to instantiate a meta-model, the code generation engine to actually generate the code, and the infrastructure to seamlessly deploy and monitor the applications.

If the low code platform is based on a static meta-model and code generation template (static in the sense that the end users don’t have any control over it), then indeed we have a specific low code platform, designed to model and generate a specific type/domain of applications. Even if the domain is quite large (for example: data centric management applications).

However, if the low code platform is open and flexible enough so that the end users (more technical experts than business users) can evolve the meta-model and the code generation templates, or even create their own full new meta-model and code generation templates, then we have a low code technology that is not specific and can cover any kind of domains needs ! You then have a low code platform that can be used by experts who will create meta-models and code generation templates, and by business users who can use specific meta-model and code generation templates tailored to their domain needs. Same as specific DSLs built by experts and then used by (ideally) business users.

This is the second option that I definitively prefer, and on top which Generative Objects is built. A “secret” of Generative Objects approach is that the platform is “bootstrapped”. It means that Generative Objects is built with Generative Objects. You can open with GO the GO meta-model, evolve it, evolve the code generation template and … regenerate GO by itself. So by design, GO allows to have this generic low-code technology approach.

DSL can be a great addition to low-code technology

For me I see DSLs as a great tool to be used as part of low-code platforms. For instance, in GO, we have a mixed Graphical/Textual DSL (built by @tvillaren !) to express and model validation rules and business rules, integrated as part of the UX of GO. This is one of the reasons I am interested in the forum !