## Administrative details

### Client name:

IPD workshop helpers

### Website name:

Leoprint

Go to the website!
P1 requirements
P2 design
P3 changes

## Problem scenarios

We gave some of the testers a problem scenario to observe how they navigated the site to solve the problem.

- You have made a CAD-document you want to 3D-print. You thought you knew how to do it, but when you went to put on the printer something went wrong and the 3D-printer did not start. You want to get help. Use the website to fix your problem.
- You are new to the industrial design program and you want to use the 3D-printer for the first time. You have heard about the website and you want to figure out how the 3D-printers work. After you figured it out you want to book a printer.
- After you figured it out you want to book a printer. You have 3D-printed something you are proud of and you want to show your design to the rest of the study program. How would you do that?

## Tester Audience

To get valuable feedback on the website, we needed to test people from our user group. The website is targeted at students from the industrial design study program, and for that reason we gathered most of our interview objects from here. We did live testing because our user group is easily accessible, and we considered live testing to give us more valuable feedback than sending out a general questionnaire. We went into different classrooms and asked if people were interested in testing the website. We experienced that people generally were positive to help us usertest. In addition, to get an outsider's point of view, we tested the website on some people with no previous knowledge with 3D-printing to make sure that our website is user friendly and easy to navigate through. In total we tested 8 students, half of which was design students.

The user testing was executed by giving the test objects different problem scenarios that they were going to solve. We also did some tests where the tester was free to explore the website without any directions. While the test objects navigated through our website, we observed them and asked them to talk freely about what they were thinking and why they did what they did. We took notes of their feedback and asked them questions during the testing if their thoughts or choices were unclear.

## Testing Platforms

We wanted to test our website on different devices to make sure that it worked for everyone. Therefore we made sure to test it both on Mac´s and PC’s, as well as testing it on screens that fit a PC screen, a tablet screen and a phone screen. We tested the website both on Chrome and Safari.

## Feedback Summary

### General feedback

People commented that our website is aesthetically pleasing and seems well thought out. one commented that you can see that we as a group have worked hard to make the detail perfect.

> "I like that you always have access to the main menu, either through the navbar at the top or in the hamburger menu when the window is small."

We got comments on nice layout, cool dynamics, the navigation is working smoothly, and could be more colorful.

> "I like how the text in the navbar moves when you hover over it."

People seem to like that the big text in the background stays fixed on the site when you scroll.

> "The animation on the burgermenu was cool"

> "The website is intuitive, informative and easy to understand"

One test-object the “hide form” button should say “back” instead.

When you send a form you get a default window with the message. It would be better if this was a pop-up on the website which matches the website better.

It is nice that you always have access to the menu.

When testing the website in Safari, the “select” tabs in the forms were not styled according to our intentions. The calendar input was not centered or the right color when using Safari.

### Booking and calendar

Even though you choose the time and printer in the calendar you still have to choose it when you fill out the book form.

> "Adjusting time is insanely cumbersome. one needs to use the drop down instead of using the keyboard. Autocomplete is appreciated."

One tester did not like how the tab function selects the box below instead of the next to the right. The tab function also jumps over the “date” box.

A suggestion to the booking calendar was that you should not be able to book a printer for the whole day.

### How to print

When the window is wide, point 8 under “get started” shows next to “what you should think through”. This is confusing. When the window is small it shows underneath as it should be, so it is less confusing.

### Gallery

The site loads a bit slowly. This is not the case when using Safari.

Everything is called “name of project”. The test-object is not sure if this is unintended.

Links to the source to the pictures should open in a new tab.

## Your Response

We could implement the suggestion of getting the information from the chosen time in the calendar to the form when booking a printer. The reason we did not do it this time is because it was challenging and we ran out of time due to other challenges we prioritized.

The gallery site loads a bit slow because the image sizes are too big so we could have used smaller image files to solve this.

We did not check the website in safari and did therefore not discover that the form style did not apply to the select elements. if we had noticed this earlier, maybe we would have fixed it.

The form validation only worked just before the end of the project and this is the reason why it is only a default message and not a pop up on the site. This would take some more time to figure out.

The details commented during the testing could be implemented in further work on the site if it was to be published.

## Self-reflection

During this project we have learnt a lot about HTML, CSS and JavaScript. We have learnt that there are a lot of functions that have to be a part of a website to make it responsive, interactable and user friendly. None of us had any previous experience with GitHub, but we discovered that it is a very helpful tool when you want to write code together. We also learnt more about how to connect several different HTML, CSS and JS files together, which we consider useful for the future.

We put a lot of our time and efforts into this project and we are proud of the results. It was a lot more time consuming than we first thought but have learned new things about ourselves and each other and valuable things we can use in group projects in the future.

We feel inspired to further develop this site to work 4 realziiizzz so Leonardo can use this and not the awful exel sheet in use now.