Posts

Week 7 Reflection Post

Week Seven Blog Post When thinking of my work as an actual UX proposal, it made me take my project a little more seriously. I actually imagined that people who are in need of a scheduling app for pets could have truly benefitted from using my app so I wanted to make it as comprehensive as possible. I wanted to make sure it was easy to navigate and that using it was intuitive. Prototyping is probably the one step I dreaded the most but as I kept editing my app to my liking, I started to feel comfortable with the process. It is fine if something is not perfect the first time when there are still many opportunities to fix it. Something I would do differently is not rush into UX project. I found that when I rushed into things and look back on work, there were glaring mistakes that could have been avoided if I had not been rushing. For example in my initial scenarios draft, I realized that my storyboarding was lackluster due to my captions being vague and barely going over the features of t...

Week 6 Reflection Post

  Week Six Blog Post I found that Figma made the design process for my dynamic prototype easier. To make a proper dynamic prototype, one would need advanced html coding skills and Figma's automation makes so that even beginners can create and edit their product to their liking. In my own work compared to one peer, I noticed that my app did not include "permanent" features. If one were to restore a deleted entry on the 'Deleted Entry' tab, it would not appear in the 'Active Schedules' tab. There would just be a pop-up saying "This entry was restored" even though it was not actually restored. I guess I did not initially understand how dynamic a dynamic prototype should be. I just thought that buttons should be able to react properly to show that they work but actual changes a user can make to prototype hadn't crossed my mind. It makes sense that one would create a dynamic prototype that includes things a creating a new entry or schedule just to...

Week 5 Reflection Post

    Week Five Blog Post Upon personal reflection, the biggest change I made involved making the ideas of my app more fleshed out in the revised prototype. I wanted it to be as user friendly as possible, so I had to make sure that the features I wanted within the app made sense. I considered a lot of possibilities of what a user may want or encounter when revising my creation and if something was missing that could possibly improve the usability of the app then I added it. For example, something missing was the ability to turn on/off the alarm for an individual entry that was already a part of an active schedule. In the draft, the user could only set an alarm for an entry through the 'Create a Schedule' tab or through turning on/off every entry in the 'Notifications' tab. I imagined this would be frustrating to only have the ability to access the alarm features through these tabs so in the revision I made sure that users can toggle the time alarm on/off in each individua...

Week 4 Reflection Post

Week Four Blog Post I think turning my sketches into wireframes gave me a clearer picture of the layout I wanted for my app.  The biggest uncertainty involved wondering if my app was truly navigable if I were to immediately make my first draft be the final product. I think to best curb this is to think of many scenarios or problems that a user might encounter when navigating the app and then tweaking it from there. I also have uncertainties about the notifications tab on my app. I feel that it is really barebones but I don't have any idea on how to make it better or what other options for notifications could be on my app. I learned that it takes a lot to code and understand the workings of a website. I also feel that my idea of the design of a website for a business can be totally different design wise if the idea came from somebody else. Since I used Figma, at first it created a design for a prototype I was not satisfied with for my app but I am able to tweak it to my liking. It m...

Week 2 Reflection Post

  Week Two Blog Post What I learned from my user interview script is that there is a lot of thought that goes into app and website planning. I also learned that people can get input about what to include in their app before the creation of the app entirely. I thought the client had to have a viewable representation of what something looks like before they can give their critique or suggestions. During the interview for Zoom, I was most surprised about how casual the interview was. It makes the interview more comfortable for clients to express their needs. The importance of Information Architecture is to give the creator a way to organize their ideas into draft of their product without having to create the actual product, in this case an app or website. This is to make sure that their website makes sense and has a flow and it is easy to navigate for its potential users. What I would do differently in the beginning stages of drafting is look at similar sites to recognize what parts o...

Week 1 First Post

Image
Week One Blog Post My first week back at school for the fall semester has been going okay so far. Specifically when it comes to the course Human-Computer Interaction and Usability, I feel that I am going at an okay start. During the first Zoom session, I will admit that I zoned out a lot. Not necessarily because I was bored of the material but because it was harder to pay attention when there wasn't a premade visual such as a PowerPoint to go along with the lecture. Luckily, the Zoom session was recorded so I can go back and pay attention to the parts that I may have missed or didn't understand. When it comes to the tasks and assignments for this class, I had a slightly easier time. I had previously used the virtual workspace for another class almost a year ago and still had the applications on my laptop so I thought that logging on wouldn't be a problem for me. Unfortunately, I had issues with connecting as it was constantly saying I had the wrong credentials when typing i...