Skip to content
FR EN

Handbook of Sustainable Design of Digital Services

MENU
← go back
Frontend    ODD#12     ODD#13    

Couldn't the expected functionality be implemented with the native capabilities of the browser ?

Recommendation 

Technology

B People

B Planet

B Prosperity

Difficulty

**

Priority

High

Récurrence

OnUpdate

Tests

What features are rewritten because native system functionality does not cover the entire need?

Precisions

Some features are available in several forms. When native, no additional code or components are required to use them, reducing the impact of the service.

Use Case

Technical documentation

Additional elements

Operational issues related to the project

Posts

Rule for assessing the level of compliance of the criterion

0 / 0

Life cycle

Réalisation

11 other criteria related to the recommendation: Use environments and tools that limit impacts

Recommendation Essential

API

Are the functionalities covered by local actions (client side) privileged rather than API exchanges ?

Recommendation

Flux

Do you use caching mechanisms to limit exchanges ?

Recommendation

API

Is the data fed back by the APIs really only the data that the application needs when it is requested ?

Advice

API

Is an openSource alternative available for APIs ?

Recommendation

Technology

Do the libraries used allow you to take only the components that are actually useful ?

Recommendation

Technology

Are unused dependencies identified and removed ?

Advice

Technology

Is an openSource alternative available ?

Recommendation

Technology

Are all the technical equipment used by the service identified ?

Advice

Technology

For each equipment, are the characteristics available ?

Advice

Technology

Are the functionalities related to regulated data processing (health, personal, banking) validated in terms of interoperability ?

Advice

networks

Are the latest technical advances used when they really help reduce impact ?