![]() ![]() ![]() The boxes represent what the user sees on the screen. ![]() Let's break this user flow down a bit more. Your low-fidelity wireframes should capture the essence of the conceptual experience, but not all the detailed interactions at this point. What information needs to be conveyed to them and/or collected from them? If you are still stuck, try thinking about the specific problem you are trying to solve for the people who will be most affected by your idea. This is the best-case scenario where someone accomplishes the goal you want them to achieve using your website or app. You start with what we call the happy path. Then, think through the flow of how you want that person to accomplish each goal. One trick is to think about the goal or goals you want people to achieve on your website. The important thing to think about is what makes your product different. This could be just a couple of screens, 1 or 2, or maybe 10. Wireframing your product’s key screens should be the first pass of your interface design, making the highest priority screens the most visible in your first version of the design document.Īsk yourself, “what are the screens that are essential to our product that make it unique from another product?” Don’t think of login or register screens at this point (unless you are a security firm □). Key screens are the interfaces that convey the essence of your product or service. Wireframing your product’s key screens should be the first pass of your interface design. Key screens convey the essence of your digital product or service. ![]()
0 Comments
Leave a Reply. |