#fredrikhallsmar

[a2group]

Final presentation

Today we have been working on the final presentation coming up this Friday. We also made some minor changes in the prototype after evaluating think-aloud analysis.

Presentation

[a2group]

Think-Aloud observation and analysis

Setting: Desktop computer Events are noted < > and thoughts ""

"Ok, so I can use this to get information on how to use the application" < User identifies the information screen as a tool to acknowledge how to interact with the application > "Placeholder feels awkward so I have to read the text under." < User reads first information > "Tap to toggle information boxes". < Instantly toggles the information box by clicking on the information box > < Sees the small detail buttons on items > "Can I click this?" < Clicks > "Aha" < Clicks out of detail > "Why is it at him?" < Notices all the detail buttons > "Aha So you can know more about specific items" < Tries to click on different detail buttons > < Clicks on bottom right information button > "Tap on box to show details, aha" < User is confusing toggle info boxes with tap on box to show details > < Toggles out of information and clicks to show detail buttons > < Toggle information > < Reads information again > "Aha you can zoom also"*

* Zoom is not supported by computer.

Short analysis: User instantly starts interacting after just reading first instruction frame. User confuses toggle info boxes with the actual information screen. This could probably be be fixed by renaming information screen to instruction screen to minimize confusion. Information boxes could be renamed detail boxes. User first tries to click on detail boxes but not until reading the instructions the 3rd time he thinks about zooming the picture. This should be considered since one of the main features is interacting with the painting by zooming. Another thing to think about is that It's not obvious for the user that the detail boxes give's the user more information about object. This should be rethinked and we should consider different buttons. Lastly, we should implement illustrating pictures for the instructions since that could make the user understand the instructions more quickly and clearly.

/ Fredrik Hallsmar

[a2group]

Presentation

Today we have been working on our first presentation for the exercise group.

You can view it here:

Presentation

[a2group]

Today we have worked on our main scenario for the presentation coming up in two weeks.

Here is the result.

[a2group]

First interactive prototype

After receiving and reviewing feedback we started editing the previous sketches. After deciding about every detail we started developing an interactive prototype using http://proto.io. Here is the prototype so far:

Prototype

[a2group]

Evaluation of group a1's project

Today we have evaluated a1's product concerning an application with museum objects prior to a museum visit. We brought forth the following feedback:

Good

They had a clear design and layout.

The concept was good and we expect the users (teachers, guides and students) to use it more than one time (as long as the material requirements of having computers/tablets are met).

The functionality was well adapted and felt central in the product.

Could be improved:

We felt that the "mini-games " took the focus away from the main purpose of the product. We thought that it was an unnecessary addition to the product because there was no clear proof that it would make the target group more interested.

It was unclear how much guides and teachers were involved in the product. The guide's role in the entire thing was mostly missing due to not having made his/her interface.

The concept is not applicable to smartphones due to size constraints with the platform. A computer or tablet is a must for this to work.

[a2group]

Final Static Design Decision

After a group voting a decision has been taken. We will proceed with the buttonless design. We have also prepared a few Powerpoint slides for the presentation on Monday.

[a2group]

After discussing both designs last meeting we made two lists of good and bad things with each design.

Good things:

+ Few distractions. Enable the user to focus on the task.

+ Easy to use with familiar gestures.

+ Modern UI.

Things needed to be improved:

- Language support.

- Instructions.

- Screen size.

We first considered the instruction issue and came up with a solution that uses a dialog box when screen is in idle (screen automatically switches to idle mode after x seconds without user). Another issue was the language support. The first prototype only supported English but since Swedish is a language that our target group uses we wanted to add it. At first we considered having language buttons in an instruction dialog box or in the bottom right corner, but since we want to minimize button usage we instead chose to take advantage of the screen width. By putting both Swedish and English information in the detail box we fulfilled our goal. The above pictures show the final result of our prototype so far.