Excuse Me Accessories

Title: Excuse Me Accessories

Group: Savaya Shinkaruk, Tommy Ting, and Chris Luginbuhl


Project Description

Our product was created from thinking about a project for our assignment Portables / Multiples.

The goal of this experiment is to create robust interactive prototypes that we can make more than one of and that we want to travel with us. – Nick and Kate.

When coming up with ideas for this project, we came up with some really cool and interesting concepts, but none we personally wanted to test or use in our everyday lives. So, after lots of thinking over a few days, we came up with Excuse Me Accessories.

We go more into depth about the journey of our process towards making our game in our blog  but the overall description of our project is:

To help people with their productivity on any task or activity we created the Excuse Me Accessories products. By using the Pomodoro Technique (work for 20 minutes – break for 5 minutes), people can follow this technique with their wearable or desktop accessory.

So, continue on to the rest of our page to read more about the Excuse Me Accessories team and our journey.


About team

Savaya Shinkaruk: Savaya Shinkaruk is a fashion stylist and journalist with a keen interest in wanting to blend components of the online fashion industry with design. She graduated with a BA in communications in 2017 and is completing her MDes in Digital Futures at OCAD University.

Chris Luginbuhl: Chris Luginbuhl is engineertist who likes to create new words and new ways of using technology to help the world.

Tommy Ting: Tommy Ting is an artist and an emerging video game designer currently in his first year MFA student in Digital Futures at OCAD University studying game design and development.


BLOG: PROCESS JOURNAL

DAY ONE

DAY ONE OF OUR EXPERIMENT:

November 24, 2017

After everyone presented the projects for Experiment #4, Kate and Nick assigned us our group members and talked about the description for Experiment #5.

The three of us got paired together (Savaya, Chris, Tommy), and we decided to take the weekend to each come up with ideas for this project for Monday.

End of day one.

Thanks!


DAY TWO

DAY TWO OF OUR EXPERIMENT:

November 27, 2017

Today in class Kate went further into the project description for Experiment #5.

She went over the requirements and the deliverables for our project.

For this experiment we are to produce 3 copies of the prototype we are intending to code and design.

During class, each group was given roughly 45 minutes to come up 5 ideas for their project. This is the first time we started to come up with ideas for this experiment.

Here are the 5 ideas we came up with:

  • Night time to Daytime t-shirt wear – exploring clothing that changes in appearing in light and dark environments – perhaps becomes more or less revealing, or adding lighting effects.
  • Linking Maps to Instagram to source the best Instagram photo opportunities in Toronto
  • Dance Wearables – clothes and accessories that produce sound and light effects in response to movement. Used for performance dance, and just dancing for fun.
  • Real life Social Media – wearing a small Eddystone/Physical Web/Puck.js beacon to broadcast your key interests via bluetooth around OCADU. You are alerted when someone within range (~10m) has overlapping interests. You then have to find the person and have a conversation to figure out your common interests.
  • Uncomfortable fashion – exploring fashion that places demands on the wearer, and negotiates with them to adjust their posture, movement and behaviour.
  • Now you see me, now you don’t – exploring the theme of wanting to be looked at or wanted to not be looked at in public. In particular, clothing that can tighten or loosen, fasten or unfasten, illuminate the wearer, or conceal.

The common thread we had for all of these ideas is that we want to make a wearable fashion item. It could be a shirt or an accessory. We are more interested in creating an accessory for this experiment.

Before class ended we had to pitch an idea (that we could change later on, and we did) to Kate so she knew the direction we were headed.

We talked to her about going on the theme of “you see me, now you don’t” and we wanted to go about this concept by creating make a device that unlocks your garments at a certain time of day (like sunset), or to make a hat that has lights that turn on at sunset.

These are some of the ideas we are running with, and we are going to meet on Wednesday, November 29, 2017 to settle on an idea.

End of day two.

Thanks!


DAY THREE

DAY THREE OF OUR EXPERIMENT:

November 29, 2017

Today we met in the DF lab to start to brainstorm more ideas for this experiment.

Here is a timelapse of us meeting and chatting about what we want to do:

The new idea we came up with is:

