New UI Adoption Info

overview with the new ui, some work might be required to adapt to the new visual style and design guidelines this can range from minor fixes such as adjustment of margins or tweaking of colors, to larger efforts such as recreating icons / visual assets, or redesigning the layout to adhere to industry standards the scope of work should be assessed on a case by case basis, ideally with the help of ux expertise, however the typical work required include review the new design guidelines identify adoption work and create design plan create visual assets make the code changes and update icons regardless of your decision on the scope of planned ui changes, you are always required to perform basic migration to the latest cet major version what is the difference between adoption and migration? basic migration refers to the mandatory effort that partners perform every release to update their code to work in the new major version according to the migration guide, regardless of old or new ui for example, code changes, compile errors, bugfixes adoption of new ui refers to the optional effort to rework the extensions to fit the new design guidelines e g update partner extension component libraries to comply to the new guidelines with new icons adoption timeline configura's plan on the transition of old ui to the new ui is outlined in the diagram above it is up to the partner to plan and decide the cadence of their updates 15 0 15 0 new ui adoption remains optional, however partners should try out the new ui and review any potential work 15 5 (november 2024) 15 5 (november 2024) configura recommends partners to start adopting the new ui this means before august partners should plan ahead to review changelog and the new ux design guidelines, and identify necessary adoption work before august partners should plan ahead to review changelog and the new ux design guidelines, and identify necessary adoption work september (feature freeze) review beta changelog, update the plan for necessary migration and perform adoption work september (feature freeze) review beta changelog, update the plan for necessary migration and perform adoption work 16 0 (may 2025) configura plans to phase out the old ui and set it to maintenance support , so adoption of new ui should occur beforehand 17 0 (may 2026) old ui will be mark for end of life which means configura will no longer support or fix any old ui related issues it is important to note that partners can decide on the cadence of their updates, so they can decide to when to work on and release the new ui changes adoption strategy and considerations in general, any ui adoption strategy should account for these steps design and prototyping read through the design system and understanding the design principles is key to unlocking a better user experience and ensuring your user interface is consistent with the rest of the system follow our examples and recommendations, and create prototypes to get a feel of how it would be like before spending countless hours on implementation in configura, we use figma to create prototypes to rapidly iterate and test if the user experience has been improved implementation depending on the breadth of the changes required, using a separate code path (to build a facelift specific library limb tree) for the new features might be required we have also added support in lazy xml to map different toolboxes between ui modes generally, minor changes like updating to the new icon style should not require a new limb tree however, larger changes such as adopting the new features or rearranging the items in the library, will require a new library limb tree to be created testing just like you would with any changes, the new ui should be tested out with users, to validate assumptions and ensure that this is an improvement in user experience and that there are no significant regression bugs metrics like user satisfaction, conversion rate, click rate, task success rate can be used to measure if the new ui is well received should i support the old ui? do i need to maintain two versions of my extensions? while configura will still maintain necessary functionality for the old ui, the old ui will be deprecated after 16 0 (may 2025), and new ui is the future while the transition period is ongoing, if you have an existing old ui toolbox, we recommend to maintain two versions of the toolbox, but any new work is expected to target the new ui it is also acceptable if you do not want to maintain the old ui anymore and go all in with the new ui, as new ui toolboxes will work in the old ui (albeit imperfectly, with a tighter spacing in its layout) adoption effort estimates here are some estimates for effort it takes to adopt the new ui for partner toolboxes on a varying level of compliance, based on internal investigation, however it may vary significantly depending on the factors outlined below the estimate is affected by these general factors how much customized functionalities there are ui/ux understanding availability of a designer or ux expertise availability of visual resources ambition level / product vision / budget time to review the guidelines / migration guide how the extension is set up (subextensions, multiple toolboxes, catalog/data driven toolboxes) technical expertise available engaging a designer to review usability and creation of the new icons may be the most time consuming part it is up to the partner to plan and decide the cadence of their updates we are still collecting data to update our estimates and continuously improve the framework to make it easier to adopt, so any feedback is much appreciated debug option force facelift style there's a new "force facelift style" debug option provided in the release debug menu which will attempt an imperfect automatic conversion of your toolbox to the new look, to aid in estimating the amount of effort needed and planning related readings tutorial adopting the new ui style for extension libraries docid\ j 7esmowa2ggsooflmwxq tutorial facelifting hybrid catalog libraries docid 2ar9 c7l1elrgbl81vbib more questions? changelog docid\ iwa76uv4j2sm rsuq1iql for what's changed, migration guide, testing guides frequently asked questions (faq) for new ui docid\ ug0 kiqcjgz4jc2kvuoej to learn more