Format: PDF / Kindle (mobi) / ePub
Learn the fundamentals of designing the user experience for applications and websites
About This Book
- Get up to speed on the industry standard design process
- Learn how to architect your product with task flow diagrams
- Create wireframes with real world examples
Who This Book Is For
Whether you are looking to become a professional UX Designer, or just need to get the job done, the principles and processes discussed in this book will help you understand how to craft reliably effective and successful design solutions.
What You Will Learn
- Generate interaction maps and task flow diagrams
- Create wireframe design proposals
- Interact with clients who need design services
- Understand your users with by creating personas
- Establish design tenets that will help you stay on the right track
- Quantify a design solution using heuristic evaluations
- Ensure your brainstorming sessions are successful
- Get started with the design process with the help of user survey and focus groups
- Use paper prototyping and other testing techniques to help you predict success
Designing the user experience (UX) for websites and applications can be an exhilarating and satisfying experience, but it can also be a chaotic and frustrating endeavor. The key to success lies in a thorough understanding of the industry standard design process, and in possessing a firm grasp of effective and proven UX design techniques.
This book is a comprehensive, yet concise, primer for those looking to better understand the core principles of UX design. It illustrates these principles with example projects, warns you of common obstacles, and introduces you to proven methodologies that help facilitate your efforts to find design solutions that work.
This book will put you on the road to becoming a UX designer by teaching you the process and techniques used by design professionals to create world-class applications and websites. This introduction to user experience design will instruct you on the required research and groundwork that will help you cut through the ambiguity commonly experienced when starting a project. It will show you how to turn the results of your research into task flow diagrams and wireframes that will be used to evolve your designs into solutions that will work for all of your customers and users.
think through everything we should have, or perhaps there was some data we didn't have access to. We should attempt to keep our minds open when this happens (and it will happen). We do ourselves no favor by staunchly defending a solution that is not comprehensive. Sometimes we have to back up and try again. This is especially true when new features are added to the project, or when unexpected complexities are found in a particular task flow. I am of the opinion that if we define and consider all
invitations to other parents, players, and league representatives to install the app and join the team roster. Selecting the "League Rep" account type will offer the ability to create and manage leagues and multiple teams. It's natural to discover elements and features we didn't account for in our flowcharts as we dig into the wireframe details. The more thorough we are while developing our interaction maps, the fewer revisions we'll have to make later on. Here are a few things to consider when
adding more content to the page, but it is also counterproductive to our ultimate goal of completing the sale. Offer the user several links out of the checkout process and they will be more likely to abandon their shopping session. In addition to the checkout process, we will likely want to remove the navigation on tasks that require multiple screens or pages to be completed. If the user is midway through entering their data and they navigate away from the page, we'll need to stop the experience
will require us to crawl through the entire site or application documenting what was executed well and what requires improvement or a full redesign. We then follow up with suggestions about what needs to be done to improve the problems we have pointed out. As we document and eventually present our findings to our client, it is important to remember to be kind. We don't want to be overly bold or critical of the flaws that we have found. Offending our client at this stage will likely be
will have a direct and relational impact on the quality of the solution we create. Rushing to design a solution without key details, such as who our audience is or what features they might need, will mean a lot of guesswork that may or may not succeed. I always like to think of it as if you want it bad, you get it bad. Regardless of the methodology we are working with, it is essential that we include research time into our development and design plan. Information architecture We transition to