We are going to are creating a wearable product that is a navigation system that informs the user if they are travelling North. In addition, when daytime turns into night and people start to feel nervous walking around in the dark, our product will light up so the user feels more safe when walking home.

We want to iterate this idea, but this is the initial concept we are going to start with and then build off of.

Some of the iterations we are looking to add are:

  • Have the navigation move in all directions: NORTH, SOUTH, EAST, WEST (like a compass)
  • Build the Puck.js on a magnet, so the user can easily move the item from their wrist, to neck, to finger.
  • For safety purposes to have the devices where if a male or female are encountered in an unsafe situation, by clicking the button it will make an alarm and blink light so the attacker leaves.

We ended up having to leave to class after these notes and work on other assignments so we are taking a break from this and will meet again tomorrow.

End of day three.

Thanks!


DAY FOUR

DAY FOUR OF OUR EXPERIMENT:

November 30, 2017

We met again today in the DF lab to go over the ideas we came up with yesterday.

We are still interested in our idea, so we are going to work on getting our proof of tech and proposal done for class tomorrow, as that is due.

We got to work on setting up the Puck.js (EMA) devices to Bluetooth.

Here is a image to show the pairing:

pairing-our-puck-js-device-to-bluetooth

To get our Puck.js (EMA) devices up and running this is the link we used to follow the steps to get it connect to Bluetooth, and to start doing tutorials on how to code: https://www.espruino.com/Puck.js+Quick+Start

Each Puck.js (EMA) devices has a 4 digit number that will be linked to our individual MACS so we know what Puck.js (EMA) is linked to whose computer.

This is Savaya’s:

bluetooth-code

We are going to use this code from this link for our proof of tech code for class on Friday, Dec 1, 2017:  http://forum.espruino.com/conversations/296979/?offset=25

Just kidding, in the end the code from the link above is not working because we need to subtract the magnetism in the area we are using this device in, for it to calibrate. And we need to set which axis you are mounting the device on. The original was not a robust enough and isn’t working.

Here is a image of the first try of the original code from link above:

firsttrycompass

So, we have sourced new code, and here is the link: http://forum.espruino.com/conversations/297915/

We are playing around with this new code because it looks like it will be easier for us to set an axis with a direction.

map

In the end, we are using the above code in the link as a template, but adding our own code into it. The personal code we are adding and changing is to assist in the calibration of the axis movement.

Here is a link to the GitHub that has the code we worked on and Chris implemented for our project: https://github.com/ChrisLuginbuhl/WalkWear/blob/master/WalkWear.js

Here is a first trail video Puck.js (EMA) working with the code:

This code is to show for our proof of tech, due tomorrow (Fri, Dec 1). We are going to iterate it a bit however as time goes on. But this is the starting point to show that when we move in a direction it navigates that and shows which direction you are headed, NORTH, SOUTH, EAST, WEST – as shown and talked about in the video above.

From there we started to work on our design ideas and noted what materials we will need for tomorrow.

Some of the design ideas we came up with for the Puck.js (EMA) are:

  • Original Idea: Magnetise the back side of the Puck.js(EMA) and then have a magnet it will attach to on the bracelet / watch, ring, and necklace. We like this magnet idea because it will be easy for people to move the device from location to location without having to undo something and tie it up again. However, the issue with this is the magnet will play with the compass too much, which will ruin the concept.
  • Prototype Idea: For Friday, Dec 1, we are going to do a prototype with velcro – which will showcase the same concept as the magnet, but won’t play with the calibration or compass.
  • Iteration Idea: We also like the idea of how Pop Sockets work. With the Pop Sockets you can also purchase a device where you can attach a car mount, where you can slide the Pop Socket into it, and it will hold you phone. We have attached images below to show what we mean:

 

pop-socket-mount popsocket

We also started to think of some working titles:

  • Wear and go
  • Navi – Direct
  • Walk Wear – WINNER!

For Friday Dec 1, here is a list of the materials we will need for our prototype:

  • Velcro
  • Wrist band – bring these products from home
  • Puck.js (EMA)

What is due for Friday Dec 1, 2017:

Proposal:

Working Title: Walk Wear

Group Members: Savaya Shinkaruk, Chris Luginbuhl, and Tommy Ting

