I like that the different types of users are considered. I have struggled to navigate the Mobius app myself, so I actually found this analysis very useful. The solution was well thought out and I like that a new app interface was presented. Each problem was specifically addressed, making it a thorough evaluation. The analysis is a bit tough to follow, but could be easily improved by adding titles to each section. Overall, I think this was a very thorough analysis, but slightly difficult to follow.

return to top of page

You did a really job of analyzing the different subsets of people that would use Mobius. Your analysis is really helpful with all the screenshots of the app and the comments directly pointing at the issues on that screen. I think a little more explanation with each menu item would help a bit. I feel like if you divided the analysis into the main sections of the app I would be able to follow along easier. Like have a different sections for purchasing or finding shops or finding the tools you need and then in those individual section piece out the parts you were analyzing. Mapping out solutions for each of the problems you encountered made your suggestions useful and descriptive. Overall, good job!

return to top of page

Vadim,

I thought your analysis was beautifully presented and professionally designed. The graphics are of high quality and work well to support the arguments that you are making.You present a really nice amount of detail as well.

The multiple screen captures were really nicely done, and I also thought the user interviews added a lot of dimension to the analysis that help me understand what you are evaluating even though I do not use maker spaces.

Great suggestion to start froma user-determined page (e.g. favorites). It really makes the app feel more functional than merely a presentation of raw information.

return to top of page

Good breakdown of the types of users the Mobius app serves and their varying needs. Very detailed examination of the app's functionality and how it relates to user needs by identifying five universal pain points. A potential improvement in the analysis is to identify which paint points are being addressed by each improvement, possibly by numbering the pain points and listing them by each of the dozen or so new/improved elements. A short conclusion linking the initial analysis and improvements would tie everything together for the reader.

return to top of page

The website would have been more effective had it been split into multiple pages. This would have likely made formatting easier as well. As it is, the comments seem cramped in some places. However, the color scheme is nice, and the flow charts are effective. If you added a navigation bar and multiple pages, this would be really awesome!

return to top of page

Again, I think if you separated the website into sections, the flow of the analysis would've been easier to follow and return to pages you wanted to revisit. Nonetheless, your presentation was really simple and it got the points across. The captions with arrows really helped point out what you were talking about in screenshots.

return to top of page

You transition clearly from explaining what the app does to offering your suggestions for improvement. There is so much detail, however, that I get lost in a lot of the suggestions. Some of the suggestions also seem nitpicky (when criticizing small text, I wasn't sure how much bigger it could actually be while still being aesthetically pleasing). Also, I didn't agree with all your points, such as Google Maps being useless. I've actually been quite impressed at the level of detail Google has on the MIT campus that makes it easier to use to navigate campus than a whereis.mit.edu setup. One option you can consider is bucketing the recommendations into thematic areas so it is easier to follow. Finally, I understand that the class is focused on engineering, but I'd like to see a bit more assessment of what value these changes create for the end users.

return to top of page

Easy to follow layout and logical progression. An introduction would help orient the reader. Currently the reader needs to scroll past the initial screen to piece this information together. Some of the later screen shots lacked captions, requiring the reader to infer the screen's main functionality. Overall, the analysis was clear and presentation well organized, thoroughly introducing the reader to the app and then walking through its uses and improvements.

return to top of page