The stages and methods of designing digital services to define the best solutions for interactions with the user.
× Filtered by: Value creation
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 ?
Is the target audience of the service determined with respect to their ability to use the service ?
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 ?
Will older equipment remain compatible, and within what limits ?
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 ?
How many different domains are used ?
Are the sensors being used as needed, rather than constantly ?
Are the pause functions available ?
Do you inform users of the size constraints and accepted file format ?
Do uploads only allow the list of authorized file types ?
Are the images to be uploaded properly resized and converted to a thin client-side format before transfer ?
Is fast navigation possible ?
Is the service suitable for different accessibility media formats ?
Is the service developed in accordance with RGAA recommendations ?
