The purpose of this section is to describe the process of upgrading shared components (i.e. Ionic Portals framework, Capacitor runtime or plugins) in web applications developed and maintained by partners and native components provided by EGYM.
The goal of the process is to minimize disruptions caused by the release of newer versions of applications, ensure that updates are rolled out in a controlled and orderly manner and that all partners follow the same guidelines, leading to a more consistent and reliable system.
The default approach is to use core plugins provided by Capacitor runtime. Adding new 3rd-party or community plugins is a subject of review by the EGYM engineering team and assessment of the potential impact on existing micro web applications (MWA) developed by other partners.
Before starting the development of the web application the partner will receive information from EGYM regarding versions of Ionic components that should be used.
The upgrade process of Ionic components is owned by the EGYM engineering team. It is required because all used Ionic components should be compatible between web and mobile parts and across all applications built by different partners.
In case if a partner requests the upgrade of any of the Ionic components, this request will be evaluated by the EGYM team for potential risks, and based on that the upgrade will be either approved and made on both web and native sides or rejected.
In case EGYM requests the upgrade of any of the Ionic components, this request will be performed by the partner within a mutually agreed timeframe, depending on the scope and priority of the upgrade.
For all major version upgrades, EGYM will assess the impact on the already released web applications and plan the upgrade process with the partner.
Please check the mwa-reference to see what the currently supported capacitor dependencies are.