The app works very well for the pre-visit scenario.
To prepare the visit, they are mainly interested by (in order of preferences): 1) Visitor information, 2) Exhibitions, 3) Collections.
To prepare the visit, all users have clicked on Visitor Information. This option seems to be mainly the first place to go when entering on the site for the first time. Information expected: museum location, how to get there, feeds, special discounts, opening hours, holidays, contact information.
Some users expect to see info about the contents of the museum on Visitor information. But this is not critical: they also understand Collections and Exhibitions options.
The most of the users are interested by Exhibitions. They arrive only at the first level, to see what exhibitions are currently on. The most of them don't go deeper.
Collections is clicked by only some of the users. Some of them point that they'd like to see some highlighted works here, instead of browsing the entire collection. They'd like to have some suggestions from the musem.
Enter Object Code option isn't understood out of the museum.
In-museum scenario
Localize objects on gallery map is missing feature--how do I find objects I collected within the museum.
In front of an object, they need to access quickly and easily to the information about the object. They don't need a lot of information. Looking at the artifact page, one user told us: "I imagine myself at the museum, in front of the object, with my two kids running around, my wife, trying to decide between so many options... it's crazy! I need to see the basic and that's it!".
When at the museum, users recognize clearly the function of Enter Object Code.
Some of the users miss the submit button.
Recommendation: use same icon for object code entry as on tombstone label
When asked about improvements, the most of the users say that they'd prefer a 3D code bar reader or RFID instead of entering a code to see info about the object.
Scenario independent annotations
Users are confused by the options that don't relate to their current location. It seems to be important to distinguish clearly the out-of-the-museum and in-museum scenarios, and refine the information the app gives to the user in each situation.
All the users say to be satisfied by the amount of information they find. They wouldn't add anything, but would remove some options and information that they don't look at.
Some users miss information about authors or artists at the museum.
Users would like audio and video content directly from home page.
Would like pre-determined tours--especially choose cross-cutting across different galleries highlighting a particular theme. Location-awareness.
One user's recommendation: allow switching between languages per page.
When entering for the first time, the users are really confused by MyCollection and Enter Object Code. Some of them also wonder about Settings.
MyCollection confuses the user when he hasn't yet collected anything.
For post-visit, people expected to find artifacts they collected on the device.
Lacking a conceptual model of how session/login should work.
Exhibition
On Exhibition Browsing, users don't understand the "event today" alert.
About...
At the Exhibition home page, users look mainly at About... They expect to find there all essential information about the exhibition.
Some of them even expect to see here the highlighted objects.
At About... attention is focused by the image.
To know exhibition fees, aprox. the half of the users go back to the home page, without noticing the alert at About...
Some users comment to state clearly if special feeds are added to general ticket prizes.
In general, the most of the visitors seem to have enough with the info that's shown on the Exhibition home page, and only click on About... if they want to get more information.
Guests' book
Users recognize easily the function of Guests' book. They look really interested to read general comments about the Exhibition.
Catalogue
Users don't mind about Catalogue. They don't enter there until we propose a task.
Some of the users have told that they'd prefer to have some recommended artifacts directly at the exhibition home page.
Events
A user told he'd prefered to interact with a calendar to select a day.
Users don't recognize the icon to send an event to personal calendar.
Audio and video
Users don't seem attracted by seeing video or listening to audio about the exhibition (curiously, the inverse happens for the artifact's page).
Artifact's page
Users are mainly interested by the image and the Audio and Video panel.
Some of the users don't have a clear idea about the function of the arrows over the image. The most of them thought that serve to go to the previous-next artifact.
Related objects
When asked about related objects, almost all of them click on "Show related objects".
Users like this option.
Some users propose to include objects not in gallery (will need to highlight objects in gallery differently).
Only few of the users are interested by what other visitors enjoyed. It can be dued to a design problem (users don't see clearly where this list comes from, what is the criterion followed, if are the most rated objects in general, or the most rated related to the current object, how can users rate objects, etc.)
Comments
The option Comment at the top of the page is quickly perceived.
The users are not very interested by seeing others' comments on the object (although they were really interested by comments on the Exhibition).
Tags
Users are not interested at all by tagging, or seeing other's tags.
Some of them don't understand where tags come from (from other users, from the museum?)
One tester (conservation technician) found it useful as a launching point to put artifacts into collection.
Two users said that they would tag only objects in their Collection.
Collect and Send options
Send option is used both to send the artifact to friends, and to remember the artifact.
Collect option is not clearly understood by some of the users [it can be dued to a label problem].
A tester (administrative) said that it would be easier if he could mark directly at the objects list when browsing.
The same tester (administrative) said that he'd like to be able to send objects to his Facebook (or similar).