Concept: For experiment number 5 Chris, Tommy, and Savaya are creating a wearable product that is a navigation system that informs the user if they are travelling North. In addition, when daytime turns into night and people start to feel nervous walking around in the dark, our product will light up so the user feels more safe when walking home.

Form: We are going to be making a wearable product that can be worn either on your wrist, hand, or neck. We are designing it so the device can be removed and then placed between your ‘bracelet / watch band’, necklace band, or ring band. For our prototype we are going to use velcro.

Electronic Component: https://docs.google.com/spreadsheets/d/1me4clmdyE9FGIMsQC5aUXlfaip62lC03WpXSjYtY48Q/edit#gid=0

Proof of tech:  https://youtu.be/vgKwKgTtEaA

Materials and production process for enclosure:  The Puck.js (EMA) will be shown as it already is built to act as an enclosure, so we are just building around it to make it into a device that can be worn on your wrist, neck, or hands.

We will work tomorrow in class on the next iteration steps of this product.

End of day four.

Thanks!


DAY FIVE

DAY FIVE OF OUR EXPERIMENT:

December 1, 2017

We had class today, where we had to hand in our proposal (which is shown above) and then we have individual team meetings with Nick to go over our project.

When talking to Nick in class, he told us that we should try and focus on one thing, and only use what the Puck.js (EMA) provides rather than adding in extra information and stuff for us to do.

The big thing for us to focus on, is the product. What is our intention and goal – and how are we going to make the Puck.js (EMA) look good and have it look like something. Ultimately, we have to make it into something because the technical side of it and input + output portion, it already does so much.

So after talking to Nick, Savaya left because she was feeling under the weather, so Chris and Tommy met to chat about some new ideas for this project.

We planned to meet tomorrow to go over what Chris and Tommy talked about.

End of day five.

Thanks!


DAY SIX

DAY SIX OF OUR EXPERIMENT:

December 2, 2017

Today we met to go over what was talked about yesterday during class hours.

And in the end we decided to go with a new idea and concept for this experiment.

New concept:

We want to make a productivity assistant app that is a smart device to inform the user when it is time to take a break and time to get back to work. Using light, green and red, it will inform the user when break time starts and ends. Along with this, when it is time for the user to take a break they have the option to have a screen pop up letting them know of their agenda for their things to do, or have their display sleep so they can take the allotted amount of time till break time ends. To turn the device off hold down the button for it to shut off.

For the display options we are looking at using this function for that side of our product: https://www.boastr.net/downloads/

Here is a list of some of the brainstorming ideas we came up with for this new concept:

  • Productivity app
  • Hardware
  • Assistance
  • Lifestyle
  • Not connected to anything – it’s a smart device (the Puck.js (EMA))
  • Does not turn anything on but turns things off
  • The goal is to disconnect – and you as the user have the choice of what that might be
  • Then when to go back to work
  • Just have the colours of Green and Red – but before it shuts OFF gives you warning
  • 20 min on – 5 off and then 25 min off – the break / work schedule.
  • Keep it a wearable
  • Keep it all in the puck.js (EMA)

We are following the Pomodoro Technique for this system where you work for 20 minutes and then take a 5 minute break and do this for an hour, and after doing this for an hour you will work for 20 minutes and then take a break for 20 minutes.

What would the user use this device for:

We talked about the ways we would individually use this:

Savaya: I would use this more for, not when i am working but for when I am taking time off my work to shop online.

Tommy: I would use this for when I am working and need a break to relax and then get back to work.

Chris: I would use this for focus computer time and remembering to take breaks.

In the end we all agreed people can use this productivity device for:  school / work / fun

For design options we would like to:

  • Have an option for a wearable / like a bracelet or watch look alike
  • Have a option for people to put this device on their desktop so they can see it  

We want to have two options for people because we believe this will help when we put this product on the market, so people can choose how they want to use it and wear it as well!

Here is a sketch of the wearable design we are thinking of:

watch-sketch

For the wearable part of this device we are looking to purchase watch bands like this (below) and to 3D print a way for the Puck.js (EMA) to sit and have the watch bands connect to the watch band connectors (shown below).

