Day 9 – 26.03.2015

(Philipp Hauptmann)

The last the day before the final presentation was marked by the pressure of getting everything done each group had in mind to implement in their prototypes.

20150326_092533The day started with a short summary of the groups’ state of the art. Each one of them seemed confident, most of the wires had been connected and most of the code written. They also explained the further and final steps to get their prototype ready to present.

20150326_093242

After this round tour, Martin showed us the blog of his previous course and pointed out some aspects he expects us to work into this year’s blog posts. Important notes were to avoid too short entries and to bring some kind of  structure into the blog.

At next, with everything concerning the organisation had been said, the groups continued working on their prototypes. While the ones who where developing software prototypes were busy with eliminating bugs, the hardware groups fixed electronical issues like not-working electronical components.

20150326_104837

Team “Schokobox” finally got their box for the final presentation. The work on this day focused on the progress bar and adding some minor design changes.

20150326_104831

Team “Alfons” handled some issues with their servo motors (“It works 4 out of 5 times”) and created a case for Alfons.

todo

Team “Embracelet” had a huge To-Do list, as well. The main problem was dealing with minor-quality electronical components (50% of their brand-new touch sensors stopped working in the hot phase of the project) and making a trade-off in the final product (less touch input area).

The teams “Matchday” and “Keepsake” went into deep-code-mode and had been seen again on the other day.

After every group possessed a reasonably working product, they had to take and cut scenes for their video prototype, needed for the final presentation. While some teams stayed inside the rooms of the building, others went outside and  took scenes in the urban environment.

Although some teams had to insert a night shift, each of them finished their prototypes for the next day.

Embracelet

Connecting couples.

(written by Benjamin Eder & Philipp Hauptmann)

The original idea
In the two weeks of the course, our team developed two bracelet prototypes which are supposed to help couples in a long-distance relationship. The basic idea came from an interview of our team member Shao. The question was: Did you ever had a hard situation in your life you had to overcome? Shao being interviewed
As a result, Shao told us that he lived in a long-distance relationship and what helped him to overcome this situation. We took his experience and extracted important points. As a result we figured out that small attention gestures like a short message are important key elements. The fact that the partner is thinking about you is more satisfying than the actual content of the message itself. In a brainstorming round we figured out what we can do to strengthen this user experience. We came out with the idea of bracelets which can transfer visual and tactile feedback between each other.  We chose the bracelet because it’s tight to the body and allows subtle interaction.

The story behind – and first decisions
Creating the story board, Shao had in mind, that the bracelet idea also seems to fit in the family context. His story introduces you to Xaver, Leni and their child Schorsch, which are apart a huge time of the day, because Xaver works in night shifts. The basic idea was, that everytime a family member touches the bracelet, all of the others receive visual feedback by their bracelet turning into the color of the sender.Xaver Storyboard Now, when Xaver wants to show that he thinks about Schorsch, Leni receives a feedback, too. This is some kind of a conflicting user experience and results out of the mixture of the different contexts ‘belonging to a group’ and ‘intimate communication’.  In order to create an unique user experience, we decided to focus on only one context.  After discussing in our group and with the help of Martin’s feedback, we settled for the original context of a couple being apart.

Basic elements
That means we’re gonna have only two bracelets, which represent the direct connection between the partners and aim to allow them emotional and physical closeness over spatial distance away. Touching your own bracelet to let your partner’s bracelet glow addresses the emotional side: the bracelet begins to fade and lights up and you know that your partner is thinking about you right now. To enhance the experienced closeness, we decided to add tactile interaction to feel your partners touches physically: stroke above your bracelet and it simulates the touch on the corresponding spot on your partner’s.
After working on the prototype for several days, we achieved every element we wanted to put in the product.


In general, Embracelet offers three modes to interact with your partner.

Mode 1:When one partner feels lonely he or she can tap on the bracelet and both bracelets glow with the sender’s color for a certain period of time. In addition the receiver’s bracelet vibrate on the same position of the sender’s tap. By simulating your partner stroking around your wrist tenderly, this shall strengthen the closeness to each other.
Mode 2: When the receiver taps on his bracelet shortly after it began to glow, both bracelets start vibrating and glowing. The new color differs from the sender’s and receiver’s color by being a mixture of both. This symbolizes the connection of the partners and both know that they are thinking of each other at the same time.
Mode 3: An additional feature is the white color of the bracelet’s LED. When you are getting regionally closer to your partner, Embracelet starts to glow in white, getting more and more intensive the closer you  get to him. That expresses the increasing anticipation you feel when you finally meet your partner again.

Technical Details
For reasons of economy, we developed the pair of bracelets as a master/slave system. One bracelet sends touch gestures, the other one receives the corresponding feedback.
At the first glance, both bracelets look identical. Both have built-in LED Strips. But the difference between sender and receiver is on the inner side: while the sender needs touch sensors to compute the input, the receiver includes vibrating mini motor disks to simulate the partner’s contact. Both bracelets are controlled by / wired to one arduino mega board which manages the software. The final product acts both as a sender and receiver.

Technical impressions