The stages and methods of designing digital services to define the best solutions for interactions with the user.
× Filtered by: Methodology
Filtered by:
Are the proposed functions really related to a use ?
Are you using proven development standards ?
Are LCA data reused in the event of an adaptation of an existing service ?
Are the functionalities covered by local actions (client side) privileged rather than API exchanges ?
Do you use caching mechanisms to limit exchanges ?
Is the data fed back by the APIs really only the data that the application needs when it is requested ?
Do the libraries used allow you to take only the components that are actually useful ?
Are unused dependencies identified and removed ?
Couldn't the expected functionality be implemented with the native capabilities of the browser ?
Are all the technical equipment used by the service identified ?
Is the backward compatibility range defined ?
Don't the functionalities of the service go beyond user needs ?
Are the reference elements known, kept up to date, and made available to the entire project team ?
Is the inventory of the input data made available for reuse in other projects ?
Do you limit the flows exchanged ?
Are there duplicate files ?
Is a clean version available for prints ?
Is a CSS alternative available for an animation ?
Are the fonts used not loaded only for a small number of objects ?
If printing, is an ink saving font installed ?
Do you limit the number of fonts loaded for the service ?
Are videos or animations outside the active area automatically paused / stopped ?
Is it really a user action that triggers the "play" ?
Is formatting in css preferred, to limit the use of images ?
Do all images have a text alternative ?
Are image resizing processed upstream and statically (server side) ?
Have the different image formats available been evaluated to select only the most effective ?