Watch bands:

ordered-watch-bands

 

Watch band connectors:

idea-watch-band-connectors

We shopped around Spadina and Queen West at multiple brick and mortar stores to find the intended materials to make our product and to know the size of what we need to 3D print for the Puck.js (EMA) to sit in / on. But we couldn’t find the right materials.

So we are ordering the items from Amazon. Which should be here Monday.

We are ordering the watch bands shown above. 

We decided on this watch bands because it will be easier for all people off all wrists sizes to wear this device without having to remove links.

We however, are not ordering watch band connectors. Because we are going to 3D print a surface for the Puck.js (EMA) to sit in. 

watchv3 watch-design watch-spring

New names/titles:

We had the title as Walk Wear, but are changing it now as we changed our concept.

  • Wear Away
  • Walk Away
  • Deskside
  • Deskside Breaktime
  • Deskside Wearable
  • Excuse Me Accessories = WINNER!

Now we are working on getting the first part of the code working: to have the red and green light on button press running, but also by clicking the button to have the display turn off and on.

Here is video of us turning Chris’s computer display off by clicking the Puck.js (EMA):

We are going to finish here today. We need to ordered the watch parts we need for this wearable, and we are going to work on Monday to 3D print what we need, so by Tuesday we have the wearable made.

End of day six.

Thanks!


DAY SEVEN

DAY SEVEN OF OUR EXPERIMENT:

December 3, 2017

Today all three of us worked separately, but kept a communication line open via Facebook Messenger.

Today we spoke more about the design of the watch, the theme colours, and branding.

We decided to use these colours, font, and included stickers in our branding because we wanted to evoke a ‘kid friendly’ feeling. When people are breaking we want people to feel like they have freedom to do whatever they want, kind of how kids act when they are playing with their toys.

We decided on this theme colour for the brand / product:

exp5-colour-theme

We also started to think about the design of the desktop holder for this product. Here are a couple ideas we came up with: ADD IMAGES

And we started to work on our branding too!

Here is one concept we are working on for the title:

branding

This is all we worked on today, independently, and communicated over Facebook Messenger.

End of day seven.

Thanks!


DAY EIGHT

DAY EIGHT OF OUR EXPERIMENT:

December 4, 2017

Today we re-connected in class and sent in our Testing Plan Proposal:

Testing Plan Proposal: Savaya, Chris, Tommy:

  • Preparations
    • What needs to be done ahead of time? Each person in our group needs 1 wearable and one desktop piece to either take home, to work, or leave at school – it is up to them where they want to test it. We just need to make sure the tester has both options – including the package given with Excuse Me Accessories.
    • Do you need extra batteries? There is the option to include extra batteries in the package each tester will receive.
    • What goes into your repair kit? Trial period of testing there will be velcro and tape supplied in the package in case anything breaks – however there is a receipt of return to Excuse Me Accessories for product to get fixed.
    • Be sure to take “before” photos. ADD IMAGE HERE.
  • The Plan
    • How will you document your own user experiences while using the device? Notes? Journaling? Photos? Video? Audio recording? Each of us (3 group members) will document our own experiences with Excuse Me Accessories by: Journaling, Photos, Video, Audio recording and a Questionnaire that we have created.
    • What will you do to ensure that your data collection methods are consistent for each group member? To ensure our data collection methods are consistent, we will give a Start and Finish time of testing that each group member has to follow. Also with answering a standard Questionnaire about the product.
    • For each group member, what are the dates & times of testing?
    • Savaya: Wednesday DEC 6 @ 9 AM – 4 PM:    AND Thursday DEC 7 @ 12 PM – 6 PM
    • Chris: Wednesday DEC 6 @ 9 AM – 4 PM:    AND Thursday DEC 7 @ 12 PM – 6 PM
    • Tommy: Wednesday DEC 6 @ 9 AM – 4 PM:    AND Thursday DEC 7 @ 12 PM – 6 PM
    • If there is a reason that (2) 6-hour testing periods don’t make sense, include a proposal for a reasonable equivalent for your device and get sign off from Kate. Not needed.
    • Will you be together or having your own experiences? We will each be having our own experience using this product.
    • Will you be doing your day-to-day activities or doing a special activity? We will be doing our day-to-day activities because we want this product to make sense for everyone and their day-to-day activities.
    • Any other details? For this testing period, we have said we cannot work on this direct assignment.
  • End of Session Reports
    • You are required to create End of Session Reports. Create a survey / form using Google Forms for each group member to fill out at the end of their 6-hour testing periods. You will end up with 6 entries (3 users x (2) 8-hour testing periods.) Link to your form here. Each of us will have to do the standard Questionnaire at the end of both of our testing periods. And taking a video sharing their experience of what they liked and did not like.
  • After – Crunching the data & documentation
    • After the field testing, how will your team structure a debriefing conversation? Each of us will read each other’s Questionnaire and watch one another’s videos, and come up with solutions to the things they didn’t like. And then we will have a discussion group / thinking out loud session about what worked and did not, and what we should update.
    • What will you do with the data and media once you find it? We have decided to not work on this assignment during testing period because we want to make each of us use this product as though we had just bought it off the shelf. When it is a break time and there are important things to note we can write it down so we don’t forget, but that is it. The goal of this testing period is to also see and discover ways to use this device and product.
    • How will you display or present your observations & findings? We will present this by doing a blog post, and video presentation.
    • Be sure to visually document each prototype after testing is complete and make notes on what state they’re in. Done deal.

