PROJECTS
My passion project is called Strive. It is a fitness app that has multiple features. The difference between my app and other apps is that this is an all-in-one app since most apps only have one or two features maximum. My stakeholder is a gym employee and he is also a personal coach with a long fitness journey and experience.
In this section I explain the inspiration that I found for my design and the moodboard that I created for it. I also explain the visual design techniques that i implemented and which ucd principles apply to my prototype.
This fits the following learning outcomes: LO1.
Gitwiki about lo1
Link Between Learning Outcomes (LO) and What I Did:
...exploring emerging trends and developments in media, design and technologies.
Fitness apps are often made with multiple health features such as sleep, fitness, and nutrition.
Exploring emerging design trends:
You create engaging concepts and translate them into interactive validated media products by applying user-centered design principles, visual design techniques...
Here I explain and show the documentation of my code, the readme file but also that I push it regularly and have clear commit messages.
This fits the following learning outcomes: LO2.
Gitwiki about lo2
I recommend you view the detailed documentation on my Gitwiki since there are a lot of screenshots and links directly to the branches, repositories, commit histories etc.
Use of CHATGPT:
In S2, I got feedback from Ame that there is nothing wrong with using AI or code from tutorials, but it would be a good way of learning to let ChatGPT explain the code and then add comments based on this explanation. I have done this for most of the JS in my passion project, and I feel like it has helped me expand my knowledge more. I wrote all of the comments myself in a way that helps me understand what’s going on better.
Explanation:
Link Between Learning Outcomes (LO) and What I Did:
You document and comment your code using version control in a personal and team context and communicate technical recommendations.
In this section I explain and show a side by side comparison of iterations that I made based on feedback from my stakeholder. I also explain why the change is an improvement.
This fits the following learning outcomes: LO3.
Gitwiki about lo3
I recommend that you view the detailed documentation since on there there is an image of the before and after side by side between versions with feedback and why it is an improvement.
Since I show the feedback that I got with screenshots from my stakeholder as well as a side by side comparision between versions, you should really visit the detailed documentation for the best experience.