Wednesday, 5 November 2014

Reflection

Well this post brings us to the end of my semester of digital prototyping. It was definitely entertaining and I have been introduced to a lot of new technology, languages and people. The Makey Makey, though not necessarily effective for my prototype, was my favourite part. It was a lot of fun!

This post will serve as a reflection of my time in this course and answer some of the questions that were asked of us in the contact. 

What else might you want to prototype in this course?
Out of my experience with digital prototyping I learned that maybe wearable technology was not the best choice. All of the prototypes that revolved around games had much more room for creative exploration - physical interaction with the games was exciting!
I was always struggling to fit my concept into the physical interaction when it should have been the other way around. I'm not disappointed in my choice because I grew to love Connect Ring and would probably use it, it was just some of my classmates Makey Makey was fantastic!

It would be exciting to be allowed a little bit more freedom. I don't see prototyping as just using code, I would personally like to "make" things and then try make them technical. I know that some of my peers have experience with arduino boards and they expressed that it would be great to be able to use that technology. I haven't used it myself so I would love the opportunity to learn more things and experiment with the unknown!

Mandatory Testing Sessions
I'm not quite sure what this point is all about as I wasn't at the contact. I assume it is just asking whether we feel the need for the testing sessions to be mandatory...
I personally didn't encounter this problem, a lot of our class turned up 75% percent of the time. I got enough test subjects every time. Callum was great at ensuring that the class swapped halfway through so we took the opportunity to look at the other side of the classrooms projects. 


Anywhere you got lost/confused?
I got lost and confused a lot of times, I'm not sure if it is because I'm unfamiliar with programming in this sense or if I just needed to spend more time working on my skills. I think that there needs to be clearer direction for those doing wearable technology and some additional tutorials for those who choose that path. I spent a lot of time working on the PONG tutorial (it was great) which wasn't specifically useful for my project. I sourced a lot of my help from youtube and google.


Needed clearer direction?
One of the things I realised when trying to teach myself a few tricks of the trade was that the internet did not necessarily have all the tools I required, or I had to look a bit harder. I think this is because we weren't allowed to do timeline based scripting...all of the help that I found showed you how to use AS3 with the timeline. This was considerably frustrating and took a bit of time to get my head around. 

Highlights
My favourite deliverable was in fact the video prototype, I don't know if that says anything about me or my skills set but it was what I enjoyed the most. It was exciting for me as I didn't have any prior video editing skills and it was something that I had been meaning to learn. 

I also enjoyed using the Makey Makey invention kit. It was fun to use! I actually enjoyed experimenting with it rather than implementing it into my projects. But I guess things are always more fun when they're for recreational use!


Interactive Prototype 3 - AS3 + Makey Makey

In all honesty Interactive Prototype 3 for me was a bit of a shambles! I was investing a lot of my time and energy into design computing studio one and was certainly not impressed with my level of engagement with this subject!

I think I threw some things together and hoped for the best...This was also impacted by my great ability to get hellishly sick at the worst possible time! I came down with tonsillitis for the first time ever and can certainly say that it was not a good time!
Drama aside I'll give some explanation into what I changed with this concept and what I hoped for it to do.

Changes to Concept/Code:

  • I added extra interface screens and created an extra interaction i.e. when two users bump the "hello" tone sounds and then the screen changes to show the new user (see below).

  • I fixed my code, huzzah! Originally my AS3 would only play the tune on a double click. I managed to fix this and made it happen on one click only. This certainly made me happy! 
  • I altered the code to get rid of the unnecessary play/pause shambles that I had for interactive prototype II. I had only included it in the second prototype because I didn't quite understand it. 
  • I was aiming to prototype an actual ring design but unfortunately my sickness knocked this one out of the park. I ran out of time and honestly just didn't have the energy. I used trusty play dough!
