Ecodesign: Difference between revisions

From Wiki for Sustainable IT
Article created
 
Ajout des liens vers ISO/IEC TS 20125 et AFNOR SPEC 2201
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
'''Ecodesign''' of digital services consists of integrating environmental impact into design choices, from the initial specification through to decommissioning.
'''Ecodesign''' of digital services consists of integrating environmental impact into design choices, from initial specification through to decommissioning.


== Principle ==
== Why design decides ==


Most of a digital service's impact is determined at design time. Once a service requires a recent device, a fast connection and continuous data exchange, no later optimisation recovers what the initial choices cost.
Most of a service's impact is fixed at design time. Once a service assumes a recent device, a fast connection and constant data exchange, no later optimisation recovers what those assumptions cost.


Ecodesign therefore acts first on '''what is built''', and only then on how it is built.
The most consequential decision is rarely technical. It is the decision about scope: which features exist at all.


== Main levers ==
== Main levers, in order of effect ==


* reduce the functional scope to what is actually used ;
# '''Reduce the functional scope''' to what is actually used. Measured usage almost always shows a long tail of features used by nobody.
* preserve compatibility with older devices, which delays their replacement ;
# '''Preserve compatibility''' with older devices. A service that still works on a six-year-old phone delays its replacement, which is the largest environmental gain available to a software team.
* limit the volume of data transferred and stored ;
# '''Limit data transferred and stored''': image formats and sizes, autoplay, prefetching, retention periods.
* avoid designs that require constant network activity ;
# '''Avoid constant network activity''', which drains batteries and keeps infrastructure busy.
* measure before and after, rather than assuming.
# '''Measure''' before and after, rather than assuming.
 
== Common misconception ==
 
Ecodesign is frequently reduced to page weight. Weight matters, but the dominant effect of a heavy service is that it accelerates device replacement, not that it consumes bandwidth. The target is the device, not the network.


== Frameworks ==
== Frameworks ==


The [[RGESN]] provides a public reference framework of criteria. The [[GR491]] provides a more extensive set of recommendations. Both are usable together: the first assesses, the second implements.
The [[RGESN]] provides 78 criteria structured for assessment. The [[GR491]] provides a broader set of recommendations, including social and ethical aspects. Both can be used together.
 
== Relationship with accessibility ==
 
An ecodesigned service and an accessible service share most of their properties: structured content, no dependence on the latest browser, usable on modest hardware and poor connections. The two disciplines reinforce each other more often than they compete.


== See also ==
== See also ==


* [[RGESN]] · [[GR491]] · [[Digital sobriety]] · [[Life cycle assessment]] · [[Sustainable IT]] · [[Digital accessibility]]
* [[ISO/IEC TS 20125]] · [[RGESN]] · [[GR491]] · [[Digital sobriety]] · [[Digital accessibility]] · [[Life cycle assessment]] · [[Sustainable IT]]


[[Category:Concepts]]
[[Category:Concepts]]
[[de:Ökodesign]]
[[es:Ecodiseño]]
[[fr:Ecoconception]]

Latest revision as of 09:37, 8 August 2026

Ecodesign of digital services consists of integrating environmental impact into design choices, from initial specification through to decommissioning.

Why design decides

Most of a service's impact is fixed at design time. Once a service assumes a recent device, a fast connection and constant data exchange, no later optimisation recovers what those assumptions cost.

The most consequential decision is rarely technical. It is the decision about scope: which features exist at all.

Main levers, in order of effect

  1. Reduce the functional scope to what is actually used. Measured usage almost always shows a long tail of features used by nobody.
  2. Preserve compatibility with older devices. A service that still works on a six-year-old phone delays its replacement, which is the largest environmental gain available to a software team.
  3. Limit data transferred and stored: image formats and sizes, autoplay, prefetching, retention periods.
  4. Avoid constant network activity, which drains batteries and keeps infrastructure busy.
  5. Measure before and after, rather than assuming.

Common misconception

Ecodesign is frequently reduced to page weight. Weight matters, but the dominant effect of a heavy service is that it accelerates device replacement, not that it consumes bandwidth. The target is the device, not the network.

Frameworks

The RGESN provides 78 criteria structured for assessment. The GR491 provides a broader set of recommendations, including social and ethical aspects. Both can be used together.

Relationship with accessibility

An ecodesigned service and an accessible service share most of their properties: structured content, no dependence on the latest browser, usable on modest hardware and poor connections. The two disciplines reinforce each other more often than they compete.

See also