Wednesday, 11 June 2014

12/06/2014

Received the final version (for now) of the app today, Images have been received with the updated logos from the various organisations as well. Still waiting on the videos.

Overall I think perhaps too much time was spent organizing the event and not what was required for the brief which is why there feels to be a slight rush at this time, however I did not want to outweigh the importance of external assets since they would help make the event as cost effective and feasible as possible. In the end I planned enough time should things go wrong or stuff went unfinished by a certain date.

Monday, 9 June 2014

09/06/2014

Did a test with a previous testee to find out the reactions of a newer version of our app and produced relatively positive responses. The test results and responses can be found in the package.

Promotion wise the material is being produced a good rate, the team is really putting in all the effort possible.

I've decided to forgo talking to the people who run the monitors as we have AuSM's support and the time is better spent elsewhere. In any case I will note it down as a projection for future pursuit of this project.

Thursday, 5 June 2014

6/06/2014

Testing with a newer version today there were issues concerning the app itself. It being unfinished made it unclear to the participant what was the purpose and goals. On top of that the AR recognition caused issues where the participant discovered it recognized all the stack end cards. This lead to "cheating" and not actually running the course properly. This then led to questioning the purpose of our app and event.

Taking the responses into consideration the positive feedback (From tests and external parties) tells us that we have a good idea and concept however the negative feedback tells us that the physical execution needs to be perfect to generate the interest necessary for the event to run successfully.

As a projection forward we would indeed need to develop the app to a stage where it functions properly thereby eliminating any confusion by the participant. This would require additional image recognition to ensure that AR only picks up the image target that we specify for the associated section.

Another thing that came up in one of the responses was that this type of event would need to be repeated more than once to achieve it's desired effect. 

Wednesday, 4 June 2014

04/06/2014

The problem with AR recognizing any stack end card persists and so is a thing that will be solved in an imaginary future, as there are some more important aspects of the app that needs addressing.

In terms of the Hub's support it's still pending however my meeting with the manager today most likely put me on the positive side of things so we will see.

One last party I haven't considered is the people who run the monitors which came up in my meeting with the Hub. I was under the assumption that we would have it's services (in theory) but I guess it's safe not to assume this?

Monday, 2 June 2014

03/06/2014

Got support from AuSM who are willing to promote the event for free by putting up our posters. Opened up a dialogue with the Hub hopefully will get their support in the coming days. We do have a poster as well as a set of instructions now, progress appears to be good. 

Most of the App and Planning work have been finished, all that remains is some more testing and the promotional material.

Updated package incoming.

Friday, 30 May 2014

30/05/2014

Had a meeting today that I thought would take longer due to the amount of issues that needed to be covered. I was however pleasantly surprised that we finished everything necessary in a short amount of time. We uncovered and discussed the crash issues as well as the over-identification and are opting currently to do as best we can to fix it, if not we will document it and move on.

Requested posters to be done by tomorrow as I need to send it off to other parties involved, hopefully to get their support. It's important in my view to know what external resources we would have (even if we're not running the event for real) as it tells us how much we have at our disposal as well as some insights into the project that I couldn't foresee (I try to be as psychic as possible in predicting every possible outcome).

Currently the project is progressing at a good rate, with things happening at the times I designate (more or less) and any errors in communication aren't too costly as I reserved time for such things in advance.



On a very separate note I just wanted to mention some articles here that I have been quoted in by Edwin:

Article 1
Article 2

Thursday, 29 May 2014

29/05/2014

Test 3

Did not happen due to the person's phone crashing on start up and this is a major problem that needs solving (hopefully with some help)