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.)
...
Samvera Design Principles (working draft)
...
Transparency | Mindful of Unintended Favouritism | Digital Safety & Wellbeing |
|---|---|---|
|
|
|
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?
2. Efficient
Modular while functioning as a whole
Q: Does the app take advantage of DRY principles and is logically separated?
Minimal (in design & latency)
Q: Does the UI display more than is needed?
Intuitive
Q: Is it easy to understand and follow with minimal to no training needed?
Q: Is it easy for users to avoid and correct errors?
Predictable, uncomplicated and precise
Q: Ex. Does the app use consistent breadcrumbs & buttons placement? Consistent color and icons usage?
Flexibility balanced with Friction
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
3. Unified
...
Follow standards, guidelines, conventions and best practices.
Q: Does the app use popular open-source libraries/packages?
Q: If core developers left the app, could its maintenance continue?
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?
5. Ethical
...
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?
...
|
...
Contribution Acknowledgements for the Samvera Design Principles:
...