Back to journal

Explain why an application video is unavailable

On November 1, I changed the application-detail view in Seasonal.Work to distinguish three situations: a candidate had no application video, a video was available to the employer, or access to the video was restricted by the employer's plan. Those states should not produce the same blank space. The interface needs to explain the difference without making an unavailable action look usable.

The change added an explicit explanation for the restricted state. An employer sees a short note about the plan required to watch the application video, rather than a link that cannot provide the expected experience. When there is no video, that note is absent. When the video is available, the existing action remains. The rest of the applicant's information, including an available CV link, does not disappear simply because the video has a different access condition.

The distinction also belongs in the data used by the screen. I connected the restricted-state indication to the view so it could decide deliberately which action to render. The restricted case does not keep a hidden player behind the explanatory text. This keeps the visible message and the available interaction consistent. It also avoids confusing a plan limitation with a missing upload or a failed media request, each of which would suggest a different next step.

The accompanying cases cover an available video, no video and restricted access, including the explanatory note and the continuing CV action. The November 1 implementation was later integrated on November 13. Those are separate dates: the work described here is the earlier application-detail change, and integration does not by itself demonstrate a live employer session.

Reflection

A useful empty state explains what is absent and why. In Seasonal.Work, distinguishing unavailable access from missing content makes the screen more precise without adding another workflow or changing the candidate information around it.