I'm prototyping a couple of fairly complex web screens. Each field in these screens has its own label, description, and a question mark (?) icon next to it —The question mark icon displays additional information and examples when clicked.

I'm trying to decide whether the description and the help text in the prototype should be the actual content I mean to have in the end result —as opposed to just some lorem ipsum.

On the upside, it would make the prototype a one-stop shop for the developer. But on the downside, it feels an awful lot like hardcoding. In SW development you always decouple the UI from the text using i18n files of some sort. Should the same apply to UX design?

2 Answers 2


Use some representative samples for description and help text

I think it will be a lot of work to keep those pieces updated. Pick representative samples of text for description and help text and use them throughout your mockups. This way you can see if the layout works with the length of the text and you give the developer a hint what kind of text needs to be there.


Always use real content if possible. If you don't your design might look weird when the actual content is added. 'Content is king'

Aside from that any testing you'll do will be more valuable as it is more realistic.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.