deviceshould

Device should is a term used in technology design and policy discourse to describe a normative principle that interactive devices ought to satisfy a set of standards. It is not a formal specification or standard itself, but a framing device for discussing desirable properties across a product’s life cycle, from design to end of use.

Core idea and scope

The concept centers on making devices safe, usable, privacy-preserving, interoperable, and sustainable. Practitioners often invoke device should to articulate expectations that products should be accessible to people with diverse abilities, protect user data by default, resist compromising security, support open or well-documented standards, and be repairable or recyclable where feasible. The emphasis is on user control, transparency, and responsible stewardship of technology.

Applications and practice

In industry, teams may employ a devices should checklist during design reviews or product roadmapping to ensure key criteria are addressed. In policy and advocacy, the term is used to frame requirements for regulatory regimes, certifications, or procurement criteria. It also appears in discussions about ethical design, responsible innovation, and accessibility initiatives. While the concept is intentionally broad, it serves as a common language for aligning stakeholders around core values.

Limitations and critique

Because devices should covers a wide range of goals, it can be imprecise and subject to interpretation. Conflicts can arise among usability, privacy, performance, and cost. Critics argue that without specific metrics or enforcement mechanisms, the principle remains aspirational rather than prescriptive.

See also

Privacy by design, security by design, universal design, right to repair, open standards.