Allumette #animation #nowordsneeded #upinthesky #Icried #drama #fairytale

10points

Official summary : Allumette tells a story about love, sacrifice and a deep bond between a young girl and her mother.

Personal review: Allumette is a non interactive VR film. It is beautiful just the way it is. The animations and the characters are on point, beautifully made. The story is a new version of the Little Match-Girl so it is expected to be really sad. In the beginning you find yourself in the sky, in a small village on the clouds. There is a girl with 3 magic matches and whenever she burns one we can go back in time.

The story itself is beautiful and the animations are amazing. The whole atmosphere is just beautiful. I like the fact that for example when there is a ship or house I can dive in them and see them inside.

The characters are so lively, I wish I could touch them.

Overall I love this piece so much! Great example of VR cinematic pieces.

Portfolio – User Experience Design 2017 Summary | Emma

Project Name:  Capsule Wardrobe

Group: Emma, Quintus, Jenny

 

 

 

User Interview: 

 

 

 

User Interview 1

User Interview 2

User Interview 3

 

User Interview 4

 

User Interview 5

 

User Interview 6

 

 

 

 

 

 

 

Prototype

 

 

 

Presentation + portfolio by Máté

Here is the link to my presentation:

https://docs.google.com/a/nyu.edu/presentation/d/13jV_kpZE7PcKGcnTTeAFZRWnTPC0rT3INp5RCI6rcXk/edit?usp=sharing

And to my portfolio (to be expanded and added to my personal website in the future):

https://docs.google.com/a/nyu.edu/presentation/d/1cDmjosljH1BjSir-Z5xHiDzAWLI5jd6w9E3FuZoyqiU/edit?usp=sharing

UX Final Project: Comiary

Motivation

My personal experience during and after studying away motivates me to create a project which can record the life. Thoughts, feelings, and attitude toward life or people change all the time. It would be nice to have my own biography in which I can record these emotions and ideas so that when I looked back I can see the change and growth.

Based on this idea, I started brain storming. At the beginning, I want to do a game. The form will be like an interactive comics. User can make choices at turning point of life, such as which college to apply, what major to choose, and what job to do. However, I soon abandoned this idea because I didn’t know what should be the proper structure of the game, and drawing comics would be a heavy work load.

Then I changed my mind: instead of making a game, I want to make a diary encouraging people to keep diary, especially young generation. I think comics can be a trigger because most of the young people enjoy different kinds of comics. Therefore, I did a second round of brain storming. You can details below.

The APP will use machine learning to recognize key words in diary entry and audio log, and match key words with the picture library. This is the mechanism of how the APP can generate comics based on the content of user’s entry.

User Research, Personas, and Scenarios

After figuring out what the product and how the products works, I worked on finding my target users and their interests.

I conducted two kinds of user researches: online survey and face-to-face interview.

Online survey

I used Tecent questionnaire to do the online survey. In the survey, I collected the basic information about potential users, such as gender, age and job. Moreover, I asked some questions related to their behavior and attitude related to diary.

I collected 57 responses in two days, which is not bad. Two-third of the people responded were female, and the majority of the people responded were students (This result is biased because I don’t have enough connections off-campus).

It is also interesting to see that people don’t keep a diary not because they have nothing to write, but because they are lazy or they don’t have enough time.

Following are the screen shots of the results of the online survey:

The gender distribution of people respondedReasons why people don’t keep diary Whether people have the habit of keeping a diary

Interview

I interviewed people who shown a strong interest in my APP. During the interview, I asked them the motivation of keeping a diary and what features they expected while using the app.

Personas and Scenarios

I built the personas based on the data I collected. Since most of the people responded are female, I assumed that female would be more interested in using my APP. Therefore, these are two female personas: one is relatively introvert, while the other is more extrovert. Besides the differences personality, they have different motivations using the APP.

You can find more info about these two users and the scenarios of using the APP.

Story Board

The following story board is about a young white collar using my APP. He had a bad day: he didn’t bring the umbrella, and it started rainy; his boss was angry about his work. After he went to home, he took out his phone and made a new diary entry about what happened and how he felt. The APP then generated a healing comics based on the content of his entry. Viewing the comics, he felt be healed. He then went to sleep.

This story board was created before making any wireframe. The interface looks different from the one of the prototype. However, the concept is the safe.

The App, Comiary, encourages people to capture event no matter big or small, and their emotions. It simplifies the process of writing a diary, and the comics generated can provide positive energy for users.

User Flow and Site Map

After several interviews in the user research, I decided to create three section in the APP: today, where user can add new dairy entry for the day; past, where user can view his or her previous diary entries or comics; future, where user can send a letter to the future or add to-do list.

The initial user flow and site map look like this:

