Photo by Abdelrahman Sobhy on Unsplash

This week, (well I guess technically last week, what even are weeks now during times like this), I started working on the beta usability test report as well as some CSS and text changes. My development environment was very behind and broke for some reason, and it took a bit too long to fix it. Installing TypeScript globally, doing a fresh node installation by deleting package-lock.json and node_modules folders, etc. More CSS change to come hopefully to make the web app a bit more mobile friendly but we’ll see. Shoutout to my teammates for being so supportive!

--

--

Photo by ShareGrid on Unsplash

This week I finished up the redux files to serve mock data to the browse page. Unfortunately, the team realized that the filter bar caused complexity we did not expect. Also, course evaluation data has some professor last and first names switched for one of the summer semesters, which created some issues with our reliance on the data for professor names. I also helped start the demo video by brainstorming the slides for my teammates to build on, and provided input when creating the script and final video slides.

--

--

Photo by Cookie the Pom on Unsplash

This week I started on my task of displaying the browse page info with mock data using redux. Redux and its associated parts (thunkers, dispatches, reducers, stores, actions) are a bit new to me, so I’m learning. My teammates said to refer to the other parts of our codebase for examples, so I will go from there.

--

--

Photo by Sabri Tuzcu on Unsplash

This week my group met up once more to assign tasks for the next iteration. Because we presented last week, this iteration has a 2 week development time instead of 1 week. I decided to take a break this week from this course to reallocate my time to other courses. See you next blog!

--

--

Photo by 傅甬 华 on Unsplash

For this week, my group came together to create our minimum viable product. Why do we only have one week to complete this? Why were we not one of the groups that signed up 30 seconds after the presentation schedule sign up link was posted?

Based on our project design document, we created and assigned issues/tasks on GitHub. Overall, I think we did a good job communicating and fulfilling our assigned tasks.

I contributed to the front-end components for the course page and the slides for the demo. Most of us were not prepared or expecting to create a minimum viable product in only one week. Hopefully our panik will be rewarded by kalm for the next iteration.

--

--

Photo by Scott Graham on Unsplash

For this week, my group conducted remote usability tests using our low fidelity prototype. I was responsible for assisting in the note taking process during the test sessions. After all the test sessions were completed, I wrote a quick draft of the usability report, (e.g. summarizing the procedure and results), for my team to build upon. Did users find our prototype intuitive? Were they able to complete the tasks easily? What went wrong???

We are still currently working on the usability report and project design document. During our meetings, I contributed suggestions towards the project design document, and also helped to finalize design changes based on the usability feedback from the test sessions. I think the main problem we currently face is creating and delegating reasonable sized technical tasks in a logical manner that fits well into our time constraints.

--

--

Photo by Visual Design on Unsplash

For this week, my group tried to create a low fidelity prototype and tasks for our potential web application. What should our users see? What do the users want to see? Where should what be?

We had an idea of what would look best based on our competitors, but not…

--

--