3

As you mentioned before, there are trade-offs between working in high and low fidelity when it comes to creating prototypes. I can offer a suggestion that might help give you the best of both worlds - create high level task flows (so not detailed task flows) but for every deviation or new pattern from the standard UI design (based on the existing UI or ...


2

welcome. There are many ways to do wireframing. The traditional lo-fi way is helpful for getting out ideas quickly, especially across multiple pages. If you're working heavily on one page, or need something more professional for stakeholders, it's absolutely OK to add some grays / muted colors to a wireframe. I would caution that full-color gets tricky ...


2

What is the Purpose of the Wireframe and the Prototype? These are specific tools used to communicate with some key differences: The wireframe communicates a layout and information/content heirarchy The prototype communicates to user flow and transition between pages Assuming that you are getting feedback (from users and stakeholders) on the design as you ...


1

Thank you for your detailed answer, Michael. When I first read your answer, a lot of the gaps in the process and the design system were oblivious to me. I have a fairly better idea now, so I thought I’d post an update based on what I understand. Short answer: Yes, covering every flow including error states in wireframes has saved a lot of additional time and ...


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