Extra article on UI, I give here advice on the way to ensure that user interfaces have been correctly developed.

Like in the previous articles, I use a Scrum tool : the definition of done which is a contract established between the developer team and the product owner on the requirement level of developments. A feature which doesn’t respect these requirements can’t go in production.

The definition of done can evolve during the project lifetime, it starts in general from a minimal list to grow with the execution capacity of the team. Most of the time we will be satisfied with a minimal list rather than living with too many rules constraining the delivery in production. But I think that it’s important to go up in quality and then in requirement while the execution capacity of the team improves. That’s why I propose here different ladders of requirement.

Definition of done for the UI part

Base ladder:

The interface specifications are respected

The verification has been done on variations of the different possible configurations

The verification has been done on at least one physical device

Choose a minimum device set combining the different configurations to simplify

Quality ladder :

Animations

The display is fluid on a mid-range device: constant 60 frames per second

The base accessibility criteria are respected

The graphic designer validates that the integration respects the specifications (good understanding, development compromises and business adjustments)

The base quality criteria defined for interface files are satisfied

Advanced quality ladder :

Interfaces are “Pixel Perfect”

The advanced accessibility criteria are respected

The verification has been done on the totality of the possible configurations

The advanced quality criteria defined for interface files are satisfied

This definition of done is a proposition. Feel free to adapt it to your team context.

Android Developer at jacquesgiraudel.com