The maintenance aspect is too heavy. Moving from one version to the other made the solution change, and not in a way that we liked. Typically there are documents about the release of new versions and a set of activities required to migrate from one to the other. This time, it was very messy. There were issues surrounding the management of the release. This could potentially be due to the fact that WebRation, in the past, had started to make some choices regarding the framework and architecture that were changed later. In the past, we'd use a strategy as the environment, as an architectural pattern for the application. Now, it's moving more on the spring framework and this initiated some change that obviously had an impact on our application. It's caused a problem with maintenance. The solution seems to have changed its approach. Now, it's more related to a federative application environment in a monolithic aspect. While the solution was interesting at one point, everything is moving towards the cloud. WebRatio should be moving also in the web approach. Currently, you have to install an environment inside the desktop. The future is the cloud. Normally with a low code environment, there is a VPN notation - maybe a WebML or FML notation. If they can move in to have an environment that has a running machine at the end, it would be great. Obviously, some components on the server-side should be deliberate. Normally it's the model you control that's step-by-step and has a very simple flow. In the digital environment, in the organization, the process is more complex. The quality of the documentation and the community surrounding the product are poor. They need to give users more documentation and build up the surrounding community. As it isn't a well-known product, it's hard to find professionals to work with it.
