Why & how
To have a summary of the context of the assignment, stakeholder, goal and schedule, we as a group made a project plan. This is beneficial for us as a team and for the stakeholders for insights.
Conclusion
A document that gives overview for outsiders of the project, stakeholders and the team itself.
Why & how
We as a group formulated multiple important subquestions for the client project, we divided these subquestions over the team. My subquestion is:
I looked at best practices and how they handle the user engagement. I also did library research on articles and trusted sources for how to keep users engaged.
Conclusion
When consulting best practices regarding the user engagement and retention, gamification is often seen. In the example of Duolingo the game elements are something to test and could be a major improvement.
As written in the hypotheses, the lack of feedback needs improving in any way possible. This can be done even a small change to a whole make over. In apps like Duolingo after completing a lesson you directly get rewarded. This gives a sense of completion and notifies the user that the lesson that has started also has ended. Without it, the flow of the experience will be abrupt and will make it unclear what the user has done. So these small subtle details do matter.
Why & how
To explain why and how I made the new app design, I made this document. I explain what the current design misses and how the new design fixes that. I used conclusions from the Subquestion research to justify my decisions.
Conclusion
I now have a design that is built and based on the validated conclusions from the Subquestion Research. The design is a high fidelity prototype that has been tested by target group users and by peers. Made from iterations of this feedback and test results.
Why & how
To hold important information we made a Miro board. We held brainstorming sessions and planned meetings via this platform.
Conclusion
We made the design challenge, user stories and divided our work via this platform. Miro is a very useful tool, I will use it more after this project.
Why & how
Using the outcomes of the before done research, I made a testable high-fidelity prototype of a new application design.
The whole document can be viewed here.
Conclusion
A testable high fidelity prototype of a researched application design.
Why & how
Using the outcomes of the before done research and designs of other team members, I helped make a high-fidelity prototype of the new application design.
The whole document can be viewed here.
Conclusion
A testable high fidelity prototype of a researched application design.
Why & how
We created and designed a document that contains which elements of our design are the most valuable to work on and which will have the biggest influence on the users.
Conclusion
A document that contains valuable mandatory information on what is feasible and kind of improvements of the app will make a difference.
Why & how
For our final product, we created a presentation that demonstrated how we approached the project, the research questions we generated, the design process we used, and an interactive prototype of the final design in operation. Finally, we've created an advice document for them, telling them which elements are the most valuable to work on initially and which will have the greatest influence on consumers to keep them returning to the app.
Conclusion
Our stakeholders were happy with the result and the design choices of the high-end prototype we explained in the advice document.
Why & how
Before the international week it was our task to do research on the research question: “What is the metaverse”. I did a variety of research methods and looked at best practices to answer this question in a subjective manner.
Conclusion
I found out that I do not really know what to expect from the metaverse, it can become a good nor bad thing. But I liked the connectivity it brings.
Why & how
We compared the differences of the cultures in the group. Eva is from Slovakia, but studies in Denmark. We did this comparisment because it was recommended by the teachers to get to know each other. To do this, we used the Hofstede Insights method.
Conclusion
We learned a lot about each other culture and this started the conversation which is a win because I gained a lot more trust in the team.
Why & how
At the end of the week we needed to hand in a video via a YouTube link. Because I like to edit, I volunteered. I used Premiere Pro and iterated on peer to peer feedback. We held multiple brainstorm sessions to get the most ideas for video.
Conclusion
To hear the video you created in a cinema is just mind bending on itself. I was really unsatisfied with the video, it was not explaining the concept well enough to be understood. And if I were to do it again, I would really focus on what the key points are of the concept. This would help greatly when there is a time pressure and you need to prioritise parts. That is exactly what went wrong, we went off script and focused on the fun things or easy things.
Why & how
To have a planning and a set goal to achieve during the project, I created a project plan. I also set priorities using the Moscow method.
Conclusion
Document containing a summary of the project, a schedule and the wanted result.
Why & how
To know how to create a prototype from the concept, I need to research what is possible and what kind of tools are available. I looked at two major languages that are used for facial analyzation. I experimented with Python and made a fist proof of concept.
Conclusion
Python is the way to go for this project, combined with the powerful open source facial analytic framework DeepFace.
I initially started looking at software possibilities however, I learned more about the hardware requirements of the application. Like the needed processor architecture and the processing power of the computer.
Why & how
To test the research I have done regarding the software possibilities, I tried to create a proof of concept (POC). With this POC I am trying to create the part of the concept where the program analyses the users face and returns an emotion. I did this during the software research, therefor I used Python with DeepFace.
Conclusion
The proof of concept is slow and the displayed emotions are not always perfect. But we should keep in mind that the laptop was at <10% battery, the lighting was not great and it was an at least five-year-old MacBook Air.
Why & how
My goal is to evaluate the concept I wrote, to do this I need some testable tangible product. As written in the reading guide, I started sketching in Figma. I looked at different tablet design with robotic like faces. I really wanted a neutral feeling, that can also become very friendly or hostile. While sketching, I also was doing literate studies on best practices and other examples that already exist.
Conclusion
A foundation for a prototype and evidence of an iteration process. With this I can perform a user test.
Why & how
Via Figma, I have made a few designs to experiment with what kind of visuals would work for the project. This is important because we can get a better understanding of how the interactive dialogue would work with these visuals.
I made a few animated prototypes in Figma to get a feeling of what kind of emotion the digital
I tested this in a user test, the prototype of this is the first flow.
You can select the different flows in the tab on the right,
Conclusion
A few animated prototypes and a showcase of emotions. Also a user test that I have tested.
Why & how
I conducted a user test to evaluate the design I created. To help sketch the scenario, I used the Figma prototype and wrote an introduction for the participants.
Conclusion
The prototype does what it was intended to do, this was surprising. I learned if people want to do the sort of happening frequent, if they think it has potential and that it makes people smile. A complete summary of the test can be seen in the document.
Why & how
This is a short document and speaks for it self. It contains the documented reactions from the user test.
Why & how
To give advice on how to further develop the product of the project, I set up an advice document.
Conclusion
A document that with valuable mandatory information on how to continue the project and realise the application. It contains a schematic explanation of the application, the concept, which libraries to use and what the quality criteria is.