Report BACK!

Fridays report back session was interesting with all the groups giving a quick heads up on where they were in their projects. It was a good chance to get more feedback from the tutors on our project and get an idea of how far ahead / behind we are compared with everyone else. Something that Peter said was super useful in that we should not get lost in the technical implementation and instead go for a simple option which we could build and start testing.

Team Wearables were tossing up between Arduino or RasperryPI to power their wearable device. GoodVibes (CHANGED THEIR NAME, treble makers was an excellent pun so now I am sad) they were also diving into the tech and had a semi-functional prototype. This seemed to be the theme for a lot of teams working their way into the technology and building their prototypes. It makes me feel like we are a little bit behind the eight-ball as we have yet to really start making any meaningful progress towards our digital prototype yet.

The tangible data team has split their group into three with everyone working on something different. Someone was working on gathering data for them and putting in a usable form for unity, someone on building the beast AI and other working on the glove wearable. This really hit home that we need to start allocating some heavy tasks to each team member so that we can get into the meat of this project.  We quickly talked about allocating our work out like such: Unity depth work, Unity animation work, Scenario design work.

Team Zhu are also going to be using the Kinect with depth sensor for their project using unity so we need to make sure we keep in touch with them. Our teams can hopefully work together on coding problems and help with technical issues.

For the presentation next week  we have a lot of work to do in terms of the actual build of the prototype  so thankfully it is an informal presentation. However we need to think about what we want to communicate to the class and the experience we want to deliver at the end.