Friday, 25 September 2015

25.09.15

CRITIQUE & FURTHER PROTOTYPING

Over the week I was given the task of looking for different visual approaches for our app and how that may or may not translate for the different age groups. We had some sort of mis-understanding with our demographic because I still thought we were going to work with little children whereas Natalie thought we had made our demographic smaller from 10 to 16 year olds. We sorted that out today in class and just thought of not to limit it as much for now just so we can see how the user interface aesthetics can change accordingly. 

So far I've looked at vector avatar art more based around the younger child demographic as opposed to a low poly art style for the older teens. It definitely juxtaposes but we will see where we go from there. We also got to talk with a 4th year student and how she perceived this app. We got some good points to look at and further implement.  

Our app involves choosing a character/avatar and I thought that might limit the user a bit too much because what if so many people choose the same one? I came across this picture that said make your own character. There were some body shapes, eyes, mouth and noses which then the user could personalise. Examples will be in the workbook anyway.

- How will kids be actually motivated to use the 'my mood' aspect of the app?
- How does it engage with the child, parents and mentor to make it a system?
- Would prompts for the parent and child app needed because we would also be looking at how the child and parents would also needed to communicate with one another. 

We also got to talk to Sam from Lifehack and he also had some good feedback and critique for our project. There are some aspects we have researched in depth that would reinforce our project such as how are children and even parents introduced to this app in the first place. It could even be this is a tool a real life service may eventually use. It was very useful because he made us think in terms of the 5 types of wellbeing and how we initially started and how our prototype would link back to our brief. It's about not losing the connection between these points. We need to make that more clear which we will definitely do in the upcoming weeks. For now our important step is to suss down what we need and don't need in terms of the app and the whole aesthetic. Ongoing research will be carried on throughout. 

I feel as if this could be a real thing if we wanted it to be and it seems like the app could get big in terms of content. I think we are on track and just need to keep on moving forward. 


Friday, 18 September 2015

18.09.15

DEVELOPMENT OF PROTOTYPE

After last week we have looked into the visual aesthetic of possible styles our app could have. We have also looked into what possible tabs could be within our app. After our mini presentation of our app we received feedback of how the user experience correlates with the age. Why would a 16 year old boy use a cute panda as an avatar? These sorts of complications we have started looking into and hope to resolve these issues by next week.

I feel like we need to suss down these aspects and get ahead with our actual prototype. Looking at our site map we feel like this app has so many functions and we ourselves don't know how big this app could be. We have thought about how this app could initially be recognised through youth centres, counsellors even GPs. 

Also another point we have to look at is how will this app change the behaviour of the user. To go with this statement we made a 'pick your lucky number' thing and tried it out. Good ol' Steven being cheerful as  always. This is the reaction we would like for our users to feel happy. 


Saturday, 12 September 2015

12.09.15

INITIAL PROTOTYPING 

Today in class we began to prototype and test our solution. At first we thought of prototyping a book but that is very 2D for now. We then just began to think about how an app would work as a 3D interface for the user. We got helpful feedback from the tutors today. Instead of assuming what the app should have we need to research and interview more people of how they would want the app to be. So whatever is in the app should be more applicable to the actual user and how it should be according to them. 

It should be aesthetically people because our aim is for the user to continuously use the app and yet be simple to use.  

Thursday, 10 September 2015

10.09.15

FURTHER RESEARCH AND SOLUTION IDEATION

I've been looking into possible solutions or our brief and it is a tough choice. There definitely are resources out there but they aren't so known particularly in New Zealand. 

Three possible solutions so far:

Picture Book according to our target audience
Website/forum that helps kids connect with other kids going through the same sort of thing
App where the child can also learn and understand divorce better. (Rough Idea) So many kids play with phones and ipads that this isn't much of an issue of how they would have access to an app. 

I had also interviewed my friend's sister because she has gone through her parents divorcing. Even before asking her anything I wanted to make sure she was okay with it because I didn't want her to get upset. The interview went well but as much as she answered the questions she realised that she is still going through the after affects of divorce. 

Sometimes I feel that the school curriculum should also include a topic about divorce and how to handle it. I mean if you can keep talking about puberty every year or shit thats going on around the world why not teach a bit about divorce so children may be able to understand the whole idea. 

She definitely wishes there was something when she was initially going through the process. 

App that informs the user of the situation yet helping you ease through it. Nowadays many kids have access to smartphone so even this solution looks realistic. We just have to think a bit more about the actual user experience. 

Website the same sort of experience as the app. To educate/inform the user whilst appealing to the user through aesthetics and user-bility. The content is yet to be decided.