My journey with coding and UX

Hey, great to meet you here again. Today, I will be discussing Design Guidelines. More particularly I will be discussing what they are, why you should use them and how to make your own. It's been a while so do bear with me if this post is a little differently formated. I'm feeling it out and need to find my footing again ^_^ 

Hey, long time no see. So, a lot has happened since my last post. I was originally working on my bachelor's and the following post regarding Design Guidelines. Well, the post is like 85% done and another very important point I graduated! Basically in between this post and the one about Design Principles a lot happened. Some good and some less fortunate things but I'm back now and I'll try my best to go back to writing about my professional growth and things I want to learn more about.  I just wanted to make sure that this was at least written here so y'all at least know that I did not completely forget about this blog but it was just put on the back burner and was left to stew for a little bit.  Talk to you later ;-)

Hey, nice for you to be here. In these following blog posts I will talk about design principles, design guidelines and design criteria/rules. Originally, I wanted to do this as one massive blogpost but because of the time it took for me to write design guidelines (which I am still busy with as of writing this post) I decided it is for the better to split them up in several posts. In this post I will talk about design principles but before I can do that let me shortly explain them all 3 and why I want to talk about all 3 of them. In the previous post I talked about the users wants and needs. These would result in some criteria to follow when creating a final design but those are not the only criteria your design will have to follow. They are still important though! Another place where criteria come from is the context of your own organisation or at least the organisation/business that will be creating and releasing the final product. A lot of organisations would like for their products ...

UX design is a thing/process that focusses on the wants and needs of the user, their experiences with products, and how those experiences influence the user. That is the definition I settled and agreed upon in my last blog post. That’s all fine and dandy but it doesn’t give me much to work with mentally too be frank with you. So, in this post I would like to explore this a little more.  Specifically, I’d like to focus on what the wants and needs of the user could be and before I can look at that I need to define what a user is. Personally, I define a user as anyone who uses the product. This means for example that someone who drinks out of a carton of milk is a user of that carton of milk. Kind of a weird example but I hope you catch my drift. Milk drinker This user might not only drink out of a carton of milk but might also pour milk out of the carton into a mug/glass/cup/etc. This will not stop them from being a user. It will be them using the carton differently. These differen...