-
Notifications
You must be signed in to change notification settings - Fork 1
Design Process
For our project, it is recommended to use the Android Phone and Google Cardboard installation as it requires less time and effort to get it to run. If a Google cardboard is unavailable, despite the experience being lost, it is still recommended to use the android phone approach. If this option is unavailable, installing it on your computer is the only option left. This particular option requires a lot more time to get it to run.
This type of installation requires cloning the most recent copy of our repository and following the steps outlined in this installation guide.
Our problem space is that teachers are scared of using technology in front of students. With our interview with Dr Boden she stated that “teachers become focused on learning the technology, and lose focus on teaching” she also said that they become quite anxious when having to use technology in front of there students. By using VR technology, such as the Google Cardboard, we hope to find a way to build confidence in technologies use in classrooms. VR will provide added benefits to any curriculum with its immersive element, allowing teachers to use authentic learning techniques. To test this we created a physics concept application, specifically a kinematic motion application designed to be used by physics teachers to teach this type of content.
How did you tackle this problem? Us images and extended captions to explain the design process and how your ideas evolved. Mention any limitations and relevant theory.
Originally we had planned to create our application similar to the below image.
As you can see the idea of having a plane and a dot to land on has always been apart of the application design. In sketch, there are three sliders present on the left, bottom, and right side of the screen. Originally there were designed to move with the user. The user would have been allowed to move the acceleration, speed/time and other things by using the reticle and the button on top of the VR headset to change the numbers. A more detailed sketch can be found below of the improved version
This image demonstrates a bit better of how the original application was to work. But as you can probably tell from the scribbled outline, is that this iteration was later abandoned. Having the scrollbars conflicted with one of the VR design principles and also does not fit in with this VR design type. Google VR Design Principles state that all 2d elements must be put into a 3d space so the scrollbars had to be replaced with the console. Having the scrollbars constantly there would become distracting. Having the scrollbars there would also not give users control over what they can see, they are forced to have the scrollbars there, so it was decided to remove the scrollbars and instead place a control panel in game to allow a more immersive experience. This is how the below sketch was created.
This sketch demonstrates the introduction of the control panel. This control panel grants the users a more immersive way of controlling the numbers in the application. With this draft, I still kept the scrollbars, but this was later changed to the number pad, which can be seen in the final version of this prototype.
This image demonstrates the control panel which users use to input the number for the distance between the brick and dot in order to get it to land in the correct space. To explain in more detail the users are given the initial velocity of 5m/s changing y displacement of 30m, and the user is supposed to figure out the change in x displacement by figuring out the time taken. In the end, t value becomes 2.47s which then makes the change in x displacement 12.37m or rounded up to be 13m. Unfortunately due to time constraints, the t aspect was never implemented into the prototype. One limitation of our prototype is it is intended to give multiple authentic learning problems but our current prototype only does one.
- interviewed one user #15
- Proposal
- wrote Interview questions for Dr Boden
- Wrote interview transcript for users #9 #5
- wrote the informed consent form e363e19
- Did Paper Prototype | history
- Did final prototype
- prototype #4 523c7dc 49df5be b8e880e 9e941e9 #22 #24 46ed368 695d6ea 8d151ce #21 9e941e9 #10 #12 b23454d 803224d ba36d58 #23 c039eaa acacba4 #26 c039eaa acacba4 0708634 46ed368
- getting player to move towards and away from the console #2
- The reticle gaze images #2 #3 c7c2372 5f25f76 523c7dc 474b841
- did readme.md | history
- Installation Manual 9d86ef3 fb5a767 f126395 aa4885f | history
- Digital Prototype #32 f912360 cef0b78 ac3d500
- functional & non-functional requirements #14 f2d7831 d2d2cc4 e9cf9bc
- User Stories e708e65 2e0c1bf f04f978
- Design Process #17
- removed raw data from github #29 0ca5028 c8ac124 f69c859 468505b
- Conference Poster
- interviewed 5 users
- Proposal
- did readme.md 813ae4f
- wrote Interview questions for Dr Boden
- reticle images #3
- one user story #16 | history
- text on console #1 #8 90ec0ec 4a14d34
- Brocure a0f8c41
- Digital Prototype 8554340 1ec54f7 c667d5d
- Functional Requirements #14 | history
- video #17
- User Stories #16 | history