How to maintain a quality UX in the long term?
This is often a recurring subject because it is complicated to maintain the code to be able to ensure consistency on all screens and over the long term.
We saw in the first lesson that a Design System could help. Today this often results in frameworks or libraries, which make it possible to propose or even impose not only a Design System, but also technologies and finally a mode of operation, or even APIs that will save time in a first time.
But precisely, the above elements can become a risk or technical debt over the long term. Indeed, each of these components and frameworks “claims” to be available for decades. In practice, we are on average lifetime times of 7 years. When you want to create applications that will last several years or decades, it is therefore a risk.
It is therefore necessary to have a Design System able to produce all the code and to maintain this layer, to change the axes discussed (see lesson 1) in order to be able to simply switch to new principles of ergonomics or navigation without having to pay the price of technical debt.