The eye behind the interface
What photography can teach us about attention, restraint, and designing software that feels intentional.
A photograph and an interface make the same request: look here. The difference is what happens next. A photograph can leave a question open. An interface usually owes you a way forward. That tension is what makes photography such a useful lens for thinking about software—not because every website should resemble a gallery, but because both disciplines involve choosing what deserves attention.
A frame is a decision
Imagine photographing a person beside a busy road. You could include the traffic, shop signs, and every passing pedestrian. Or you could move a little, wait for a gap, and let the person become the unmistakable subject. Nothing has been added to the scene. Its meaning has changed because its boundaries have changed.
An interface offers the same opportunity. A project page does not need to introduce the technology stack, biography, contact form, and every project screenshot at equal volume. First establish the problem and the result. Let supporting detail arrive when the reader needs it. The design question is not merely what belongs on the page; it is what belongs in this particular moment.
Contrast creates a reading order
When everything is bright, large, and moving, nothing feels important for very long. A quiet surrounding gives a strong element somewhere to stand. In a photograph, that could be a lit window against a dark building. On a writing page, it could be one generous headline surrounded by restrained metadata.
Try a simple exercise before adjusting colours: describe the intended reading order in a sentence. “Notice the title, understand the topic, then choose whether to read.” Now inspect every visual decision against that order. A decorative badge that attracts attention before the title is competing with the purpose of the page, even if the badge is beautiful.
Interaction is a change of viewpoint
Hover and scroll can reveal relationships, but they should not be required to understand the content. A project thumbnail might shift slightly to acknowledge focus; its title must already be visible. A photograph can open into a larger view; its description must not depend on the cursor finding an invisible hotspot.
This is also where the analogy has limits. A photograph is a fixed composition. A website must survive a narrow screen, larger text, keyboard navigation, and different motion preferences. The frame belongs partly to the visitor. W3C's guidance on interaction-triggered animation is a useful reminder that expressive movement needs an accessible alternative.
Leave room for the subject
My preferred test is subtraction. Remove one flourish and ask whether the content becomes easier to see. If the answer is yes, the flourish was probably asking for attention it had not earned. If removing it erases character or useful feedback, bring it back with intention.
The aim is not a completely silent interface. It is a considered one: enough personality to feel authored, enough restraint to let the work remain the subject.
Further reading: W3C: Animation from interactions.