Focus on user benefitsĪnnotations shouldn’t just focus on the element or what it does. When using annotations, visibility is key – you don’t want the viewer to mistake the numbered icons as part of your UI. Notice how the red numbered icons are visually distinct from the black and white color scheme of the wireframe. ![]() ![]() Rather, focus on the minimum number of words to communicate your point effectively.įor instance, the annotations on this wireframe might seem wordy, but every sentence actually contributes to the overall explanation. But don’t make them too short either, to the point of being vague.Ī good approach is not to base it on length. If they’re long and rambling, they might confuse your audience even more. ![]() Remember, they exist to clarify your wireframe. Here are some best practices to consider: Keep annotations shortĬonciseness is a key characteristic of a good annotation. Best practices for creating wireframe annotationsĪnnotating might seem simple, but they are easy to get wrong and risk further miscommunication. The act of documenting also forces you to think through the process. It allows you to record every thought and logic, so you don’t forget. Unless you document everything separately, you’ll begin to second-guess your wireframe.Īnnotating as you’re wireframing is the better approach. You might forget why you included a certain element or how it’s supposed to behave. ![]() There are two approaches on when to do annotations-during or after wireframing.Īfter wireframing seems like the obvious approach, but it has its shortcomings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |