UX Framework

<aside> 💡 If you don't have a business need to modify TRIRIGA-built Perceptive apps or develop your own custom-built UX apps, then you don't have to worry about these general best practices. But if you choose to customize your own UX apps, then follow these best practices to avoid most issues.


What are some best practices for customizing UX apps?

If you built and extended your first UX apps by following the examples and exercises in my earlier articles, you'll probably remember that HTML (Polymer 1) or JavaScript (Polymer 3) view files were stored in your local folders. For example, if you added the jay-uxbo-view.html starter file, the jay-uxbo-view folder was also created. By recognizing this behavior, you can make regular backups of your work.

Be aware that by customizing TRIRIGA-built Perceptive apps, there's no guarantee that future upgrades of these Perceptive apps will be backward compatible with your custom changes. So don't forget to document your changes by commenting in your HTML/JS view files or elsewhere.

Simple Backup of HTML/JS Views

Here are the basic steps for backing up your HTML/JS views:

Advanced Backup of HTML/JS Views and UX Metadata

Here are more advanced steps for backing up your UX metadata: