To keep your apps future proof and up to date with the latest improvements, you should only use artifacts (such as features, APIs, themes, etc.) that are still actively developed.
If an artifact is no longer developed, we mark it as deprecated. Usually, the deprecated artifact is replaced by a newer and better alternative.
You can usually still use deprecated artifacts for a while - they will remain part of the codeline until they are removed. However: This is not recommended since you can't expect the artifact to be developed any further. In addition, any deprecated artifact can be removed from the codeline entirely with one of the next OpenUI5 releases. If you update your app to a OpenUI5 version that doesn't contain the deprecated artifact any longer, your app will potentially break.
If you want to make sure that your app is future proof and stays compatible with new versions of OpenUI5, make sure that you don't use deprecated artifacts.
APIs that have been flagged as deprecated can be found in the API Reference: API Reference: deprecated. To find more information on the topic of deprecations, check the Related information section.
Some features delivered with OpenUI5 are flagged as experimental. These experimental features are not part of the officially delivered scope that is guaranteed for future releases. Their purpose is to get user feedback at an early point of time, allowing customers or partners to influence the potential future feature accordingly.
Feel free to test those features, but do not use experimental features or controls in a productive environment or with data that has not been sufficiently backed up.
Experimental features and controls can be changed or deleted at any time without notice and without a formal deprecation process. They may also be incompatible to changes provided in an upgrade. So, be careful!
APIs that have been flagged as experimental can be found in the API Reference: API Reference: experimental.
Related Information