During class we also talked about our branding. We created the stickers to go over the Puck.js (EMA) to dress up. We will need to find clear adhesive stickers and change the opacity on some of the stickers colours so it they don’t cover the Green and Red light.

We also worked after class on the BetterTouchTool software, to see how it works and play around with it, and also see what trigger makes the most sense for the user.

BetterTouchTool is a software application on Mac that allows you to create triggers and gestures to result in a action. We are playing around with it so that when your computer wakes up from sleeping – your reminders app / page will pop up on your screen so you can see what you need to do.

better-touch-tool-commands

We are also going to meeting after class in the DF lab around 6:00 PM to discuss what we need to do tomorrow and aim to finish.

End of day eight.

Thanks!


DAY NINE

DAY NINE OF OUR EXPERIMENT:

December 5, 2017

Today we worked on building our watches, finishing the code, and making our desktop accessories.

To start of the day we started working on ordering the proper stickers we need for our product design. We went to Staples and Michaels but they didn’t the right ones we need. So we ordered some from Amazon, https://www.amazon.ca/gp/product/B007Z7LQ54

And we then put our designs into the proper template, and we will print them off tomorrow!

We also purchased our desktop accessories and painted them!

painted-desktop-accessories desktop-accessories

From there, we put together our first watch!

 

The middle part is 3D printed, and the pink straps are the ones we purchased from Amazon.

The 3D part of the watch is slightly too far apart where we need to attach the watch bands, but with soldering we were able to push them together. But we might reprint these again just so the bands do not fall off when someone is wearing them.

While working on the code we also learnt more about how we will be using BetterTouchTool with the code.

We are using BetterTouchTool to pull up peoples note taking and reminder apps on their computer after their computer wakes up from sleep mode.

We are also using BetterTouchTool as a command to turn your display sleep by hitting Control D. This is the hotkey.

With the code we have it working when, you press the button (Puck.js (EMA)) the light turns GREEN and it starts the timer for 20 minutes (working time), and after 20 minutes the light turns RED and it sends the hotkey (BetterTouchTool command ; control D) to turn screen display to sleep. And Green blinking light = break time over, but it will not turn your computer display on.

We are working on the code to have a 5 minute timer for break times, and right now there is no way to turn off the computer all together.

Here is a video of wearing the device and turning your display on after a break and off to take a break:

End of day nine.

Thanks!


DAY TEN

DAY TEN OF OUR EXPERIMENT:

December 6, 2017

Today we met at 10 AM in the DF Lab to finish building the watch accessories and update the code too.

Here is a video of how you would pair your Puck.js (EMA) to bluetooth / the code we are using:

We also wrote a instruction manual for users to follow and read so they know how to use our Excuse Me Accessory.

Today is the first day for our testing period!

Testing Period #1:

