Tag Info

Hot answers tagged

7

No, it's not always necessary. System-defined screens are not obligatory, and there is no need to reproduce clone pages/elements with minor changes. Alternatives to hi-fi prototypes are lo-fi wireframes, user journey maps, PRDs. Yes, paper sketches/prototypes are legitimate prototypes if they are detailed enough and capture/highlight on all important parts. ...


2

You're right that one practice might not suit every single company. What's more, it might even differ from dev to dev. The simplest way you can go is just ask the devs what's their preferred way of working. Some people hate having someone else looking at their screens, while others may have lots of questions and would rather have you around. It varies from ...


1

Just to add to the other answers, you should actually avoid making the mocks look finished until the functionality is also finished. To quote Joel Spolsky: If you show a nonprogrammer a screen which has a user interface which is 100% beautiful, they will think the program is almost done. (source) To this, I would add that even people who aren't ...



Only top voted, non community-wiki answers of a minimum length are eligible