App Concept

AR Build Studio is a workspace where users can prototype spatial designs by scanning a surface and using virtual blocks in augmented reality. Users can save their builds, as well as reopen and edit them.

Team members: Emil Größinger, Livia Gaind

Use case: AR Build Studio enables spatial prototyping and professional planning in AR. Users, like creative individuals and Planners, or Professionals and Designers can scan real-world surfaces like tables, floors or counters and place, move, and arrange with virtual blocks to plan and build layouts, design spaces, and visualize concepts before implementing them.

Target users: Professionals, Designers, Planners, Creative Individuals

Prototype pictures

Welcome Screen Scanning Surface Add Block Choosing Shape Scaling Block Choosing Color Place Block Save Workspace

Database Entity Relationship Diagram

erd

Heuristic Evaluation

heuristic evaluation

Usability Testing

Usability Test Plan

Purpose and Hypothesis/Research Questions

Our primary goal of the usability testing was to evaluate the ease of use and fun of our AR Build Studio app. We also wanted to find out if any features were missing or if we needed to alter the UI. We conducted the usability test by starting with Pre-Test questions to get demographics like age, gender and how familiar they already are with AR. After that we conducted the usability test. Directly after completing each task we asked the user how easy it was from a scale from 1-7. After the test, users had to fill out a SUS-questionnaire and a few Post-Test questions . After conducting the test with 3 participants, we decided to improve our app based on the points that were often mentioned by the previous participants. Then we continued our Usability Testing with 3 more participants, now with the improved version.

Demographics

First Test: 1 male, 2 female

Second Test: 2 male, 1 female

Initial Hypothesis

The app is fun and easy to use without need of prior knowledge of AR Apps.

Which Data to collect

Demographics of the users and finding out if they have experience with AR apps

Ease of use with SEQ (Single Ease Question) after each task

SUS (System Usability Scale) after the test

Qualitative feedback during and after the test using questions in the form after the test and the think aloud comments during the test.

Methods

The participants were asked to complete a series of tasks while thinking aloud. The following 5 tasks were given:

  1. Create a build using at least 3 different colours & at least 3 different shapes
  2. Try to delete any block at least once
  3. Place one more block
  4. Save the build & name it & go back to start screen
  5. Load their build, add one more block/do any change you want & save it again

User Test Results

6 participants in total, 3 female & 3 male

4 participants age 20, 1 participant age 26, 1 participant age 36

Graph of "How familiar are you with using AR apps?"
Familiarity with AR Apps
SEQ-Graph (1-7 point ease of use questions for each task)

1 = hardest, 7 = easiest

SEQ Scores
SUS Graph
SUS Scores
Feedback from the post test questionnaire & think aloud

It would make more sense if deleting is an own button or I would just make a toggle button.

Deleting is a little confusing/ hard to find

Change the mode dropdown to a toggle button to switch between create and delete (mode).

Why colour button blue and shape button violet? → choose one and make them same color

Add Brush icon for colour button, cube for shape button

Primary Buttons (mode, color, shape) hard to reach, should change so be reachable , but not back button and save button.

Implementation of research

Example of how we implemented the feedback & results of our usability test

Screenshots of final App

start without saved builds

Start screen

Ar Activity

AR Activity

Select Color

Color selection

select Shape

Shape selection

Deleting a block

Deleting a block

Save Build Screen

Save & name build

start with saved builds

Start Screen with a saved build

Deleting an entire build

Deleting an entire build

Reflection

Emil

Contributions

UI, Code, Design, Pages/Documentation, User Test Plan, User Testing, Logo, Database Setup, Presentations

Challenges

Any logic that had to do with the AR was complicated, but one of the hardest parts was figuring out how to allow multiple 1 wide blocks be able to be placed on a 2 or 3 wide block. Finally figuring it out and seeing it work felt very rewarding.

Did we achieve our initial concept?

Absolutely :)

I am really happy with the UI & overall coherent design. The functionality of the AR is better than I envisioned and I am really proud of how well the saving and loading of builds work.

What could be further possible improvements?

Rotation & Scaling of each block, Even more color & shape options, Tutorial for first time using the app, long tap vs short tap gestures having different functions

Livia

Contributions

UI, Code, Design, Pages/Documentation,User Test Plan, User Testing, Presentations

Challenges

One point that really challenged me was changing the logic of the code after we added a new feature and the code suddenly stopped working or did not work the way we intended it to work. But it also helped us a lot because it made us aware of errors or just inconsistency in the code that might have slowed us down or might have caused us problems later on.

Did we achieve our initial concept?

Yess! I think we achieved our initial concept, I think the way the different features work and the design and whole UI we implemented fits perfectly with our app. We made good process early on in implementing all the things we wanted to have in our app within the two weeks.

What could be further possible improvements?

I think adding a Tutorial screen that appears when you use the app for the first time but which could also be called up, to be able to view it again would be nice. Being able to rotate a block, changing the size of a block freely or choosing from several sizes would also be a great improvement. To be able set a custom icon to a build for better recognition could be added too.