Duration: 12 PM – 6 PM (for all of us).

  1. Take before videos / pictures of where you are testing and what accessory you are testing with and how you will be testing it.
  2. Write notes during testing period about things you like / don’t like.
  3. Take video during the 6 hour period of what you are doing and how you are using it. (We won’t be filming the full 6 hour period, just intervals of it).
  4. Test these accessories however you would like to!
  5. At the end of the 6 hour period take a video of your findings.
  6. At the end of the 6 hour period also complete the survey: https://docs.google.com/forms/d/e/1FAIpQLSf7FQ9jBOA8BOaoMN2CQpqUsHTAXv-PGnW7K97MhyYRyEu6Ww/viewform

The dates and times of testing period #1 are as follows:

All of us will be testing for 6 hours today -independently- from

Savaya: Will be testing from home using both the wearable and desktop accessory

Tommy: Will be testing from school (in the DF lab) using both the wearable and desktop accessory

Chris: Will be testing from school (in the DF lab) and at home using both the wearable and desktop accessory

*Chris, Tommy, and Savaya will be using our Apple Computers.

We also decided that if we want to update any part of the code and test the new version, rather than waiting for tomorrow’s testing period to test it, we will check in with one another every 2 hours to see how things are going. And update it then and test it during Testing Period #1.

We have individually written our own notes and taken video of our first testing period – and in our blog post we have added links to each of our observations. (Links are shown in Finale Project Blog Post).

Before testing started we worked on the setup and plan for Friday’s presentation of our product.

We took some of the required photos we need for our presentation on Friday.

After we got the code up and running, chatted about Friday, went over our testing schedule, and took some images of our product and device, we went on our own paths to test our product for the first time.

Notes on how things went for all of us will come soon!

End of day ten.

Thanks!


DAY ELEVEN

DAY ELEVEN OF OUR EXPERIMENT:

December 7, 2017

Today we met in the DF lab to take video for our final presentation on Friday.

Today is also the second day of our testing period!

Testing Period #2:

Duration: 12 PM – 6 PM (for all of us).

  1. Take before videos / pictures of where you are testing and what accessory you are testing with and how you will be testing it.
  2. Write notes during testing period about things you like / don’t like.
  3. Take video during the 6 hour period of what you are doing and how you are using it. (We won’t be filming the full 6 hour period, just intervals of it).
  4. Test these accessories however you would like to!
  5. At the end of the 6 hour period take a video of your findings.
  6. At the end of the 6 hour period also complete the survey: https://docs.google.com/forms/d/e/1FAIpQLSf7FQ9jBOA8BOaoMN2CQpqUsHTAXv-PGnW7K97MhyYRyEu6Ww/viewform

The dates and times of testing period #2 are as follows:

All of us will be testing for 6 hours today -independently- from

Savaya: Will be testing when walking around Toronto to run errands, using the wearable

Tommy: Will be testing at his gym using the wearable

Chris: Will be testing from home using both the wearable and desktop accessory

*Chris, Tommy, and Savaya will be using our Apple Computers.

We have individually written our own notes and taken video of our first testing period – and in our blog post we have added links to each of our observations. (Links are shown in Finale Project Blog Post).

We also worked on our instruction manual:

  • To turn on pair your device to bluetooth by… going to this website: https://www.espruino.com/ide/… click the yellow square in the top left corner and choose a device number that hasn’t been taken // then click PAIR // and wait for it to connect.
  • When you have to work the light will be GREEN.
  • When you have to break the light will be RED.
  • When the GREEN light is blinking it means break time is almost over.
  • When it is break time your screen will sleep.
  • To make your computer sleep go to BetterTouchTool and go to the tab that says Keyboards – then click +Add New Shortcut or Key Sequence and in Shortcut put ‘control – option – D’ then go to Trigger Predefined Action and select Sleep Display.
  • Working with BetterTouchTool.. You can include commands to trigger an app to launch when your screen wakes up. Go to the previous action above and then click on it and choose +Add New Shortcut or Key Sequence and select Trigger Predefined Action and choose Open Application / File / Apple Script… in Controlling other Applications list.
  • To turn device off hold your EMA for a few seconds so light will device off.
  • You are given an extra battery
  • You are given stickers
  • Desktop accessory
  • Watch Band
  • EMA 3D printed holder
  • To turn it on you click the EMA once quickly

