Deco2300 Blog

For the prototype, I did simple scripts. I couldn't get some of the effects I wanted such as changing the volume of music on button press so I made it print in debug instead to know that the buttons still work. It was interesting to make the power button as it would change colour depending if it was clicked or not. A solution to the shifting buttons due to resolution was found; it was a simple one: set the resolution to be same across the device used. This made working with the prototype easier and more consistent as I didn't need to keep rearranging the buttons each time. I believe that my interactive prototype was completed enough to test the user interface and interactivity.

Age of empires Selecting the units Building buildings Combat with enemies UI with controls such as stop/attack/defend etc. Mouse and keyboard Selecting the units ingame, buildings. Different way to interact with units Touch screen (drag and touch) Joystick to control pointer (mouse pointer?) Using other objects such as fruits to replace keyboard Tinder Swipe Tap Touchscreen Swipe Shake the phone left or right to swipe Use a controller such as a joystick to move/swipe left or right Physically swipe people (???) Microsoft Word Typing with keyboard Typing method of selecting character or typing connect to tablet and physically draw out the character / word large pad on ground and use feet to stamp on pads to input words wrist pad? keys on a wrist pad?

Most of the work done in unity was learnt through YouTube tutorials. Practice with Unity made it easier to work with. At first, the camera/navigating was very disorientating but overtime, I became used to it. For my interactive prototype I, I decided to use buttons as my method of interaction. One problem that came up was that due to using different devices (laptop and computer) to make the prototype, the resolution change was mess up the placements of the buttons. This would need to be solved as the buttons would shift depending on the screen size / resolution.

Revisiting Some Old Questions: Were you able to complete the tasks? If yes, was it difficult? If no, why not?  How easy was it to identify the buttons?  Did the buttons do what you expected them to do?  How easy was it to use?  Rewording: 1. If you were able to complete the tasks, how difficult did you find it? If not, why were you unable to complete the task? 2. On a scale of 1-5 how easy was it to identify the buttons, with 5 being the easiest 3. When you pressed the buttons, did the buttons produce the effect that you thought it will? 4. On a scale of 1-5, how easy was it to use the device overall? 

Horizontal prototype: A menu screen and map screen as well as icons for the functions such as "drop" functions This tests the user interface such as how does the user navigate from menus, do they understand what icons do etc. Vertical prototype: A map where you can "drop" reminders onto it and check the state such as complete and incomplete. Testing the actual functionality of the map and the "drop" reminder function Diagonal prototype: Testing how the user could go from the menu to the map and if they can use the map functions such as "drop" reminders This tests both user interface (navigation) and usability ("drop" function)

What is complex; unfamiliar; new; changed; in your concept? Different functionality (additional) compared to other concepts. UX story If the user is sensitive to sudden changes in sound volume such as being in public locations (construction, busway, etc) Functional story User wears headset -> user presses button -> user adjusts using the app Information story Information is being sent from the makey makey to the unity project but information is not being sent back (1 way information)

What components are relevant to making a phone call? The device itself, handset and buttons. What are the interactions of those components with the caller when making a phone call? Caller picks up handset, presses buttons and speaks / listens to the phone. What goal is implied by these specific questions & are there other goals? How the user interacts with the phone (usability?) What are the functional components? the buttons, handset and screen What components are relevant to making a phone call? the buttons and handset What are the interactions of those components with the caller when making a phone call? user presses the buttons to dial desired number and uses handset to communicate What would you test (in frame of previous q's)? Usability - how different users use the phone in different situations such as in a rush or emergency How would you test that? Put the user under time constraint to dial a number