Maze Compatibility (April 27, 2020)
In this week’s reading I learned about creating a user flow diagram. The
user flow lays out the user’s movement through the product, mapping out
each and every step the user takes— from entry point right through to
the final interaction. It is a visual representation that lays out every
possible scenario or outcome in order to achieve its desired end goal.
Each touch point is represented by a visual image or shape. People use
user flow designs in order to help them understand how heir app will be
navigated in the hands of the actual consumer. There are several types
of flowchart/diagrams used for creating good user flows: task flows and
wireframes (or sometimes, people can combine them in order to show the
multiple outcomes produced)
The quote I really found useful comes at the end of Cameron Brown’s online article “What Are User Flows In User Experience (UX) Design?” by emphasizing that “The mark of a successful app or website is in the intuitiveness of its design.” I take this to mean that the design of the app will become successful and used often by consumers if the app itself doesn’t cause problems or confusion, allowing them to visit the app or website again and the likelihood of receiving great and/or positive feedback.
In relation to my project and app, I decided to create two different user scenarios that relates to the project-style app that I am currently working on for class. Despite the majority of the class guiding me to the virtual study group app, I talked with my teacher and finally decided on doing it based on the second of the 101 Mobile App Ideas listed from the article a while back: a digital mall navigation app that will store a digital map of all the shopping malls in an area.
I’m giving it the title of “Labirynth” for now until I come up with a better one.
Since I mentioned user scenarios, I have to explain what they are. Well, it’s not that hard to explain as scenarios explain themselves. Scenarios describe the stories and context behind why a specific user or user group comes to your site. They note the goals and questions to be achieved and sometimes define the possibilities of how the user(s) can achieve them on the site. There are different types of scenarios, but the one I am going with and choosing for my project is a goal-or-task-based scenario, which are scenarios that emphasize what you want the user to do, and how many steps (or touches) it requires of them to get from point A to point B.
The quote I really found useful comes at the end of Cameron Brown’s online article “What Are User Flows In User Experience (UX) Design?” by emphasizing that “The mark of a successful app or website is in the intuitiveness of its design.” I take this to mean that the design of the app will become successful and used often by consumers if the app itself doesn’t cause problems or confusion, allowing them to visit the app or website again and the likelihood of receiving great and/or positive feedback.
In relation to my project and app, I decided to create two different user scenarios that relates to the project-style app that I am currently working on for class. Despite the majority of the class guiding me to the virtual study group app, I talked with my teacher and finally decided on doing it based on the second of the 101 Mobile App Ideas listed from the article a while back: a digital mall navigation app that will store a digital map of all the shopping malls in an area.
I’m giving it the title of “Labirynth” for now until I come up with a better one.
Since I mentioned user scenarios, I have to explain what they are. Well, it’s not that hard to explain as scenarios explain themselves. Scenarios describe the stories and context behind why a specific user or user group comes to your site. They note the goals and questions to be achieved and sometimes define the possibilities of how the user(s) can achieve them on the site. There are different types of scenarios, but the one I am going with and choosing for my project is a goal-or-task-based scenario, which are scenarios that emphasize what you want the user to do, and how many steps (or touches) it requires of them to get from point A to point B.
Comments
Post a Comment