The new release reaffirms one of the key advantages of WebRatio Low-Code: technology can evolve without shifting the full complexity of upgrades onto development teams.
The release can be downloaded from the myWebRatio Download Center or installed by upgrading the version currently in use.
You can also consult the WebRatio Platform 9 Release Notes for details on the fixes and other updates included in version 9.3.3. They also highlight the deprecated features that will no longer be available from version 9.4 onward (e.g., CVS and SVN integration in favor of Git).
Starting August 31, 2026, new applications and updates submitted to Google Play must target Android 16, corresponding to API level 36.
Full details are available on the official page covering Google Play's target API level requirements.
When Android, iOS, a library, or an application store introduces a new requirement, WebRatio updates the platform components and the generation process. The technology upgrade is therefore implemented once, centrally, and made available to all users through a new release.
There is no need to analyze and manually modify each codebase to update its frameworks, libraries, SDKs, and configurations. A new version of the application is generated using the updated technology stack provided by the platform.
With this platform-managed application evolution approach, upgrades do not disappear altogether: the new version of the application still needs to be tested and published. However, most of the repetitive technical work required to adapt the code manually is eliminated.
Developers do not need to examine every change introduced by SDKs, update dependencies one by one, or solve the same problems across multiple applications. WebRatio incorporates these changes into the platform and its generators.
When a company manages numerous applications, even a seemingly limited update can require weeks of work. With WebRatio Platform, automatic generation can be applied to all compatible projects, accelerating upgrades across the entire portfolio.
Applications are regenerated using consistent components, configurations, and build processes. This reduces the risk of different teams adopting different solutions or some applications remaining tied to obsolete technologies.
Technology upgrades are not postponed because they are too complex or costly. Regeneration keeps applications aligned with the platform's evolution, limiting the accumulation of obsolete code and unsupported dependencies.
Adapting to new requirements does not turn into a reengineering project every time. Activities become more standardized and easier to plan, with less impact on maintenance time and costs.
Developers can focus on features that create value for users and the business, rather than spending an increasing share of their time maintaining the underlying technology infrastructure.
The models, processes, and business logic developed over time remain the application's core assets. When the underlying technology changes, these elements can be reused to generate a new, updated version without having to start from scratch.