Limitations:
  • My final prototype is still quite shallow and I wished I had have been able to further explore this concept. 
  • I really struggled with the concept of changing images/sounds on the same mouse click event. I had to watch several tutorials and this limited my exploration process a lot. I didn’t successfully get the image to change over on click (so frustrating) but I hope to fix this before testing on the blog. At present I have the two images arranged on top of each other I just have to work out how to change them on click!
  • I had also hoped to 3D print my design but this proved harder than expected, but I guess when in doubt just use the dough! 




Feedback:

Is prototype II or III more self-explanatory? Why/why not?
Prototype III is more self-explanatory even though the interaction did not completely work. It is handy to be notified that the interaction actually did something i.e. the next interface screen.
Did you find prototype III to give a clearer response and indication that the connection had been successful?
As mentioned above, yes.
Would you prefer to just tap the screen?
No I found this kind of interaction fun, it makes the whole concept seem more social.
How do you picture the final design of Connect Ring?
I don’t really know, I don’t think about things like this too often. I liked the other design you showed me a couple of weeks ago (ringly) that was stylish.
Is there any other wearable accessory that you think would be better suited i.e. a bracelet rather than a ring?
A bracelet would be handy but then so would a ring. There’s no difference really. I guess one is more bulky…
What changes would you make to the interface? How would you like to connect with friends?
I thought you were going to prototype sharing your photos with friends. I thought that was pretty cool. It would be great to automatically share with people based on their location. 


This feedback was not as in-depth as I wanted. I didn't have access to my peers as I was quarantined to the house. As such it took a lot longer to get answers as I firstly had to explain the concept from the beginning...lazy I know. 
However, it was great to get an outsiders perspective that is not design orientated. It actually made me have a bit more fun as there was no fear of judgement i.e. don't judge my prototype or look at how messy my code is haha.

I would love to be able to take this concept one step further and prototype the actual ring. I know I have been saying this from the beginning but the thought has stuck with me terribly!

Interactive Prototype 2 - Feedback

For this testing round I used pre-formulated questions and recorded the users reactions and answers. I didn't want the users to fill out a questionnaire as I find that a bit formal and believe you get stifled answers. I personally just don't enjoy filling surveys out!

An example of the answers I received is below:
  1. Was the interface graphic self-explanatory? Why/why not?Yes, very. The picture was so big and it made it clear.
  2. Did you find the physical interaction of ‘bumping’ rings to be necessary?Not necessary but fun. Little bit more exciting than tapping the screen.
  3. Would you prefer to just tap the screen?
  4. What alert tone did you find most appealing and why?The hello tone.
  5. What other physical interactions do you think should be tested?It would be fun if it responded to location-based services. I.e. taking photos in certain areas.
  6. How do you see the final representation of Connect Ring?Just a normal ring, totally circular. Inconspicuous. Something sleek and fashionable. 

The changes I made to my concept or design based on the responses I received:
  • I kept the interface picture the same as all users mentioned that it was self-explanatory and easy to understand. I aim to create more interface screens for the last prototype to further cement this interaction.
  • The majority of users (4 of 6) said that they enjoyed the "hello" tone the most. As such I will use it for the last prototype.
  • I hope to prototype the final representation of Connect Ring, something standard yet still fashionable. I need to get my hands on some resin! I think that is the only material that will be helpful...

Interactive Prototype 2 - AS3 + Makey Makey

Interactive Prototype 2 was my first attempt at Makey Makey with a protoype! It was a good time. Thankfully for me there is a few physical interactions that can be tested for Connect Ring but nothing too exciting.
I took a lot of extra time working on my statement of delivery and testing section this time round, I'm learning that this is important for the development stage of the concept!

The prototype uses physical interactions in the "connection" of two users. I am simulating a "bump" that I developed from using applications like "Line" (See picture below) and the "Commbank App". However, the commbank app no longer lets users bump to share contact details, I think this could have been associated with security and privacy.



The picture above shows the interface design for Connect Ring. It is super similar to the line app because I think they perfectly modelled what people need to see! I used an old image from my Connect Ring video and cleaned/sharpened it up a little bit.


