While designing for our user I realized how difficult it was to prototype the various functions of an app. To most people who use their phones every day, we don’t realize how much thinking was done behind the simple calendar app or even Instagram. I had to think about the tiniest details that a person goes through while using an app. For example: how accessible are the different functions, what display is most visually effective, how many options should the settings have, what sort of symbols or shapes should be used to indicate direction/another function, etc.? There could be many features for an app so my group had to brainstorm and narrow down the important features. We had to make sure that our app design met our user’s needs. For example, a calendar function was necessary to input to do lists and homework, a reminders function to help our user stay on task, a start button for the holograph function, a blocking system for social media etc.
My perspective of design has changed based on the testing of prototypes that we conducted with our classmates and our user. I noticed what we design doesn’t always translate the same way to another person. We need to be thinking about different scenarios where the product is being used and think about obstacles to the design ahead of time. The low res prototype building helped my group think about design in terms of practicality and a product that can be easily brought around. Since we don’t actually have the app made, our group used illustrations to depict what each function would look like on a phone screen.