Leena Al Sallakh Design

Tangible Interactions Flow Diagram for A1 The flow diagram I have created for my A1 assessment, is all connected, where I made sure pathways between each and every interaction had two options that either linked to the before interaction or the after interaction. When looking at examples, during the tech workshop and completed flow diagrams for our class exercises (that I haven't posted due to how bad they are and the amount of no common sense involved in my attempts) I came to the understanding that a flow diagram should clearly display the interactions as well as keywords to indicate which sensor is being used where etc. My flow diagram below it was I created for Ruff's Cookies; My simple but slightly complex diagram, follows a couple rules...these are rules that I have created from looking at other flow diagrams and working on an example in class with my Tutor.  The diagram must have three different types of shapes that clearly represent the questions, the answers and the res...

 My initial idea involved a RFDI chip but has since evolved and changed to using a hall effect sensor that does the same thing but is a lot easier to code.  The hall effect sensor used a magnetic to interact with, you simply tap it against and a red light flashes to notify you that it's connected. I have also coded the hall effect sensor so that when you tap against it, the warnings stop.  In the scenario with my idea, this means the hall effect sensor will be used as an overide. So parents can basically have a cookie anytime they want and control the childrens intake. The video below, shows how the hall effect sensor will be used in the scenario;

 After talking to a Tutor for advise on my code/arduino set up, there was a problem where the buzzer continues to make noise when it's not supposed to.  To fix this, it was suggested that we use a potentiometer instead of a tilt switch to see if that would change or fix things. As you can see, in the video, this was not the case. The noise still continued to happen but admittedly it was a lot easier to turn on, in my Tutor's word, the potentiometer has more stability than the tilt switch. This gives me something to think about as, while it's more stable, the interaction isn't as physical as the tilt switch, which means I might need to rethink how I will integrate it into my design.

My second experiment with the ultrasonic sensor went a lot better than I thought it would. This tutorial came from the Arduino website:  Arduino Distance Detector With a Buzzer and LED's In the below video, we can actually see an interaction where the closer you are to the sensor the higher you here the buzz, with different warning sounds as well as the lights that show three warnings! 

For my A1 tech task with the cookie, I'm looking at using the tilt switch as the turn on and off. Its the start of the interaction. To turn it the cookie jar on, you have to tilt the jar and that's when the sensor will be turned on. I have done a previous experiement with the tilit sensor, however, in the video it was used to detect vibration and was not the main instrument. In the below, video you can see how I have used the tilt switch sensor as an input that you must interact with in order to one, start the system, and two, to turn the LED light on in order to know that it's turned on. I am very pleased with the result of the tilt switch and now just need to join it with the ultrasonic sensor for my code. I hope it works!

My first experiment using the ultrasonic, didn't actually go that well... Admittedly, it could be my fault but I followed the directions to a T, crossed my t's and dotted my i's etc.  I followed the tutorial from this website:  https://howtomechatronics.com/tutorials/arduino/ultrasonic-sensor-hc-sr04/ But this happened: In the video, as you can see, I ended up removing the black cable and it seemed to work or at least respond...ish. This example didn't really help with my understanding nor did it help with my A1 assessment. 

Ultrasonic for the Win  To detect motion in order to set off the warning 'growls', I have looked at using a PIR sensor.  While I can use it, I have been advised by the world's best tutor, i.e. James (See James I am a nice person!) that it's not the best sensor to use and would basically be a massive pain trying to code and deal with its delicate sensibilities. To instead use an ultrasonic sensor to detect motion etc. They are easier to code and will get the job just as good. Basically, the moral of the post, is to avoid PIR and always listen to your Tutors, they know what's best!

 For my A1 idea, I have been thinking of types of inputs and outputs that I could use to achive my aims. The outputs I want: Sound - growls and warning barks Vibrations - Rubbles, shaking LED - light flashing, warning, green warm, friendly etc. The inputs I came up with (and with help) Tilt switch sensor - turn on, start? RFDI chip to identify, interact individually with ice cream Motion sensor, PR sensor, to detect movement

 In class, I wanted to explore the tilt switch sensor as I want to use it in my design, but not sure how to work it.  I used the project 8 example, from DFRobot, the Vibration sensor, to introduce myself to how it works. The video demonstrated a good way to use the tilt switch and the LED light to show its been turned on or off. The code needs working on to make it easier for me. I need to find more examples of the tilt switch sensor being used.

For my A1 design, I have been playing around with the idea of timed snacks. An interactive product that you can set goals with and time when you can get your rewards. This idea initally began as a device that protected your food from your family, i.e. your siblings.  A quick example of a scenario where this device would be needed; You buy yourself a carton of ice-cream that you don't want to share. Your siblings also want ice cream so they go looking for it...Buttt they can't, cause you got locks and alarms. Ice cream is protected against theft. As mentioned this idea, turned into a reward system, that locks the ice-cream awat from you until the set time comes. It's designed to coerce you into doing work.

  DNH603 Recommended Reading  The next reading to be is AskTOG First Principles of Interaction Design  by Bruce Tognazzini ( https://asktog.com/atc/principles-of-interaction-design/ ). Notes from Webpage; instill a sense of control, can see options, goals etc Apple has great interfaces but even they have mistakes bad interactions Aesthetics "Principle: Aesthetic design should be left to those schooled and skilled in its application: Graphic/visual designers Principle: Fashion should never trump usability Principle: User test the visual design as thoroughly as the behavioral design" not detract from user experience - ensure satfication and productivity against old to test, should be the same or better, never less (if its less not worth aesthetic) Principle: Any time you use color to convey information in the interface, you should also use clear, secondary cues to convey the information to those who cannot see the colors presented. "Color as a vital interface element"...

DNH603 Recommended Reading  The next reading to be is A Brief Rant on the Future of Interaction Design  by Bret Victor ( http://worrydream.com/ABriefRantOnTheFutureOfInteractionDesign/ ). Notes from Webpage; Productivity Future Vision - interactions with touch surfaces, books, top surfaces etc the video vision isn't visionary - doesn't have a vision  "a group of inspired people is the most powerful force in the world" adressing human needs > human capabilities  can do and want to do - design for both human capabilites have been neglected, to design to be used by a person need to know and look and what they can do, what they are currently doing from video > hands to interact, to feel, to manipulate, mould etc. hands interacting with a book, the familiarity of it, flicking through, weight of the book, changing pages...one page vs two page > you know things cause you do it drinking water from glass > can feel weight in hand, know how much is left...object re...

User Interview with Steve Another interview was conducted with Steve from Spinal Life Australia. This interview was done in joint collaboration with Ellie McBain and her group that is also focusing on theme 1; Assistive Devices.  Steve is a T4 paraplegic. This means he can't feel from the chest down. The interview with Steve provided us with many insightful key points and numerous opportunities: Steve uses a manual chair and will only use a power chair when he has to. If he can, Steve would like to be as independent as he can be and would prefer to not have to use a powered wheelchair at all. Balance was a ket factor that Steve mentioned was something he had to get used and was quite difficult due to his height.  The shower chair is an inconvenience, its bulky and "looks like its been designed for the last century" Where he can Steve tries to "only go down hill" It's quite easy for him to transfer The bathroom routine isn't a pleasant situation but is ju...

In our week 4 tech workshop, we were provided with advice and how best to test your code and your inputs as a result.  For auto formatting – Ctrl + T Signal testing, wiring input > need more than just power, basic circuit in slides Multimeter > can test if circuit is complete Serial monitor to display serial functions Serial print to check if its running correctly and can use to get range etc Next step to test what’s happening Test each input at a time, set up one and test that so you know its working, so you can start figuring out what’s wrong Versioning code extremely important Using fault testing tools to detect things Start from base and then do trial and error to tweak the code already there for your purpose   It's important to note that our wiring diagram must be as good as perfect or our code won’t work without it. A trigger, what a switch could be…could use time of day as an event…and they have a trigger event system To code and figure things out, we were a...

Product Ecosystems To get a better understanding of product ecosystems, the below article was used to understand how products are connected; Future Product Ecosystems: discovering the value of connections by our very own Industrial Design Lectures at QUT Tim Williams and Marianella Chamorro-Kocb. The link:  https://static1.squarespace.com/static/55ca3eafe4b05bb65abd54ff/t/5747499960b5e9634c0cdf34/1464289694043/295+Williams.pdf Key notes that were taken from the article; Product Ecosystem Theory is an emerging approach to understand value networks for products As an industrial designer, the trend of an interconnected ecosystem is benefical to the overall design, it adds value.  "For example a television of the 1960s required a power supply, transmission of programs and not much else. A modern television in contrast, may sit within an ecosystem of DVD players, pay TV, streamed content, free to air content, remote controls, surround sound systems, internet connectivity and so...

  DNH603 Recommended Reading  The next reading to be is  The Encyclopaedia of Human-Computer Interaction: interaction design  by Jonas Löwgren ( https://www.interaction-design.org/literature/book/the-encyclopedia-of-human-computer-interaction-2nd-ed/interaction-design-brief-intro ). Notes from Webpage; needs, desires of the people, products, services pleasure, satisfaction and enjoyment "Interaction design is about shaping digital things for people’s use" shaping - creating, building, designing design is transformation - change interaction design - digital things - implementing a new initiative (?) Its about exploring possible futures - divergent work user studies are used in interaction design processes, fieldwork "Design entails framing the “problem” in parallel with creating possible “solutions” " thinking, sketching - for tangible representations sketching in software and hardware as well as low-fi modelling for interaction design purpose and intention is import...

After our Monday meeting, I reviewed the feedback that was provided from my group and edited the two personas I created. I wanted to make sure I included all the needed content, covering their needs, frustrations, goals and motivations very clearly.  In case the personas I've created, I have also created a list of character descriptions, hobbies and interests, and other motivations. These list, along side the above personas, are to help me visualise and build the personas so when I'm designing, I have a clear indicator for who the users are. Ryan Hobbies Gym Cooking Video Games Character Strong Logical Loyal Self-control Kind Determined Adventurous Motives Increase independence Have enough savings Be able to support himself Chloe Hobbies Reading Family Time Cooking Character Generous Kind Sincere Loyal Patient Optimistic Motive Her family When creating the visual representation for the research presentation, the persona will b...

Story of a Persona I need to start focusing on the reason a persona is created. To help tell a story. The more personas that I  have created the less I feel the story is being potrayed.  When I was looking for inspirations for how the persona could be visualised (as I tend to show some basics but have left my persona looking very text heavy) I discoverd this link:  https://uxdesign.cc/personas-e60c1c06ead1 While the above image from the article is very text heavy, it highlights what I need to make sure are clear in my own personas. That I am highlighting our users needs and fears etc. It made me think back to our ritual project in our first year of design and how we used the personas to tell a story. It made me remeber why personas were so essential to the design process and how it sets the scene, it tells the story. The below images, are examples of personas I looked for on Google and Pinterest.