The above image shows me testing the interactions at home. This photo is ironic because it is the interaction that didn't work. Because I was connecting silver to silver the Makey Makey was going so haywire! I don't know how often I would use the invention kit outside of this subject, simply because it is so touchy!

I am excited to see the response from testing as a I have a little bit more to work with this time round!
Finally, here is my statement of delivery for interactive prototype II:






Restaurant Dining Experience

This weeks exercise was all about the restaurant dining experience! To be honest I'm a bit of a cheap skate when it comes to ordering out (uni student budgets and income I suppose) but I still expect good service. As someone who has worked in retail for over 8 years I like to receive the kind of service that I give consumers on a daily basis! It doesn't take much to deliver your service with a smile, it can impact the whole experience for the customer and make your day run smoother!
That said there are several factors internal/external that are sometimes out of your control - the following questions ask us to think about those and how technology could help or hinder these experiences/problems...

What external/internal factors impact on the experience?
External Factors

  • Weather (obvious I know) - Can play an important role in determining whether your restaurant will be busy or not. If it's galeforce winds/hail/rain then there is absolutely no doubt that people will be less inclined to go out and more inclined to recline indoors. (Restaurant Owner POV)
  • Events/Holidays - With the G20 coming up and all the predicted road closures and security searches I suspect that Southbank will be a ghost town. No doubt the local businesses in that area will suffer unless they are being graced by the presence of our world leaders. (Restaurant Owner POV)
  • Neighbouring Competitors - If a new restaurant opens/has killer promotions running it will most definitely impact the experience of the of the restaurant owner and patrons of the restaurant. No one wants to eat when it's dead quiet and everyone can hear what you're eating, let alone saying. (Restaurant Owner POV)

Internal Factors

  • Sad/Angry Staff - This happens to be one of my pet hates. I know I haven't worked in hospitality but I do work in customer service and I try to give excellent service every time. However, I get that everyone has off days. That said, sad/angry staff can ruin the mood of the customers experience, slow restaurant operations and decrease the mood of the staff. (Overall POV)
  • The time between ordering and serving - The wait for the meal can be excruciating and it can drive some people to insanity. If it takes an excessive amount of time to receive your meal 
  • Can I Take Your Order? - From another point of view it can be frustrating for waiters who have to come back to tables several times to grab their order because patrons are either - waiting on someone who is late, on their phones, engaged in deep conversation, haven't bothered to open their menu etc. This slows down the whole cycle within the restaurant and means that less people get through the door and to a table. (Restaurant/Waiter POV)
What aspects of the existing experience could be
enhanced/augmented/supported with technology?

  • Can I Take Your Order? - Having buttons on the table for patrons to click when they require service for ordering/bill. If your business requires high turn over - have a timer to let patrons know how long they have left in their seat for e.g. sushi trains.
  • Can I Take Your Order? - Having menu screens that allow patrons to order from their seat. There are a couple of restaurants that already do this and it's fabulous. This includes my valley favourite - Wagaya (see below)
  • The time between ordering and serving - Similar to can I take your order - have a system that records when meals are ordered to ensure that they are cooked in the correct order. 
  • Sad/Angry Staff - Use music and/or wearable tech to remind staff that they are appreciated. People who are praised are immediately put in a better mindset. Allow them to wear headsets with their music of choice to keep them motivated - have the technology respond to voice to pause the song when they start speaking. 

How would introducing technology in to this context
change the experience?

  • The concept of adding menu screens and timers would if anything increase efficiency. It would ensure that things run smoother and on time. However, if you're going to catch up these technology adjustments will decrease the mood and almost make your meal feel rushed. There are other places to socialise though - parks/coffee shops/homes/riverside etc.
  • The wearable tech for the staff would definitely increase their mood. I personally think it would be a good time! I certainly get sick of listening to the same cd's on repeat for 8 hours.

