Anda di halaman 1dari 7

Suite X on Device Y

SUMMARY
This study focused on evaluating the core touch scenarios for reading and reviewing documents and creating and completing documents on a Device Y. Apps included in the current study were a, b, and c. The study was conducted on a Device Y with the latest builds of the Desktop Apps. 7 current Suite X and Device Y users participated in the study Research Goals The research goals of this study include: Evaluate the usability and desirability of the current builds of A and B for Reading and Reviewing Documents and Creating and Completing documents Understand how Desktop apps work on the Device Y environment and the effect it has on the user experience for these scenarios Gauge improvements in the user experience since the previous code assessment Measure the desirability of the SuiteX Apps for these scenarios

How is Desktop Touch doing overall? Currently, without most of the keyboard work or scenario push items having been implemented yet the UX pass rate is rather low this is expected to increase over the next few weeks. Overall Desktop Touch on Y Platform UX Pass Rate UX pass rate for scenarios tested in this study.

FINDINGS APP A

What worked well?


Floatie usage

Users could quickly and easily edit and work with their content using the Floaties UI. Users all noted that basic editing (such as copy/paste, italicize and change font size) worked well and easily.

Spell checking o Users really liked the new right hand side spell checking pane. The design utilizes large buttons that make it feel extremely touch friendly on Y Device. The majority of users spell checked by going to the Review tab and tapping on Spelling and Grammar.

Users liked how touch friendly the spell check UI felt.

Adding a table Adding a table was really easy for users all users went to the ribbon and used the new touch optimized table drop down to add a table (see image below)

Image of the touch friendly UI for inserting a table users were very successful with inserting tables

What didnt work as well?


Working with tables o o o Adding a table was really easy for users (see above). When asked to add an extra column and row to the table users started to struggle. 4/7 users accidentally added in extra rows or columns when they were only trying to add one. Three of the users were able to determine what went wrong and could fix their error. One user was stuck and could not figure out how to just add one row and one column. o The problem several users encountered is that when you insert a new row or column, the row or column you just inserted is highlighted and the Floatie stays up (see image below).

The next step users then take is since the Floatie remains up is to immediately tap Insert again to insert an additional column or row. However, since the previous row is highlighted when users does this it inserts the number of columns as are highlighted (in the above image if you tapped on Insert, three more columns would be added for a total of 6 when users were asked to insert just one for a total of 4).

Working with tables has been a struggle for users across apps, it has been a known issue that once they have added a table making lots of edits/changes to that table wont feel as easy or smooth as just adding a table.

Recommendation: Currently working with the teams to understand the selection and F
Floatie dismiss behavior for tables and to determine if there are ways to make the table experience easier.

Commenting o o 4/7 users struggled noticing the commenting icon (the designs for commenting icons have been changed in build xxx). 3/7 users also noted that commenting did not feel smooth this related to several aspects, some noted that the canvas shifting whenever the users tried to tap in the canvas. Performance was an issue and typing in the commenting pane was at a slower pace (tracked by bug xxxxx)

Recommendation: The issues noted in the study are either fixed in the current builds or
are being tracked by bugs noted above.

Overall smoothness of working with App A o The build being used for the study had bugs relating to scrolling how the canvas acts when you tap on it. For example, every time you scrolled using your finger the entire canvas would shift left briefly and then shift back to center. This would also happen whenever you tapped into the canvas to place the IP. o o This has been fixed in build xxx and A is continuing to make other aspects more smooth, such as reading mode animations (tracked by bug xxxx).

Recommendation: As seen in the user perceptions of A bugs relating to basic tasks such
as scrolling and to the overall smoothness feeling of the app are important. Most of these bugs have been resolved in the current build and others are being tracked.

APP B

What worked well?


