Thanks for your feedback. I agree most people like to see a graphical design to judge a proposal, and that sometimes it makes no sense to put a lot of work in wireframes when you could just as well show graphic design mockups.
I (try to) use wireframes for three main purposes:
To illustrate more complex situations and flows (as you suggested too) and enable people to get a feeling for the interaction experience in an early stage.
To communicate the requirements in the project team: it gives the designers more of a sense what needs to be designed, and the programmers what needs to be build
To check we have a complete picture of the work to be done: do we know where to get the content from, how to present it, and what happens when clicking a button or link
(And it's because of points 1 and 2 I was looking for a suitable online solution that allows for more people working on the same wireframes)
Hi George, Thanks for your
Hi George,
Thanks for your feedback. I agree most people like to see a graphical design to judge a proposal, and that sometimes it makes no sense to put a lot of work in wireframes when you could just as well show graphic design mockups.
I (try to) use wireframes for three main purposes:
(And it's because of points 1 and 2 I was looking for a suitable online solution that allows for more people working on the same wireframes)