The stages and methods of designing digital services to define the best solutions for interactions with the user.
× Filtered by: Volumetry
Filtered by:
Is the deliverables's output (documentary production included) used upstream of the project and is it produced to allow it to be reused in subsequent projects ?
Does the service work with weak connections ?
Are the features used by the user ?
Are an archiving schedule and a lighter version of the old searchable content implemented ?
Does the user experience take into account possible changes to the service (adding / removing features) ?
Is a systemic approach method implemented, handled by the actors and associated with tools ?
Has the solution been prototyped upstream, with the user journey and interactions ?
Have user's behavior and feedback been examined to best meet their needs ?
Have the most frequent searches been investigated and submited so that they are either cached or displayed to the user without sending unnecessary requests or clicks. ?
Is a media management / use policy in place to reduce their impact, with criteria for media compression and formats ?
Are the number of fonts and the variants of fonts called (weight, characters used in the project) limited ?
Can the functionality be offered without calling external scripts or libraries (JS, AJAX, ...) ?
Can the native system features and components match as needed ?
Are videos and animations only used when they add value to the user ?
Are the images optimized for their functions ?
Have the notification of all machine / user interactions been taken into account to systematically give the user the result of his actions and manage errors ?
Are each of the actions initiated by the user ?
How well is the user's attention controlled by the service ?