Interacting with your slides o Users could easily add slides, delete or add content on their slides, change the design and insert tables. All of these basic functionalities worked really well for users. For most of the tasks users utilized the Floatie to complete the task. Slideshow mode o In previous studies a major pain point was how to invoke the slide show menu on a touch device. Press and hold wasnt discoverable enough and the new design invokes it on tap (sliding your finger across the screen would transition the slide without invoking the slideshow menu). The concern was that it was too easy to discover and would potentially become a distraction. o 4/7 users tried swiping to advance to the next slide when they first entered slideshow mode. The rest tried a tap (which invoked the slideshow menu) and used the arrows to advance. Of those three users that tapped instead of swiped, two of them spontaneously also discovered that a swipe would advance the slides without invoking the menu. o o The ability for users to easily invoke the menu made tasks like inking and exiting the slide show much easier for users to complete. In a previous study, two users were completely unable to exit slideshow mode and felt stuck and trapped in this study there was 100% success rate for exiting the slide show.

What didnt work as well?


Working with tables o Similar to A, users had no trouble adding a table to their slide users would easily find it either from tapping on the table icon on the slide, or from the insert tab from the ribbon. o Problems arose when users tried to add an extra column or row to their table. Just as in a, once youve added a column or a row that row/column stays highlighted and the Floatie stays up, so when users go to tap on insert from the Floatie more rows/columns are inserted than they expect. o -

Recommendation: Same as with A: currently exploring options for making the tables
experience easier.

Inking: exiting inking o o o o Users were very successful at starting to ink they found the menu and quickly understood which icon would let them add inking to their slide show. It was not clear to all users how to stop inking or that they needed to de-select the Pen selection when they were done inking. When users were in inking mode 4/7 of them accidentally tried to swipe to move to the next slide (but since they were ink mode it left a big red mark across the screen. There is not enough indication to the users that they are still in pen mode. See the images below, the left hand side nothing is selected and on the right hand side pen is selected. o

Recommendation: Make the indication that pen mode is enabled more clear to users for
example, actually utilize the color pen they have selected as an indicator on the slide show menu (the swirl around the pen could be thicker and red if red pen was selected).

APP C

What worked well?


Identifying icons o One concern and research question for C on a touch device was that with the lack of hover states, will users be able to understand what the icons mean? If they arent 100% sure what it means will they still be confident to tap on it and see what happens or worried that they might accidentally video chat with someone for example? o Users could easily identify all of the icons (see image below):

Image of the C 15 icons in the main window

For the icon, even if they couldnt articulate exactly what they were expecting to see they did think it would be more options or more information. They grasped the concept that the three ellipses would give those more than that they were looking at.

Opening a new IM window o Almost all users expected a double tap to invoke a chat menu and it worked. Some users saw the icons and invoked it from the IM icon that way. Either way, the actual invocation of the IM window was not difficult for users.

What didnt work well?


Getting the icons to appear o Users were unsure on how to get the icons to appear, they assumed that tapping anywhere on the users name should invoke the icons rather than only having to tap right on the users name. o One concern is if making any of the area invoke the icons would also make it possible to double tap anywhere to invoke the IM window? If not, it would be more important to prioritize double tapping to invoke the chat window. o

Recommendation: Consider the users expectation is to be able to tap anywhere in that


space to invoke the icons. Allow for this functionality to happen as long as it still ensures that double tap to invoke the IM window is still possible.

Typing in the chat box o When the chat box appeared, users noted how if they tried to type more than one sentence the keyboard would be covering their content. Several users struggled to move the chat box out of the way (see image below). Both to move it out of the way to they could actually see a large part of the IM window, but also without accidentally bringing it up to the top where it would stretch out to a full screen window. o

Recommendation: Implement the work to auto invoke the keyboard as well as move
content out of the way for users. The C team is currently tracking the work to have the keyboard automatically invoke as well as move content out of the way with DCR# xxxx.

USER PERCEPTION

APP A

Expectations
7 6 5 4 3 2 1 0 Exceeded expectations Met expectations Expectation Range Overall, the bugs with scrolling tainted the users experience with A: Buggy, my patience would have run out [I found A on Y Device acceptable to use] as long as the bugs are worked out Users are still excited about the prospect of A on a Device Y: I would love using this in my everyday life Because it worked as if I was using a PC which makes reusing documents very easy Not met expectations # of Respondents

APP B
Users were pleasantly surprised by B and enjoyed using it on a tablet:

Expectations
# of Respondents 5 4 3 2 1 0 Exceeded expectations Met expectations Expectation Range Not met expectations

Very smooth, very user friendly Great touch product! Most definitely useful on a touch device

RESOURCES
<removed>