Introduction
For this visual survey we were supposed to observe artistic styles in toys, DVD or video game cover art and figure out what age demographic it was targeted for. The reason being so we could learn what artistic styles are appropriate for the age demographic we intend to target, which is 9-12 year olds.
Process
I searched online on Google, and on Amazon for "kids toys", "kids movies" and "kids video games" as well as just the general searches for older ages too. When I had collected a reasonable amount of material I then sorted it into age appropriate sections according to my assumptions.
Choices
I originally planned to go to the store and conduct my survey in the toy aisles of the store. However, not having a vehicle, it being freezing outside, and unsuccessful in finding a ride, I surfed the Internet instead. I chose to sort my findings into small manageable age increments because it allowed me to create a section for my target age group, 9-12 year olds. Additionally, I chose to survey movies, cartoon shows, video games and toys because they provide a good window into the artistic styles children are attracted to. All of the things I chose to survey are things that kids interact with on a daily basis and have had the most success in their markets already. Why re-invent the wheel?
Conclusions
This exercise helped me to understand how to communicate more effectively with the 9-12 years that I am targeting with this diabetes management app. If they can't relate to it, they won't use it. I have to be careful from making it too mature for them and also the other side of things, too immature. Which I would err on the side of too mature. If they think you are dumbing it down too much for them they will feel insulted. If it's leaning more towards the too mature side it may not be as noticeable, and will age with them and they won't necessarily be insulted.
Katie Jean Studios - Blog
Monday, February 28, 2011
A 2.01 | Concept Map
Introduction
In order to gain a fuller grasp on the project at hand we were asked to conceptualize a map for what exactly this app. should be able to do. The map is just supposed to help visualize the main concept behind the functional processes of the system.
Process
To create my concept map I used the information we gained from interviewing our "inside man" and also from other research I'd done on diabetes. I basically began to imagine this app's potential. I brainstormed possible functionality and interactivity with the device and the app itself. I began addressing the problem, what can a mobile app do to help a child and their parents manage diabetes? What would be most helpful? What would be the basic functionality needed to make this idea a practical reality?
Choices
I chose to illustrate my concept map as I did because it just made sense to me that way. As more of a "first pass" at pinning down a concept I limited the processes to the basic necessities, leaving out any "extras" or things that could easily be added on in future releases of the app, but aren't critical to it's initial functionality or success.
Conclusions
Doing a concept map helped me put down on paper what I had started formulating in my head ever since I found out what our project was going to be on. It allowed me to focus my imagination in a functional and realistic way. And it got me to start thinking about the problem and how I could solve it in an efficient and an aesthetic way.
In order to gain a fuller grasp on the project at hand we were asked to conceptualize a map for what exactly this app. should be able to do. The map is just supposed to help visualize the main concept behind the functional processes of the system.
Process
To create my concept map I used the information we gained from interviewing our "inside man" and also from other research I'd done on diabetes. I basically began to imagine this app's potential. I brainstormed possible functionality and interactivity with the device and the app itself. I began addressing the problem, what can a mobile app do to help a child and their parents manage diabetes? What would be most helpful? What would be the basic functionality needed to make this idea a practical reality?
Choices
I chose to illustrate my concept map as I did because it just made sense to me that way. As more of a "first pass" at pinning down a concept I limited the processes to the basic necessities, leaving out any "extras" or things that could easily be added on in future releases of the app, but aren't critical to it's initial functionality or success.
Conclusions
Doing a concept map helped me put down on paper what I had started formulating in my head ever since I found out what our project was going to be on. It allowed me to focus my imagination in a functional and realistic way. And it got me to start thinking about the problem and how I could solve it in an efficient and an aesthetic way.
Labels:
ART 337R
Friday, February 11, 2011
Lab 01 | Horizontal Menu
Horizontal Navigation Tabs with State Changes
This a tutorial on how to create horizontal navigation tabs with state changes. Meaning the tab changes appearance when you rollover the tab with your mouse and/or click the tab. You can try it out by clicking on my demo below.
| Click for DEMO |
How I did It
In my HTML document I first created an unordered list, known in syntax as a 'ul' tag. I then added list items, 'li', to the unordered list; each containing the 'a href=""' tag specifying the list item content is a link since they will be linking to other pages. HTML code for this:
<div id="horizontal">
<ul>
<li><a href="#">Vanilla</a></li>
<li><a href="#">Chocolate</a></li>
<li><a href="#">Strawberry</a></li>
<li><a href="#">Mint Chocolate Chip</a></li>
<li><a href="#">Neapolitan</a></li>
<li><a href="#">Moose Tracks</a></li>
</ul>
</div>
Now that we have our framework for the navigation tabs it's time to add a little paint. That's where the CSS comes in. Right away I want to get rid of those pesky bullet points that automatically display with unordered lists. To do this I set 'list-style' to 'none', as you can see in the CSS code below. Second, I want to make this a horizontal navigation, not vertical as is the default with lists. To do this, I simply set the list items to "float left". You can see how I did this in the code below as well:
#horizontal li
{
list-style-type: none;
color: #ffffff;
float: left;
font-family: Helvetica, sans-serif;
font-size: 16px;
margin: 3px;
}
Rounded Corners
In order to round the corners of the tabs you need to insert a bit of CSS (in this case specifically to the link elements) shown below. As you can see you have to cater to the different browsers with slightly different syntax to do the same thing. In order to increase cross-browser compatibility you'll want to include as many as possible. I believe there is a different way to round corners for IE and a few other browsers, but I chose not to use them it for this particular lab. You can also round the bottom radius' as well if you so choose. However, it is important to note that this method doesn't work for all browsers. When used, it's best viewed in Firefox, Safari and Chrome.
{
#horizontal a
/*--OMITTED--other css styles here--*/
-moz-border-radius-topright: 10px; /*Firefox*/
-moz-border-radius-topleft: 10px;
-webkit-border-top-right-radius:10px; /* Safari and Chrome */
-webkit-border-top-left-radius: 10px;
}
State Changes on hover
In order to help the user experience it is important to let them know something is a button, or is "clickable". To solve this I use hover state changes in my CSS to give the tab a different appearance when someone moves their mouse over the top of the tab. In this case I changed the background color of the tab from a dark green to more of a lime green and everything else stays the same. As you can see in my code below:
#horizontal a:hover
{
color: #ffffff;
background-color: #96c31c;
padding-right: 32px;
padding-left: 32px;
padding-top: 20px;
padding-bottom: 20px;
}
Active State Change
I also wanted the user to know when they were actually clicking a tab so I simply decided to just change the text color to blue since blue is the default link color. I chose to use the default link color of blue because it's what users are used to seeing with links so they would know when they clicked on it that it would be linking them to something outside of that current page. All I had to do to achieve this was set the list items that are links in the active state to a new color.
#horizontal li a:active
{
color: #0c00ff;
}
Labels:
ART 337R,
ART337R LAB
Tuesday, February 8, 2011
A 1.10 | Final Calculator
Introduction
This is the final phase of the calculator assignment. We needed to use everything that we had learned from the whole process leading up to this point, especially the feedback gained from the market survey.
Process
I took my last Photoshop design and enlarged my buttons, changed the color of the clear button and got rid of the extra designs that were up near the top under the answer screen. The non-functional buttons were removed and I changed the font from the default Myriad Pro to Sketch Rockwell and enlarged the font size to make them more legible.
Choices
I chose to make the changes that I made because I saw a need for them to be made. Issues that I observed earlier on came up in the market survey and urged me even more so to make the changes in my final design. I wanted to keep the bright vibrant colors because that is something that is popular right now. And even though they are traditionally "girly" colors, more boys are liking this color combo these days. Purple happens to be my fifteen year old brother's favorite color. I liked the asymmetrical shape of the calculator body so I kept that in my final design, I just used the space better. I wanted the clear and equals buttons to stand out so I made them bright colors and kept them near one another so they would be easy to find and convenient to use. I made the buttons and type on the buttons bigger to increase legibility.
Conclusions
I learned a lot through this entire assignment. Looking back on my very first sketches to what I have now as my final calculator design I have come a long way. I wanted to make the user happy and I wanted to design something that I would like as well. Even though my final design isn't what I originally designed within the Quantum Leap theme, I am pleased with where I took it. As a calculator it serves its purpose much better when the users calculator interacting experience is taken into careful consideration. I think that I successfully used the feedback from my peers and those surveyed to create a clear, functioning, unique calculator.
Labels:
ART 337R
Saturday, February 5, 2011
A 1.09 | Market Survey
Introduction
This part of the assignment asked us to conduct a market survey on the other calculators in our class. The point of this was to really find out what people think of the calculators we have designed. Using their feedback will help us in creating our final calculators.
Process
In class we brainstormed some questions to ask our sample observation units and discussed the importance of their feedback. I took notes and then asked my roommates the questions I thought were relevant. I observed their reactions and asked follow up questions as well. Then we came back together as a class and discussed the feedback we'd received. I took notes on what had been said about my calculator as well as what was successful about others.
Choices
I tried to survey my subjects on as many calculators as possible so I could observe their reactions to all of the calculators. I chose to survey my roommates because I have ten roommates and that provided a good number of subjects to observe.
Conclusions
From conducting this survey and then taking notes on feedback other students collected I have a much better idea of which direction I want to take my final calculator design in. Before I had worried that my buttons were too small and that was verified during this survey assignment. Also confirmed were my concerns about the non-functional buttons in the top left corner. I will be removing those in my final design. I also learned that users like the clear button and the equals button to be near one another and prefer them to be a different color/value and/or size than the rest of the buttons. Designs that simplified the button organization, keeping function keys together and number keys together tended to be more successful. Something to keep in mind for my final design.
This part of the assignment asked us to conduct a market survey on the other calculators in our class. The point of this was to really find out what people think of the calculators we have designed. Using their feedback will help us in creating our final calculators.
Process
In class we brainstormed some questions to ask our sample observation units and discussed the importance of their feedback. I took notes and then asked my roommates the questions I thought were relevant. I observed their reactions and asked follow up questions as well. Then we came back together as a class and discussed the feedback we'd received. I took notes on what had been said about my calculator as well as what was successful about others.
Choices
I tried to survey my subjects on as many calculators as possible so I could observe their reactions to all of the calculators. I chose to survey my roommates because I have ten roommates and that provided a good number of subjects to observe.
Conclusions
From conducting this survey and then taking notes on feedback other students collected I have a much better idea of which direction I want to take my final calculator design in. Before I had worried that my buttons were too small and that was verified during this survey assignment. Also confirmed were my concerns about the non-functional buttons in the top left corner. I will be removing those in my final design. I also learned that users like the clear button and the equals button to be near one another and prefer them to be a different color/value and/or size than the rest of the buttons. Designs that simplified the button organization, keeping function keys together and number keys together tended to be more successful. Something to keep in mind for my final design.
Labels:
ART 337R
Thursday, January 27, 2011
A 1.08 | Working Prototype
Introduction
For this part of the project I had to make a working prototype of my final calculator design. A working prototype means that I need to coordinate the HTML and CSS code with my design.
Process
I worked in Photoshop to create my new design and then I used Coda to edit the CSS to match with my design. I tediously adjusted the padding of each button as well as the size of the buttons. I used the preview mode in Coda frequently to check the changes I would make in the CSS to make sure everything was aligned correctly.
Choices
I really didn't like my final comp and based off the feedback from my peers I decided to take my design in a completely different direction. Early on in the assignment I thought it would be fun to attempt to emulate a design similar to the 'handlink' found in one of my favorite television shows, Quantum Leap. I decided that the handlink used in the more recent seasons was really cool, but I had no idea how to recreate anything remotely similar in Photoshop. So I opted to work on a design similar to the handlink used in earlier seasons. Originally my design was very similar to the design used on the TV show. However, I eventually chose to change the colors and rearrange the buttons.
Observations
I think that the change in design is a positive change. However after interacting with my prototype more I noticed that the buttons are kind of small for the format. Only being 200x300 and used on a screen I need to think more about the space. A lot of the calculator space is not being utilized for anything useful or functional to the calculator. And I predict that in the market research, the buttons in the top left corner that aren't actually buttons might bother people. I may want to continue to tweak my design.
For this part of the project I had to make a working prototype of my final calculator design. A working prototype means that I need to coordinate the HTML and CSS code with my design.Process
I worked in Photoshop to create my new design and then I used Coda to edit the CSS to match with my design. I tediously adjusted the padding of each button as well as the size of the buttons. I used the preview mode in Coda frequently to check the changes I would make in the CSS to make sure everything was aligned correctly.
Choices
I really didn't like my final comp and based off the feedback from my peers I decided to take my design in a completely different direction. Early on in the assignment I thought it would be fun to attempt to emulate a design similar to the 'handlink' found in one of my favorite television shows, Quantum Leap. I decided that the handlink used in the more recent seasons was really cool, but I had no idea how to recreate anything remotely similar in Photoshop. So I opted to work on a design similar to the handlink used in earlier seasons. Originally my design was very similar to the design used on the TV show. However, I eventually chose to change the colors and rearrange the buttons.
Observations
I think that the change in design is a positive change. However after interacting with my prototype more I noticed that the buttons are kind of small for the format. Only being 200x300 and used on a screen I need to think more about the space. A lot of the calculator space is not being utilized for anything useful or functional to the calculator. And I predict that in the market research, the buttons in the top left corner that aren't actually buttons might bother people. I may want to continue to tweak my design.
Tuesday, January 25, 2011
A 1.07 | Final Photoshop comp
Introduction
The assignment was to create a complete Photoshop comp. This is the final phase before we start adding in functionality. The comp is supposed to be a very clean final looking piece.
The assignment was to create a complete Photoshop comp. This is the final phase before we start adding in functionality. The comp is supposed to be a very clean final looking piece. Process
This design is my final static comp. I kept with the spherical theme and used some of my cloud & sky inspiration from another comp I designed prior to this one. I made special consideration for the buttons and how and where each should be placed to make the experience as familiar but also unique to the user as possible. The numerical buttons are grouped together in the traditional sequence, and the operators are all grouped around the equals button. I made sure to keep the 'plus' and 'minus' buttons together and the 'multiply' and 'divide' buttons together and made sure the four of them were close to each other as well.
Because this calculator is intended to be viewed on a screen I wanted to give the calculator a three dimensional feel to render it as close to an actual object as possible. I added some beveling and shading to achieve this goal.
Choices
I also wanted to take advantage of the fact that this calculator will be viewed on a virtual screen and made the buttons appear as if they are hovering slightly above the body of the calculator itself, something that wouldn't be possible if it were a real object. I chose to go with this comp because I felt like it was the cleanest of my computer comps.
Observations & Conclusions
I think this design provides a fun calculator experience for users. The next step will be to add implementation and dynamic interaction with this calculator. Things to consider are how the buttons will sound and or look when pushed. I also might want to reconsider color choices because the gray and the blue are kind of similar in value
Labels:
ART 337R
Subscribe to:
Posts (Atom)