After a discussion with Professor Azure, I decided to delete the ‘future’ section, because the function of this section went too far away from my initial idea and the core task of the APP: recording life.

Following is the site map for my prototype:

Wireframe

My wireframe is base on the user flow diagram and the design of APP icon I made earlier.

The idea of the icon is the combination of “D” from diary and an element representing the feature of comics. I chose a face without mouth because I want to leave space for user to add his or her feeling.

 

 

During the process, I found it quite different from drawing the user flow. I needed consider so many details, such as the position of a segment, the grid, the exit button. Moreover, when I added a new button, several interfaces needed to be added. When adding one new function, a UX designer needs to consider a lot of things.

You can get a general idea of my wireframe through this screen recording: ScreenRecording_09-26-2017-0020 or see the pictures below. At that stage, I didn’t think about the details of the “setting” menu.

Usability Test

Before the National Holiday, I interviewed several students, two freshmen, 1 sophomore, 1 Junior,  2 seniors and 1 staff (who is about 4 years older than me). Following are the pictures of my notes (in Chinese though).

The interviewees gave me several useful suggestions:

  1. The name of the APP need to be clear enough to tell the user that it is an APP generate comics based on your diary entry. Therefore, I create “COMIARY”, which is a combination of “comics” and “diary”.
  2. The theme color of the app should be a warm an healing, instead of black and white. since it is an diary app in which people will express their negative feelings, using black and white may make them feel more upset. However, since different people have different taste, user can choose the theme color based on their preference.
  3. The section on the home page need to be refined. It is should to based on a timeline, instead of simply using present and past.
  4. The ‘adding a new entry’ button is not clear enough.
  5. User do not see that they need to input the weather and their mood before they make an new entry.
  6. There should be loading bar when generating the comics so that the users can know how long they need to wait. Moreover, it should be clear on the editing page that the next step will be generating the comics.
  7. About the voice input, it can be a short voice memo about 1-2 minutes long which can be inserted into the diary entry.
  8. Before generating the comics, let the user choose what kind of comics they want. There can be preview of what the comics will be like of each kind of comics. What’s more, user can choose they want the comics in black and white or in color.
  9. When a user is reading the comics, the gesture they use shouldn’t be scroll up and down but left and right.
  10. If the comics can be combined with the diary entry and the voice input somehow, it would be great.

Prototype

Based on these suggestions, I made the first version of prototype. You can see the screen recording here (There is some link errors).

After we learnt the design principle, I refined my prototype.

After researching on color mood on pinterest, I chose to use the color of this picture because orange is warm and attractive to capture people’s attention. Primary color: #ff5722; secondary color: #004d40; other colors: #ffffff, #ff8a50, #b2dfdb

I used Sketch to design the interface, and the Sketch Mirror helped me lot.

You can play with prototype on Marvel: https://marvelapp.com/10eda9ig/screen/33704055

 

Mock Up

To make the sense that users can use the App anytime and anywhere, I made several mockups with placeit.net.

Reference

  • pinterest.com
  • material.io
  • marvelapp.com
  • placeit.net
  • Diary Apps: 

Special Thanks to:

Professor Azure Qian

UX “S U C K E R S” Final Documentation

For my UX design final, I decided to continue on with the project that I’d been doing for the entirety of the course that I plan on eventually applying to my capstone. However, despite the fact that it is the same project, it’s changed so much since the course began that I wouldn’t be surprised if someone thought it was a different one entirely! For starters, in the beginning, the project was originally called The Art of Peace (in pieces), and while this may seem like an artificial change, it ultimately came down to the same thing that a lot of my changes were motivated by: the user research that I did simply didn’t indicate that people were all that interested in playing a video game (i.e. the “in pieces” bit of the title).

In fact, despite my initial impulses to completely gamify the experience, when asked on a scale of 0-10 the importance of having a game component to the success of the project, the score averaged out to ~5.58, showing a degree of apathy considering the alternatives (needing a game component to consider the project a success and not having a game component to consider the project a success). In addition, when asked on a scale of 0-10, how much of a gamer one would consider themselves, responses averaged even lower at only ~4.08.

But yet, those two responses drastically changed the direction of the project… Not only did it change the name from Art of Peace to S U C K E R S, it helped me reduce the number of personas I had to focus on to two in particular, it allowed me to simplify the number of interactions that I would have–which ultimately also impacted my user flow and “app map,” and it helped me focus my wireframes (both pen + paper and digital) and visual prototype to just interactions that had to do with playing video and the location-based components of the project.

