Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Human-Centered. Efficient. Unified. Sustainable. Ethical.

Human-Centered

Inclusive & Equitable

Accessible & Universal

Engaging & Unambiguous

  • How Welcoming/Approachable is the App?

  • Where/How does the app (unintentionally) leave any users out (culturally, language, eye-sight conditions, etc)?

  • How obvious is it How to request help or Report a problem?

  • How does the design translate well to multiple communities and account for cultural/institutional differences? Neurodiverse communities?

  • How does the user experience stay consistent across different devices?

  • How does the app empower the user to successfully complete their journey?

  • How familiar does the user interface feel?

  • How cluttered does the application feel?

  • How does the app stay responsive across viewport sizes?

  • How easy is it to find and manipulate any accessibility features?

  • How does the app use simple language (Ie. Explains all accronyms)?

  • How easy is it to translate to other languages for different users?

  • How easy is it to navigate without a mouse? with a touch screen?

  • Are used icons universally recognized for desired function?

  • What technical proficiency level does the app assume/require of its users?

For Developers:

  • Does the app follow WCAG requirements? At what level?

  • How does the app adapt to various devices?

  • How does the app actively engage/empower users?

  • How easy is it to switch from using another application to this application?

  • Where does the user feel friction when trying to complete a task?

  • How important and easy is it to share?

  • How does the user know this is the correct application to use for their need?

  • How does the application user interface promote focus and minimize distraction from the task?

Efficient

Modular while functioning as a whole

Minimal (in design & latency)

Intuitive & Predictable

Configurability Balanced with Efficiency

  • How does the app take advantage of DRY principles (what is DRY)?

  • How is it logically separated?

  • Does the UI display more than is needed?

  • Can the action be carried out with fewer lines of code?

  • How easy is it to understand and follow with minimal to no training needed?

  • How easy is it for users to avoid and correct errors?

  • How does the app use consistent breadcrumbs & buttons placement?

  • How does the app use consistent color and icons?

  • Does the application create endless configurability/flexibility to the detriment of the workflow? Ie. Endless top folder creation instead of applying information architecture/minimum rules for information organization/categorization. Ie. Endless choice typically doesn’t lead to efficiency

Unified

Standards & Best-Practices

Consistent behavior patterns & functionality

Clearly documented (for designers and users)

  • Does the app use popular open-source libraries/packages?

  • How would the application continue to meet standards & best-practices if core developers left?

  • Does the app feel very different on any screens?

  • Where would a user find the app’s documentation?

  • Does the documentation branding and structure stay consistent throughout for the application and across Samvera or organization’s applications?

  • Where would a developer find the. app’s documentation?

Sustainable

Mindful of Trends

Maintenance Demands Match Resourcing Realities

Forward Thinking

  • Is the app built upon technologies less than 2 years old?

  • How would the application continue to be maintained if core developers left?

  • Who has access to the source code?

  • Are bug issues outweighing new feature issues?

  • Are there any trends in design you are considering incorporating reliant on Proprietary systems?

Ethical

Transparent

Mindful of Unintended Favouritism

Digital Safety & Wellbeing

  • Is the app’s codebase open source (for ease of Adoption & Integration)

  • Is the app Community driven/managed

  • Does the app have a visible public policy around User Data Collection and Analysis?

  • Does the app rely heavily on 3rd party modules (FB/Google/etc)?

  • Does the app assume the user has access to specific 3rd party modules?

  • Does the app prioritize security in code?

  • What risks are there of the app being used as an entry point for ransomware and other cybersecurity threats?

  • How does the application interface with other applications that may hold or process personal/high security/restricted data and what risks, if any, are introduced through that integration?

  • What does the user need to know about how the application acquires, uses, and stores personal/high security data before they use the application?

...

Contribution Acknowledgements for the Samvera Design Principles:

...