What are some best practices for UX?


[Admin: This content comes from the original mobile-friendly PDF.]

Navigating UX: What are some best practices for UX?

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 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 view files or elsewhere.

Simple Backup of HTML Views.

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

  • Make a backup copy of your HTML view folder and its files.
  • Rename your backup folder with an easy identifier, like today’s date.
  • Create a new snapshot of the related UX view metadata record.
  • Continue to work with your active HTML view folder and its files.

Advanced Backup of HTML Views and UX Metadata.

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

  • Make a backup copy of your HTML view folder and its files.
  • Rename your backup folder with an easy identifier, like today’s date.
  • Create and rename a brand new UX view metadata record.
    • Rename your active HTML view folder and its files to match this new metadata record.
    • Add your active HTML view, and any other supporting HTML and CSS files, to this new metadata record.
    • Create, rename, and reconnect any brand new UX model, data source, model-and-view, and application metadata records related to your new UX view metadata record.
  • Continue to work with your active HTML view folder and its files.

Compare and Merge HTML Views.

Because HTML tools, practices, and requirements can vary from organization to organization, team to team, and developer to developer, it is the responsibility of your organization to determine the details of how to compare and merge your custom HTML views with upgraded versions.

Here are the basic steps for comparing and merging your HTML views:

  • Perform a simple or advanced backup of your HTML views.
  • Use a HTML “diff” (difference) tool to compare the versions.
  • If a customization has no related upgrade, use the customization.
  • If no customization affects a related upgrade, use the upgrade.
  • But if a customization affects a related upgrade, make a decision to use the customization, use the upgrade, or take a new approach.
  • Continue to test and work with your active HTML views.

Continue reading →

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s