UX Planet

UX Planet is a one-stop resource for everything related to user experience.

Follow publication

Member-only story

5 Simple Rules For Using Images More Effectively

Nick Babich
UX Planet
Published in
4 min readFeb 22, 2019

--

Images are part of visual language product designers use to communicate with users. Images can tell a story, communicate a complex idea or accompany the text to provide more details.

The process of creating or selecting visual content for your app is time-consuming. But there are a few tricks and tools you can use to simplify this task:

1. Use context-relevant images

Each image in your design should serve a clear functional purpose.

Avoid purely decorative images

Purely decorative images rarely provide a positive experience for users — in many cases, users simply ignore them, but in some case, such images can overwhelm and distract them.

For example, many corporate websites are notorious for using abstract photos of buildings in design. The idea behind that is simple — give visitors a sense of a modern corporation. Unfortunately, such photos give zero valuable information to anyone who visits a website.

Don’t use an image because it looks nice, always think about the message you’re delivering

Test the meaning of your images

Imagery, like any other element of UI, should be tested for usability. It’s vital to test and see that the message you try to convey using images is absolutely clear to your users.

Take user emotions into account

Your images should have an emotional impact on your users. They should reinforce the feelings you are trying to create.

Text may be read and forgotten, but a vivid image has a better chance to stay in the minds of users

Taking user emotions into account is especially important when users face problems. For example, if your users get an error message during form submission, showing a smiling face a person next to error message won’t create a…

--

--

Published in UX Planet

UX Planet is a one-stop resource for everything related to user experience.

Responses (1)

Write a response