The last time I posted I was somewhat stressed with the direction of my project and what I still have to do. Although this generally still is the case I have put together a series of simple, yet direct, questions to ask myself regarding the direction and scope of the project. I’m hoping that I’ll be able to nail down certain elements and continue with others.

You see, I think I have reached a stage where  have over thought a lot of things; a brief chat with Graham this morning about whether or not it was worth rebuilding the physical aspects of the project let me realise that it’s OK to leave certain elements at a not-quite-complete stage provided that they are neither key to the overall user experience or outside the scope of the project (something which I hope to narrow down in this post).

So, here goes…

What is the point of this project? This is not a description of the service / product but rather a summary of what I wanted to achieve from this project.

At the very beginning of 4th year I knew one thing, and one thing only, about my final degree project: that it wasn’t going to be a website. Coding websites is a skill I have and something which I find relatively easy to do (when the ideas are flowing), however, I wanted to step outside my comfort zone and learn a thing or two about physical computing.

I want this project to be visually strong, technically challenging and very much a learning curve. However, I also want the project to gel together strongly and ultimately justify a strong grade.

In short, I suppose, I want to be adventurous and have fun experimenting with possible alternatives for my project but at the same time craft all the elements with enough care and attention to detail a strong final grade deserves. Even shorter, I want something which works really effing well and looks good too.

What is the service / product? This is the description of the service / product.

The service is called SlopeScope; a pre-installed, automated video recording system for snowboarders using indoor slopes (edit: I have since decided that although my tech would function better in an indoor environment with sufficient funding / research the system could be brought to life practically outdoors; this is the obviously more exciting final goal). A series of cameras track the rider as he progresses down the slope recording high quality footage simultaneously from multiple angles.

Once out of the visible range of the cameras the system then compiles a ‘memento video’ alongside each individual source which the rider can then access later on either on the slope via a mobile device (such as iPhone) or online via a web browser.

What are the key elements / interactions / features of the service / product?

One of the key features of the system is its passive nature; the ability to allow the rider to focus on their sport is a very attractive feature. In order for that to work (or rather to demonstrate persuasively in the prototype) the movement must be fluid and highly responsive. this is especially important if my iPhone app and website are going to have high quality videos appearing within them - it must be conceivable that the prototype was capable of such recordings, even if it is just able to physically move ‘nicely’ enough.

The second key areas of interaction are more ‘conscious’; the iPhone app and the website will be actively used to judge the overall usability and efficiency of the system. If the scenario arose where the tech worked perfectly and from a control engineering point-of-view was very advanced but the website and the app were ugly, buggy and shoved together in the last minute then the end user would leave with the impression that the entire system was flawed. It is imperative that all elements be at a sufficiently high standard so as not to bring the others down but the real decision is to decide which parts are polished slightly more.

Realistically, what would be an ideal finished product?

This question is very subjective and relies heavily on what is available to me; however, no holes barred, here’s a sum up based on what I’ve got at the moment. I have reached the conclusion that I am unable to (and indeed it is unnecessary to) build a prototype which works perfectly. I am ‘faking it’ with a very large percentage of the overall system but that is fine as each element is simply there to demo the concept of that particular aspect of the service.

I am happy to produce prototypes which ‘feel like’ prototypes, I’m not too concerned with covering my tracks completely. It was even discussed today that it may be in my interest to redesign the camera housing (but only if I’m doing it anyway to incorporate new hardware) so that some of the internal components are clearly visible - further highlighting the case that THIS IS NOT HOW IT WILL BE IN REAL LIFE. The iPhone app and the web app however I do want to hide the inner workings i.e: just show off how it would work and play on the fact that at the degree show there will be no snow (well, here’s hoping, we all know my luck). Therefore, making it acceptable for the app and website to not update with ‘live’ footage from the prototype camera.

In roder for the website and app to succeed though I will need some strong footage ‘from the prototype’. Which leads me on to my Tell Phase - how I’m going to fake my project.

TELL PHASE

With only 30 days (yeep!) till the viva I am running very late with my video and great image. Looking back at past project I have never been one to excel at the video stage; I want this to change for this project. Whilst I’m not looking to work primarily in the film industry I would like to be able to prove that I am capable of producing high quality video if needed as I feel it’s a valuable skill in communicating ideas and concepts quickly and accurately. Anyway, some thoughts…

Thoughts for the video…

My oh my - the ever looming Tell video. In all honesty I haven’t a clue how I want to approach this video. So, in true client-from-hell style I’ll start by saying what I dislike and what is a definite no-no.

Firstly, this video can’t be an advert. An advert relies on the service actually existing, or at least existing in such a way that a product can be seen. As the prototype is cardboard and deliberately not been designed for the real world I cannot justify an approach which is selling the service.

I do however feel that it is appropriate, and entirely necessary, to portray the feeling of what it may be like being recorded. It could be a deliberate play that throughout the video you don’t actually see the cameras as when using the system you’re supposed to ignore them anyway (did that make sense?). So the video would be about the concious interactions; the journey to the slope, the putting on of kit, the ride and then the review whilst on the tow back to the top.

I don’t know, thoughts on a postcard please.

Thoughts for the One Great Image…

This I haven’t even thought about slightly. How on Earht do I capture all the essance of the project in an image? On one hand I could focus on the cardboard prototype - a great image of the project as a whole. Or something a bit more defined, over-the-shoulder of someone using the iPhone app with the snow and board clearly visible; a great image of the conceptual service?

Gack. Who knows. My brain is fried for today, it’s been too sunny to work properly.