Versions Compared

Key

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

Samvera community packages run the gamut from Ruby gems, to generators, to Rails and Elixir applications, Node modules, JavaScript UI components and more. Thinking about a meaningful purpose the UX Interest Group could serve the community in 2021, the following questions have surfaced.

...

  • Backend Developers (current & future)

  • Front End Developers (current & future)

  • Administrative Users

  • End Users / Patrons (students, faculty, research, general public, etc.)

***We want to put in questions with each principle we settle on to help people think thru how they are/arent' reaching those principles. **

Samvera Design Principles (working draft)

Samvera is a vibrant and welcoming community of information and technology professionals who share challenges, build expertise, and create sustainable, best-in-class solutions, making the world’s digital collections accessible now and into the future.

Design Principle

Sub-Theme

Qs for All

Additional Qs for Developers

Human-Centered

Inclusive & Equitable

Q:
  • Does the app feel welcoming?

Q:
  • Does the app (unintentionally) leave any users out (culturally, language, eye-sight conditions, etc)?

Q:
  • Is it obvious where to request help? Report a problem?

Human-Centered

Accessible & Universal

Q:
  • Is the app “approachable”?

Q:
  • Does the app feel cluttered?

Q:
  • Is the app responsive across viewport sizes?

Q:
  • Easy to find and manipulate any accessibility features?

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

Human-Centered

Engaging & Unambiguous

Q:
  • How does the app actively engage/empower users?

Human-Centered

Unassuming

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

Q:
  • Are used icons universally recognized for desired function?

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

Q:
  • How is the user experience changed when used on different devices?

Q:
  • Does the app assume a certain level of technical proficiency to navigate?

Q:
  • How does the app adapt to various devices?

Efficient

Modular while functioning as a whole

Q:
  • Does the app take advantage of DRY principles and is logically separated?

Efficient

Minimal (in design & latency)

Q:
  • Does the UI display more than is needed?

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

Efficient

Intuitive

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

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

Efficient

Predictable, uncomplicated and precise

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

Q:
  • How does the app use consistent color and icons?

Efficient

Managed Flexibility

Q:
  • Does the application create endless 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

Follow standards, guidelines, conventions and best practices.

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

  • If core developers left the app, could its maintenance continue?

Unified

Consistent behavior patterns and functionality

  • Does the app feel very different on any screens?

Unified

Clearly documented (for designers and users)

  • 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

Prioritise Sustainability over Trends

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

Sustainable

Maintenance demands should match organizational commitment to a resource.

  • Are bug issues outweighing new feature issues?

Sustainable

Design (visual, technical, etc.) should be forward-looking, taking into account likely future scenarios, and avoid short-term trends.

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

Ethical

Transparent

  • 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?

Ethical

Mindful of trends and unintended favouritism thru integration choices (ie. FB, Google+ integrations)

  • 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?

Ethical

Safety

  • 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?

1. Human-Centered

  • Inclusive & Equitable

    • Q: Does the app feel welcoming?

    • Q: Does the app (unintentionally) leave any users out (culturally, language, eye-sight conditions, etc)?

    • Q: Is it obvious where to request help? Report a problem?

  • Accessible & Universal

    • Q: Is the app “approachable”?

    • Q: Does the app feel cluttered?

    • Q: Is the app responsive across viewport sizes?

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

    • Q: Easy to find and manipulate any accessibility features?

  • Engaging & Unambiguous

    • Q: How does the app actively engage/empower users?

  • Unassuming

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

    • Q: Are used icons universally recognized for desired function?

    • Q: Does the design translate well to multiple communities and account for cultural/institutional differences?

...

  • Follow standards, guidelines, conventions and best practices.

    Clearly documented (for designers and users)

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

    • Q: If core developers left the app, could its maintenance continue?

  • Consistent behavior patterns and functionality

    • Q: Does the app feel very different on any screens?

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

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

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

4. Sustainable

  • Prioritise Sustainability over Trends

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

  • Maintenance demands should match organizational commitment to a resource.

    • Q: Are bug issues outweighing new feature issues?

  • Design (visual, technical, etc.) should be forward-looking, taking into account likely future scenarios, and avoid short-term trends.

    • Q: Are there any trends in design you are considering encorporating reliant on Proprietary systems?

...

  • Transparent

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

    • Q: Is the app Community driven/managed

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

  • Mindful of trends and unintended favouritism thru integration choices (ie. FB, Google+ integrations)

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

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

  • Safety

    • Q: Does the app prioritize security in code?

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

    • Q: 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?

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

  • Ease of Adoption for all communities

    • Q:

  • Prioritise Design choices that favour all communities.

    • Q:

...

Contribution Acknowledgements for the Samvera Design Principles:

...