Shift from UI design to Desktop Experience
In Class:
Our class is now shifting from UI mobile design to UX Desktop experience for web design. With all design there are constraints such as weight, dimensions, time, materials, cost and function. Constraints are everywhere. For web design the normal document flow is top to bottom in html and to create a layout we use css by floating elements.
For our studies we will be 30% designing the site, 20% thinking about the front end development which has to deal with html, css, optimizing images and more. Finally we will be 50% UX developing. The UX developer are more computer science majors who deal with the flow, user, wireframes, sitemaps and the overall experience. In most job settings we will be place in either one or two spots but for the project we must think about the over all design and function of the page.
For the most part, I have basic understanding of html and css and feel comfortable using both. My strength is problem solving when it comes to the code and have an easy time reading the format and knowing where things go within the code. The first few weeks will be review but I think this will benefit me because it helps me remember things I may have forgotten from the last time I use html and css.
We started working with a basic exercises in class which are the photos below.
Homework:
Assignment- To create a static webpage explaining a dream vacation and things about the vacation that may go on and how to get to the destination. This static layout means the flow goes from top to bottom.
I felt this was a nice refresher because I got to practice in-style design in html. Some things I had to look up by using www.w3schools.com and previous assignments I worked on, were the hover on and hover off for images, line heights by using em's and how to create a wrapper for the body copy instead of having a long string of content run across the page.
Reading: Above the Fold
Chapter 1: Web Site Planning (Reflection)
Before you are able to start design for a website you must plan out what the function of the site will be. In short terms the site planning is taking the client's goals and business needs and align them with the target user group. It helps to map out the site first by thinking it as the big picture to accomplish the mail goals of the webpage. This chapter focused on getting the functionality of the site solid by using assent inventory which is the logos, copywriting, imagery that can all be collected by spread sheets. Some things I learned were that you can never use spaces in files names because other servers may not pick up on it and the file names must all be in lowercase. Another little fact that I didn't know about was that your suppose to keep the navigation bar to no more than 7 items or the user creates them into subcategories. Other ways to start laying out the function of a page is by information architecture the underpainting of a layout. The next steps are creating a sitemap for showing linked pages and their relationship. After that we move to the wireframes which illustrates a blueprint map of each individual page with the important elements. Each one of theses steps are a way to fine tool all the little details. After wireframes usability diagrams are used to show the flow a user may take. Prototyping is a major portion because it helps the developer fix all the bugs with trial and error. After prototyping is when you can really start designing. Concept designs are similar to mood boards to start and understand the clients goals in a creative way. Imagergy, iconography, color, texture and typography can be used to illustrate the client goals. The last two things that the chapter talks about are style tiles/element collages and metaphors or the inferences to show the user clickable items to better understand the content with the design of the site.
I really enjoy reading this book because it's very informational and I feel like everything is very clear and to the point.