Improved performance and resource consumption

The previous version of the app had been developed in hybrid mode, using a mechanism for downloading and rendering HTML templates at run-time. This architecture resulted in poor performance and higher resource consumption, such as data connection, storage space, and battery. In the new version of the app, we implemented a new native layer, with particular attention to optimizing performance and resource usage. The web layer was also optimized by adapting the website’s page logic to work within the app’s WebView.

Fragmentation between App News and Digital Edition

The Digital Edition features and the news features were initially split into two separate apps, leading to fragmentation among users, especially in terms of subscriptions, as well as lower efficiency in maintenance and future development. In the new version of the Gazzetta app, we unified the two apps into what became known as the "App Unica." To minimize maintenance and development time and costs, the Gazzetta app was reorganized into a target/flavor architecture, so that the functionalities reside in a shared codebase, with app-specific modules for styles and configurations.

Improvement of SDK update cycles integrated in the app

The previous version of the app suffered from a lack of dedicated maintenance cycles for updating third-party SDKs and, most importantly, those related to the operating system. In the new version, also thanks to the fact that the app is a target/flavor of the App Unica, we improved maintenance cycles by planning them annually in the periods preceding new operating system releases. In addition, the number of integrated third-party SDKs has been streamlined, keeping only those truly essential for the functioning of the app.