Here is a image of the battery being used:

battery

Here is the final instruction manual which user would get in their package when purchasing this product:

https://docs.google.com/a/ocadu.ca/document/d/1zW0JyQokGSjLWK2eN_BKDi7QTTDJu2hzPR6c5kjh5lM/edit?usp=sharing

End of day eleven.

Thanks!


DAY TWELVE – THE REVEAL OF EXCUSE ME ACCESSORIES

DAY TWELVE OF OUR EXPERIMENT:

December 8, 2017

Today we are presenting our product to our class, and we are so excited about it!

Here is our code: https://github.com/ChrisLuginbuhl/WalkWear

Here is image  of people trying on our product: yiyi

Here is our video / presentation: https://vimeo.com/246383252

This is our final project description:

We created a product that assists people with their productivity by using the Pomodoro Technique. We made and designed the Excuse Me Accessories that are available in wearables and desktop accessories for you to choose how you want to wear or use our device. In the delivery package you will receive, the EMA device, a 3D printed EMA holder, a watch band, a desktop accessories, extra battery, and stickers.

End of day twelve.

Thanks!


FINAL PROJECT BLOG POST

Project overview:

Project title: Excuse Me Accessories

Group: Savaya Shinkaruk, Chris Luginbul, Tommy Ting

Project description, including overview of object and intended context and users:

To help people with their productivity on any task or activity we created the Excuse Me Accessories products. By using the Pomodoro Technique (work for 20 minutes – break for 5 minutes), people can follow this technique with their wearable or desktop accessory.

We tested this product in multiple ways because we want this product to be usable and available for people to use it how they choose. This product is great to use when in school or during work hours to help you focus on the tasks at hand. But it is also a great product to use when out and about running errands to know how much time you are spending in stores shopping.

2-minute video presenting the portable & summarizing the field testing plan & results:

https://vimeo.com/246383252

Image of device on its own:

img_7131

img_7146

Images with device being worn / used by each group member:

portraits-1

portraits-2

portraits-3

Production materials

Design files: more are in the blog above. 

stickers stickers3 stickers2

Final Bill of Materials (spreadsheet including costs & suppliers):

https://docs.google.com/spreadsheets/d/1clJ1SG9paU3YRE_ewiWXgeS4Wr1ZE-hx4iZrrl9CGBc/edit?usp=sharing

Final circuit diagram:

watchv3

ema

pugk-js-device

Code:  https://github.com/ChrisLuginbuhl/WalkWear

User testing materials

User testing plan:

For both of our testing periods we stuck to this consistent formula – but had the freedom to use this product to our own regards.

Duration: 12 PM – 6 PM (for all of us each day).

  1. Take before videos / pictures of where you are testing and what accessory you are testing with and how you will be testing it.
  2. Write notes during testing period about things you like / don’t like.
  3. Take video during the 6 hour period of what you are doing and how you are using it. (We won’t be filming the full 6 hour period, just intervals of it).
  4. Test these accessories however you would like to!
  5. At the end of the 6 hour period take a video of your findings.
  6. At the end of the 6 hour period also complete the survey: https://docs.google.com/forms/d/e/1FAIpQLSf7FQ9jBOA8BOaoMN2CQpqUsHTAXv-PGnW7K97MhyYRyEu6Ww/viewform

The dates and times of testing period #1 are as follows:

All of us will be testing for 6 hours today -independently- from

Savaya: Will be testing…*location

Tommy: Will be testing…*location

Chris: Will be testing…*location

*Chris, Tommy, and Savaya will be using our Apple Computers.

We have individually written our own notes and taken video of our first testing period – and in our blog post we have added links to each of our observations. (Links are shown in Finale Project Blog Post).

Link to end-of-session report forms:

Here is our feedback from the survey we each completed after both of our trail runs:

Savaya:

Testing Period ONE: https://docs.google.com/forms/d/e/1FAIpQLSf7FQ9jBOA8BOaoMN2CQpqUsHTAXv-PGnW7K97MhyYRyEu6Ww/viewanalytics