What experience scenarios might you test with the
technology?

  • Testing out these scenarios at different times of the day would be great. Different people with different schedules are always eating at different times of the day.
    Timers may work for the busy period, but during the low-period of mid-afternoon to dinner your patrons may not feel like being rushed!

Makey Makey + Physical Interactions


This week we are starting to prepare to work with Makey Makey! I didn't know what Makey Makey was until a couple of weeks ago. I signed up to digital prototyping late and missed the first contact. I think this was when Makey Makey was originally mentioned or perhaps it is just assumed knowledge. I had great fun going through all of the youtube videos of instances where people had used Makey Makey! It looks like its going to be super fun. 

As Makey Makey works using physical interactions and physical objects to replace keyboard and mouse functions we started looking at web applications in a physical way. Our exercise for this week focused on this concept:

Given the following applications of "Super Mario Brothers" and "Email" and come up with at least five different physical interactions. Focus on tangible and/or embodied interactions.
  • Focus on elements/controls of each application that would afford an alternative interaction method.
  • How would you map the interactions onto and/or into physical objects/actions?


Super Mario Bros

The elements of control in this game is the arrow pad and the space bar. Essentially you could map all of these elements onto physical objects or encourage physical interactions. 
  • By connecting with a dance pad you could actually "jump" to jump in the game and "step" in a variety of directions to change the direction of your character.



Email

It was a little bit more difficult for me to brainstorm things for this one but physical interactions for email could be:
  • Clap to send.
  • Speak/audio record to type.
  • You could have a reply, forward, save system in front of the computer with physical buttons instead of options on the screen? See image below:


  • Potentially you could get people to type the email out, print it and then physically deliver it to the person. I'm not 100% sure if I have a firm grasp on this exercise :)

Interactive Prototype 1 - Feedback


Click Yes = Alhambra Lounge

Click No = Black & White Cabs

The testing of Interactive Prototype 1 was rather informal and did not produce many results - that is really my own fault. There was not much that a user could do...They could click yes or click no, it wasn't rocket science. 
Before interaction users were told that both they, and their friend, are wearing a Connect Ring and are out and about in the town on Saturday night. Earlier in the evening they 'connected' and since then the two friends have lost each other. Ann-Maree has found herself in an awkward social situation and as such needs saving. The user then receives a notification telling them of Ann-Maree's location - "Save Me!"

If the user decides to save Ann-Maree they click yes and they are taken to an external webpage showing the location of the bar (Alhambra Lounge). If they decide they can't be bothered then they are taken to an external webpage showing Black and White cabs to order their friend a taxi...

Feedback from this interaction was designed to see whether users would want the webpage to open in the application. The comments made were:

  • Users wanted the webpage to open in the application. They find it frustrating when a webpage opens in safari and shows yet another tab to close. 
  • Users suggested having a chat screen so that if they didn't feel like meeting their friend they weren't just simplying saying "no, now get in a cab". This comes off as rude etc.
  • Users expressed that it was difficult to imagine the interface as it looked like their was two sets of buttons. On one occasion a user clicked the yes on the wireframe rather than the actual button.
Improvements that I would have liked to make to the prototype to improve testing:
  • Make the interface button actually a button.
  • Allow the user to be able to chat or write a message to their friend (see wireframes in statement of delivery).
  • Prototype the other side of this interaction i.e. the actually dropping a pin. Allow the user to draw a map pin and send it to their friend.

Interactive Prototype 1 - AS3


This prototype was to test the interface and boy was the whole process a hair raiser! Unfortunately for me I spent a lot of time working on pong tutorials and trying to understand elements of AS3 that I really didn't need to waste time on. I'm going to say here but AS3 is just not my gig, I can't say that I'm having fun wrapping my head around it. 
That said, the tutorials that I have been working on have been super helpful and I know if I have any questions I can always ask.

As I said in my previous posts I was planning to implement an interface that allows the user to test the "dropping a pin" function of the ring and app. Some of the ideas for the interface I got from Ringly - this design that fuses fashion and technology seems to interest me!