Ultimately this is all just to say that I found the User Research phase of the design process quite helpful, potentially even the most helpful of the stages that I went through. And now, since I’m going to continue on with this project for my capstone, I’m pleased to have some more skills in my toolset. In fact, since giving my presentation, I’ve started another survey and started to circulate it through different social media channels. Though, I will say, that this time around I’m going to try harder to get respondents that I don’t necessarily know as I didn’t quite get as much feedback as I would’ve liked from the last survey. I also plan on definitely getting more one-on-one user testing now that I have a higher fidelity prototype, since the last time I did user interviews they weren’t quite the level of professionality that I would normally strive for: they weren’t recorded and the basic wireframing of the app made the responses much more abstract since the app’s direction was still in limbo considering that I still wasn’t that sure about if I was going to include the game aspects or not yet.

On another note, I was also quite pleased with the course because it enabled me to really get in the trenches when it came to defining the visual/artistic direction of the project. I’m extremely proud of how thoroughly I was able to design the aesthetic of the project, especially considering how early I am in to this capstone process! I loved searching through the depths of the internet to try to find the coolest retro UIs and pixelated icons, and even though I wasn’t able to include some cool finds and extra work that I did to make elements that worked with my overall artistic vision, again, I look forward to adding them as the year goes on!

Any how, here’s the link to the current Behance of the project and I hope you contribute to the new survey!

Final Project

My app idea was an app that takes your existing entertainment media accounts like iTunes, Netflix, Kindle, and Youtube and recommends media in the language you are learning to you. The apps target audience is younger people who have already been learning a language in a formal setting for at least two consecutive years. While it is not meant for people who have not been actively trying to learn a language, while interviewing people I realized there is a small portion of users who would use it just because they enjoy the that specific genre of media(international movies and music) and would use it to find more than what they can access on Netflix by themselves since they would have troubles searching for titles using just English. Surprisingly my survey showed that many people did use media to watch/listen to media in their target language. The average length for people to study a language was 7 years, which was good because that is within my target audience. Since my app would mostly function as a resource that draws information from other sites I think I would end up marketing it as free or at least a very low price especially since I think it would be easy to get money from ads. All of the people who took my survey wrote they would be interested in it especially if it were free. I had originally thought it would be used to get people interested in the language again after learning it for so long and getting bored with it, but only a few people out of 31 stated that they were any less bored with learning the language than when they first started learning it. It seems that people just want recommendations so they  can improve their language skills faster, increase their cultural understanding beyond the language, and improve their language in a less grade focused way. When I conducted individual interviews people told me they think that once you have hit the 3-4 year mark it is a good point to start trying to listen/watch media in the target language and that from personal experience they think it really helps them increase their language skills. I think the mark to start listening to media in a different language might be a little different depending on the persons age, but my app would target high schoolers and above so I think it is fine. The only real question they had was would the algorithm to suggest media be as good as Youtube autoplay.

Here are my storyboards, user flow, and brainstorm kth276_10-30-2017_17-41-56.

Below are the icons and logo I made for the app. The tagline I came up with is “Fluent Faster”.These are the early versions app,  app2.0 the first one is the wire frame and the second is when I started doing the mockups. While I was user testing people told me my app was a little text heavy. In general they didn’t have too many problems with navigation, but they didn’t think the layout was that attractive for a mobile app. They also had some questions about how I named some of the features and I realized that some of the names I had were just things I saw in other apps and actually weren’t important for me to have. I don’t think it was as confusing for them as me, but sometimes I had to think about how it would work between playing things on the app or whether the app would be purely for recommendations. You can see at one point I added a search bar, but I decided against it because I wanted it to be recommendations not a place like Youtube where you could just find everything. Some people said it was a little crowded and how it would work if you chose a language that was less popular and I think it would have to be one of those apps that relies on user feedback to a certain extent. Also some of the screens didn’t seem to perfectly line up with the last one that just caused some discomfort while trying the prototype but I think that is partially due to the fact that I used inDesign to build it.

Here are the persona’s and respective scenarios I created for users of my app. Persona1 Persona2 Persona3.

Here are screenshots from my first drawing of the app and uploaded to Marvel.

 

This is the final product I came up with : SpeakEz.

UXdesign Final: Final portfolio and thoughts on it (Diamond)

Project name: Visictivity

Function:

Create Event and join event based on realtime-based Projecting shapes and QR codes.

Inspiration:

When finishing our courses and having some free time, many of us tend to do something to relax or doing something collectively. However, it is not easy to meet everyone’s time so that a group can be formed and then have lunch or do other things. In this case, using emails or social media seems slow and has a potential risk to be “ignored” by others. So I feel like to create a platform focusing on finding the nearby people who would like to respond your advocation and group and chill.

Tool used:

Balsamic (for mock-up), Xtensio(for persona), Photoshops&Skecth (Interface design).

Continue reading