Testing Period TWO: https://docs.google.com/forms/d/e/1FAIpQLSf7FQ9jBOA8BOaoMN2CQpqUsHTAXv-PGnW7K97MhyYRyEu6Ww/viewanalytics

Tommy:

Testing Period ONE: Shown in his Google Doc.

Testing Period TWO: Shown in his Google Doc.

Chris:

Testing Period ONE: https://docs.google.com/forms/d/1vjf0zSr_2iWvGgt04cNeQrbLx7yqAydsGli3gOBK2tU/edit#response=ACYDBNjmFDXXOQ6Hd-VSOB6JoJtaJ0wiu9POMmWGkvu1JetOWe62f7v11YIl_A

Testing Period TWO:

https://docs.google.com/forms/d/1vjf0zSr_2iWvGgt04cNeQrbLx7yqAydsGli3gOBK2tU/edit#response=ACYDBNheNu74TooUHnBuqjHPLqsVlysUGnVt5D8tffGapAItLMut3ALzoig1BQ

Link to data collected: NOT APPLICABLE – our data is our feedback shown in our notes and survey (above).

Photos, video, or other media gathered in the field:

Photos, video, or other media gathered in field is represented in our individual Google Docs.

Summary of the testing process: Information is included in our individual Google Doc Links.

Savaya: https://docs.google.com/document/d/1CRPUb4gkZqGOY5HT9sN97NA_C4V-HzqGcLCNI3hviHE/edit

Chris: https://docs.google.com/document/d/14ZC8tYcGWOSXoA-tu3VwBUTSjqD1SYjhLelLFA1RQII/edit

Tommy: https://docs.google.com/document/d/1r_Hzi_QUvadfG6nPVTHZBSKM4YTKxPf7xu96qmMWD58/edit

Reflections on your findings:

Information is included in our individual Google Doc Links and Survey links listed above or in our individual Google Docs.

Any summary materials presented at the critique: This would be our desktop accessories and wearable, and stickers available (images in above blog post).

Code development notes:

Part of the reason for using Puck.js as our platform was that we wanted a compact, battery operated package.

The Puck.js is based on the Espruino architecture. This is an open source javascript interpreter for arduino-like microcontrollers. It is programmed via a web IDE, which uses web Bluetooth to connect to the puck.

The use of Javascript means this is an event-based development approach, which is a good solution for battery-operated projects that spend a lot of time waiting for something (a timer, a button press, a certain pin to change states, etc).

The use of Javascript requires a change in mindset and a change in libraries from what is normally used with Arduino, however! The web IDE does contain modules that function similarly to libraries in Arduino, which extend the functionality of the device, and allow access to hardware features. They are also pre-compiled, and so run more efficiently than writing lots of Javascript.

We used a Bluetooth HID library (HID = Human Interface Device – i.e. mouse, keyboard, etc), which allowed the Puck to connect to Windows and Mac computers as a bluetooth keyboard, and send hotkeys which would sleep the display or the computer.

Although javascript for Espruino is quite compact and concise, it was hard to develop for this environment because of

  1. i) the relatively young age of this system. Espruino was first funded in 2013 and Puck.js was first funded in 2015.
  2. ii) Javascript is normally run in web browsers, so most of the examples and conventions available relate to screen-based devices.

iii) There are still some bugs in the web IDE. Once or twice we were able to fix a bug simply by removing code that was already commented out!

Here is a image to show the old / new firmware we used in our process making:

old-vs-new-firmware

Further considerations:

Although it is quick and easy to make updates to the code and flash devices with small fixes, it quickly became clear that version tracking would be important. There is no way to check what version of code is running on a device once it has been flashed to that device. For testing and debugging, it was important to use github and not make spur-of-the-moment changes to code to be used in testing

References & related works:

Any references / support materials used for the project:

References to related articles, papers, projects, or other work that provide context for your project. Write about the relationship between your project and these references:

Do more and have fun with time management. (n.d.). Retrieved December 2, 2017, from https://cirillocompany.de/pages/pomodoro-technique

Misfit. (n.d.). Retrieved December 3, 2017, from https://misfit.com/fitness-trackers/misfit-shine

 

Leave a Reply