I am the kind of personality that loses my phone in my handbag or can misplace it for hours, so having a simple technology like Ringly would be super handy. But enough of that for now.
I attempted to use the tutorial that Mayi linked me (I think I mentioned this earlier): http://www.flashandmath.com/bridge/intro/time.html. However I really struggled to implement it. As such I was left with a bunch of wireframes (see SOD below) and not a lot of interaction. As a result I have switched my testing approach not to test the interaction of dropping a pin but the opposite, what a user does when their drunk friend sends them a pin.
The interaction itself allows for two possibilities - if you would like to meet up with your friend click yes and if you wouldn't like to meet up with your friend press no.

Yes: takes you to the location of Alhambra Lounge 
No: takes you to the black and white cabs website to order a cab for your friend.

I would have liked to create the interface including the buttons and not have them to the side. In all honesty I was a little bit time poor and had to do the bare minimum. I must keep improving my skills before the next prototype!

Here is my statement of delivery for this prototype:




Interactive Prototypes

What are interactive prototypes?
Interactive prototypes are working models of websites or applications, built for testing before further design and development work is to be undertaken. For the instance of digital prototyping, as a subject, our interactive prototypes will be used to test our original concept to review its success and where there is room for improvement. As I have chosen wearable technology my interactive prototype will have to include physical interactions, wearable tech and an interface.

What is actionscript?
ActionScript is an object-orientated programming language that is used primarily for the development of websites and software. The language is a dialect of ECMAScript (had to google that) that is a superset of the syntax and semantics of JavaScript. ActionScript primarily targets the Adobe Flash Player platform.
JavaScript is not exactly my forte so I am looking forward to seeing how well I handle it. 

In this weeks tutorial I had a crack at very basic actionscript and can say I had a good time playing with stickmen and pug heads. A little bit immature but it excited me more than approaching the Pong tutorial. See my creations below:


CRC Cards

Because I didn't attend this contact I didn't realise what CRC cards were before it was too late. As such I didn't really use them in my design process and feel like it was a little bit after the fact. 
To be honest I should have because they're helpful in determining what classes you're going to need and the responsibility of all of the objects in your code. For such an AS3 novice they're really helpful and so I gave it a shot anyway. 

Examples for CRC

Connect Ring Video + Feedback


The above video is my submission for the first assignment! For someone with no previous video and/or editing skills I was quite impressed with my attempt. Because of my lack of skills I focused on exactly what the concept is and tried to communicate that clearly.

To get around my lack of video skills I drew a lot of the aspects of my concept. This idea was actually influenced by the Google Docs in Plain English video - simple yet effective. After drawing them I transferred them into adobe illustrator and just converted them to outlines - from this I just transferred them into photoshop. To my surprise photoshop was actually quite effective and easy to use! Unfortunately I don't have any photos of my original drawings anymore to blog here (I smashed my phone just this week - sigh).


The feedback that I got about Connect Ring was quite vague. I have since realised that I should have been prepared with a series of questions and some sort of testing approach...
The feedback that I did receive though was quite positive and a lot of my peers found the humour in the concept and said that it would actually be helpful to keep track of their drunk friends.

Some of the things that people mentioned to improve the concept was:

  • How do two users connect/what is the physical interaction/is there an alert tone? Two people mentioned these questions...Callum was one of the two and he was helping me to start think about physical interactions for further prototypes and Makey Makey.
  • There is similar technology already being developed by other companies/students alike and to consider looking at their products in preparation for design and development.
  • The quality of the video was good and the drawings were simplistic and easy to understand. In some cases the audio was a little bit difficult to understand.
  • One user mentioned that they like the background song.
  • Another user mentioned that this concept is quite novelty and though it would be fun would people continue to use a product like this?

For the next stage I will prototype the interface and perhaps how users can drop a pin...Mayi linked me to a great tutorial for how to draw a triangle with actionscript but I think it could be a little bit advanced for me...

Also, here is my Statement of Delivery for the Connect Ring video: