Beta-Testing Feedback


Warning: Undefined variable $num in /home/shroutdo/public_html/courses/wp-content/plugins/single-categories/single_categories.php on line 126

Warning: Undefined variable $posts_num in /home/shroutdo/public_html/courses/wp-content/plugins/single-categories/single_categories.php on line 127

I sent out a survey to five people and then also included my family who had originally seen the project to get more formalized feedback. For my beta-test, I asked the following questions: What are the critiques of the overall format of the website; What do you think about the following features (Timeline, Glossary, Map Overlays); Does the project fulfill the goals that it sets out to achieve; What information about Davidson would you like/need to know to make the site more interesting.  The website that is discussed below can be accessed by clicking here.

Style

In terms of the first question regarding the overall layout of the the website,  I thought that perhaps there were too many dots and that people would not want to spend time looking through all the memories. The timeline, I hoped, might simplify this process if a user wanted to look at a specific decade. The comments that I recieved were positive about the layout and many enjoyed looking at the map. One person found the main flaw that I find with Neatline maps, which is the ability to zoom the map beyond the scope of the project, and another commented that the zoom button should be larger. One user liked the fact that the project automatically zooms in when you press a button, however, I do not like this feature and need to fix it. Another respondent had an issue with technology that prevented the satelitte image–the background of the base map–from loading. Other technological issues included a user who thought that the dots were hard to click on and see on one computer, but using the website on another computer fixed the problem.  In terms of the website layout, one respondent suggested providing a route to find the main page again after entering the map, however, I believe this issue can be more easily solved if the users just press the back button on their browser. Another user reasonably suggested that I provide more a ‘user’s guide’ on the main page to help people navigate the page.

The specific features–the timeline, glossary, and map overlays–received mixed feedback. For the timeline, many respondents thought it was not easy to use, and some were misunderstood the question and, instead of looking at the timeline on the map, went back to the Neatline site and looked at the timeline page that was incomplete. In order to solve this issue, I have removed the extra page on the website. One respondent who had seen the project previously said, “I think that the layout is a bit more navigable with the dragging timeline.” Another user thought it was odd that the Neatline timeline extended far into the future and the past (I agree) and suggested sarcastically that maybe I should include future memories as well. Still another thought (as I do) that the aesthetic of the timeline is visually unappealing because it is too wide and overwhelms the map. Unfortunately, this cannot be fixed. Although the glossary page was not meant to be accessed through the Neatline page, some users, instead of finding words that hyperlinked to the page, went and looked at the glossary in order to respond to my question.  Others could not find the glossary at all either from hyperlinked entries or on website. The glossary pages came form the Davidson archive, and included pictures and other quotes about the places. One user liked the picture aspect of the glossary, which makes me think I should add pictures to the main exhibit. Most appreciate the map overlays as a “cool addition,” but I do not think that most found it to be helpful in terms of thinking about the history of campus. One negative response thought that the overlay maps were, “Not very interesting, the old ones are kind of ugly lookig, the google map is the nicest.” One user though that the overlays are not an intuitive feature and he said, “Map overlays were really pretty cool, and helped me better relate the stories I was reading to the geography in which they took place- that being said, I wouldn’t have found it if you hand’t told me what to click.” For the same user that had  previously faced technological issues, the overlays maps were “blurred and not helpful.”

Content

In terms of content, given the responses of the respondents, I think that my original suspicion that there are too many dots is true. Many people get tired of looking through the memories and, thus, give recommendations for entries that already exist. For example, one respondent replied that he would have enjoyed longer entries about activities that occurred in specific buildings that might not take place there anymore, which is the entire point of most entries. However, I believe that his response may have been because this particular respondent moves in the science circles of Davidson that are not as prominent on the map.  Many people said they would have liked to see more modern memories although others expressed their appreciation in the historical aspect of the project. For example, a history major that reviewed the project said, “I really like the idea of being able to hear voices from on campus over the course of many years. Its a good reminder that this is a dynamic and changing place.”

Other content related feedback regarded whether the project is interesting and what information would make it more informative. In terms of the whether the project was interesting, I got feedback that ranged from responses that the project was “moderately interesting” to users who just wanted to know “Where have people made out in the last century?” One user wanted to know the source of the memory, which is something that I could include in the ‘About’ section or in a ‘User Guide.’

Conclusion

From the responses that I got, I think that I need some way to limit the user and also guide them on how to use the site. Also, because not many people were that invested in exploring the site, maybe I need to think of some way to make the site more engaging, such as including pictures with every entry, providing more maps, or entering more modern memories.

Beta Feedback


Warning: Undefined variable $num in /home/shroutdo/public_html/courses/wp-content/plugins/single-categories/single_categories.php on line 126

Warning: Undefined variable $posts_num in /home/shroutdo/public_html/courses/wp-content/plugins/single-categories/single_categories.php on line 127

After getting my project into a presentable form, I was able to send out the file to others to take a look at the app. I got both Davidson students and students from other schools even, though coordinating with faculty over the weekend ended up being problematic. There are many improvements suggested and while I would like to address all of them, some of them are just implausible with my current range of skills.

One of the complaints was about the Davidson map itself, as the image was too blurry to see well and could not be zoomed in or moved to suit the users preference. This can be easily fixed by getting a higher resolution photo and adding scrolling capability to the screen and is something that shouldn’t take too long to implement.

Another user stated that the search function was confusing. While I admit that the web viewer of Davidson’s search engine is a little clunky, unfortunately it is the only way I can present it without creating an entirely new website, which would take more than the deadline by far and would require me to learn a lot more things. I will try to adjust the into screen text to help users use the search function clearly, but aside from that there is little I can do.

Another user also suggested that the app show where a place is on the map. While motion tracking is a bit out of my current skills, it should be possible to add some cropped sections of the Davidson map to give users a better sense of where things are. I would personally hope that the directions included in the descriptions would also be help enough, and they may be since it didn’t seem like the testers spent much time reading them.

Another final point to mention is that the test did help me find one particular glaring error, where the search screen did not redirect to an existing screen. In addition, I discovered that certain settings had to be unlocked to allow the app to work since it was being read as a “third party source.” I do not think this would be the case for an official version of the app, but I am at least now aware of the process.

 

PA 9 – Beta testing responses


Warning: Undefined variable $num in /home/shroutdo/public_html/courses/wp-content/plugins/single-categories/single_categories.php on line 126

Warning: Undefined variable $posts_num in /home/shroutdo/public_html/courses/wp-content/plugins/single-categories/single_categories.php on line 127

As I described in one of my previous blog posts I sent a questionnaire out to 10 participants. I received feedback from six over the weekend which I believe is enough to record my results.

Overall there were positive responses to my questions on functionality. Every button worked and every picture loaded, but I found a variety of critiques on the ease of use of my project. For the participants I sat down with I found myself explaining what to do a lot of times. One suggestion, that could go under style was to have each feature loaded in the sidebar as a waypoint, that way no one would accidentally skip over some features (which many participants admitted did happen).

In terms of the authors intent, the participants suggested that I place a blurb at the beginning of the neatline exhibit explaining the intent. While a few participants read through my introduction and literature review on the other exhibit pages, others admitted that those were a little long to read for a website. Many that I sat down with understood the intent once I explained how to work the neatline exhibit, but finding a way to limit my need for explanation would be helpful. I have instructions at the bottom of the exhibit but, again,one participant suggested for them to go at the top. While this is an excellent suggestion, I am not quite sure how to do this.

The questions that received the most feedback were the ones surrounding style. One suggestion was to include a variety of the images I have collected throughout my project. Because I have these already digitized, the participants argued that it would make the text seem a lot shorter if there are images to accompany it. While I do not agree that it will make the text shorter, adding pictures will add context and another visually appealing aspect. The trick now is to figure out how to add images without it getting to cluttered. I had a lot of feedback about the timeline feature. While I thought it was extremely cool that the participant was forced to scroll through time and various maps would pop up, one participant found this confusing, one was not sure when the chapters switched, and one admitted that she could not figure out how to use this feature. One participant suggested having each chapter available on the sidebar or make them visible on the actual timeline itself. While I was against putting them on the sidebar at first, the participant had a convincing argument. They said that although I want my text to be read in sequential order, one of the most powerful parts of my project is comparing maps from time periods that are very far apart.

The most useful feedback I received about the storytelling part of my project goes alongside functionality. For two participants it was their first instinct to click on the chapter title instead of introduction first. While I said in the instructions to select introduction to begin the story, two participants said that instinct will probably win over my instructions. With that they argued that my story would flow very well if I had the introduction be a part of the chapter title. I believe I want the introduction to be a separate step, but I think labeling each feature with numbers could direct the audience towards the linear story. One thing I don’t particularly like about that idea is that its interesting to click random features because many developments happened at the same time, and it allows for more interactivity. In all, the thing I will take from the suggestions about storytelling is that people will click on the chapter title first, and to make that an opening picture or statement about that chapter.

Many participants liked the interactivity of the project. One problem people ran into was the project looks different on different sized computer screens. For example, the project is very visually pleasing and easy to navigate on a school desktop computer, but a personal laptop was harder to see and click through buttons. I am not sure how to fix this besides explicitly saying that in the instructions. One participant did use her iphone with it which proved to be a huge disaster. Overall, all participants enjoyed clicking through the features, but mentioned that scrolling through the timeline was tedious. When I thought scrolling through years in seconds would not be tedious, I did not see the extra work it took participants who could not figure it out.

Lastly, I received interesting feedback on the purpose of my project. 8 5 informants said it added to their understanding of Davidson’s history and 1 said it added to their understanding of Davidson’s landscape history. This response was troubling to me. My purpose for my project was to examine social and landscape changes and how they are related, but I believe the environmental aspect was lost in the website. I think one way to fix this would be to explicitly state when I am talking about social changes, and when I am talking about landscape changes. Almost every introduction mentioned only social changes so I could rewrite that section to explicitly discuss social changes instead of presenting it as an overarching introduction to each chapter.

Along with purpose I added one question on my proposed map on the ideal Davidson. As I have already created this map I know I can add it easily, but I asked various participants what they thought and what they thought it would add. Overall 5 participants suggested that I leave the map out because it will not add to my overall purpose. 1 participant suggested that I put it in a different neatline exhibit. Because I want to spend my time making the best exhibit possible, I have decided to leave out this aspect of my exhibit. Hopefully this decision will not be a bad one.

In all, I received a variety of helpful suggestions which I plan to implement in the next few days.